Code:
Loading Dump File [H:\BSODDmpFiles\juraj74\dmp\012612-22932-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a50000 PsLoadedModuleList = 0xfffff800`03c95670
Debug session time: Wed Jan 25 19:53:14.517 2012 (UTC - 7:00)
System Uptime: 0 days 12:56:40.391
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : tcpip.sys ( tcpip!TcpUpdateMicrosecondCount+79 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6662616561633066
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: linpack64.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f223f8 -- (.exr 0xfffff88002f223f8)
ExceptionAddress: fffff80003a16800 (hal!KeQueryPerformanceCounter+0x000000000000010c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f224a0 -- (.trap 0xfffff88002f224a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000025c6250f04 rbx=0000000000000000 rcx=0000000000000001
rdx=0000971800000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a16800 rsp=fffff88002f22630 rbp=0000000000000001
r8=00000000a5ecafe0 r9=0000000000351f96 r10=fffff80003a50000
r11=fffffa800adea208 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!KeQueryPerformanceCounter+0x10c:
fffff800`03a16800 4883c420 add rsp,20h
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003ac45fe to fffff80003accc10
STACK_TEXT:
fffff880`02f214d8 fffff800`03ac45fe : 00000000`00000006 fffff880`0173b2d1 fffff880`02f21c50 fffff800`03af8830 : nt!KeBugCheck
fffff880`02f214e0 fffff800`03af84fd : fffff800`03cd671c fffff800`03c13c30 fffff800`03a50000 fffff880`02f223f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f21510 fffff800`03af72d5 : fffff800`03c17028 fffff880`02f21588 fffff880`02f223f8 fffff800`03a50000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f21540 fffff800`03b08361 : fffff880`02f223f8 fffff880`02f21c50 fffff880`00000000 fffff880`02f226b0 : nt!RtlDispatchException+0x415
fffff880`02f21c20 fffff800`03acc2c2 : fffff880`02f223f8 0000006c`7fff70a6 fffff880`02f224a0 fffffa80`0adea178 : nt!KiDispatchException+0x135
fffff880`02f222c0 fffff800`03acabca : 00000000`00000002 00000000`00000000 fffffa80`0ad37820 fffffa80`0ae35080 : nt!KiExceptionDispatch+0xc2
fffff880`02f224a0 fffff800`03a16800 : fffffa80`0acacd40 00000000`00000000 00000000`00000000 00000001`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f22630 fffff880`017495d9 : 00000000`00351f96 0000006c`7fff70a6 00000000`00000200 00000000`00000001 : hal!KeQueryPerformanceCounter+0x10c
fffff880`02f22660 fffff880`0174868a : 00000000`00000008 00000000`00000001 fffffa80`0adea178 00000000`00000000 : tcpip!TcpUpdateMicrosecondCount+0x79
fffff880`02f226a0 fffff800`03ad85fc : fffff880`009ed180 00000000`00000001 fffff880`02f22830 00000000`00000000 : tcpip!TcpPeriodicTimeoutHandler+0x7a
fffff880`02f227a0 fffff800`03ad8496 : fffffa80`0adea248 00000000`002d94b1 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff880`02f22810 fffff800`03ad837e : 0000006c`7fff70a6 fffff880`02f22e88 00000000`002d94b1 fffff880`009f0ba8 : nt!KiProcessExpiredTimerList+0xc6
fffff880`02f22e60 fffff800`03ad8167 : fffff880`009ed1c1 fffff880`002d94b1 00000000`00000000 00000000`000000b0 : nt!KiTimerExpiration+0x1be
fffff880`02f22f00 fffff800`03acf765 : 305f2343`7f2a4a84 fffffa80`0daac580 00000000`00000000 fffff880`044cf588 : nt!KiRetireDpcList+0x277
fffff880`02f22fb0 fffff800`03acf57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0b0f6be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
tcpip!TcpUpdateMicrosecondCount+79
fffff880`017495d9 488b4c2450 mov rcx,qword ptr [rsp+50h]
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: tcpip!TcpUpdateMicrosecondCount+79
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tcpip
IMAGE_NAME: tcpip.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e83e948
FAILURE_BUCKET_ID: X64_0x1E_0_tcpip!TcpUpdateMicrosecondCount+79
BUCKET_ID: X64_0x1E_0_tcpip!TcpUpdateMicrosecondCount+79
Followup: MachineOwner
---------
The crash was a result of Intel burn test. It may be due to overclocking the system. Do the following steps.
- If you are overclocking anything, please stop.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.