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: BSOD after i log into Win 7

12 Mar 2012   #1

Windows 7 Ultimate x64
BSOD after i log into Win 7

It all started when the computer was starting up, it then asked for permission to check the hard drive. After that was done i haven't been able to log into Windows without the BSOD comes. It works fine in safe mode.

It can stand with the logon for hours but when i log on the BSOD pops up.

I have uploaded som dump files, i hope someone can help me :)

I got an Acer Aspire 5930G laptop
Cpu: Intel P7350
Memory: 4GB Kingston DDR2 PC5300
HDD: 1 WD 500GB and 1 Corsair 120GB Sand Force F120

My System SpecsSystem Spec
12 Mar 2012   #2

Win 8 Release candidate 8400

These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, 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/Win7 Startup Repair feature).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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
16 Mar 2012   #3

Windows 7 Ultimate x64

Thanks for the fast response :) I did run the verifier test, and hope it gives some answers. I hope i uploaded the right file, because i don't know where the verifier test file i located.
My System SpecsSystem Spec

18 Mar 2012   #4

Windows 7 Home Premium 64 Bit

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Kingston\BSODDmpFiles\sirivar\031612-6661-01\031612-6661-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c19000 PsLoadedModuleList = 0xfffff800`02e5e670
Debug session time: Fri Mar 16 13:36:15.713 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:15.428
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800162c300, fffffa80069e33e0, 0}

*** 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+1300 )

Followup: MachineOwner

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

The IO manager has caught a misbehaving driver.
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800162c300, The address in the driver's code where the error was detected.
Arg3: fffffa80069e33e0, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:

BUGCHECK_STR:  0xc9_23e


fffff880`0162c300 4053            push    rbx

fffff880`0162c300 4053            push    rbx

IRP_ADDRESS:  fffffa80069e33e0

DEVICE_OBJECT: fffffa8005edba30





LOCK_ADDRESS:  fffff80002e94b80 -- (!locks fffff80002e94b80)

Resource @ nt!PiEngineLock (0xfffff80002e94b80)    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

	Lock address  : 0xfffff80002e94b80
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000311f3dc to fffff80002c95c40

fffff880`031ee9a8 fffff800`0311f3dc : 00000000`000000c9 00000000`0000023e fffff880`0162c300 fffffa80`069e33e0 : nt!KeBugCheckEx
fffff880`031ee9b0 fffff800`0312947a : fffff800`0311d9f0 fffff880`0162c300 fffffa80`069e33e0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031ee9f0 fffff800`0312a34e : 00000000`0000023e 00000000`00000000 fffffa80`069e33e0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031eea40 fffff800`0313571f : fffffa80`069bd150 fffffa80`05f3b3d0 fffffa80`05f3b488 fffff880`0163007c : nt!VfErrorReport6+0x6e
fffff880`031eeb10 fffff800`03135b63 : fffffa80`05f3b3d0 00000000`00000002 fffffa80`05edba30 fffff880`0162c3d0 : nt!IovpCallDriver2+0x13f
fffff880`031eeb70 fffff800`0313bc2e : fffffa80`069e33e0 fffffa80`069e33e0 00000000`00000002 fffffa80`05edba30 : nt!VfAfterCallDriver+0x353
fffff880`031eebc0 fffff880`00f240c2 : fffff880`00f9d7c0 fffffa80`06963c60 00000000`00000025 fffffa80`05f3b3d0 : nt!IovCallDriver+0x57e
fffff880`031eec20 fffff880`00f3959f : fffffa80`069e3520 00000000`00000000 fffff880`00000000 fffff880`071d75d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`031eecd0 fffff880`071ebe95 : fffffa80`00000020 fffffa80`069e3520 fffffa80`06963c60 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`031eed20 fffff880`071ec2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`031eeee0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`031eed80 fffff880`071eaf04 : 0000057f`f969fcf8 fffff880`031eeee0 fffffa80`069d96b0 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`031eeeb0 fffff880`071e9825 : fffffa80`00000002 fffffa80`06960670 fffff880`071e13b8 0000057f`f969fcf8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`031eef80 fffff880`00f8e9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00f97620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`031eefc0 fffff880`00f8e94e : fffffa80`069600b0 00000000`0000000c fffff880`00f97620 fffff880`00f97600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`031eeff0 fffff880`00f82b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f97620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`031ef060 fffff880`00f826eb : 00000000`00000312 00000000`00000000 fffff880`00f97600 fffff800`02cc1830 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`031ef090 fffff880`00f8238e : fffffa80`057a39d0 00000000`00000040 fffff880`00f973e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`031ef1c0 fffff880`00f8206c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`057a39d0 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`031ef230 fffff880`00f8fb5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`031ef2c0 fffff880`00f8fabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0313a5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`031ef2f0 fffff880`00f8b950 : fffffa80`057a39d0 00000000`00000001 00000000`00000000 fffff880`00f93ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`031ef370 fffff880`00f8b372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`057a33c0 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`031ef3e0 fffff880`00f87a45 : 00000000`00000000 fffffa80`057a33c0 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`031ef470 fffff880`00f87841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`02c9bfda : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`031ef4b0 fffff880`00f874fe : fffffa80`057a39d0 fffff880`031ef5e0 00000000`00000004 fffff880`00f96390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`031ef520 fffff880`00f87201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`057a39d0 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`031ef590 fffff880`00f7ed9c : 00000000`00000000 fffffa80`057a39d0 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`031ef620 fffff880`00f7ddd6 : fffffa80`0695d890 00000000`00000002 00000000`00000000 fffffa80`057a39d0 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`031ef650 fffff880`00f4d245 : fffffa80`069dd760 fffffa80`069dd760 fffffa80`057a33c0 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`031ef6c0 fffff880`00f4d14b : fffff880`031ef7a8 fffffa80`069dd760 00000000`00000002 fffffa80`057a33c0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`031ef6f0 fffff800`0313bc16 : fffffa80`069dd760 00000000`00000002 fffffa80`057a33c0 fffffa80`057a33c0 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`031ef730 fffff800`0304ed6e : fffffa80`069dd760 fffffa80`069d9830 fffffa80`057a33c0 fffffa80`05be9010 : nt!IovCallDriver+0x566
fffff880`031ef790 fffff800`02d8687d : fffffa80`05edba30 fffffa80`069d9830 fffff800`02d8ffa0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031ef7d0 fffff800`0305e0b6 : fffff800`02e94940 fffffa80`0695dd90 fffffa80`069d9830 fffffa80`0695df38 : nt!PnpStartDevice+0x11d
fffff880`031ef890 fffff800`0305e354 : fffffa80`0695dd90 fffffa80`03d2002a fffffa80`03d21b80 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`031ef920 fffff800`03081a86 : fffffa80`0695dd90 fffffa80`03d21b80 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`031ef950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296

STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1300

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys


FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1300

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1300

Followup: MachineOwner
Verifier enabled crash. Points to Daemon Tools.

Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.

I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
My System SpecsSystem Spec
18 Mar 2012   #5

Windows 7 Ultimate x64

Thank you very much for the help :) My computer is running smooth again now:)
My System SpecsSystem Spec
18 Mar 2012   #6

Windows 7 Home Premium 64 Bit

Glad to see that. :)

Did you disable Verifier? Start Menu -> All Programs -> Accessories -> Right click Command Prompt ->
verifier /reset
-> Restart your computer.
My System SpecsSystem Spec

 BSOD after i log into Win 7

Thread Tools

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 08:06.
Twitter Facebook Google+