Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002da5b2a, 0, 4e}
Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80002d5ef9a, 0, 4e}
Unable to load image \SystemRoot\system32\DRIVERS\AppleCharger.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AppleCharger.sys
*** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
Probably caused by : AppleCharger.sys ( AppleCharger+26c0 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff88000c0b263, 0, ffffffffffffffff}
Probably caused by : CI.dll ( CI!CiValidateImageData+2f )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff880091e5088, fffff880091e48f0, fffff80002acfd46}
Probably caused by : Ntfs.sys ( Ntfs+cb642 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1, {75692dd9, 0, 40000, fffff88003c77ca0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeStartIoCallBack+2e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\WMP54Gv41x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WMP54Gv41x64.sys
*** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x64.sys
Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+165b8 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ac98b6, fffff880090277d8, fffff88009027040}
Probably caused by : WMP54Gv41x64.sys ( WMP54Gv41x64+3252 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : afd.sys ( afd!AfdTimeoutPoll+22 )
Followup: MachineOwner
CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050830
Arg2: fffff8800334d6c8
Arg3: fffff8800334cf30
Arg4: fffff80002a86905
Debugging Details:
------------------
EXCEPTION_RECORD: fffff8800334d6c8 -- (.exr 0xfffff8800334d6c8)
ExceptionAddress: fffff80002a86905 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800334cf30 -- (.cxr 0xfffff8800334cf30)
rax=0000000019cc0004 rbx=fffff80002c11660 rcx=fffff80002c11670
rdx=fffbfa8007e69f81 rsi=0000000000000030 rdi=0000000000000030
rip=fffff80002a86905 rsp=fffff8800334d900 rbp=fffff8800334d9c0
r8=fffbfa8007e69f80 r9=0000000000000030 r10=fffff80002c11670
r11=fffff8a008fc8000 r12=0000000011fd08c7 r13=fffff8800334d978
r14=fffff8800334d970 r15=0000000000000011
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02a86905 498b08 mov rcx,qword ptr [r8] ds:002b:fffbfa80`07e69f80=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbb0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a86905 498b08 mov rcx,qword ptr [r8]
FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`02a86905 498b08 mov rcx,qword ptr [r8]
BUGCHECK_STR: 0x34
LAST_CONTROL_TRANSFER: from fffff80002a6e419 to fffff80002a86905
STACK_TEXT:
fffff880`0334d900 fffff800`02a6e419 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault16
fffff880`0334d910 fffff800`02a4bcbf : 00000000`00000001 fffff880`0334d9c0 00000000`00000018 00000000`00000030 : nt!PfFbLogEntryReserve+0x59
fffff880`0334d950 fffff800`02e3e7c9 : 00000000`00000001 00000000`00000001 fffff8a0`0a19f6f0 00000000`00000000 : nt!PfLogEvent+0x4f
fffff880`0334d9a0 fffff800`02db922e : fffffa80`074efa10 c774d318`a94e263e 00000000`00000000 00000000`00000000 : nt!PfCheckDeprioritizeFile+0x419
fffff880`0334da10 fffff800`02a9c567 : 00000000`00000000 fffffa80`066f5ff0 00000000`00000000 00000000`00040000 : nt! ?? ::NNGAKEGL::`string'+0x19266
fffff880`0334da50 fffff800`02a73274 : 00000000`00000001 fffffa80`074eeb20 fffffa80`074efa00 00000000`00000000 : nt!CcUnmapVacbArray+0x1b7
fffff880`0334dae0 fffff800`02a76d1c : fffffa80`074efa10 00000000`00000011 fffffa80`074efa10 00000000`00000000 : nt!CcDeleteSharedCacheMap+0x140
fffff880`0334db50 fffff800`02a77520 : fffff800`02c8a100 fffff880`0334dc58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x5bc
fffff880`0334dc00 fffff800`02a90961 : fffffa80`06729550 fffff800`02d7fc20 fffff800`02c8a140 fffffa80`00000003 : nt!CcWorkerThread+0x1c8
fffff880`0334dcb0 fffff800`02d27c06 : 9b279b27`16081608 fffffa80`06723040 00000000`00000080 fffffa80`06705040 : nt!ExpWorkerThread+0x111
fffff880`0334dd40 fffff800`02a61c26 : fffff880`0316a180 fffffa80`06723040 fffff880`031750c0 56e156e1`baa9baa9 : nt!PspSystemThreadStartup+0x5a
fffff880`0334dd80 00000000`00000000 : fffff880`0334e000 fffff880`03348000 fffff880`0334d9f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!ExpInterlockedPopEntrySListFault16+0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff8800334cf30 ; kb
FAILURE_BUCKET_ID: X64_0x34_nt!ExpInterlockedPopEntrySListFault16+0
BUCKET_ID: X64_0x34_nt!ExpInterlockedPopEntrySListFault16+0
Followup: MachineOwner
---------