BSOD when Computer is Shutting Down Error 0x10000009f

Eniatnof · 18 Sep 2015

Hello All,

Yesterday I started having problems with the computer BSOD each time it is shutdown. The shutdown process seems to hang for a considerable amount of time and then the BSOD message occurs. This has happened three times in the last two days. Each time the error message states the same information.

Any insight would be greatly appreciated.

koolkat77 · 20 Sep 2015

Clean boot

Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

How to Change, Add, or Remove Startup Programs in Windows 7

Code:

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


Loading Dump File [C:\Users\KOOLKAT77\Downloads\DESKTOP-Fri_09_18_2015_143947_64\SFdebugFiles\091815-14539-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`12430a12?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`2b220022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`191f9022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`2244da12?

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18939.amd64fre.win7sp1_gdr.150722-0600
Machine Name:
Kernel base = 0xfffff800`03619000 PsLoadedModuleList = 0xfffff800`03860730
Debug session time: Sat Sep 19 01:32:03.005 2015 (UTC + 6:00)
System Uptime: 0 days 22:36:02.817
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
..........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa8006d02040, fffff800051ca3d0}

Implicit thread is now fffffa80`06d02040
Probably caused by : mountmgr.sys ( mountmgr!MountMgrCheckDiskForNoDriveLetter+9d )

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d02040, The thread currently holding on to the Pnp lock.
Arg4: fffff800051ca3d0, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now fffffa80`06d02040

DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa8006d02040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80003691802 to fffff8000368edaa

STACK_TEXT:  
fffff880`037ee490 fffff800`03691802 : fffffa80`06d02040 fffffa80`06d02040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`037ee5d0 fffff800`0369401f : 00000000`00000000 fffffa80`0faf7858 00000000`00000000 00000000`00000014 : nt!KiCommitThreadWait+0x1d2
fffff880`037ee660 fffff800`0370d2be : fffffa80`0f0e2200 fffffa80`00000000 fffff880`037ee800 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`037ee700 fffff880`00eac891 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff880`00ea25a8 : nt! ?? ::FNODOBFM::`string'+0x479af
fffff880`037ee7c0 fffff880`00eacc16 : fffff8a0`24808a50 00000000`00000000 fffff880`00000000 fffffa80`0f0e2210 : mountmgr!MountMgrCheckDiskForNoDriveLetter+0x9d
fffff880`037ee800 fffff880`00eadf95 : 00000000`00000000 ffffdaf3`d593cd64 fffff880`037eea98 00000000`00000000 : mountmgr!MountMgrMountedDeviceArrival+0x34a
fffff880`037ee9b0 fffff800`038f5c9c : fffff8a0`0031e850 00000000`00000000 00000000`00000000 42706e50`00000000 : mountmgr!MountMgrMountedDeviceNotification+0x75
fffff880`037ee9e0 fffff800`03ad5068 : fffff8a0`0031e850 fffff880`037eea98 fffff8a0`2c2edab0 00000000`ffffffff : nt!PnpNotifyDriverCallback+0x5c
fffff880`037eea70 fffff800`039fb64c : 00000000`00000000 fffffa80`077f59d0 fffff8a0`159e40c0 00000000`00000000 : nt!PnpNotifyDeviceClassChange+0x188
fffff880`037eeb10 fffff800`036961b5 : fffff800`038f4d70 fffff8a0`2c2eda40 fffff800`038372d8 fffffa80`0b5aac58 : nt! ?? ::NNGAKEGL::`string'+0x519d1
fffff880`037eeb70 fffff800`039258e2 : 00000000`00000000 fffffa80`06d02040 00000000`00000080 fffffa80`06cee040 : nt!ExpWorkerThread+0x111
fffff880`037eec00 fffff800`0367df46 : fffff880`03565180 fffffa80`06d02040 fffff880`0356ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037eec40 00000000`00000000 : fffff880`037ef000 fffff880`037e9000 fffff880`037edd70 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa8006d02040 ; kb

FOLLOWUP_IP: 
mountmgr!MountMgrCheckDiskForNoDriveLetter+9d
fffff880`00eac891 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  mountmgr!MountMgrCheckDiskForNoDriveLetter+9d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: mountmgr

IMAGE_NAME:  mountmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55a68df5

IMAGE_VERSION:  6.1.7601.18933

FAILURE_BUCKET_ID:  X64_0x9F_4_mountmgr!MountMgrCheckDiskForNoDriveLetter+9d

BUCKET_ID:  X64_0x9F_4_mountmgr!MountMgrCheckDiskForNoDriveLetter+9d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_4_mountmgr!mountmgrcheckdiskfornodriveletter+9d

FAILURE_ID_HASH:  {6b628703-ad38-e710-8f6d-251d771a6b1d}

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

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

Hard Drive Diagnostics

Double click and open my computer.
Right click on desired drive and hit properties.
Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:

Make scans with the following:

Kaspersky TDSSKiller

Anti-rootkit utility TDSSKiller

ESET online scanner:

Free Online Virus Scanner | ESET

Temp Monitoring

Check for heating issues using Speccy or HWMonitor.

Upload a screen shot with either of the tools: Screenshots and Files - Upload and Post in Seven Forums