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:
- Remove Daemon Tools
- Reboot computer
- Enable Driver Verifier the same way you did it before
- Wait for system to crash few times (it shouldn't be crashing at the boot time now)
- Disable driver verifier
- 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: