Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8 BSOD when shutting down
New Posts  All Forums:Forum Nav:

Windows 8 BSOD when shutting down

post #1 of 4
Thread Starter 
Okay so a few weeks ago I had issues when shutting down Windows. Basicly my PC would Shutdown then start back up. Fixed it by disabling Fast Boot. Today when I tried to shut it down I got a BSOD, it shut down then rebooted. I immidietly tried to shut it down and it was fine, so I checked and tried to ENABLE fast boot, it shut down fine. The bsod I got is 0x00000c2 Bad_Pool_Header Caused by Driver: ntoskrnl.exe

I've done a full memtest a month ago and did prime tests so I don't believe it ram, also considering ever issue I have involves shut down I doubt its ram.

OS : Windows 8
4 weeks old

Gene V 1802 Bios
GSkill 1600ghz DDR3 1.65v
680 GTX SC + Windows7_Vista_jcgriff2.zip 206k .zip file
Edited by maneil99 - 7/16/13 at 4:20pm
post #2 of 4

Moved to proper forum. Also, please refer to the following and reply accordingly - http://www.overclock.net/t/1288510/blue-screen-of-death-bsod-posting-instructions-windows-8-7-vista/0_50


post #3 of 4
Thread Starter 
Okay I adjusted accordingly
post #4 of 4

The attached DMP is of the BAD_POOL_CALLER (c2) bugcheck. Essentially, this means that the current thread is making a bad pool request.

We have no address on the 4th argument to run a !poolval or !pool to check for pool corruption, so I cannot say whether this is memory or likely device driver related from this dump alone.

As you can see, we only have two parameters in this DMP rather than 4:
Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
Arg2: fffffa800c03c1c0, Address being freed
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

Enable Driver Verifier to see if we can catch a possible device driver bug:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:


Edited by pjBSOD - 7/17/13 at 11:53am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 8 BSOD when shutting down