Re: DRIVER_POWER_STATE_FAILURE ..technical information:STOP 0x0000009f
We have many dumps attached, most with the WINLOGON_FATAL_ERROR (c000021a)
bugcheck. Essentially it means that the Winlogon process terminated unexpectedly.
We also have PAGE_FAULT_IN_NONPAGED_AREA (50)
This indicates that invalid system memory has been referenced.
Usual causes are a bug in a device driver, hardware related memory issues, corrupt NTFS volume, anti-virus software.
If we look at the call stack:
b36b7a3c 82a43aa8 00000001 c170a000 00000000 nt!MmAccessFault+0x104
b36b7a3c 8b36aa7b 00000001 c170a000 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
b36b7b0c 8ac32ad1 9724a8f8 c1708000 00000010 CFRMD+0x7a7b
b36b7b58 8ac48641 85fcf3c8 0359d768 00000010 fltmgr!FltpFilterMessage+0x9d
b36b7b8c 8ac48a69 852e8400 00000000 0359d768 fltmgr!FltpMsgDeviceControl+0xa9
b36b7bd0 8ac31339 85c71f08 8535bd40 852e8400 fltmgr!FltpMsgDispatch+0x91
b36b7bfc 82a39c1e 85c71f08 8535bd40 8535bd40 fltmgr!FltpDispatch+0x33
b36b7c14 82c2dbe9 852e8400 8535bd40 8535bdb0 nt!IofCallDriver+0x63
b36b7c34 82c30dd2 85c71f08 852e8400 00000000 nt!IopSynchronousServiceTail+0x1f8
b36b7cd0 82c77751 85c71f08 8535bd40 00000000 nt!IopXxxControlFile+0x6aa
b36b7d04 82a408c6 00000cf8 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b36b7d04 77ca70f4 00000cf8 00000000 00000000 nt!KiSystemServicePostCall
0390fd70 00000000 00000000 00000000 00000000 0x77ca70f4
We can see a CFRMD.sys
call a little before the bugcheck. This is the COMODO Safe Delete Filter driver. I would recommend removing COMODO asap.
If after uninstalling COMODO you're still crashing, please enable Driver Verifier so we can see if there's further device driver corruption and or conflicts:
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 if it detects a violation.
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"
Windows 8 - Restore Point - Create in Windows 8
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.
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 24 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 %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users