Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD's + Driver verifier startup crash

31 May 2011   #1

Windows 7 Ultimate x64
 
 
Random BSOD's + Driver verifier startup crash

Hello,

I have recently build build my own pc. This pc has never worked stable, i've been experiencing random bsod's. Sometimes they come 20 in a row and the system is stable for only a few minutes. Sometimes, usually when I tweaked a little with the system, like increased the voltage over the ram modules or removed a network card which I didn't use, reinstall windows, the system would be stable for days before the bsod's came in big numbers again.

Today I used the driver verifier to see if the problem was driver related. When my computer would start up with driver verifier enabled, the system would crash before it could startup windows. It did however generate a minidump file containing information about the crash. The last 5 minidumps that are attached are caused by the driver varifier startup crash, the other files are due to random crashes over the past month.

My system specs:
Windows 7 Ultimate x64, Full Retail
Processor: AMD Phenom II X6 1055T Processor 2.80 GHz
Memory: 2x 2GB DDR3-1333G
Video Card: Asus Eah-5670, 512 MB
Motherboard: MSI 870A-G54 - Socket AM3 - ATX

I hope dat I have provided you with enough information. Any help on this matter would be greatly appreciated!


My System SpecsSystem Spec
.

31 May 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jim Tol View Post
Hello,

I have recently build build my own pc. This pc has never worked stable, i've been experiencing random bsod's. Sometimes they come 20 in a row and the system is stable for only a few minutes. Sometimes, usually when I tweaked a little with the system, like increased the voltage over the ram modules or removed a network card which I didn't use, reinstall windows, the system would be stable for days before the bsod's came in big numbers again.

Today I used the driver verifier to see if the problem was driver related. When my computer would start up with driver verifier enabled, the system would crash before it could startup windows. It did however generate a minidump file containing information about the crash. The last 5 minidumps that are attached are caused by the driver varifier startup crash, the other files are due to random crashes over the past month.

My system specs:
Windows 7 Ultimate x64, Full Retail
Processor: AMD Phenom II X6 1055T Processor 2.80 GHz
Memory: 2x 2GB DDR3-1333G
Video Card: Asus Eah-5670, 512 MB
Motherboard: MSI 870A-G54 - Socket AM3 - ATX

I hope dat I have provided you with enough information. Any help on this matter would be greatly appreciated!
virtually all were identical and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd. I would remove it to test.


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\053111-24850-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032a3e50
Debug session time: Tue May 31 10:35:50.580 2011 (GMT-4)
System Uptime: 0 days 0:00:19.876
Loading Kernel Symbols
...............................................................
......................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88002a2d308, fffff9800e57eea0, 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+1308 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffff88002a2d308, The address in the driver's code where the error was detected.
Arg3: fffff9800e57eea0, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1308
fffff880`02a2d308 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1308
fffff880`02a2d308 4053            push    rbx

IRP_ADDRESS:  fffff9800e57eea0

DEVICE_OBJECT: fffffa800471bd50

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800035613dc to fffff800030d6740

