BSOD

I think I started getting the BSOD about two days ago.
I've tried Googling the error codes, but they seem to change on me sometimes, so I'm feeling a little lost on what to do next...
Right now, I'm using BlueScreenView to look at them, but if there's a better tool out there, please let me know. Also, if someone could help me figure out how to post these codes here so they actually make sense, I'd really appreciate the help...

Here are the BSOD codes I pulled from WhoCrashed..

System Information (local)
--------------------------------------------------------------------------------

computer name: LUX-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, 970 Pro3 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 4249604096 total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\Minidump\093014-26052-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
This looks like a typical software driver bug rather than a hardware issue.
The crash happened within the Windows kernel. It’s possible another unidentified driver is causing the trouble.

Your computer crashed on Tuesday, September 30, 2014, at 6:28:27 PM
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDA15)
Bugcheck code: 0x50 (0xFFFFF8001303DE88, 0x0, 0xFFFFF80002EC4E9F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 driver bug
Bug check description: This indicates that invalid system memory has been referenced.
This seems to be a standard software driver bug and likely isn't a hardware problem.
The crash occurred in a standard Microsoft module. There might be an issue with your system configuration, or possibly another driver we haven't caught yet.

Your computer crashed on Tuesday, September 30, 2014, at 6:26:39 PM
crash dump file: C:\Windows\Minidump\093014-25849-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x23975)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception that the error handler didn't catch.
This appears to be a typical software driver bug and shouldn't be a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration could be off, or it could be another unidentified driver.

Your computer crashed on Tuesday, September 30, 2014, at 6:22:59 PM
crash dump file: C:\Windows\Minidump\093014-24102-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80002EE3567)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
It looks like a standard software driver bug rather than anything involving your hardware.
The crash happened within the Windows kernel. It’s possible some other unidentified driver is causing the trouble here.

Your computer crashed on Tuesday, September 30, 2014, at 5:47:20 PM GMT
crash dump file: C:\Windows\Minidump\093014-19702-01.dmp
This was likely triggered by this module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
It seems like a third-party driver is the most likely culprit for this system error.
Google query : CUSTOM_ERROR

Your computer crashed on Tuesday, September 30, 2014, at 5:14:54 PM GMT
crash dump file: C:\Windows\Minidump\093014-27346-01.dmp
This was likely triggered by this module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF88001FBB180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means a secondary processor in a multi-processor setup didn't receive its expected clock interrupt within the set timeframe.
This looks like a typical software driver bug and probably isn't a hardware issue, though it could potentially be related to overheating.
The crash occurred in the Windows kernel. There might be another driver involved that we can't pinpoint just yet.

Your computer crashed on Tuesday, September 30, 2014, at 4:39:19 PM GMT
crash dump file: C:\Windows\Minidump\093014-21465-01.dmp
This was likely triggered by this module: usbport.sys (USBPORT+0x2D27C)
Bugcheck code: 0xA (0xFFFFF80000BACB90, 0x2, 0x1, 0xFFFFF80002E8F4A1)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This suggests that Microsoft Windows or a kernel-mode driver tried to access paged memory while at DISPATCH_LEVEL or higher.
This appears to be a common software driver bug and is unlikely to be a hardware problem.
The crash happened in a standard Microsoft module. Your system settings might be off, or perhaps another driver on your machine is causing the issue without being identified yet.

That’s a bit too optimistic for me. Honestly, the quickest and smartest move is just to back up your vital files and reinstall Windows. You've got a whole mess of errors popping up tied to a few different drivers, plus some random glitches you can't even pin down...

Thanks for the quick reply!

I tried reinstalling my DNS settings thinking it might stop the Blue Screen of Death, but no luck there :S
I'm kind of at a loss... I can't say exactly when the BSOD first popped up, but I think it started after I was messing around in the BIOS with my RAM timings. I didn't touch the voltage or anything. I probably need some tools to check if the RAM itself is failing or something... just so you know, I'm running a single 4GB Patriot Viper3 1866MHz stick.

Just jump back into the BIOS and reset everything to defaults 😉... that'll probably fix it, assuming you didn't fry them with something first.

I actually checked that a little while ago

Look, I remember this one time back at a repair shop where I picked up a Duron processor that clocked in 200MHz higher than what I was running. I popped it into my rig and everything seemed fine—it actually ran great... until I tried to install Windows. Every single time I got into the installation process, it would just throw a Blue Screen of Death right in my face. It happened over and over again. But here's the kicker—as soon as I swapped my old processor back in, the installation went through without a single hiccup. I’m not saying your CPU is definitely dead, but you should probably double-check everything... something clearly gave out, unless your BIOS is just completely fried.

I've got the BIOS updated.
I ran a quick MemTest86+ to check my RAM, but everything came back clean—no errors at all.
I've never overclocked my CPU... I did read somewhere that it could actually be a processor issue, but I honestly don't think that's what's happening here.

Here’s what I ran into today...

Your computer hit a wall and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-23634-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75BC0).
Looks like I ran into a 0x1E bugcheck. Here’s the info: (0xFFFFFFFFC0000096, 0xFFFFF80002EAF95C, 0x0, 0x0).
I ran into a KMODE_EXCEPTION_NOT_HANDLED error earlier. Has anyone else dealt with this one?
It looks like you're pointing toward C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows operating system
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
It looks like a kernel-mode program threw an exception that the error handler just couldn't catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened within the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is just yet.

Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:53:57 GMT.
I've got a crash dump file located at C:\Windows\memory.dmp.
It looks like this issue was likely triggered by this specific module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0).
Looks like you're running into a 0x1E bugcheck. It’s a bit of a headache, but we can figure this out.
Google query : KMODE_EXCEPTION_NOT_HANDLED
Basically, this means a kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue to me, so I wouldn't worry too much about your hardware being the culprit here.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I can't quite pin down which one just yet.

Your computer hit a snag and crashed on Wednesday, October 1st, 2014, at 8:21:22 GMT.
I've got the crash dump file right here: C:\Windows\Minidump\100114-18423-01.dmp
It looks like this was likely triggered by the usbport.sys module (USBPORT+0x160A4).
Looks like I ran into a 0xA bugcheck. Not exactly the start to my day that I was hoping for.
I ran into an IRQL_NOT_LESS_OR_EQUAL error. Any ideas what might be causing this?
It looks like you're pointing to C:\Windows\system32\drivers\usbport.sys.
Microsoft Windows
Microsoft Corporation
Just a quick heads-up regarding the USB 1.1 & 2.0 Port Driver.
Basically, this means a Microsoft Windows driver or some part of the kernel tried to touch paged memory while running at DISPATCH_LEVEL or higher. It's one of those classic errors.
It looks like a classic software driver glitch rather than anything actually wrong with your hardware.
It looks like the crash happened within a standard Microsoft module. There's a chance your system configuration might be a bit off, or perhaps another driver is causing some trouble behind the scenes that hasn't been identified yet.

Your computer hit a snag and crashed on Wednesday, October 1, 2014, at 8:17:46 GMT.
I've got the crash dump file here: C:\Windows\Minidump\100114-18049-01.dmp
It looks like this issue was likely triggered by the ntoskrnl.exe module (nt+0x75B90).
I ran into a Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0). Any ideas what might be causing this?
I ran into a KMODE_EXCEPTION_NOT_HANDLED error today. Any ideas?
It looks like the culprit is located at C:\Windows\system32\ntoskrnl.exe.
Microsoft Windows
Microsoft Corporation
Microsoft Corporation description : NT kernel & system bug
Basically, this means some kernel-mode program threw an exception that the error handler just wasn't able to catch.
It looks like a classic software driver issue rather than anything going wrong with your actual hardware.
It looks like the crash happened right in the Windows kernel. It’s possible some other driver is causing the trouble, but I haven't been able to pin down exactly which one it is yet.

Every time I hit a crash, the error points toward a software issue rather than anything with the hardware. Honestly, I'm starting to think that might actually be the culprit.
I have a feeling my GPU might be the culprit. I picked up a used one on eBay a few days ago, and since my motherboard doesn't have integrated graphics, I was totally stuck without it. I only started seeing the Blue Screen of Death the day after I finally got it installed. I'm starting to suspect there's something wrong with the card itself.

I was thinking about it and decided to just reinstall Windows, since I have a hunch the issue lies with my GPU drivers.
Right now, I don't have any drivers installed for my HD 5770, and I'm not getting any BSOD. I'm not going to spend all day installing drivers just to see if the BSOD pops up again. If it stays away, then I know for sure it’s a driver issue. Just to recap, I only picked up this GPU a few days ago, and I haven't even been able to use the PC much because my motherboard doesn't have integrated graphics. As soon as the GPU arrived and I started updating the drivers, things went sideways. I've also seen online that GPU driver issues are pretty common...
It looks like the latest versions might not be fully compatible right now. I'll keep an eye on it through the end of the day to see if the BSOD returns; if it doesn't, then the Catalyst drivers are definitely the culprit.
I'm honestly not sure which version would be the most stable to install.
At this point, it's all just guesswork, but as time goes by without a BSOD, I'm feeling a bit more happy about it. 😁
I'll check back in later with more info.

Nicholas Miller6
Try installing the drivers from the CD that came with your graphics card.
If you're still getting a BSOD after that, your card is officially dead in the water.😢

I picked up a used GPU a few days ago, but it didn't come with a driver CD. The seller said he didn't have it and just told me to grab them from the AMD site.
I don't think he was being shady, though, because I asked him for some screenshots from GPU-Z before he shipped it just to make sure everything looked solid.
So far, even without the drivers installed, everything seems to be running fine; no BSOD to report yet.
I could really use a suggestion on which specific drivers I should install, since I'm pretty sure the driver is where the trouble will start. I've already seen some stuff online about people running into similar headaches with those Catalyst drivers.

Turns out that didn't fix it, since I just hit another BSOD.

On Wednesday 10/01/2014 at 4:38:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED

On Wednesday 10/01/2014 at 5:11:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100114-17940-01.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800524F5E0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
A third party driver was identified as the probable root cause of this system error.
Google query : KMODE_EXCEPTION_NOT_HANDLED

Nicholas Miller6
You basically screwed him over by selling that junk 🙂

What kind of card are we looking at here? And if you don't mind me asking... what did it actually set you back?

HD 5770 1GB - $150
No issues so far... I tried swapping the RAM to a different slot, moved the GPU around, and even replaced the SATA cables inside the case...
If I hit a BSOD, I'll let you guys know. I watched a few tutorials on YouTube, and apparently, if a Blue Screen pops up, I should try booting into Safe Mode. If it still crashes there, it's definitely a hardware issue; if it stays stable, then it's likely just a software glitch, probably some buggy driver.

Sorted.
I honestly doubt it was actually a BIOS issue, mostly because I was running updates right when things started acting up. I was messing around with so many different things that day—installing my new GPU, getting everything set up after being offline for a couple of weeks—that I kind of lost track of what I had changed...
It was probably just a BIOS glitch or some messy GPU drivers.
Could be a lock...