locked
Driver errors causing BSOD RRS feed

  • Question

  • Hello!

    I've been experiencing BSODs for a while now, but troubleshooting myself didn't really help. so you guys are my last resort.

    Here's minidump files I have.

    https://onedrive.live.com/redir?resid=B59FDEF26C23034F!107&authkey=!ANgMiXZ4E6OOCok&ithint=file%2c.zip

    Would really appreciate your help! 

    Saturday, June 14, 2014 10:37 PM

Answers

  • Hi,

    All of the attached DMP files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bug check.

    This indicates that a system thread generated an exception which the error handler did not catch.

    7: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`033b6e28 fffff880`00e80790 nt!DbgBreakPoint
    fffff880`033b6e30 fffff880`00e7e14d Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
    fffff880`033b6e70 fffff880`00e8aa6c Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
    fffff880`033b6ec0 fffff880`00ef32cf Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
    fffff880`033b6f30 fffff880`00e810f8 Wdf01000!FxPkgPnp::PowerGotoD3Stopped+0x73
    fffff880`033b6f90 fffff880`00e80da6 Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`033b70f0 fffff880`00e81627 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`033b7160 fffff880`00ef939f Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`033b7200 fffff880`00e7dae7 Wdf01000!FxPkgPnp::PowerPolStopping+0x1b
    fffff880`033b7230 fffff880`00e7d5b9 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x1d7
    fffff880`033b7390 fffff880`00e81a01 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x145
    fffff880`033b7400 fffff880`00ef6c9a Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
    fffff880`033b74a0 fffff880`00e92df5 Wdf01000!FxPkgPnp::PnpEventFailedIoStarting+0xe
    fffff880`033b74d0 fffff880`00e92ac6 Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
    fffff880`033b7570 fffff880`00e92879 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`033b75e0 fffff880`00ef56bd Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
    fffff880`033b7680 fffff880`00e6d5d7 Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25
    fffff880`033b76b0 fffff880`00e6c79a Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`033b7710 fffff880`00e6c866 Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`033b7750 fffff800`03545571 Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`033b7790 fffff800`036c63a1 nt!IopSynchronousCall+0xe1
    fffff880`033b7800 fffff800`036c0d78 nt!IopRemoveDevice+0x101
    fffff880`033b78c0 fffff800`036c5ee7 nt!PnpSurpriseRemoveLockedDeviceNode+0x128
    fffff880`033b7900 fffff800`036c6000 nt!PnpDeleteLockedDeviceNode+0x37
    fffff880`033b7930 fffff800`0375697f nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`033b79a0 fffff800`0375753c nt!PnpProcessQueryRemoveAndEject+0x6cf
    fffff880`033b7ae0 fffff800`0364073e nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`033b7b10 fffff800`032e3261 nt! ?? ::NNGAKEGL::`string'+0x54d9b
    fffff880`033b7b70 fffff800`0357573a nt!ExpWorkerThread+0x111
    fffff880`033b7c00 fffff800`032ca8e6 nt!PspSystemThreadStartup+0x5a
    fffff880`033b7c40 00000000`00000000 nt!KxStartSystemThread+0x16
    

    Wdf01000.sys sent a wait for a signal on a system. I presume given the last call on stack (nt!DbgBreakPoint) you tried to break in and kernel debug?

    ------------------------------

    1.In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    2. Uninstall SysEnter ASAP!

    3.

    7: kd> lmvm androidusb
    start             end                 module name
    fffff880`09e74000 fffff880`09e83000   ANDROIDUSB   (deferred)             
        Image path: \SystemRoot\System32\Drivers\ANDROIDUSB.sys
        Image name: ANDROIDUSB.sys
        Timestamp:        Mon Oct 26 04:54:23 2009

    I have seen this driver cause crashes time and time again. If the above two don't help, please uninstall this software + remove the device (if any) from the system for troubleshooting purposes.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Yolanda Zhu Thursday, July 3, 2014 7:34 AM
    Saturday, June 14, 2014 11:01 PM

All replies

  • Hi,

    All of the attached DMP files are of the SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) bug check.

    This indicates that a system thread generated an exception which the error handler did not catch.

    7: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`033b6e28 fffff880`00e80790 nt!DbgBreakPoint
    fffff880`033b6e30 fffff880`00e7e14d Wdf01000!_FX_DRIVER_GLOBALS::WaitForSignal+0x70
    fffff880`033b6e70 fffff880`00e8aa6c Wdf01000!FxIoQueue::StopProcessingForPower+0x1ed
    fffff880`033b6ec0 fffff880`00ef32cf Wdf01000!FxPkgIo::StopProcessingForPower+0x22c
    fffff880`033b6f30 fffff880`00e810f8 Wdf01000!FxPkgPnp::PowerGotoD3Stopped+0x73
    fffff880`033b6f90 fffff880`00e80da6 Wdf01000!FxPkgPnp::PowerEnterNewState+0x1d8
    fffff880`033b70f0 fffff880`00e81627 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
    fffff880`033b7160 fffff880`00ef939f Wdf01000!FxPkgPnp::PowerProcessEvent+0x1b3
    fffff880`033b7200 fffff880`00e7dae7 Wdf01000!FxPkgPnp::PowerPolStopping+0x1b
    fffff880`033b7230 fffff880`00e7d5b9 Wdf01000!FxPkgPnp::PowerPolicyEnterNewState+0x1d7
    fffff880`033b7390 fffff880`00e81a01 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x145
    fffff880`033b7400 fffff880`00ef6c9a Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1c1
    fffff880`033b74a0 fffff880`00e92df5 Wdf01000!FxPkgPnp::PnpEventFailedIoStarting+0xe
    fffff880`033b74d0 fffff880`00e92ac6 Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a1
    fffff880`033b7570 fffff880`00e92879 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
    fffff880`033b75e0 fffff880`00ef56bd Wdf01000!FxPkgPnp::PnpProcessEvent+0x18d
    fffff880`033b7680 fffff880`00e6d5d7 Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x25
    fffff880`033b76b0 fffff880`00e6c79a Wdf01000!FxPkgPnp::Dispatch+0x18f
    fffff880`033b7710 fffff880`00e6c866 Wdf01000!FxDevice::Dispatch+0x19a
    fffff880`033b7750 fffff800`03545571 Wdf01000!FxDevice::DispatchWithLock+0xa6
    fffff880`033b7790 fffff800`036c63a1 nt!IopSynchronousCall+0xe1
    fffff880`033b7800 fffff800`036c0d78 nt!IopRemoveDevice+0x101
    fffff880`033b78c0 fffff800`036c5ee7 nt!PnpSurpriseRemoveLockedDeviceNode+0x128
    fffff880`033b7900 fffff800`036c6000 nt!PnpDeleteLockedDeviceNode+0x37
    fffff880`033b7930 fffff800`0375697f nt!PnpDeleteLockedDeviceNodes+0xa0
    fffff880`033b79a0 fffff800`0375753c nt!PnpProcessQueryRemoveAndEject+0x6cf
    fffff880`033b7ae0 fffff800`0364073e nt!PnpProcessTargetDeviceEvent+0x4c
    fffff880`033b7b10 fffff800`032e3261 nt! ?? ::NNGAKEGL::`string'+0x54d9b
    fffff880`033b7b70 fffff800`0357573a nt!ExpWorkerThread+0x111
    fffff880`033b7c00 fffff800`032ca8e6 nt!PspSystemThreadStartup+0x5a
    fffff880`033b7c40 00000000`00000000 nt!KxStartSystemThread+0x16
    

    Wdf01000.sys sent a wait for a signal on a system. I presume given the last call on stack (nt!DbgBreakPoint) you tried to break in and kernel debug?

    ------------------------------

    1.In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

    2. Uninstall SysEnter ASAP!

    3.

    7: kd> lmvm androidusb
    start             end                 module name
    fffff880`09e74000 fffff880`09e83000   ANDROIDUSB   (deferred)             
        Image path: \SystemRoot\System32\Drivers\ANDROIDUSB.sys
        Image name: ANDROIDUSB.sys
        Timestamp:        Mon Oct 26 04:54:23 2009

    I have seen this driver cause crashes time and time again. If the above two don't help, please uninstall this software + remove the device (if any) from the system for troubleshooting purposes.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Yolanda Zhu Thursday, July 3, 2014 7:34 AM
    Saturday, June 14, 2014 11:01 PM
  • Thanks a lot for your response!

    I will try what you're suggesting, however I don't quite understand what do you mean by uninstalling SysEnter.

    Sunday, June 15, 2014 6:58 AM
  • My pleasure, please keep me updated.

    The software I was speaking of is - SysEnter Application Beijing Weitong Xincheng Network Technologies Co., Ltd. It appears to be called PassGuard.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Sunday, June 15, 2014 7:19 AM