BSOD during shutdown, error 0x000009f

I recently installed 12GB DDR3 memory and changed it to AHCI mode. Then I installed the moberboards AHCI drivers from their website. This is the most recent thing I have installed.

Now whenever I shutdown my computer it takes forever and then eventually reboots saying "windows has recovered from an unexpected shutdown...blue screen/bug check etc" message.

I performed an analysis on the dump file and it produced the results below but I'm not exactly sure where the problem is.

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\050412-18283-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00201022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`018b0282?
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Windows\winsxs
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`02054000 PsLoadedModuleList = 0xfffff800`02298650
Debug session time: Fri May  4 03:10:55.256 2012 (UTC - 4:00)
System Uptime: 0 days 8:06:03.130
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8009d3a680, fffff8000358f510}

Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

Followup: MachineOwner
---------
0: kd> 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8009d3a680, The thread currently holding on to the Pnp lock.
Arg4: fffff8000358f510

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8009d3a680

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800020c66c2 to fffff800020d3b7a

STACK_TEXT:  
fffff880`021b5890 fffff800`020c66c2 : fffffa80`09d3a680 fffffa80`09d3a680 00000000`00000000 00000000`00000002 : nt!KiSwapContext+0x7a
fffff880`021b59d0 fffff800`020d7a9f : 00000000`00000000 00000000`00000000 00000000`00000022 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`021b5a60 fffff800`020b0c3e : 00000000`00000000 fffff800`0000001b 00000000`00000000 fffff880`0205d100 : nt!KeWaitForSingleObject+0x19f
fffff880`021b5b00 fffff800`020d5eac : ffffffff`fd9da600 fffffa80`0b4fdf70 fffff800`022ceb60 fffffa80`09d3a680 : nt!ExpWaitForResource+0xae
fffff880`021b5b70 fffff800`0240acb2 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff800`0206f078 : nt!ExAcquireResourceExclusiveLite+0x14f
fffff880`021b5be0 fffff800`021ccc20 : 00000000`00000000 fffff800`022702b8 00000000`00000001 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x1c44c
fffff880`021b5c10 fffff800`020da361 : fffff800`021ccbe0 fffff800`02270201 fffff800`024b7500 00000000`00000000 : nt!PnpDeviceActionWorker+0x40
fffff880`021b5cb0 fffff800`0236afda : 71207120`67f367f3 fffffa80`09d3a680 00000000`00000080 fffffa80`09d02b30 : nt!ExpWorkerThread+0x111
fffff880`021b5d40 fffff800`020c19c6 : fffff880`0205d180 fffffa80`09d3a680 fffff880`02067fc0 5ed55ed5`23b323b3 : nt!PspSystemThreadStartup+0x5a
fffff880`021b5d80 00000000`00000000 : fffff880`021b6000 fffff880`021b0000 fffff880`021b45d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8009d3a680 ; kb

FOLLOWUP_IP: 
nt!KiSwapContext+7a
fffff800`020d3b7a 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiSwapContext+7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

FAILURE_BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

BUCKET_ID:  X64_0x9F_4_nt!KiSwapContext+7a

Followup: MachineOwner
---------

0: kd> !analyze -show
Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

I reinstalled the GPU driver and will see what that does.

That is a good troubleshooting step for that particular crash. The most common causes of a DRIVER_POWER_STATE_FAILURE are display card drivers, network drivers, and audio drivers.


Since you switched to AHCI, you may actually need to do a fresh install of Windows after backing up important data. The switch from AHCI to IDE usually does not cause problems, but the switch from IDE to AHCI can decrease stability with Windows until it is freshly installed. I do not know if a fresh install is entirely necessary, but just thought I would mention it so you are prepared if it is needed.

I might need it because I have been experiencing several program lockups (including explorer.exe) as well as my desktop shortcuts displaying black boxes (no I have not tweaked the shortcut arrows).

I removed the iconcache file and the problem still persists. The good thing is that I have not experienced a BSOD since the GPU driver. I think it's about time I reinstall Windows and hope that I can use my old MSDN key.

Thank you.

You're welcome. Take a look at Clean Reinstall - Factory OEM Windows 7 for good steps for the clean re-install.

Alright so I got around to reinstalling Windows 7. Everything seems to be working fine now after a bunch of updates. Although now my external hard drive shows up as a removable device. It's a 1TB eSATA.

Yes I installed all the drivers including AHCI (and enabling it in BIOS). Which brings me to my next question. Even though AHCI is enabled I do not see the AHCI options under my Drive Policies (for my SSD).

Isn't this what I'm supposed to see?


This is what I see on my SSD:

You will only see the Removal Policy options if the drive is removable. What you see is correct if the drive you are looking at in Policies is your system drive.

How do I fix this then?

Now you have reached a problem that is beyond my expertise... Recommend starting a thread in Hardware & Devices - Windows 7 Forums

I am not familiar with eSATA devices (I assume this is your eSATA drive?).

Yes this is an external eSATA hard drive. This is the first time this has happened to this device. Last time it happened to all of my drives but once I installed the AHCI drivers it fixed it.