Suddenly getting bsod memory management issue after Updating to windows 10
up vote
4
down vote
favorite
I recently upgraded to windows 10, most things seemd to work fine, aside from a few issues here and there which was easily resolved. Thou i had to reinstall the Nvivida Driver for the graphic card. (it was trying to run from the integrated motherbord graphic).
However i've suddenly been plagued with BSOD errors, both in page_....
and Memory management error, did a Windows memory diagonstics tool scan which showed hardware error, but gave no future explaination than that.
Is it possible that windows 10 is causeing the BSOD, were i just that unlucky and one of the RAm peices broke during the installation of windows 10 ?
Any suggestion/tips is appreciated.
Whocrashed now gives crashlog
crash dump file: C:Minidump73115-4656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000036000, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Setting up a memtest86+ (thanks for the tip)
Also the info from Bluescreen view gives this info.
==================================================
Dump File : 080215-7531-01.dmp
Crash Time : 02.08.2015 13.37.26
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041792
Parameter 2 : fffff6bf`fe555000
Parameter 3 : 00000000`20000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80215-7531-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 263 550
Dump File Time : 02.08.2015 13.38.13
==================================================
Adding a secound mini dump.
==================================================
Dump File : 080115-6703-01.dmp
Crash Time : 01.08.2015 22.15.10
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`001db080
Parameter 3 : 00000000`00000011
Parameter 4 : 00000000`00000010
Caused By Driver : win32kfull.sys
Caused By Address : win32kfull.sys+d329f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80115-6703-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 265 086
Dump File Time : 01.08.2015 22.15.57
==================================================
I must thank you all again for your assistance and time.
Will add the kernel dump, the next time it crashes (switched it from making a mini dump to a kernel dump).
memory bsod windows-10
asked Aug 2 '15 at 12:30
Joakim D
21113
|
show 1 more comment
up vote
4
down vote
favorite
I recently upgraded to windows 10, most things seemd to work fine, aside from a few issues here and there which was easily resolved. Thou i had to reinstall the Nvivida Driver for the graphic card. (it was trying to run from the integrated motherbord graphic).
However i've suddenly been plagued with BSOD errors, both in page_....
and Memory management error, did a Windows memory diagonstics tool scan which showed hardware error, but gave no future explaination than that.
Is it possible that windows 10 is causeing the BSOD, were i just that unlucky and one of the RAm peices broke during the installation of windows 10 ?
Any suggestion/tips is appreciated.
Whocrashed now gives crashlog
crash dump file: C:Minidump73115-4656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000036000, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Setting up a memtest86+ (thanks for the tip)
Also the info from Bluescreen view gives this info.
==================================================
Dump File : 080215-7531-01.dmp
Crash Time : 02.08.2015 13.37.26
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041792
Parameter 2 : fffff6bf`fe555000
Parameter 3 : 00000000`20000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80215-7531-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 263 550
Dump File Time : 02.08.2015 13.38.13
==================================================
Adding a secound mini dump.
==================================================
Dump File : 080115-6703-01.dmp
Crash Time : 01.08.2015 22.15.10
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`001db080
Parameter 3 : 00000000`00000011
Parameter 4 : 00000000`00000010
Caused By Driver : win32kfull.sys
Caused By Address : win32kfull.sys+d329f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80115-6703-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 265 086
Dump File Time : 01.08.2015 22.15.57
==================================================
I must thank you all again for your assistance and time.
Will add the kernel dump, the next time it crashes (switched it from making a mini dump to a kernel dump).
memory bsod windows-10
asked Aug 2 '15 at 12:30
Joakim D
21113
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59
|
show 1 more comment
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I recently upgraded to windows 10, most things seemd to work fine, aside from a few issues here and there which was easily resolved. Thou i had to reinstall the Nvivida Driver for the graphic card. (it was trying to run from the integrated motherbord graphic).
However i've suddenly been plagued with BSOD errors, both in page_....
and Memory management error, did a Windows memory diagonstics tool scan which showed hardware error, but gave no future explaination than that.
Is it possible that windows 10 is causeing the BSOD, were i just that unlucky and one of the RAm peices broke during the installation of windows 10 ?
Any suggestion/tips is appreciated.
Whocrashed now gives crashlog
crash dump file: C:Minidump73115-4656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000036000, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Setting up a memtest86+ (thanks for the tip)
Also the info from Bluescreen view gives this info.
==================================================
Dump File : 080215-7531-01.dmp
Crash Time : 02.08.2015 13.37.26
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041792
Parameter 2 : fffff6bf`fe555000
Parameter 3 : 00000000`20000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80215-7531-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 263 550
Dump File Time : 02.08.2015 13.38.13
==================================================
Adding a secound mini dump.
==================================================
Dump File : 080115-6703-01.dmp
Crash Time : 01.08.2015 22.15.10
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`001db080
Parameter 3 : 00000000`00000011
Parameter 4 : 00000000`00000010
Caused By Driver : win32kfull.sys
Caused By Address : win32kfull.sys+d329f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80115-6703-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 265 086
Dump File Time : 01.08.2015 22.15.57
==================================================
I must thank you all again for your assistance and time.
Will add the kernel dump, the next time it crashes (switched it from making a mini dump to a kernel dump).
memory bsod windows-10
asked Aug 2 '15 at 12:30
Joakim D
21113
I recently upgraded to windows 10, most things seemd to work fine, aside from a few issues here and there which was easily resolved. Thou i had to reinstall the Nvivida Driver for the graphic card. (it was trying to run from the integrated motherbord graphic).
However i've suddenly been plagued with BSOD errors, both in page_....
and Memory management error, did a Windows memory diagonstics tool scan which showed hardware error, but gave no future explaination than that.
Is it possible that windows 10 is causeing the BSOD, were i just that unlucky and one of the RAm peices broke during the installation of windows 10 ?
Any suggestion/tips is appreciated.
Whocrashed now gives crashlog
crash dump file: C:Minidump73115-4656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000036000, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Setting up a memtest86+ (thanks for the tip)
Also the info from Bluescreen view gives this info.
==================================================
Dump File : 080215-7531-01.dmp
Crash Time : 02.08.2015 13.37.26
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041792
Parameter 2 : fffff6bf`fe555000
Parameter 3 : 00000000`20000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14d220
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80215-7531-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 263 550
Dump File Time : 02.08.2015 13.38.13
==================================================
Adding a secound mini dump.
==================================================
Dump File : 080115-6703-01.dmp
Crash Time : 01.08.2015 22.15.10
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041793
Parameter 2 : fffff680`001db080
Parameter 3 : 00000000`00000011
Parameter 4 : 00000000`00000010
Caused By Driver : win32kfull.sys
Caused By Address : win32kfull.sys+d329f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14d220
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:Minidump80115-6703-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10240
Dump File Size : 265 086
Dump File Time : 01.08.2015 22.15.57
==================================================
I must thank you all again for your assistance and time.
Will add the kernel dump, the next time it crashes (switched it from making a mini dump to a kernel dump).
memory bsod windows-10
memory bsod windows-10
asked Aug 2 '15 at 12:30
Joakim D
21113
asked Aug 2 '15 at 12:30
Joakim D
21113
edited Aug 2 '15 at 16:00
asked Aug 2 '15 at 12:30
Joakim D
21113
asked Aug 2 '15 at 12:30
Joakim D
21113
asked Aug 2 '15 at 12:30
Joakim D
21113
21113
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59
|
show 1 more comment
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
0
down vote
I had the same BSOD and the http://www.memtest86.com/download.htm (booted in UEFI mode) revealed that the RAM is broken around gigabyte nr. 4.
After removing the first 8gb module, it detects no more problems.
I had been running Windows 8.1 and a memtest86 a month ago without any problems, so I hope its not Windows 10 that caused the RAM to break.
answered Aug 30 '15 at 7:01
masterxilo
24617
add a comment |
protected by Community♦ Aug 10 '15 at 11:02
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I had the same BSOD and the http://www.memtest86.com/download.htm (booted in UEFI mode) revealed that the RAM is broken around gigabyte nr. 4.
After removing the first 8gb module, it detects no more problems.
I had been running Windows 8.1 and a memtest86 a month ago without any problems, so I hope its not Windows 10 that caused the RAM to break.
answered Aug 30 '15 at 7:01
masterxilo
24617
add a comment |
up vote
0
down vote
I had the same BSOD and the http://www.memtest86.com/download.htm (booted in UEFI mode) revealed that the RAM is broken around gigabyte nr. 4.
After removing the first 8gb module, it detects no more problems.
I had been running Windows 8.1 and a memtest86 a month ago without any problems, so I hope its not Windows 10 that caused the RAM to break.
answered Aug 30 '15 at 7:01
masterxilo
24617
add a comment |
up vote
0
down vote
up vote
0
down vote
I had the same BSOD and the http://www.memtest86.com/download.htm (booted in UEFI mode) revealed that the RAM is broken around gigabyte nr. 4.
After removing the first 8gb module, it detects no more problems.
I had been running Windows 8.1 and a memtest86 a month ago without any problems, so I hope its not Windows 10 that caused the RAM to break.
answered Aug 30 '15 at 7:01
masterxilo
24617
I had the same BSOD and the http://www.memtest86.com/download.htm (booted in UEFI mode) revealed that the RAM is broken around gigabyte nr. 4.
After removing the first 8gb module, it detects no more problems.
I had been running Windows 8.1 and a memtest86 a month ago without any problems, so I hope its not Windows 10 that caused the RAM to break.
answered Aug 30 '15 at 7:01
masterxilo
24617
edited Aug 30 '15 at 9:21
answered Aug 30 '15 at 7:01
masterxilo
24617
answered Aug 30 '15 at 7:01
masterxilo
24617
answered Aug 30 '15 at 7:01
masterxilo
24617
24617
add a comment |
add a comment |
protected by Community♦ Aug 10 '15 at 11:02
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
You should run Memtest86+ which is bootable and scans your memory without windows being loaded. That way you can easily see if its the hardware or software that isn't working properly.
– Christian Isaksson
Aug 2 '15 at 12:34
What are the BSOD error messages? BlueScreenView should provide this information. Please edit your question to include this.
– DavidPostill♦
Aug 2 '15 at 12:37
I'll get my memory stick later to set up memtest86+ And thank you for your time and assistance. I'll try to get the full minidump up, but the usual view system i used for windows 8.1 dosn't appear to read the minidump file correctly
– Joakim D
Aug 2 '15 at 12:57
0x41792 = A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. I need the kernel dump (C:WindowsMemory.dmp) to see more details.
– magicandre1981
Aug 2 '15 at 15:54
Alright, i'll have it create a kernel dump for the next time it crashes (about once a day). Will Update the original question with the kernel dump information when i aquire it.
– Joakim D
Aug 2 '15 at 15:59