New
#21
The above crash indicates driver or hardware issues. I noted that another crash indicated possible data corruption.Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\Vimicry\Windows_NT6_BSOD_jcgriff2\Windows_NT6_BSOD_jcgriff2\042512-17409-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02eac650 Debug session time: Wed Apr 25 20:56:46.247 2012 (UTC - 6:00) System Uptime: 0 days 1:22:32.730 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {800000, 2, 0, fffff80002cef7a2} Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000800000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80002cef7a2, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f16100 0000000000800000 CURRENT_IRQL: 2 FAULTING_IP: nt!KiProcessExpiredTimerList+72 fffff800`02cef7a2 803818 cmp byte ptr [rax],18h CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff80000b9c450 -- (.trap 0xfffff80000b9c450) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000800000 rbx=0000000000000000 rcx=fffffa8004af7b80 rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002cef7a2 rsp=fffff80000b9c5e0 rbp=000000000004d828 r8=fffff80002e80f01 r9=000000000000002a r10=fffff80002e59e80 r11=fffff80002e80fa0 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiProcessExpiredTimerList+0x72: fffff800`02cef7a2 803818 cmp byte ptr [rax],18h ds:1288:00000000`00800000=?? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ce4229 to fffff80002ce4c80 STACK_TEXT: fffff800`00b9c308 fffff800`02ce4229 : 00000000`0000000a 00000000`00800000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff800`00b9c310 fffff800`02ce2ea0 : fffffa80`00000001 fffff880`00000064 fffffa80`04a6fb50 fffffa80`04af7ba0 : nt!KiBugCheckDispatch+0x69 fffff800`00b9c450 fffff800`02cef7a2 : fffffa80`04af7ba0 fffffa80`04af7be8 fffffa80`04af7be8 00000000`00000102 : nt!KiPageFault+0x260 fffff800`00b9c5e0 fffff800`02cef6de : 0000000b`880ebb75 fffff800`00b9cc58 00000000`0004d828 fffff800`02e5c788 : nt!KiProcessExpiredTimerList+0x72 fffff800`00b9cc30 fffff800`02cef4c7 : 00000002`9585d9c2 00000002`0004d828 00000002`9585d9d0 00000000`00000028 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02cdc98a : fffff800`02e59e80 fffff800`02e67cc0 00000000`00000000 fffff880`01ccda00 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiProcessExpiredTimerList+72 fffff800`02cef7a2 803818 cmp byte ptr [rax],18h SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiProcessExpiredTimerList+72 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55 FAILURE_BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+72 BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+72 Followup: MachineOwner ---------
I also see that the crashes were gone for a couple weeks. Was this due to inactivity with the system, or have you done something different in the past two days that may have changed the system, i.e. added hardware or software that you were not previously using?
- Run Disk Check with Automatically fix file system errors checked. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
Quote