BSOD when sleep,error 0x0000009f

Page 2 of 4 FirstFirst 1234 LastLast

  1. zhenjames
    Posts : 16
    window 7 Ultimate X64
    Thread Starter
       New #11

    The report is attached.
      My Computer
    Quote Quote

  3. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #12

    Do you have any external device plugged in?
      My Computer
    Quote Quote

  4. zhenjames
    Posts : 16
    window 7 Ultimate X64
    Thread Starter
       New #13

    Nothing else but a wireless mouse.
      My Computer
    Quote Quote

  6. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #14

    Ok.. what's the age of your computer? Since when did this problem start?
      My Computer
    Quote Quote

  7. zhenjames
    Posts : 16
    window 7 Ultimate X64
    Thread Starter
       New #15

    It's age is less than 1 year. I can not tell the exact earliest day when this problem occur, but approximately 1 month ago.
      My Computer
    Quote Quote

  8. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #16

    Did you make any changes? Hardware/Software wise?
      My Computer
    Quote Quote

  10. zhenjames
    Posts : 16
    window 7 Ultimate X64
    Thread Starter
       New #17

    This system is still the original one that I got from the manufacturer, but I keep updating it using the Mircrosoft automatic update, and the Lenovo update utility.
      My Computer
    Quote Quote

  11. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #18

    Let's run driver verifier and see if it catches any misbehaving drivers:
      My Computer
    Quote Quote

  12. zhenjames
    Posts : 16
    window 7 Ultimate X64
    Thread Starter
       New #19

    I run the driver verifier and the BSOD occured right after I started up the system, I can not even login the windows, so I had to restore the system to the state without enableing the driver verifier. The report is attached.
      My Computer
    Quote Quote

  13. koolkat77
    Posts : 15,026
    Windows 10 Home 64Bit
       New #20

    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88001c9f324, fffff980079feee0, 0}

*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
Unable to load image \SystemRoot\system32\DRIVERS\dtsoftbus01.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88001c9f324, The address in the driver's code where the error was detected.
Arg3: fffff980079feee0, IRP address.
Arg4: 0000000000000000, Status code.

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


OVERLAPPED_MODULE: Address regions for 'Npfs' and 'cdrom.sys' overlap

BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1324
fffff880`01c9f324 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1324
fffff880`01c9f324 4053            push    rbx

IRP_ADDRESS:  fffff980079feee0

DEVICE_OBJECT: fffffa800b11ed50

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000375d3dc to fffff800032cec40

