07-23-2014 01:32 AM - last edited on 03-05-2024 10:00 PM by ROGBot
*************************************************************************
Unable to load image \SystemRoot\system32\drivers\Wdf01000.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
FAULTING_MODULE: fffff802ee27a000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5215f850
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffffff850fca00
CURRENT_IRQL: 0
FAULTING_IP:
Wdf01000+7db9
fffff801`4d526db9 8b8affc90f85 mov ecx,dword ptr [rdx-7AF03601h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff802ee3d9ae9 to fffff802ee3cdfa0
STACK_TEXT:
ffffd000`24864248 fffff802`ee3d9ae9 : 00000000`0000000a ffffffff`850fca00 00000000`00000002 00000000`00000000 : nt+0x153fa0
ffffd000`24864250 00000000`0000000a : ffffffff`850fca00 00000000`00000002 00000000`00000000 fffff801`4d526db9 : nt+0x15fae9
ffffd000`24864258 ffffffff`850fca00 : 00000000`00000002 00000000`00000000 fffff801`4d526db9 ffffe000`dc7c01a0 : 0xa
ffffd000`24864260 00000000`00000002 : 00000000`00000000 fffff801`4d526db9 ffffe000`dc7c01a0 00000000`00000000 : 0xffffffff`850fca00
ffffd000`24864268 00000000`00000000 : fffff801`4d526db9 ffffe000`dc7c01a0 00000000`00000000 00000000`00000000 : 0x2
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
Wdf01000+7db9
fffff801`4d526db9 8b8affc90f85 mov ecx,dword ptr [rdx-7AF03601h]
SYMBOL_NAME: Wdf01000+7db9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Wdf01000
IMAGE_NAME: Wdf01000.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
---------
07-23-2014 11:44 AM
redduc900 wrote:
Open Windows Update and check to see if there's an update available for .NET Framework, or any updates available for that matter.
KoolASUS wrote:
IRQL_NOT_LESS_OR_EQUAL BSOD's can often mean hardware failure ! 😞
07-23-2014 12:11 PM
07-23-2014 02:22 PM
07-23-2014 05:12 PM
11-06-2014 06:07 AM