BSOD 0x0000009f win7 x64 while shuting down my PC

gvp · 05 Dec 2014

message
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x0000000000000258, 0xfffffa80039df040, 0xfffff80000b9a4d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120414-17097-01.

Any idea why ?

koolkat77 · 12 Dec 2014

Code:

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


Loading Dump File [C:\Users\USER\Downloads\Compressed\PC-04_12_2014_215143,52\120414-18049-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`02441c32?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`035536b2?
Symbol search path is: SRV*c:\symbols*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
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034a8890
Debug session time: Thu Dec  4 06:41:56.811 2014 (UTC + 6:00)
System Uptime: 0 days 4:29:04.215
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80039df040, fffff80000b9a4d0}

Implicit thread is now fffffa80`039df040
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : WUDFRd.sys ( WUDFRd!RdDevice::MarkForDelete+26 )

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 (usually 10 minutes).
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa80039df040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9a4d0, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`039df040

DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032d05f2 to fffff800032dda8a

STACK_TEXT:  
fffff880`033c4100 fffff800`032d05f2 : fffffa80`039df040 fffffa80`039df040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`033c4240 fffff800`032e199f : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`05f339d0 : nt!KiCommitThreadWait+0x1d2
fffff880`033c42d0 fffff800`033eb875 : 00000000`00000000 fffffa80`00000000 fffffa80`05f33400 fffffa80`05f33a00 : nt!KeWaitForSingleObject+0x19f
fffff880`033c4370 fffff880`0764f9ea : fffffa80`0682e560 fffffa80`05f339d0 fffffa80`21444d55 00000000`0000041f : nt!IoReleaseRemoveLockAndWaitEx+0x45
fffff880`033c43b0 fffff880`0764ee52 : 00000000`00000000 fffffa80`05f339d0 fffffa80`06829702 fffffa80`0682e560 : WUDFRd!RdDevice::MarkForDelete+0x26
fffff880`033c43e0 fffff880`0764e37e : fffffa80`0607fce0 fffffa80`0607fce0 fffff880`07674158 fffffa80`05f339e0 : WUDFRd!RdDriver::DeleteDrvMgrCtrlDevice+0x1e
fffff880`033c4410 fffff880`07657db4 : 00000000`00000001 fffffa80`05f339e0 fffffa80`7c444d55 00000000`0000046b : WUDFRd!RdDriver::UnprepareSharedResources+0x92
fffff880`033c4440 fffff880`076579dc : 00000000`00000001 fffffa80`06829790 00000000`ffffffff fffffa80`04fecbf0 : WUDFRd!RdFdoDevice::~RdFdoDevice+0x264
fffff880`033c44c0 fffff880`0764bd0d : 00000000`00000000 fffff880`07651e05 fffffa80`06829702 fffff880`07674158 : WUDFRd!RdFdoDevice::`vector deleting destructor'+0x14
fffff880`033c44f0 fffff880`0764c1af : fffffa80`04fecbf0 fffff880`0764bd0d 00000000`00000000 fffff800`032dda00 : WUDFRd!CUMDFUnknown::Release+0x21
fffff880`033c4520 fffff880`0765270a : fffffa80`039ceb30 fffffa80`05f336a0 fffffa80`05f87010 00000000`00000000 : WUDFRd!WdfObject::ReleaseWait+0x7f
fffff880`033c4560 fffff880`07652a33 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000001 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x342
fffff880`033c45f0 fffff880`0765232f : fffffa80`05f87010 fffffa80`05f87010 fffffa80`05f3361b 00000000`00000103 : WUDFRd!RdPnpTracker::RdPnpProcessor+0x66b
fffff880`033c4680 fffff880`07650de6 : 00000000`0000001b fffffa80`05f336a0 fffffa80`05f87010 fffff8a0`000a2690 : WUDFRd!RdPnpTracker::RdPnp+0x407
fffff880`033c46f0 fffff880`0764d4ce : 00000000`00000000 00000000`c000001b fffffa80`05f87010 00000000`c000001b : WUDFRd!RdDevice::ProcessIrp+0x132
fffff880`033c4730 fffff800`03546571 : fffffa80`05f33420 fffff880`033c4828 00000000`c00000bb fffffa80`05f87010 : WUDFRd!RdDriver::RdDispatch+0xda
fffff880`033c4770 fffff800`036c73c1 : fffffa80`06829790 00000000`00000000 fffffa80`0685c010 00000000`00000801 : nt!IopSynchronousCall+0xe1
fffff880`033c47e0 fffff800`033dd063 : fffff8a0`039ccd10 fffff8a0`039ccd10 00000000`0000002b 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`033c48a0 fffff800`036c6f14 : fffffa80`0685c010 00000000`00000000 00000000`00000002 00000000`00000008 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`033c48f0 fffff800`036c7020 : 00000000`00000000 fffffa80`06829700 fffff8a0`03c5a850 fffff800`034deca0 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`033c4920 fffff800`036c7119 : fffffa80`04fec602 fffffa80`04fec660 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`033c4990 fffff800`036c7291 : fffffa80`04fec660 00000000`00000000 fffffa80`04fec660 00000000`00000001 : nt!PnpDelayedRemoveWorker+0x79
fffff880`033c49e0 fffff800`033dd29a : 00000000`00000000 fffffa80`0694c220 00000000`0000000a 00000000`00000000 : nt!PnpChainDereferenceComplete+0x131
fffff880`033c4a20 fffff800`037582c0 : 00000000`00000000 fffffa80`0685c010 fffff8a0`04d5c670 00000000`00000001 : nt!PnpIsChainDereferenced+0xda
fffff880`033c4aa0 fffff800`0375855c : fffff880`033c4c78 00000000`00000000 fffff8a0`0d99b800 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`033c4be0 fffff800`0364173e : 00000000`00000000 fffffa80`03b85070 fffff8a0`04d5c670 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`033c4c10 fffff800`032e4261 : fffff800`035453d8 fffff8a0`04d5c670 fffff800`034802d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x54d9b
fffff880`033c4c70 fffff800`0357673a : 00000000`00000000 fffffa80`039df040 00000000`00000080 fffffa80`039ceb30 : nt!ExpWorkerThread+0x111
fffff880`033c4d00 fffff800`032cb8e6 : fffff880`03163180 fffffa80`039df040 fffff880`0316dfc0 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`033c4d40 00000000`00000000 : fffff880`033c5000 fffff880`033bf000 fffff880`0a4c6730 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WUDFRd!RdDevice::MarkForDelete+26
fffff880`0764f9ea 4883c428        add     rsp,28h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  WUDFRd!RdDevice::MarkForDelete+26

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WUDFRd

IMAGE_NAME:  WUDFRd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5010aabe

FAILURE_BUCKET_ID:  X64_0x9F_4_WUDFRd!RdDevice::MarkForDelete+26

BUCKET_ID:  X64_0x9F_4_WUDFRd!RdDevice::MarkForDelete+26

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

0: kd> lmvm WUDFRd
start             end                 module name
fffff880`07648000 fffff880`0767e000   WUDFRd     (pdb symbols)          c:\symbols\WUDFRd.pdb\C78C2B37DADA49AEADDEFD5150BF44C31\WUDFRd.pdb
    Loaded symbol image file: WUDFRd.sys
    Mapped memory image file: c:\symbols\WUDFRd.sys\5010AABE36000\WUDFRd.sys
    Image path: \SystemRoot\system32\DRIVERS\WUDFRd.sys
    Image name: WUDFRd.sys
    Timestamp:        Thu Jul 26 08:26:06 2012 (5010AABE)
    CheckSum:         000365F0
    ImageSize:        00036000
    File version:     6.2.9200.16384
    Product version:  6.2.9200.16384
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     WUDFRd.sys
    OriginalFilename: WUDFRd.sys
    ProductVersion:   6.2.9200.16384
    FileVersion:      6.2.9200.16384 (win8_rtm.120725-1247)
    FileDescription:  Windows Driver Foundation - User-mode Driver Framework Reflector
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

SPTD Removal:

Uninstall the software using Add/Remove Programs.
Reboot the system.
Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

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:

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

gvp · 12 Dec 2014

thank you