New
#11
updated the driver, now it just crashes right away like it did before.
updated the driver, now it just crashes right away like it did before.
Same driver again Driver Reference Table - Tpkd.sys
It's related to a program ilock or interlock pro.
Uninstall that program and see how things go.
Welcome
And this driver, too.
Two drivers to change. GEARAspiWDM.sysGearaspiwdm.sys file descriptionProductname:GEARAspi Description:Filter Driver for 2k and XP Company:GEAR SoftwareCode:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Richard\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\059CV01G\Minidump\081012-40529-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 Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030 Machine Name: Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e48670 Debug session time: Fri Aug 10 15:03:45.190 2012 (GMT-4) System Uptime: 0 days 0:00:47.814 Loading Kernel Symbols ............................................................... ............................................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {23e, fffff88001401324, fffff98003beaee0, 0} Unable to load image \SystemRoot\system32\DRIVERS\GEARAspiWDM.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for GEARAspiWDM.sys *** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.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+1324 ) Followup: MachineOwner --------- 1: 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: fffff88001401324, The address in the driver's code where the error was detected. Arg3: fffff98003beaee0, IRP address. Arg4: 0000000000000000, Status code. Debugging Details: ------------------ BUGCHECK_STR: 0xc9_23e DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23e FAULTING_IP: dtsoftbus01+1324 fffff880`01401324 4053 push rbx FOLLOWUP_IP: dtsoftbus01+1324 fffff880`01401324 4053 push rbx IRP_ADDRESS: fffff98003beaee0 DEVICE_OBJECT: fffffa80095d6460 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800031093dc to fffff80002c831c0 STACK_TEXT: fffff880`031a0738 fffff800`031093dc : 00000000`000000c9 00000000`0000023e fffff880`01401324 fffff980`03beaee0 : nt!KeBugCheckEx fffff880`031a0740 fffff800`0311347a : fffff800`031079f0 fffff880`01401324 fffff980`03beaee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`031a0780 fffff800`0311434e : 00000000`0000023e 00000000`00000000 fffff980`03beaee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`031a07d0 fffff800`0311f71f : fffffa80`09724090 fffffa80`09a5c4a0 fffffa80`09a5c558 fffff880`01405228 : nt!VfErrorReport6+0x6e fffff880`031a08a0 fffff800`0311fb63 : fffffa80`09a5c4a0 00000000`00000002 fffffa80`095d6460 fffff880`014013f4 : nt!IovpCallDriver2+0x13f fffff880`031a0900 fffff800`03125c2e : fffff980`03beaee0 fffff980`03beaee0 00000000`00000002 fffffa80`095d6460 : nt!VfAfterCallDriver+0x353 fffff880`031a0950 fffff880`00d590c2 : fffff880`00dd27c0 fffffa80`09ad7890 00000000`00000025 fffffa80`09a5c4a0 : nt!IovCallDriver+0x57e fffff880`031a09b0 fffff880`00d6e59f : fffffa80`09ae5da0 00000000`00000000 fffff880`00000000 fffff880`015d45d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a fffff880`031a0a60 fffff880`015e8e95 : fffffa80`00000020 fffffa80`09ae5da0 fffffa80`09ad7890 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b fffff880`031a0ab0 fffff880`015e92f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`031a0c70 : cdrom!DeviceSendRequestSynchronously+0xc9 fffff880`031a0b10 fffff880`015e7f04 : 0000057f`f6337fd8 fffff880`031a0c70 fffffa80`09888250 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec fffff880`031a0c40 fffff880`015e6825 : fffffa80`00000002 fffffa80`09cc8390 fffff880`015de3b8 0000057f`f6337fd8 : cdrom!DeviceCacheDeviceInquiryData+0xbc fffff880`031a0d10 fffff880`00dc39d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00dcc620 : cdrom!DeviceEvtSelfManagedIoInit+0x105 fffff880`031a0d50 fffff880`00dc394e : fffffa80`09ad6ad0 00000000`0000000c fffff880`00dcc620 fffff880`00dcc600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34 fffff880`031a0d80 fffff880`00db7b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00dcc620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a fffff880`031a0df0 fffff880`00db76eb : 00000000`00000312 00000000`00000000 fffff880`00dcc600 fffff6fc`c001dfd0 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f fffff880`031a0e20 fffff880`00db738e : fffffa80`09ad6b60 00000000`00000040 fffff880`00dcc3e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db fffff880`031a0f50 fffff880`00db706c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`09ad6b60 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e fffff880`031a0fc0 fffff880`00dc4b5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4 fffff880`031a1050 fffff880`00dc4abb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`031245ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe fffff880`031a1080 fffff880`00dc0950 : fffffa80`09ad6b60 00000000`00000001 00000000`00000000 fffff880`00dc8ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7 fffff880`031a1100 fffff880`00dc0372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`09ccae00 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8 fffff880`031a1170 fffff880`00dbca45 : 00000000`00000000 fffffa80`09ccae00 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2 fffff880`031a1200 fffff880`00dbc841 : 00000000`00000101 00000000`00000108 00000000`00000108 07100001`b4288860 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111 fffff880`031a1240 fffff880`00dbc4fe : fffffa80`09ad6b60 fffff880`031a1370 00000000`00000004 fffff880`00dcb390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5 fffff880`031a12b0 fffff880`00dbc201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`09ad6b60 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122 fffff880`031a1320 fffff880`00db3d9c : 00000000`00000000 fffffa80`09ad6b60 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1 fffff880`031a13b0 fffff880`00db2dd6 : fffffa80`08e777e0 00000000`00000002 00000000`00000000 fffffa80`09ad6b60 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20 fffff880`031a13e0 fffff880`00d82245 : fffff980`03bb4d80 fffff980`03bb4d80 fffffa80`09ad7e20 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2 fffff880`031a1450 fffff880`00d8214b : fffff880`031a1538 fffff980`03bb4d80 00000000`00000002 fffffa80`09ad7e20 : Wdf01000!FxDevice::Dispatch+0xa9 fffff880`031a1480 fffff800`03125c16 : fffff980`03bb4d80 00000000`00000002 fffffa80`09ad7e20 fffff800`0312137e : Wdf01000!FxDevice::DispatchWithLock+0x93 fffff880`031a14c0 fffff800`0312852a : fffff980`03bb4ee0 fffffa80`09ad7e20 fffffa80`09adbe00 fffffa80`09a5eb20 : nt!IovCallDriver+0x566 fffff880`031a1520 fffff800`03125c16 : fffff980`03bb4d80 00000000`00000002 fffffa80`09adbe00 fffffa80`09494760 : nt!ViFilterDispatchPnp+0x13a fffff880`031a1550 fffff880`07218202 : fffffa80`09adbe00 00000000`00000000 fffffa80`09cca190 fffffa80`09494760 : nt!IovCallDriver+0x566 fffff880`031a15b0 fffffa80`09adbe00 : 00000000`00000000 fffffa80`09cca190 fffffa80`09494760 fffff980`03bb4fb8 : GEARAspiWDM+0x7202 fffff880`031a15b8 00000000`00000000 : fffffa80`09cca190 fffffa80`09494760 fffff980`03bb4fb8 fffffa80`09a1d2b8 : 0xfffffa80`09adbe00 STACK_COMMAND: .bugcheck ; kb SYMBOL_NAME: dtsoftbus01+1324 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dtsoftbus01 IMAGE_NAME: dtsoftbus01.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f10358a FAILURE_BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1324 BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1324 Followup: MachineOwner ---------
This is from Daemon (virtulization software). I would remove that software.
Dtsoftbus01.sys file descriptionProductname:DAEMON Tools Lite Description:DAEMON Tools Virtual Bus Driver Company:DT Soft Ltd
Dont forget about TPKD sys as suggested by Derkimo
Productname:InterLok(R) Description:64bit Tpkd Device Driver Company:PACE Anti-Piracy, Inc.
Last edited by richc46; 11 Aug 2012 at 23:42.
Can you update the driver for gear software Driver updates - GEAR Software
Afterwards reenable driver verifier and post back any resulting dumps.
if i enable verifier in safemode then restart, will it still be on? Or do i have to enable verifer in the regular mode and then leave my computer on
heres the new ones, sigh anything there targeting now?
Since Derek is not online, I decided to help. With the both of us I am sure that we will be able to solve your problem.
I started with the last two reports that your submitted. In both cases this was the process that was involved in the BSOD.
mmloaddrv.exe - What is mmloaddrv.exe ?
You may want to update or change, if possible. I tried to download an updated version and I was not able to boot and had to use A Macrium Image to restore.
http://www.tweaktown.com/articles/56...de/index2.html
Ati, is updated. Each BSOD of death seems to give different ones