STACK_TEXT:  
fffff880`035bc508 fffff800`0375d3dc : 00000000`000000c9 00000000`0000023e fffff880`01c9f324 fffff980`079feee0 : nt!KeBugCheckEx
fffff880`035bc510 fffff800`0376747a : fffff800`0375b9f0 fffff880`01c9f324 fffff980`079feee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035bc550 fffff800`0376834e : 00000000`0000023e 00000000`00000000 fffff980`079feee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`035bc5a0 fffff800`0377371f : fffffa80`0b28a040 fffffa80`08556b30 fffffa80`08556be8 fffff880`01ca3228 : nt!VfErrorReport6+0x6e
fffff880`035bc670 fffff800`03773b63 : fffffa80`08556b30 00000000`00000002 fffffa80`0b11ed50 fffff880`01c9f3f4 : nt!IovpCallDriver2+0x13f
fffff880`035bc6d0 fffff800`03779c2e : fffff980`079feee0 fffff980`079feee0 00000000`00000002 fffffa80`0b11ed50 : nt!VfAfterCallDriver+0x353
fffff880`035bc720 fffff880`00e24d3b : fffff880`00eb6d20 fffff880`035bc7f0 00000000`00000025 fffffa80`08556b30 : nt!IovCallDriver+0x57e
fffff880`035bc780 fffff880`00e26d65 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0bc466b0 : Wdf01000!FxIoTarget::SubmitSync+0x24b
fffff880`035bc830 fffff880`087c5e95 : fffffa80`00000020 fffffa80`0bc466b0 fffffa80`0b2e1880 fffffa80`0bc0a300 : Wdf01000!imp_WdfRequestSend+0x2d1
fffff880`035bc8c0 fffff880`087c62f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`035bca80 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`035bc920 fffff880`087c4f04 : 0000057f`f4d21728 fffff880`035bca80 fffffa80`0b5a1970 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`035bca50 fffff880`087c3825 : fffffa80`00000002 fffffa80`0b2deb80 fffff880`087bb3b8 0000057f`f4d21728 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`035bcb20 fffff880`00e57ef0 : 00000000`00000000 00000000`00000010 00000000`0000000c fffff880`00eb70c0 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`035bcb60 fffff880`00e3afaa : fffffa80`0b2de140 00000000`0000000c fffff880`00eb70c0 00000000`00000002 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`035bcb90 fffff880`00e465db : 00000000`00000000 00000000`00000000 fffff880`035bcd30 fffff880`00eb70c0 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`035bcc00 fffff880`00e31c3c : 00000000`00000312 fffff880`035bcd30 00000000`ffff7fff fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`035bcc30 fffff880`00e32106 : fffff880`00eb6e80 fffffa80`0b2de548 fffffa80`0b2de390 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
fffff880`035bcd90 fffff880`00e31e9f : 00000000`00000000 fffff880`035bce70 fffffa80`0b2de530 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`035bce00 fffff880`00e47afe : 00000000`00000000 00000000`00000501 00000000`00000501 fffff800`037650ce : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
fffff880`035bcea0 fffff880`00e3be99 : 00000000`00000501 fffff880`035bcf40 00000000`00000500 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`035bced0 fffff880`00e32a9b : fffffa80`0b2de5f8 fffffa80`0b2de600 fffffa80`0b2de390 fffffa80`0b2de5f8 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c9
fffff880`035bcf70 fffff880`00e32595 : 00000000`00000000 fffff880`035bd050 fffffa80`0b2de5e8 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3df
fffff880`035bcfe0 fffff880`00e469c1 : 00000000`00000000 fffffa80`0b59f230 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
fffff880`035bd080 fffff880`00e4681d : 00000000`00000101 00000000`00000108 00000000`00000108 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`035bd0c0 fffff880`00e47032 : 00000000`00000002 fffffa80`0b2de4b8 fffffa80`0b2de390 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
fffff880`035bd160 fffff880`00e46cdd : 00000000`00000000 fffff880`035bd240 fffffa80`0b2de4a0 fffffa80`0b2de390 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`035bd1d0 fffff880`00e46b3e : 00000000`00000000 fffffa80`0b2de390 fffffa80`0851ee40 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
fffff880`035bd270 fffff880`00e2fecf : fffffa80`0b2d5280 fffff880`035bd2f0 00000000`00000000 fffffa80`098c41c8 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
fffff880`035bd2a0 fffff880`00e279da : fffff980`0796cd80 00000000`00000051 fffff980`0796cd80 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x18f
fffff880`035bd300 fffff880`00e27aa6 : fffff980`0796cd80 00000000`00000002 fffffa80`0b2e1e10 fffffa80`0b2e1e10 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880`035bd340 fffff800`03779c16 : fffff980`0796cd80 00000000`00000002 fffffa80`0b2e1e10 fffff800`0377537e : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880`035bd380 fffff800`0377c52a : fffff980`0796cee0 fffffa80`0b2e1e10 fffffa80`0b59d080 fffffa80`0b0cf650 : nt!IovCallDriver+0x566
fffff880`035bd3e0 fffff800`03779c16 : fffff980`0796cd80 00000000`00000002 fffffa80`0b59d080 fffffa80`0b0d08c0 : nt!ViFilterDispatchPnp+0x13a
fffff880`035bd410 fffff880`0a9f9082 : fffffa80`0b59d080 00000000`00000000 fffffa80`0b59f630 fffffa80`0b0d08c0 : nt!IovCallDriver+0x566
fffff880`035bd470 fffffa80`0b59d080 : 00000000`00000000 fffffa80`0b59f630 fffffa80`0b0d08c0 fffff980`0796cfb8 : GEARAspiWDM+0x4082
fffff880`035bd478 00000000`00000000 : fffffa80`0b59f630 fffffa80`0b0d08c0 fffff980`0796cfb8 fffffa80`098c42b8 : 0xfffffa80`0b59d080


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1324

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10358a

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324

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

0: kd> lmvm dtsoftbus01
start             end                 module name
fffff880`01c9e000 fffff880`01ce7000   dtsoftbus01 T (no symbols)           
    Loaded symbol image file: dtsoftbus01.sys
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: dtsoftbus01.sys
    Timestamp:        Fri Jan 13 19:45:46 2012 (4F10358A)
    CheckSum:         00046D1E
    ImageSize:        00049000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Uninstall: Daemon Tools driver Possible BSOD issues in Win7 and CD-ROM Class Filter Driver by Gear Software. Also comes with iTunes

    Please uninstall DAEMON Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. 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.

    As an alternative, many people recommend the use of Total Mounter or Magic ISO
    And then try enabling verifier again.
      My Computer
    Quote Quote

 
Page 2 of 4 FirstFirst 1234 LastLast

  Related Discussions
Recently I have been having problems with shutting down and putting my computer to sleep. I do not know the cause nor have I had this problem before. I sadly do not have the stop code parameter information but I do have the files made by the dm collector. All I know about this code is that it may...
Hello All, Please help me with my BSOD problem. I attached three screen shots of BSOD and the zip file as requested. Thanks a lot in advance for your help Hasan
I have dual booted windows 7 and ubuntu 11.04 .For this I had to reinstall windows 7.I use grub loader to dual boot the os.Ever since dual booting i have problems in putting windows 7 to sleep (by closing the lid).sometimes it does sleep but other times it just shuts down and gives me the bsod...
- x86 (32-bit) or x64 ? x64 - the original installed OS on the system? Yes - an OEM or full retail version? OEM - What is the age of system (hardware)? 20 months - What is the age of OS installation 20 months Been seeing DRIVER_POWER_STATE_FAILURE a lot recently. Seems to happen when the...
I'd appreciate any help you can offer. It's an HP G62-435DX, about six to eight months old. The OS is Windows 7 Home Premium 64 bit OEM, and I have not reinstalled the OS since purchase. The system is set to go into sleep mode when I shut the lid. It's worked fine up until the last four or five...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 04:38.
Find Us