STACK_TEXT:  
fffff880`02f4e888 fffff800`035613dc : 00000000`000000c9 00000000`0000023e fffff880`02a2d308 fffff980`0e57eea0 : nt!KeBugCheckEx
fffff880`02f4e890 fffff800`0356b47a : fffff800`0355f9f0 fffff880`02a2d308 fffff980`0e57eea0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`02f4e8d0 fffff800`0356c34e : 00000000`0000023e 00000000`00000000 fffff980`0e57eea0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`02f4e920 fffff800`0357771f : fffff980`0e412fe0 fffffa80`041fe2f0 fffffa80`041fe3a8 fffff880`02a30dbc : nt!VfErrorReport6+0x6e
fffff880`02f4e9f0 fffff800`03577b63 : fffffa80`041fe2f0 00000000`00000002 fffffa80`0471bd50 fffff880`02a2d3d8 : nt!IovpCallDriver2+0x13f
fffff880`02f4ea50 fffff800`0357dc2e : fffff980`0e57eea0 fffff980`0e57eea0 00000000`00000002 fffffa80`0471bd50 : nt!VfAfterCallDriver+0x353
fffff880`02f4eaa0 fffff800`0357cc42 : fffff980`0e57ef70 00000000`00000002 fffffa80`0477ef50 fffffa80`041fe2f0 : nt!IovCallDriver+0x57e
fffff880`02f4eb00 fffff800`0357dc16 : fffff980`0e57eea0 00000000`00000002 fffffa80`0477ee00 fffff880`00ef1e5b : nt!ViFilterDispatchPower+0x62
fffff880`02f4eb30 fffff880`00ef20c2 : fffff880`00f6b7c0 fffff980`0de18df0 00000000`00000025 fffffa80`04637500 : nt!IovCallDriver+0x566
fffff880`02f4eb90 fffff880`00f0759f : fffff980`0e50eda0 00000000`00000000 fffff880`00000000 fffff880`040fc5d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`02f4ec40 fffff880`04110e95 : fffff980`00000020 fffff980`0e50eda0 fffff980`0de18df0 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`02f4ec90 fffff880`041112f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`02f4ee50 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`02f4ecf0 fffff880`0410ff04 : 0000067f`f22097e8 fffff880`02f4ee50 fffff980`0e582fd0 fffff880`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`02f4ee20 fffff880`0410e825 : fffff980`00000002 fffff980`0ddf6b80 fffff880`041063b8 0000067f`f22097e8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`02f4eef0 fffff880`00f5c9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00f65620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`02f4ef30 fffff880`00f5c94e : fffff980`0dc9af90 00000000`0000000c fffff880`00f65620 fffff980`0dd12e90 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`02f4ef60 fffff880`00f50b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f65620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`02f4efd0 fffff880`00f506eb : 00000000`00000312 00000000`00000000 fffff880`00f65600 00000000`00000008 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`02f4f000 fffff880`00f5038e : fffff980`0dd14b60 00000000`00000040 fffff880`00f653e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`02f4f130 fffff880`00f5006c : 00000000`00000000 00000000`00000040 00000000`00000501 fffff980`0dd14b60 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`02f4f1a0 fffff880`00f5db5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`02f4f230 fffff880`00f5dabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`03199c3b : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`02f4f260 fffff880`00f59950 : fffff980`0dd14b60 00000000`00000001 00000000`00000000 fffff880`00f61ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`02f4f2e0 fffff880`00f59372 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`02f4f350 fffff880`00f55a45 : 00000000`00000000 fffffa80`0477e980 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`02f4f3e0 fffff880`00f55841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffffa80`01840228 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`02f4f420 fffff880`00f554fe : fffff980`0dd14b60 fffff880`02f4f550 00000000`00000004 fffff880`00f64390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`02f4f490 fffff880`00f55201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffff980`0dd14b60 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`02f4f500 fffff880`00f4cd9c : 00000000`00000000 fffff980`0dd14b60 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`02f4f590 fffff880`00f4bdd6 : fffff980`02d8ee70 00000000`00000002 00000000`00000000 fffff980`0dd14b60 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`02f4f5c0 fffff880`00f1b245 : fffff980`0e5ecdc0 fffff980`0e5ecdc0 fffffa80`0477ebe0 fffffa80`00000001 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`02f4f630 fffff880`00f1b14b : fffff980`0e5ecdc0 00000000`00000002 fffffa80`0477ebe0 fffffa80`04640b10 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02f4f660 fffff800`0357dc16 : fffff980`0e5ecdc0 00000000`00000002 fffffa80`0477ebe0 fffff800`0357937e : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`02f4f6a0 fffff800`0358052a : fffff980`0e5ecf68 fffffa80`0477ebe0 fffffa80`0477e980 fffffa80`04640b10 : nt!IovCallDriver+0x566
fffff880`02f4f700 fffff800`0357dc16 : fffff980`0e5ecdc0 00000000`00000002 fffffa80`0477e980 fffffa80`0350b840 : nt!ViFilterDispatchPnp+0x13a
fffff880`02f4f730 fffff800`034958fe : fffff980`0e5ecdc0 fffffa80`04315820 fffffa80`0477e980 fffffa80`0350b840 : nt!IovCallDriver+0x566
fffff880`02f4f790 fffff800`031d00ed : fffffa80`0471bd50 fffffa80`04315820 fffff800`031d5d50 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`02f4f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PnpStartDevice+0x11d


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1308

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2eb75c

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1308

Followup: MachineOwner
---------
My System SpecsSystem Spec
01 Jun 2011   #3

Windows 7 Ultimate x64
 
 

Thank you for your reply. I have removed daemon tools and also used the software located here: DuplexSecure - FAQ to remove the SPTD driver which daemon tools uses.

Right after I removed these however, the BSOD's came again in big numbers. In the last 10 minutes I had 5 BSOD's and the system acting weird overall, I couldnt start programs due to .dll errors for example. A few minidump files were created, I have attached these to this post.

Later today, when the system is more stable, I will try to run the driver verifier again to see if the early bsod's caused by daemon tools are gone.

Thanks in advance.
My System SpecsSystem Spec
.


01 Jun 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jim Tol View Post
Thank you for your reply. I have removed daemon tools and also used the software located here: DuplexSecure - FAQ to remove the SPTD driver which daemon tools uses.

Right after I removed these however, the BSOD's came again in big numbers. In the last 10 minutes I had 5 BSOD's and the system acting weird overall, I couldnt start programs due to .dll errors for example. A few minidump files were created, I have attached these to this post.

Later today, when the system is more stable, I will try to run the driver verifier again to see if the early bsod's caused by daemon tools are gone.

Thanks in advance.
The most recent crashes seem to be caused by memory corruption so memtest would also be a good idea. Just to be cautious I would also suggest you download malwarebytes and run it in safe mode .


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



Driver verifier

Quote:
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
My System SpecsSystem Spec
03 Jun 2011   #5

Windows 7 Ultimate x64
 
 

I have just tested using memtest, and my memory seemed fine. I have let it pass for over 8 passes on each ram-socket and no problems were detected. I'm going to run malwarebytes now, ill report back with the results when it is done running.

Thanks for the help!
My System SpecsSystem Spec
03 Jun 2011   #6

Windows 7 Ultimate x64
 
 

I just completed a full system scan but I don't think malware was the problem. Malwarebytes displayed a text file containing the following information:



Malwarebytes' Anti-Malware 1.51.0.1200
Malwarebytes : Free anti-malware, anti-virus and spyware removal download

Database version: 6763

Windows 6.1.7600 (Safe Mode)
Internet Explorer 8.0.7600.16385

6/3/2011 8:16:25 PM
mbam-log-2011-06-03 (20-16-25).txt

Scan type: Full scan (C:\|)
Objects scanned: 717308
Time elapsed: 1 hour(s), 5 minute(s), 29 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 1

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
c:\audioconverter\audioconverter.exe (Backdoor.Agent) -> Quarantined and deleted successfully.


Are there any more tests I could run? Thanks in advance.
My System SpecsSystem Spec
04 Jun 2011   #7

Win 8 Release candidate 8400
 
 

Obviously was a malware issue and may now just be hardware

Files Infected:
c:\audioconverter\audioconverter.exe (Backdoor.Agent) -> Quarantined and deleted successfully.

Are you still having the same problem?
My System SpecsSystem Spec
04 Jun 2011   #8

Windows 7 Ultimate x64
 
 

Unfortunately yes, I experienced several bsod's on startup today again (without driver verifier on).

I tried to run driver verifier again to see if the system could point out any other corrupt drivers but with driver verifier on, my computer crashes without a bsod.

I have attached a zip file containing the dump files of the bsod's I have experienced in the past days, after I removed daemon tools (the cause of the early crash using driver verifier). Thank you for helping me!
My System SpecsSystem Spec
09 Jun 2011   #9

Windows 7 Ultimate x64
 
 

I have experienced more bsod's the past days. Maybe they can shed more light tot this problem. I have included the file to this post. Any help on this matter is greatly appreciated!

Please note that my system was not stable enough to perform the BSOD analysis software, therefore I copied the minidump files to another computer and I ran the program there. Therefore, the information about the specifications of the system are not correct. I hope this does not interfere with any other information the program gives.

Thanks in advance.
My System SpecsSystem Spec
09 Jun 2011   #10

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Jim Tol View Post
Unfortunately yes, I experienced several bsod's on startup today again (without driver verifier on).

I tried to run driver verifier again to see if the system could point out any other corrupt drivers but with driver verifier on, my computer crashes without a bsod.

I have attached a zip file containing the dump files of the bsod's I have experienced in the past days, after I removed daemon tools (the cause of the early crash using driver verifier). Thank you for helping me!

None of these are driver verified on. In fact no even mention verifier. Did you follow the instructions carefully?

When you think it is on can you go to start>cmd>type verifier /query and it should tell you what drivers it is verifying. If it does not its off.

The newest blames memory corruption but doesnt say which driver is doing it. for that we need verifier.
My System SpecsSystem Spec
Reply

 Random BSOD's + Driver verifier startup crash




Thread Tools



Similar help and support threads for2: Random BSOD's + Driver verifier startup crash
Thread Forum
Random Crash, Freeze, Black Screen or BSOD shortly after startup. BSOD Help and Support
BSOD random, looks like driver crash, Inpage data error BSOD Help and Support
BSOD on startup with verifier active, computer also restarts itself BSOD Help and Support
BSOD after driver verifier BSOD Help and Support
Driver verifier crash BSOD Help and Support
BSOD BAD_POOL_CALLER at Startup after using Verifier.exe BSOD Help and Support
BSOD BAD_POOL_CALLER at Startup after using Verifier.exe BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 02:20 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33