BSODs with Verifier.exe

[7uui8uy7]

BSOD with driver verifier enabled

So I was wondering if I have any other driver problems and enabled driver verifier. Now, I can't even boot windows. Minidump is in attachment.

Let me know.

Thanks!

 

[7uui8uy7]

I pinned down that the problematic driver is dtsoftbus01.sys. I think it's related to Daemon Tools.

 

[7uui8uy7]

Now I got a new one. Dump in attachment.

"The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c4 (0x00000000000000e3, 0xfffffa8007f92531, 0x000000000674f208, 0x0000000000000000). A dump was saved in: C:\Windows\Minidump\102811-14430-01.dmp. Report Id: 102811-14430-01."

 

[7uui8uy7]

Anybody?

 

[7uui8uy7]

Tried WhoCrashed program and it gave me:

[FONT=Segoe UI, Arial]On Fri 28.10.2011 16:49:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-14430-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x7CC40)
Bugcheck code: 0xC4 (0xE3, 0xFFFFFA8007F92531, 0x674F208, 0x0)
Error: [FONT=Segoe UI, Arial]DRIVER_VERIFIER_DETECTED_VIOLATION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver has made a call to a kernel-mode ZwXxx routine with a user-mode address as a parameter. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
[/FONT]
Not much to do with that