Need Help Troubleshooting Multiple BSODs

Toggle sidebar Toggle sidebar
p40whk

p40whk

Reputable
Nov 6, 2014
7
0
4,510
In July I decided to upgrade my computer for gaming and switched out my mother board and processor to an ASrock Z97 and an Intel Core i-5 4690K. It ran fine with my single MSI Geforce GTX770 graphics card.

I decided I wanted to try SLI and needed to upgrade the 500W power supply so I replaced it with an EVGA Supernova 850 B2. I haven't bought the new GTX770 but did install the PSU and have been getting random BSODs constantly since.

It has always been the following 3 errors:

BAD_POOL_HEADER 0x00000019

IRQL_NOT_LESS_OR_EQUAL 0x0000000A.

SYSTEM_SERVICE_EXCEPTION 0x0000003B

If it was the same one each time it might be easier to troubleshoot but I'm at a loss for where to start.

My temps are right at 35C-38C and I haven't checked the voltages yet.

I have uninstalled any unnecessary software and drivers. Removed and reinstalled all GPU drivers. Made sure all my Window's drivers were up to date, and run multiple diagnostic tools.

I will reinstall Windows if I have to but as a last resort since I don't have access to my DVD at the moment (it's packed in storage during a move).

I plan to switch the old power supply back in tonight to see if that's the issue but other than that I'm stumped. I don't have a lot of experience reading Window's Event Viewer so that hasn't been much help to me.

Any direction you can give on what I can look for would be appreciated.
 
Sort by date Sort by votes
rvilkman

rvilkman

Distinguished
Jun 12, 2009
2,307
0
20,960
Obviously replacing the PSU with the old one to see if it solves the problem would make the most sense. It will be able to rule out a problem with the PSU. The last time i had such issues the PSU was going bad, you might have gotten a lemon. Replace the PSU with a good one, no issues whatsoever.

Shy of that the usual suspects are memory and motherboard. But i'd go with the PSU test first as it should be the definitive answer to see if you need to even look further. It being the only item changed, shy of some power connectors not being connected properly, it seems a very likely culprit.
 
Upvote 0 Downvote
p40whk

p40whk

Reputable
Nov 6, 2014
7
0
4,510


Well, no luck there :(

PSU didn't solve the issue and I even removed and reset all components so that's not it either.

This is getting pretty frustrating. Here are more specifics and anyone can point me in the right direction. I don't have another video card to swap out but could pick up a cheap one if I needed to. According to the notes below though, it's indicating a driver issue:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, Z97 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17125613568 total

On Fri 11/7/2014 2:15:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110614-6380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031A8522, 0xFFFFF8800A6B1EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 11/7/2014 2:15:30 AM 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: 0x3B (0xC0000005, 0xFFFFF800031A8522, 0xFFFFF8800A6B1EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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

-----------------

And from earlier:

On Fri 11/7/2014 1:17:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110614-6318-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x1684D454D4C, 0x2, 0x1, 0xFFFFF80002EC2CA8)
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.
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


Any help would be appreciated
 
Upvote 0 Downvote
p40whk

p40whk

Reputable
Nov 6, 2014
7
0
4,510
Finally Solved (so far) my problem and it turned out to be a corrupt driver. I wish I would have found this trobleshooting method a few weeks ago so I'll post what I did here in case anyone else is having issues.

The Corrupt driver was the nvlddmkm.sys driver wich comes from Nvidia. I had previously uninstalled all of my Nvidia drivers and reinstalled them but I did that using a driver uninstall tool in a regular windows boot which obviously didn't remove all of the drivers.

The way I found it was by using the Window Drive "Verifier" tool which basically stress tests your drivers in an attempt to make them fail. I set it up per instructions I found online with the exception of selecting individual sets of drivers rather than Automatically selecting unassigned drivers as recommended.

I took a screen shot with my phone to remember which drivers I selected and ran the Verifier until I got the BSOD which Identified the bad driver. I had to run the Verifier 3 times with different set of drivers selected to find the culprit.

To uninstall the driver completely, I booted into safe mode "Without" networking and used Driver Booster to uninstall all my Nvidia drivers. I then opened Device Manager and selected "Display Adapters" which still showed my graphics card (telling me that Driver Booster couldn't completely uninstall all drivers), Right clicked on the adapter and selected Properties. From the Driver tab you can uninstall the driver completely.

Reboot, Download new drivers from Mfr. website and install. No probllems for at least a day!

Hope this helps someone having similar issues
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom