BSOD...Please Help! Thanks.

Code:
BUGCHECK_STR:  0xc9_23e
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e
FAULTING_IP: 
dtsoftbus01+1360
fffff880`0198e360 4053            push    rbx
FOLLOWUP_IP: 
dtsoftbus01+1360
fffff880`0198e360 4053            push    rbx
IRP_ADDRESS: fffff98005af4ee0
DEVICE_OBJECT: fffffa80062bca30
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:  fffff803d4aeb700 -- (!locks fffff803d4aeb700)
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  dtsoftbus01+1360
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dtsoftbus01
IMAGE_NAME:  [B]dtsoftbus01.sys[/B]
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}

It identifies dtsoftbus01.sys driver (it belongs to Daemon Tools application) as the possible cause of the crash.

Unfortunately, as per this page, this is a know issue, which doesn't really mean it's causing all other BSODs. Anyhow, due Daemon Tools being well known for causing crashes as well as this particular issue with Driver Verifier, interrupting with our troubleshooting, I would suggest you to do the following:

  1. Remove Daemon Tools
  2. Reboot computer
  3. Enable Driver Verifier the same way you did it before
  4. Wait for system to crash few times (it shouldn't be crashing at the boot time now)
  5. Disable driver verifier
  6. Attach new files from C:\Windows\Minidump

In addition, I was just curious, what were you using Daemon Tools for? Windows 8 already has built in ISO mounting support, which means you can mount an image just by double-clicking on it. In case the reason is you need to mount other image formats, not ISO only, I would suggest you using Virtual Clone Drive.

Hi,

I thought I'd seen the last of that Daemon Tools driver, but it seems not! It is a known BSOD cause in Windows 7, and 8 as it seems. When removing Daemon Tools, it's a good idea to use the official removal tool.

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

It was such a common cause when I was doing regular debugging, that I actually checked for the program in the installed program list before I even looked at the dump files.

Stephen
 
Last edited:
122913-77891-01.DMP still shows the Daemon Tools driver:

Code:
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1360 )

If you removed Daemon Tools and we are still seeing the driver, probably the uninstaller left it. Could you please do the following:

  1. Download Autoruns
  2. Extract the files and launch autoruns.exe
  3. Once launched, click File -> Run as Administrator
  4. Navigate to Drivers tab
  5. Find and uncheck dtsoftbus01.sys
  6. Reboot the computer
 
Thanks.

As per our latest discussions, you had to enabled Driver Verifier (following these steps), anyhow, I still do not see it enabled in the dumps:

Code:
Verify Flags Level 0x00000000

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks
    [ ] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [ ] (0x00008000) Power framework delay fuzzing

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x0
  Synch Executions     0x0
  Trims                0x0

  Pool Allocations Attempted             0x0
  Pool Allocations Succeeded             0x0
  Pool Allocations Succeeded SpecialPool 0x0
  Pool Allocations With NO TAG           0x0
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x0 for 00000000 bytes
  Peak paged pool allocations            0x0 for 00000000 bytes
  Current nonpaged pool allocations      0x0 for 00000000 bytes
  Peak nonpaged pool allocations         0x0 for 00000000 bytes

Not having it enabled makes finding the cause more difficult.

Anyhow, it looks all the crashes have atikmpag.sys driver on the call stack. Could you please download and install the latest driver (12/18/2013) for your AMD Radeon HD 7520G GPU?
 
Thanks.

As per our latest discussions, you had to enabled Driver Verifier (following these steps), anyhow, I still do not see it enabled in the dumps:

Code:
Verify Flags Level 0x00000000

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [ ] (0x00000001) Special pool
    [ ] (0x00000002) Force IRQL checking
    [ ] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [ ] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [ ] (0x00000100) Security checks
    [ ] (0x00000800) Miscellaneous checks
    [ ] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [ ] (0x00008000) Power framework delay fuzzing

    [X] Indicates flag is enabled


Summary of All Verifier Statistics

  RaiseIrqls           0x0
  AcquireSpinLocks     0x0
  Synch Executions     0x0
  Trims                0x0

  Pool Allocations Attempted             0x0
  Pool Allocations Succeeded             0x0
  Pool Allocations Succeeded SpecialPool 0x0
  Pool Allocations With NO TAG           0x0
  Pool Allocations Failed                0x0

  Current paged pool allocations         0x0 for 00000000 bytes
  Peak paged pool allocations            0x0 for 00000000 bytes
  Current nonpaged pool allocations      0x0 for 00000000 bytes
  Peak nonpaged pool allocations         0x0 for 00000000 bytes

Not having it enabled makes finding the cause more difficult.

Anyhow, it looks all the crashes have atikmpag.sys driver on the call stack. Could you please download and install the latest driver (12/18/2013) for your AMD Radeon HD 7520G GPU?
 
I had enabled Driver Verifier (following the steps) and rebooted on safe mode and it was a success ;) . Now i'm waiting for a crash and i'll post it. Thks
 
I had enabled Driver Verifier (following the steps) and rebooted on safe mode and it was a success ;) . Now i'm waiting for a crash and i'll post it. Thks

Just to be sure, you need to boot to normal mode and wait for BSOD after enabling Driver Verifier. Driver Verifier is not active in Safe Mode.
 
OK, Driver Verifier is active in these crashes:

Code:
Verify Flags Level 0x000209bb

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [X] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [X] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

The bad thing is all these crashes are pointing to different Microsoft components (e.g TCPIP.SYS, CLASSPNP.SYS). Could you try running MemTest to see if there are issues with your RAM module(s)?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top