Help me get to the bottom of my BSOD!

Toggle sidebar Toggle sidebar
T

t3hfuhr3r

Honorable
May 25, 2012
15
0
10,510
So I've been having this random BSOD issue. It started a few months ago, and has been getting worse. I have no idea what I changed on the computer that could have started it, so uninstalling updates or software is out. I've had 3 BSODs today.

Usually, it doesn't even leave a crash report. Every once in a while it does, but after installing WhoCrashed, it says it's probably a driver issue, except for a couple that say it might be a memory issue.

I'm pretty close to reinstalling everything from windows up. AFAIK, all drivers are up to date.

Specs:
Windows 7 Enterprise x64
Intel i7-3770K 3.5GHz
Asus P8Z77 V-Pro
16GB RAM
ASUS GTX 760.

Some bugcheck codes:

crash dump file: C:\Windows\Minidump\050316-31122-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC500F6938, 0x803000018AE33882, 0xFFFFF6FC500F6929)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xA (0x1FF8655E2, 0x2, 0x0, 0xFFFFF80003D5FBA6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe


crash dump file: C:\Windows\Minidump\050316-34991-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xA (0x1FF8655E2, 0x2, 0x0, 0xFFFFF80003D5FBA6)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe


crash dump file: C:\Windows\Minidump\041916-34429-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x6A8E6, 0x158136000D51DC)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe


crash dump file: C:\Windows\Minidump\030316-38485-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80007BF5A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe


crash dump file: C:\Windows\Minidump\030216-41480-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x735C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8A017BA1010, 0xFFFFF8A017BA1010, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe

Any ideas where I should go from here?

Update:

I ran memtest for a total of 16 hours in two sessions, and it found no errors. After the inevitable next crash, I opened up. Everything seems to be seated properly, and I changed the RAM around in its slots. For whatever reason, it failed to boot the first time not making it into BIOS, but it worked fine after that.

Latest crash report seems a bit different:

crash dump file: C:\Windows\Minidump\050416-36395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xC1 (0x180ABB2800000000, 0x180ABA0C00000010, 0x0, 0x82)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe

Maybe it's time to throw another $200 at some new RAM?
Update 2:
Three times in 20 minutes, a new record!

crash dump file: C:\Windows\Minidump\050416-36395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0xC1 (0x180ABB2800000000, 0x180ABA0C00000010, 0x0, 0x82)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe

crash dump file: C:\Windows\Minidump\050316-31122-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x743C0)
Bugcheck code: 0x1A (0x411, 0xFFFFF6FC500F6938, 0x803000018AE33882, 0xFFFFF6FC500F6929)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
 
Solution
Flyfisherman
Hi,

Bugcheck code: 0xA
https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129%28v=vs.85%29.aspx

BlueScreenView - Free - scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table.
http://www.nirsoft.net/utils/blue_screen_view.html

It could be problems with the memory s, so that is where I suggest to start.
Download and burn memtest86+ on a CD (it's a small program) or put it on a booatble flash stick http://www.memtest.org/
The computer will boot up and directly running the memory test. You should let it run for at least over night. If there are any error you can just shutdown the computer. Nothing at all will happen to your operating...
Sort by date Sort by votes
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Hi,

Bugcheck code: 0xA
https://msdn.microsoft.com/en-us/library/windows/hardware/ff560129%28v=vs.85%29.aspx

BlueScreenView - Free - scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table.
http://www.nirsoft.net/utils/blue_screen_view.html

It could be problems with the memory s, so that is where I suggest to start.
Download and burn memtest86+ on a CD (it's a small program) or put it on a booatble flash stick http://www.memtest.org/
The computer will boot up and directly running the memory test. You should let it run for at least over night. If there are any error you can just shutdown the computer. Nothing at all will happen to your operating system and it will not under any circumstances be affected of memtest86+

If any error, try to remove all the memory sticks but one (mounted in the correct slot, probably the nearest or second nearest to the CPU, check in the motherboard manual), then run the memttest86+ again, shut down and replace the memory stick. Perhaps it's possible to isolate the faulty memory. The test will be much faster with less memory in and it should be running to pass 8 or pass 9.

If there is a faulty memory, take a picture of the screen and if returning these on warranty, all memory's in one complete memory kit must be returned.

Best Regards from Sweden
 
Upvote 0 Downvote
Solution
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Ahh, and also check that all memory sticks are properly seated in their slots.
Check also all connectors, graphics card and its power connectors, so everything is properly mounted.

Be careful of the ESD (Electrostatic Discharge) and try to use an ESD wrist strap attached to a non painted metal part of the chassis.
antistatic-wrist-chiosz-robots-3.jpg
 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
Hi again,
I'm sorry that I have not been around lately.

Ok. Do You still have the same problem?
Your latest Bugcheck code: 0x1A suggest there is a severe memory problem: https://msdn.microsoft.com/en-us/library/windows/hardware/ff557391%28v=vs.85%29.aspx

You have an Asus P8Z77 V-Pro
with 16GB RAM - but exactly what is the brand and model, manufactory part number (mpn)?
Either there is a faulty memory or You have incompatible memory's for your motherboard or a faulty motherboard?
Very hard from distance to say.

Check this out: https://www.asus.com/Motherboards/P8Z77V_PRO/HelpDesk_QVL/

Or use any big memory manufacturer and their memory configurator such as:
Corsair: http://www.corsair.com/en-us/memory-finder
G-skill: http://www.gskill.com/en/configurator
Kingston: http://www.kingston.com/us/memory/search/Options
Etc.

With just one memory stick which [strike]should[/strike] must be placed in the Blue memory slot second from the CPU DIMM_A2
in the manual pdf page 29/164 http://dlcdnet.asus.com/pub/ASUS/mb/LGA1155/P8Z77-V_PRO/E7198_P8Z77-V_PRO.pdf?_ga=1.31478590.1015468463.1454155183

Then you can just swap that memory stick and try again, I mean run memtest 86+ again, and it will be faster with less memory to check.
Best Regards from Sweden

 
Upvote 0 Downvote
Flyfisherman

Flyfisherman

Distinguished
May 29, 2012
1,136
8
20,365
And You should also reset the BIOS settings:

When you start up the computer, the system provides you with the opportunity to run this program.
Press [Del] during the Power-On Self-Test (POST) to enter the Setup utility. Otherwise, POST continues with its test routines.
If you wish to enter Setup after POST, press [Ctr] + [Alt] + [Delete], or press the reset
button on the system chassis to restart the system. You can also turn the system off and then
turn it back on to restart the system. Do this last option only if the first two failed

From there first check Your BOOT priority, I mean in which order your disks is booting from first and memorize that.
Then do "Load Optimized Defaults settings" press [F5], then if necessary change the disk boot priority and [F10] Save & Exit
 
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