Hello,
I have recently acquired all hardware to build a desktop PC.
At the beginning there was no problem, but soon they started:
While playing games that were not very demanding I had no problem, but then I started Diablo 3 and I started to experience BSODs. After the BSOD, I experienced (let's say) repetitions right after rebooting, already in Windows again, but they never occurred doing other than gaming for the first time. I have had these with many different games now, even with those less demanding that once caused no troubles.
Since it seemed to be a faulty graphics card, I removed it and was playing for about two weeks with no issue with the motherboard graphics. Then I decided to send it back to the store and they sent me a new one. Well, this new one causes the same troubles. At the moment I don't know how to proceed. I have run memory checks, disk checks, even a graphics card benchmark with 3DMark, but nothing happened.
Some times I can foresee the crash, because something strange happens, like buttons on full-screen I cannot press, anomalies in some others, not being able to go out of full-screen with ALT+TAB, etc.
Right now I just experienced a singular behaviour: I stopped playing The Division, I closed the game and left the PC. When I came back it had crashed 3 times each of them with 12 minutes of delay, and happened again, after exactly another 12 minutes, while executing another game. For the record:
1st: MEMORY_MANAGEMENT
2nd: PAGE_FAULT_IN_NON_PAGED_AREA
3rd: MEMORY_MANAGEMENT
4th: IRQL_NOT_LESS_OR_EQUAL
Note: Before I sent the graphics card back, I tested the RAM sticks by removing one at a time, but I had BSODs with both independently.
I would be glad if somebody could help me. What else could I share to ease the investigation? Any idea is welcomed.
Thank you in advance.
Here my PC specs:
- SSD 250GB Samsung 850 Evo 2.5" (6.4cm) SATA 6Gb/s TLC Toggle (MZ-75E250B/EU)
- CPUK Arctic Freezer 7 Pro Rev. 2 Tower Kühler
- MB ASRock Z170 Pro4S Intel Z170 So.1151 Dual Channel DDR4 ATX Retail
- CPU Intel Core i5 6400 4x 2.70GHz So.1151 BOX
- DDR4 8GB (2x 4096MB) G.Skill RipJaws V rot DDR4-2400 DIMM CL15-15-15-35 Dual Kit
- PSU 450 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Silver
- VGA 4096MB MSI GeForce GTX 960 Gaming 4G Aktiv PCIe 3.0 x16 1xDVI/1xHDMI 2.0/3xDisplayPort (Retail)
- and one additional SATA HD, also new.
WhoCrashed report:
Welcome to WhoCrashed (HOME EDITION) v 5.51
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit Resplendence Software - Contact and Support Form
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: CASTERLYROCK
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z170 Pro4S
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540618752 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 21/04/2016 20:41:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002610254E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:41:31 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002610254E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:29:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4609-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800001E458, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
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.
On Thu 21/04/2016 20:17:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFC401D361256E, 0x0, 0xFFFFF8011684F340, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:05:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4640-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFFC48068, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
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.
On Tue 19/04/2016 21:07:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041916-4656-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680E6FFA788, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
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.
On Tue 19/04/2016 20:57:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041916-4578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5002, 0xFFFFF58010804000, 0x4CC5, 0x84CF0FFFFFFE)
Error: MEMORY_MANAGEMENT
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.
On Fri 08/04/2016 14:25:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040816-5734-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFFAE000AAF688, 0x8000000001080121, 0xFFFFD00021377C40, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 07/04/2016 19:57:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-4937-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF6E0808476C0, 0x2, 0x0, 0xFFFFF8005C8DB5C2)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 07/04/2016 19:49:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-4625-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFDFF040601700, 0x8000000001080121, 0xFFFFD00023B53390, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
I have recently acquired all hardware to build a desktop PC.
At the beginning there was no problem, but soon they started:
While playing games that were not very demanding I had no problem, but then I started Diablo 3 and I started to experience BSODs. After the BSOD, I experienced (let's say) repetitions right after rebooting, already in Windows again, but they never occurred doing other than gaming for the first time. I have had these with many different games now, even with those less demanding that once caused no troubles.
Since it seemed to be a faulty graphics card, I removed it and was playing for about two weeks with no issue with the motherboard graphics. Then I decided to send it back to the store and they sent me a new one. Well, this new one causes the same troubles. At the moment I don't know how to proceed. I have run memory checks, disk checks, even a graphics card benchmark with 3DMark, but nothing happened.
Some times I can foresee the crash, because something strange happens, like buttons on full-screen I cannot press, anomalies in some others, not being able to go out of full-screen with ALT+TAB, etc.
Right now I just experienced a singular behaviour: I stopped playing The Division, I closed the game and left the PC. When I came back it had crashed 3 times each of them with 12 minutes of delay, and happened again, after exactly another 12 minutes, while executing another game. For the record:
1st: MEMORY_MANAGEMENT
2nd: PAGE_FAULT_IN_NON_PAGED_AREA
3rd: MEMORY_MANAGEMENT
4th: IRQL_NOT_LESS_OR_EQUAL
Note: Before I sent the graphics card back, I tested the RAM sticks by removing one at a time, but I had BSODs with both independently.
I would be glad if somebody could help me. What else could I share to ease the investigation? Any idea is welcomed.
Thank you in advance.
Here my PC specs:
- SSD 250GB Samsung 850 Evo 2.5" (6.4cm) SATA 6Gb/s TLC Toggle (MZ-75E250B/EU)
- CPUK Arctic Freezer 7 Pro Rev. 2 Tower Kühler
- MB ASRock Z170 Pro4S Intel Z170 So.1151 Dual Channel DDR4 ATX Retail
- CPU Intel Core i5 6400 4x 2.70GHz So.1151 BOX
- DDR4 8GB (2x 4096MB) G.Skill RipJaws V rot DDR4-2400 DIMM CL15-15-15-35 Dual Kit
- PSU 450 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Silver
- VGA 4096MB MSI GeForce GTX 960 Gaming 4G Aktiv PCIe 3.0 x16 1xDVI/1xHDMI 2.0/3xDisplayPort (Retail)
- and one additional SATA HD, also new.
WhoCrashed report:
Welcome to WhoCrashed (HOME EDITION) v 5.51
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit Resplendence Software - Contact and Support Form
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: CASTERLYROCK
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, Z170 Pro4S
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8540618752 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Thu 21/04/2016 20:41:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4703-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002610254E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:41:31 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8002610254E)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:29:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4609-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6800001E458, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
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.
On Thu 21/04/2016 20:17:48 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4593-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFC401D361256E, 0x0, 0xFFFFF8011684F340, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 21/04/2016 20:05:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042116-4640-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFFC48068, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
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.
On Tue 19/04/2016 21:07:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041916-4656-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF680E6FFA788, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
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.
On Tue 19/04/2016 20:57:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041916-4578-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5002, 0xFFFFF58010804000, 0x4CC5, 0x84CF0FFFFFFE)
Error: MEMORY_MANAGEMENT
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.
On Fri 08/04/2016 14:25:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040816-5734-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFFAE000AAF688, 0x8000000001080121, 0xFFFFD00021377C40, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 07/04/2016 19:57:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-4937-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF6E0808476C0, 0x2, 0x0, 0xFFFFF8005C8DB5C2)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 07/04/2016 19:49:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040716-4625-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xBE (0xFFFFDFF040601700, 0x8000000001080121, 0xFFFFD00023B53390, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
14 crash dumps have been found and analyzed. Only 10 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
