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 "Starting windows" screen....


21 Aug 2011   #1
NRT

Windows 7 Ultimate 64-bit SP1
 
 
BSOD after "Starting windows" screen....

BSOD after "Starting windows" screen.... report is attached.... any help wud be appreciated...

My System SpecsSystem Spec
.

21 Aug 2011   #2
NRT

Windows 7 Ultimate 64-bit SP1
 
 

any help...???
My System SpecsSystem Spec
21 Aug 2011   #3

Windows 8.1 Pro x64
 
 

Boot into safemode and

Please REMOVE Deamon Tools or any similar software, it was the cause of your BSODs
Code:
dtsoftbus01.sys    dtsoftbus01.sys+126c    0x8c814000    0x8c84f000    0x0003b000    0x4d2eb753    13/01/2011 12:26:59
Turn OFF Driver Verifier
Driver Verifier - Enable and Disable
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, 8c81526c, 97f92f68, 0}

Unable to load image \SystemRoot\system32\DRIVERS\cdrom.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
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+126c )


DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: 8c81526c, The address in the driver's code where the error was detected.
Arg3: 97f92f68, IRP address.
Arg4: 00000000, Status code.

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


BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+126c
8c81526c 55              push    ebp

FOLLOWUP_IP: 
dtsoftbus01+126c
8c81526c 55              push    ebp

IRP_ADDRESS:  97f92f68

DEVICE_OBJECT: 8cb34030

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  82db0f60 -- (!locks 82db0f60)

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

PNP_TRIAGE: 
    Lock address  : 0x82db0f60
    Thread Count  : 0
    Thread address: 0x00000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 82f7ff03 to 82d27dd0

STACK_TEXT:  
877183f4 82f7ff03 000000c9 0000023e 8c81526c nt!KeBugCheckEx+0x1e
87718414 82f822cd 8c81526c 8771844c 8c81526c nt!VerifierBugCheckIfAppropriate+0x30
8771842c 82f82414 0000023e 8c81526c 00000000 nt!ViErrorFinishReport+0xc9
8771849c 82f80620 0000023e 97f92f68 00000000 nt!VfErrorReport6+0x51
877184cc 82f7fe5f 95bc673c 95bc66d8 00000000 nt!IovpCallDriver2+0x155
877184e0 82f7a6d4 95bc673c 00000000 97c45878 nt!VfAfterCallDriver+0x119
87718504 82c87463 00000000 95bf4478 8cb34030 nt!IovCallDriver+0x269
87718518 84e1349c 683ba780 877185a4 00000000 nt!IofCallDriver+0x1b
8771855c 84e1effe 00bf4478 877185a4 87718588 Wdf01000!FxIoTarget::SubmitSync+0x198
87718580 8500f198 00000020 95bf4478 97c45878 Wdf01000!imp_WdfRequestSend+0x178
WARNING: Stack unwind information not available. Following frames may be wrong.
877185b4 8500fbe1 683ba500 95bf4550 00000001 cdrom+0xf198
8771865c 85011a66 683ba500 00718698 97c9bed8 cdrom+0xfbe1
877186dc 8501383c 97c45cc0 97c45af8 8cb5fd10 cdrom+0x11a66
877186f8 84e5c126 683ba500 87718728 84e5c0e2 cdrom+0x1383c
87718704 84e5c0e2 8cb5fd10 87718724 84e652d0 Wdf01000!FxSelfManagedIoMachine::Init+0x1b
87718728 84e53c6b 8a709770 95bab420 877187c0 Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0xce
87718738 84e52d81 95bab420 95bab52c 95bab420 Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x22
877187c0 84e53bb2 00000316 95bab52c 95bab420 Wdf01000!FxPkgPnp::PowerEnterNewState+0x11c
877187e4 84e545bb 877187fc 00000008 95bab420 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x171
87718808 84e5d6e5 00000000 8771883c 84e5d67c Wdf01000!FxPkgPnp::PowerProcessEvent+0x15c
87718814 84e5d67c 95bab420 95bab59c 95bab420 Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xf
8771883c 84e5a7f5 00000501 95bab59c 95bab420 Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x105
87718860 84e5b388 00000001 00000008 95bab420 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x264
87718884 84e585a8 00000000 00000000 00000008 Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x172
877188a0 84e57484 95bab420 95bab4c8 95bab420 Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x90
877188c8 84e57db2 00000108 95bab4c8 95bab420 Wdf01000!FxPkgPnp::PnpEnterNewState+0x104
877188ec 84e5847a 87718904 8a709770 95bab420 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x149
87718910 84e5140b 00000002 00000000 87718940 Wdf01000!FxPkgPnp::PnpProcessEvent+0x13e
87718920 84e50e02 95bab420 87718948 97fecf20 Wdf01000!FxPkgPnp::_PnpStartDevice+0x1e
87718940 84e2da3f 97fecf20 87718968 84e2dc63 Wdf01000!FxPkgPnp::Dispatch+0x207
8771894c 84e2dc63 97c459d8 97fecf20 8cbeb3b0 Wdf01000!FxDevice::Dispatch+0x7f
87718968 82f7a6c3 97c459d8 97fecf20 97fecffc Wdf01000!FxDevice::DispatchWithLock+0x7b
8771898c 82c87463 00000000 87718a10 97c459d8 nt!IovCallDriver+0x258
877189a0 82df3d60 00000000 8cb34030 95bf2410 nt!IofCallDriver+0x1b
877189bc 82c5f499 877189ec 82c5eb88 95bf2410 nt!PnpAsynchronousCall+0x92
87718a20 82df9bdc 82c5eb88 95bf2410 8cb27bc8 nt!PnpStartDevice+0xe1
87718a7c 82df9aa5 95bf2410 0000002a 00000000 nt!PnpStartDeviceNode+0x12c
87718a98 82df28a1 00000000 00000001 00000000 nt!PipProcessStartPhase1+0x62
87718c94 82dd6a2a 84de1578 8a747798 87718cc8 nt!PipProcessDevNodeTree+0x188
87718cd4 82c5efbd 8a747798 82daee80 84dd7020 nt!PiProcessStartSystemDevices+0x6d
87718d00 82cb900b 00000000 00000000 84dd7020 nt!PnpDeviceActionWorker+0x241
87718d50 82e5966d 00000001 a206afe4 00000000 nt!ExpWorkerThread+0x10d
87718d90 82d0b189 82cb8efe 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+126c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d2eb753

FAILURE_BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+126c

BUCKET_ID:  0xc9_23e_VRF_dtsoftbus01+126c

Followup: MachineOwner
---------
My System SpecsSystem Spec
.


21 Aug 2011   #4
NRT

Windows 7 Ultimate 64-bit SP1
 
 

Yowan,

Thank u for the input....
My System SpecsSystem Spec
Reply

 BSOD after "Starting windows" screen....




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 02:48 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