New
#1
BSOD Loop / Frequent BSOD
Hey everyone! I was referred to you great people by the folks over at TomsHardware forums. They said you guys should be able to help me more than they can. We already narrowed my issue down to drivers, and not the hardware. Well, most likely not the hardware. I will go into depth below. I am also attatching at the bottom a list of 5 crashes from WhoCrashed. I have a feeling it may have been the AMD drivers that needed an update a few days after I installed my 2nd GPU. It was around that time that a game would crash here or there, when I tried playing BF1 on Origin is when this all really started though. BF1 is the first game in DX12 that would take advantage of both GPUs and the new drivers as well...
My computer is only a few months old and it has a Gigabyte Gaming 7 Mobo, 16gb of DDR4 Ram, an Intel i7 6700K overclocked to 4.5ghz at 1.3v running at 30 degrees. I am running 2 AMD RX 480's from MSI, and I have a soundblaster ZX sound card. The OS is on a samsung 120gb SSD, and most of my games are on a WB Black 2tb HDD all of this powered by a 750w 80+Platinum EVGA PSU.
The computer has been mostly trouble free for the past few months, the second GPU has been in for about a week, as well as the sound card. I got my first BSOD before installing those two, and it was somewhat common. I then de-clocked the CPU and let the Gigabyte BIOS do auto-overclocking and voltage, thinking maybe I 'lost' the silicone lottery and got a chip that cant be pushed too hard. The Bios thinks that 4.3ghz is good, and after letting the BIOS do its own thing, my BSOD frequency dropped dramatically.
Everything was fine, I was able to get a 3dMark Firestrike score of 14,000 and I was happy.I was able to run OBS to stream myself playing GTA V At max settings, H1Z1, you name it. Until last night when my friends were streaming, I was going to jump into Battlefield 1 to play with them. Then Origin required an update, half way through that update I got a BSOD.
Since that, I havent been able to login for more than few minutes without a blue screen. It will sometimes boot, I hear the MOBO speaker I installed beep, then blue screen, or it will let me login, open a program or two, then blue screen. So it is inconsistent. the message it gives me also seems to change. I wrote them down at home, but I am at work now and I will get you the messages when I get home.
So far to rectify this, I have ensured all drivers, windows and GPU are up to date. I have gone back into the case to make sure the GPU and Sound Cards are seated properly. I also took an air blaster to it to get rid of any loose dust or anything else. I am planning on checking all power connections and maybe reseat the RAM? This kind of thing is usually hardware related, but everything seems fine. Any suggestions? Thanks everyone!!!
I should also state, this computer is done almost entirely for school work, gaming, and streaming. I havent so much as looked at a Torrent or porn with this thing. I baby this computer lol.
Welcome to WhoCrashed (HOME EDITION) v 5.53
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 or black 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 www.resplendence.com/support
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 ...
System Information (local)
Computer name: DESKTOP-C3MQPN6
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., Z170X-Gaming 6
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17126776832 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 11/29/2016 12:31:15 PM your computer crashed
crash dump file: C:\Windows\Minidump\112916-6875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xD1 (0xFFFFF40FC8AC34A0, 0x2, 0x8, 0xFFFFF40FC8AC34A0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 11/29/2016 12:31:15 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP!ClassIoComplete+0x63B)
Bugcheck code: 0xD1 (0xFFFFF40FC8AC34A0, 0x2, 0x8, 0xFFFFF40FC8AC34A0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 11/28/2016 10:13:39 PM your computer crashed
crash dump file: C:\Windows\Minidump\112816-5671-01.dmp
This was probably caused by the following module: usbxhci.sys (0xFFFFF80D7D578712)
Bugcheck code: 0xD1 (0xFFFFC31033948470, 0x2, 0x0, 0xFFFFF80D7D578712)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbxhci.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB XHCI Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 11/28/2016 12:38:21 PM your computer crashed
crash dump file: C:\Windows\Minidump\112816-5890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8029389DFE3, 0x1, 0x100000032)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 Sun 11/27/2016 1:34:50 PM your computer crashed
crash dump file: C:\Windows\Minidump\112716-5828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xEF (0xFFFFB90DB4940780, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
11 crash dumps have been found and analyzed. Only 5 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.