locked
BSOD IRQL_NOT_LESS_OR_EQUAL RRS feed

  • Question

  • My PC showing BSOD IRQL_NOT_LESS_OR_EQUAL almost once per day. This is the minidump file : http://sdrv.ms/1bBuPhD .
    I have no idea how to fix this so some help would be greatly appreciated.
    Thursday, January 30, 2014 3:09 PM

Answers

  • Vishera

    The verified DMP was related to dtsoftbus01.sys which is usually either Alcohol120% or daemon tools. 

    Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

    They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

    Use this SPTD uninstaller DuplexSecure

     http://www.duplexsecure.com/downloads

    when you're done you can use this Freeware:

    MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

    http://www.magiciso.com/download.htm

    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff803`3740a000 PsLoadedModuleList = 0xfffff803`376ce990
    Debug session time: Thu Jan 30 11:01:12.011 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.830
    Loading Kernel Symbols
    
    
    BugCheck C9, {23e, fffff80000c17360, ffffcf8006d4aea0, 0}
    
    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+1360 )
    
    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: fffff80000c17360, The address in the driver's code where the error was detected.
    Arg3: ffffcf8006d4aea0, IRP address.
    Arg4: 0000000000000000, Status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
    
    FAULTING_IP: 
    dtsoftbus01+1360
    fffff800`00c17360 4053            push    rbx
    
    FOLLOWUP_IP: 
    dtsoftbus01+1360
    fffff800`00c17360 4053            push    rbx
    
    IRP_ADDRESS: ffffcf8006d4aea0
    
    DEVICE_OBJECT: ffffe000030963d0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LOCK_ADDRESS:  fffff803376d9360 -- (!locks fffff803376d9360)
    
    Resource @ nt!PiEngineLock (0xfffff803376d9360)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0xfffff803376d9360
    	Thread Count  : 0
    	Thread address: 0x0000000000000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from fffff80337a766a8 to fffff80337557ca0
    
    STACK_TEXT:  
    ffffd000`20de6268 fffff803`37a766a8 : 00000000`000000c9 00000000`0000023e fffff800`00c17360 ffffcf80`06d4aea0 : nt!KeBugCheckEx
    ffffd000`20de6270 fffff803`37a79169 : fffff803`37a69470 fffff800`00c17360 ffffcf80`06d4aea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`20de62b0 fffff803`37a6fbca : ffffe000`00e51310 ffffd000`20de6410 ffffe000`00f364d0 00000000`00000000 : nt!ViErrorFinishReport+0x10d
    ffffd000`20de6310 fffff803`37a75bcd : ffffe000`00e53110 00000000`00000000 ffffe000`00e51310 ffffd000`20de6b30 : nt!IovpCallDriver2+0x33e
    ffffd000`20de66e0 fffff803`37a6a928 : ffffcf80`06d4aea0 00000000`00000002 ffffcf80`06d4aea0 ffffd000`20de6920 : nt!VfAfterCallDriver+0x289
    ffffd000`20de6770 fffff800`00207711 : ffffe000`032c8d80 ffffd000`20de6859 ffffe000`031ea7b0 ffffe000`00e51310 : nt!IovCallDriver+0x3e4
    ffffd000`20de67c0 fffff800`00207fe9 : ffffcf80`06d4af00 ffffcf80`06d4af90 00001fff`fcd37200 ffffd000`20de6920 : Wdf01000!FxIoTarget::SubmitSync+0x191
    ffffd000`20de68c0 fffff800`00802432 : ffffe000`00000020 ffffe000`032c8d80 ffffe000`031ea7b0 00000000`00000000 : Wdf01000!imp_WdfRequestSend+0xe9
    ffffd000`20de6920 fffff800`008187a2 : ffffd000`20de6b01 ffffcf80`06d4aea0 ffffe000`0323c350 ffffe000`032c8f20 : cdrom!RequestSend+0xb2
    ffffd000`20de6990 fffff800`00818617 : ffffd000`20de6b30 ffffd000`20de6b69 ffffe000`02fbca50 ffffe000`031e9b01 : cdrom!DeviceSendRequestSynchronously+0x7e
    ffffd000`20de69d0 fffff800`0081cf72 : 00001fff`fce16788 ffffd000`20de6b00 00000000`00000000 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x357
    ffffd000`20de6b00 fffff800`00819ee4 : ffffe000`00000002 ffffe000`031e9b60 00001fff`fce16788 00000000`00000000 : cdrom!DeviceCacheDeviceInquiryData+0xaa
    ffffd000`20de6bd0 fffff800`002328c3 : 00000000`00000000 00000000`00000010 00000000`00000000 fffff800`002a13d0 : cdrom!DeviceEvtSelfManagedIoInit+0x100
    ffffd000`20de6c50 fffff800`00226e49 : 00000000`00000002 00000000`0000000c fffff800`002a3c00 fffff800`002a3c00 : Wdf01000!FxSelfManagedIoMachine::Init+0x33
    ffffd000`20de6c80 fffff800`002161fe : ffffe000`031ea020 00000000`00000000 ffffd000`20de6e20 fffff800`002a3c00 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x111
    ffffd000`20de6cf0 fffff800`00212268 : 00000000`00000312 ffffd000`20de6e20 fffff800`002a3be0 00000000`00000001 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x4f
    ffffd000`20de6d20 fffff800`0021265a : ffffe000`031ea1f8 00000000`00000000 ffffe000`031ea020 fffff800`002a39c0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x138
    ffffd000`20de6e70 fffff800`002123df : 00000000`00000000 ffffd000`20de6f60 ffffe000`031ea220 00000000`00000504 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xc6
    ffffd000`20de6ef0 fffff800`00216062 : 00000000`00000000 ffffe000`031ea020 00000000`00000501 ffffd000`20de7120 : Wdf01000!FxPkgPnp::PowerProcessEvent+0xef
    ffffd000`20de6f90 fffff800`00211c74 : ffffe000`031ea020 ffffd000`20de7030 00000000`00000500 ffffe000`030963d0 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
    ffffd000`20de6fc0 fffff800`00212069 : ffffe000`031ea2d0 00000000`00000000 ffffe000`031ea020 00000000`00000001 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0xf4
    ffffd000`20de7050 fffff800`00211dd8 : 00000000`00000000 ffffd000`20de7140 ffffe000`031ea2f8 fffff800`0020bdc6 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x1df
    ffffd000`20de70d0 fffff800`00218022 : 00000000`00000000 ffffe000`031eae20 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x10c
    ffffd000`20de7170 fffff800`00210942 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff803`37a789e6 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9e
    ffffd000`20de71b0 fffff800`00210a5a : ffffe000`031ea178 00000000`00000002 ffffe000`031ea020 ffffe000`031ea100 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x102
    ffffd000`20de7240 fffff800`00210bc4 : 00000000`00000000 ffffd000`20de7330 ffffe000`031ea150 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0xc2
    ffffd000`20de72c0 fffff800`0021727a : 00000000`00000000 ffffe000`031ea020 00000000`00000000 ffffe000`031ea020 : Wdf01000!FxPkgPnp::PnpProcessEvent+0xe4
    ffffd000`20de7360 fffff800`0020b936 : ffffe000`031ea020 ffffd000`20de73f0 00000000`00000000 ffffe000`02f203d0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
    ffffd000`20de7390 fffff800`00206a18 : ffffcf80`06d82dc0 ffffcf80`06d82dc0 00000000`0000001b ffffe000`031e9870 : Wdf01000!FxPkgPnp::Dispatch+0xd2
    ffffd000`20de7400 fffff803`37a6a911 : ffffe000`00e4e3f0 00000000`00000002 ffffe000`030963d0 fffff803`37a76469 : Wdf01000!FxDevice::DispatchWithLock+0x7d8
    ffffd000`20de74e0 fffff803`3785dca2 : ffffcf80`06d82dc0 ffffe000`0323c390 ffffe000`031eae20 ffffe000`00e4e350 : nt!IovCallDriver+0x3cd
    ffffd000`20de7530 fffff803`374d27f1 : ffffe000`030963d0 ffffd000`20de75d9 00000000`00000000 00000000`00000000 : nt!PnpAsynchronousCall+0x102
    ffffd000`20de7570 fffff803`3785f967 : ffffe000`031e7010 ffffe000`031e7010 ffffe000`0323c390 00000000`6c644d56 : nt!PnpStartDevice+0xc5
    ffffd000`20de7640 fffff803`3785fa7f : ffffe000`031e7010 ffffe000`031e7010 00000000`00000000 00000000`00010286 : nt!PnpStartDeviceNode+0x147
    ffffd000`20de7710 fffff803`3785e4da : ffffe000`031e7010 00000000`00000001 00000000`00000001 ffffe000`000c2d30 : nt!PipProcessStartPhase1+0x53
    ffffd000`20de7750 fffff803`37924113 : ffffe000`0005b1a0 00000000`00000001 00000000`00000000 fffff803`377da542 : nt!PipProcessDevNodeTree+0x3ce
    ffffd000`20de79d0 fffff803`374fc2a0 : 00000001`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PiProcessStartSystemDevices+0x87
    ffffd000`20de7a20 fffff803`374ab1b9 : fffff803`374fbf50 ffffd000`20de7b50 00000000`00000000 ffffcf80`00574fb0 : nt!PnpDeviceActionWorker+0x350
    ffffd000`20de7ad0 fffff803`374972e4 : 00000000`00000000 ffffe000`013e4040 ffffe000`013e4040 ffffe000`000a5900 : nt!ExpWorkerThread+0x2b5
    ffffd000`20de7b80 fffff803`3755e2c6 : ffffd000`20900180 ffffe000`013e4040 ffffd000`2090c2c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20de7be0 00000000`00000000 : ffffd000`20de8000 ffffd000`20de1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  dtsoftbus01+1360
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dtsoftbus01
    
    IMAGE_NAME:  dtsoftbus01.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51c2adcb
    
    FAILURE_BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
    
    BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc9_23e_vrf_dtsoftbus01+1360
    
    FAILURE_ID_HASH:  {aac2c460-fec6-e4d4-73d0-fb24caa4df98}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Friday, January 31, 2014 2:50 AM
    Thursday, January 30, 2014 5:14 PM

All replies

  • This crash was related to memory management (probably caused by a driver). 

    Please run this test to find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.


    Driver verifier (for complete directions see our wiki here)
    Co-Authored by  JMH3143

    Wanikiya and Dyami--Team Zigzag

    Thursday, January 30, 2014 3:29 PM
  • I tried to run verifier as you suggested and follow the instruction but when I reboot my PC after setup the verifier it got BSOD DRIVER_VERIFIER_IOMANAGER_VIOLATION. I'm not overclock my PC thought the BIOS on default setting. I don't know how to fix it it make me depressed
    Thursday, January 30, 2014 4:13 PM
  • Vishera

    That id what it is supposed to do. All you need to do is to upload that DMP file and we can tell you what the underlying problem is.


    Wanikiya and Dyami--Team Zigzag

    Thursday, January 30, 2014 4:19 PM
  • Vishera

    That id what it is supposed to do. All you need to do is to upload that DMP file and we can tell you what the underlying problem is.


    Wanikiya and Dyami--Team Zigzag

    I already upload the minidump on the first post, here the second : http://sdrv.ms/1baivVR . Thank you for the response of my problem :)
    Thursday, January 30, 2014 4:25 PM
  • Vishera

    The verified DMP was related to dtsoftbus01.sys which is usually either Alcohol120% or daemon tools. 

    Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

    They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

    Use this SPTD uninstaller DuplexSecure

     http://www.duplexsecure.com/downloads

    when you're done you can use this Freeware:

    MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

    http://www.magiciso.com/download.htm

    Windows 8 Kernel Version 9600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    Machine Name:
    Kernel base = 0xfffff803`3740a000 PsLoadedModuleList = 0xfffff803`376ce990
    Debug session time: Thu Jan 30 11:01:12.011 2014 (UTC - 5:00)
    System Uptime: 0 days 0:00:09.830
    Loading Kernel Symbols
    
    
    BugCheck C9, {23e, fffff80000c17360, ffffcf8006d4aea0, 0}
    
    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+1360 )
    
    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: fffff80000c17360, The address in the driver's code where the error was detected.
    Arg3: ffffcf8006d4aea0, IRP address.
    Arg4: 0000000000000000, Status code.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xc9_23e
    
    DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
    
    FAULTING_IP: 
    dtsoftbus01+1360
    fffff800`00c17360 4053            push    rbx
    
    FOLLOWUP_IP: 
    dtsoftbus01+1360
    fffff800`00c17360 4053            push    rbx
    
    IRP_ADDRESS: ffffcf8006d4aea0
    
    DEVICE_OBJECT: ffffe000030963d0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LOCK_ADDRESS:  fffff803376d9360 -- (!locks fffff803376d9360)
    
    Resource @ nt!PiEngineLock (0xfffff803376d9360)    Available
    
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    
    
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    
    1 total locks
    
    PNP_TRIAGE: 
    	Lock address  : 0xfffff803376d9360
    	Thread Count  : 0
    	Thread address: 0x0000000000000000
    	Thread wait   : 0x0
    
    LAST_CONTROL_TRANSFER:  from fffff80337a766a8 to fffff80337557ca0
    
    STACK_TEXT:  
    ffffd000`20de6268 fffff803`37a766a8 : 00000000`000000c9 00000000`0000023e fffff800`00c17360 ffffcf80`06d4aea0 : nt!KeBugCheckEx
    ffffd000`20de6270 fffff803`37a79169 : fffff803`37a69470 fffff800`00c17360 ffffcf80`06d4aea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
    ffffd000`20de62b0 fffff803`37a6fbca : ffffe000`00e51310 ffffd000`20de6410 ffffe000`00f364d0 00000000`00000000 : nt!ViErrorFinishReport+0x10d
    ffffd000`20de6310 fffff803`37a75bcd : ffffe000`00e53110 00000000`00000000 ffffe000`00e51310 ffffd000`20de6b30 : nt!IovpCallDriver2+0x33e
    ffffd000`20de66e0 fffff803`37a6a928 : ffffcf80`06d4aea0 00000000`00000002 ffffcf80`06d4aea0 ffffd000`20de6920 : nt!VfAfterCallDriver+0x289
    ffffd000`20de6770 fffff800`00207711 : ffffe000`032c8d80 ffffd000`20de6859 ffffe000`031ea7b0 ffffe000`00e51310 : nt!IovCallDriver+0x3e4
    ffffd000`20de67c0 fffff800`00207fe9 : ffffcf80`06d4af00 ffffcf80`06d4af90 00001fff`fcd37200 ffffd000`20de6920 : Wdf01000!FxIoTarget::SubmitSync+0x191
    ffffd000`20de68c0 fffff800`00802432 : ffffe000`00000020 ffffe000`032c8d80 ffffe000`031ea7b0 00000000`00000000 : Wdf01000!imp_WdfRequestSend+0xe9
    ffffd000`20de6920 fffff800`008187a2 : ffffd000`20de6b01 ffffcf80`06d4aea0 ffffe000`0323c350 ffffe000`032c8f20 : cdrom!RequestSend+0xb2
    ffffd000`20de6990 fffff800`00818617 : ffffd000`20de6b30 ffffd000`20de6b69 ffffe000`02fbca50 ffffe000`031e9b01 : cdrom!DeviceSendRequestSynchronously+0x7e
    ffffd000`20de69d0 fffff800`0081cf72 : 00001fff`fce16788 ffffd000`20de6b00 00000000`00000000 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x357
    ffffd000`20de6b00 fffff800`00819ee4 : ffffe000`00000002 ffffe000`031e9b60 00001fff`fce16788 00000000`00000000 : cdrom!DeviceCacheDeviceInquiryData+0xaa
    ffffd000`20de6bd0 fffff800`002328c3 : 00000000`00000000 00000000`00000010 00000000`00000000 fffff800`002a13d0 : cdrom!DeviceEvtSelfManagedIoInit+0x100
    ffffd000`20de6c50 fffff800`00226e49 : 00000000`00000002 00000000`0000000c fffff800`002a3c00 fffff800`002a3c00 : Wdf01000!FxSelfManagedIoMachine::Init+0x33
    ffffd000`20de6c80 fffff800`002161fe : ffffe000`031ea020 00000000`00000000 ffffd000`20de6e20 fffff800`002a3c00 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x111
    ffffd000`20de6cf0 fffff800`00212268 : 00000000`00000312 ffffd000`20de6e20 fffff800`002a3be0 00000000`00000001 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x4f
    ffffd000`20de6d20 fffff800`0021265a : ffffe000`031ea1f8 00000000`00000000 ffffe000`031ea020 fffff800`002a39c0 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x138
    ffffd000`20de6e70 fffff800`002123df : 00000000`00000000 ffffd000`20de6f60 ffffe000`031ea220 00000000`00000504 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0xc6
    ffffd000`20de6ef0 fffff800`00216062 : 00000000`00000000 ffffe000`031ea020 00000000`00000501 ffffd000`20de7120 : Wdf01000!FxPkgPnp::PowerProcessEvent+0xef
    ffffd000`20de6f90 fffff800`00211c74 : ffffe000`031ea020 ffffd000`20de7030 00000000`00000500 ffffe000`030963d0 : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
    ffffd000`20de6fc0 fffff800`00212069 : ffffe000`031ea2d0 00000000`00000000 ffffe000`031ea020 00000000`00000001 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0xf4
    ffffd000`20de7050 fffff800`00211dd8 : 00000000`00000000 ffffd000`20de7140 ffffe000`031ea2f8 fffff800`0020bdc6 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x1df
    ffffd000`20de70d0 fffff800`00218022 : 00000000`00000000 ffffe000`031eae20 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x10c
    ffffd000`20de7170 fffff800`00210942 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff803`37a789e6 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x9e
    ffffd000`20de71b0 fffff800`00210a5a : ffffe000`031ea178 00000000`00000002 ffffe000`031ea020 ffffe000`031ea100 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x102
    ffffd000`20de7240 fffff800`00210bc4 : 00000000`00000000 ffffd000`20de7330 ffffe000`031ea150 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0xc2
    ffffd000`20de72c0 fffff800`0021727a : 00000000`00000000 ffffe000`031ea020 00000000`00000000 ffffe000`031ea020 : Wdf01000!FxPkgPnp::PnpProcessEvent+0xe4
    ffffd000`20de7360 fffff800`0020b936 : ffffe000`031ea020 ffffd000`20de73f0 00000000`00000000 ffffe000`02f203d0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
    ffffd000`20de7390 fffff800`00206a18 : ffffcf80`06d82dc0 ffffcf80`06d82dc0 00000000`0000001b ffffe000`031e9870 : Wdf01000!FxPkgPnp::Dispatch+0xd2
    ffffd000`20de7400 fffff803`37a6a911 : ffffe000`00e4e3f0 00000000`00000002 ffffe000`030963d0 fffff803`37a76469 : Wdf01000!FxDevice::DispatchWithLock+0x7d8
    ffffd000`20de74e0 fffff803`3785dca2 : ffffcf80`06d82dc0 ffffe000`0323c390 ffffe000`031eae20 ffffe000`00e4e350 : nt!IovCallDriver+0x3cd
    ffffd000`20de7530 fffff803`374d27f1 : ffffe000`030963d0 ffffd000`20de75d9 00000000`00000000 00000000`00000000 : nt!PnpAsynchronousCall+0x102
    ffffd000`20de7570 fffff803`3785f967 : ffffe000`031e7010 ffffe000`031e7010 ffffe000`0323c390 00000000`6c644d56 : nt!PnpStartDevice+0xc5
    ffffd000`20de7640 fffff803`3785fa7f : ffffe000`031e7010 ffffe000`031e7010 00000000`00000000 00000000`00010286 : nt!PnpStartDeviceNode+0x147
    ffffd000`20de7710 fffff803`3785e4da : ffffe000`031e7010 00000000`00000001 00000000`00000001 ffffe000`000c2d30 : nt!PipProcessStartPhase1+0x53
    ffffd000`20de7750 fffff803`37924113 : ffffe000`0005b1a0 00000000`00000001 00000000`00000000 fffff803`377da542 : nt!PipProcessDevNodeTree+0x3ce
    ffffd000`20de79d0 fffff803`374fc2a0 : 00000001`00000003 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PiProcessStartSystemDevices+0x87
    ffffd000`20de7a20 fffff803`374ab1b9 : fffff803`374fbf50 ffffd000`20de7b50 00000000`00000000 ffffcf80`00574fb0 : nt!PnpDeviceActionWorker+0x350
    ffffd000`20de7ad0 fffff803`374972e4 : 00000000`00000000 ffffe000`013e4040 ffffe000`013e4040 ffffe000`000a5900 : nt!ExpWorkerThread+0x2b5
    ffffd000`20de7b80 fffff803`3755e2c6 : ffffd000`20900180 ffffe000`013e4040 ffffd000`2090c2c0 00000000`00000000 : nt!PspSystemThreadStartup+0x58
    ffffd000`20de7be0 00000000`00000000 : ffffd000`20de8000 ffffd000`20de1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    SYMBOL_NAME:  dtsoftbus01+1360
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dtsoftbus01
    
    IMAGE_NAME:  dtsoftbus01.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51c2adcb
    
    FAILURE_BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
    
    BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+1360
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0xc9_23e_vrf_dtsoftbus01+1360
    
    FAILURE_ID_HASH:  {aac2c460-fec6-e4d4-73d0-fb24caa4df98}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Friday, January 31, 2014 2:50 AM
    Thursday, January 30, 2014 5:14 PM
  • So the BSOD caused by Daemon Tools Lite conflicted on Windows 8.1 system. I will remove it . Thank you very much :)
    Friday, January 31, 2014 2:16 AM
  • Vishera

    Glad we could help and thanks for letting us  know.


    Wanikiya and Dyami--Team Zigzag

    Friday, January 31, 2014 2:50 AM