Help with Windows 7 BSOD with windbg minidump !analyze -v results
- by Kurt Harless
Hi gang,
Windows 7 X64 Ultimate is BSODing occasionally. I suspect an overheating issue or something related to the use of my GTX-295 card that runs very hot.
Here is an !analyze -v listing of the most recent minidump.
Any and all help greatly appreciated.
Kurt
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\122810-31387-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03065000 PsLoadedModuleList = 0xfffff800`032a2e50
Debug session time: Tue Dec 28 11:04:03.597 2010 (UTC - 7:00)
System Uptime: 2 days 2:28:40.407
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800033b8873, fffff8800e322dc0, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlCompareUnicodeStrings+c3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800033b8873, Address of the instruction which caused the bugcheck
Arg3: fffff8800e322dc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!RtlCompareUnicodeStrings+c3
fffff800`033b8873 488b7c2418 mov rdi,qword ptr [rsp+18h]
CONTEXT: fffff8800e322dc0 -- (.cxr 0xfffff8800e322dc0)
rax=0000000000000041 rbx=fffff8a015a3c1c0 rcx=0000000000000024
rdx=0000000000000003 rsi=fffff8800e3238b0 rdi=0000000000000009
rip=fffff800033b8873 rsp=fffff8800e323798 rbp=000000000000000d
r8=fffff8a018cb374c r9=000000200a98fdc4 r10=fffff8800e323988
r11=fffff8800e32398e r12=fffff8a018127c18 r13=fffff8800126e550
r14=0000000000000001 r15=fffffa800abe1570
iopl=0 nv up ei pl nz ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216
nt!RtlCompareUnicodeStrings+0xc3:
fffff800`033b8873 488b7c2418 mov rdi,qword ptr [rsp+18h] ss:0018:fffff880`0e3237b0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: ccSvcHst.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800033b8873
STACK_TEXT:
fffff880`0e323798 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlCompareUnicodeStrings+0xc3
FOLLOWUP_IP:
nt!RtlCompareUnicodeStrings+c3
fffff800`033b8873 488b7c2418 mov rdi,qword ptr [rsp+18h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!RtlCompareUnicodeStrings+c3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
STACK_COMMAND: .cxr 0xfffff8800e322dc0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_nt!RtlCompareUnicodeStrings+c3
BUCKET_ID: X64_0x3B_nt!RtlCompareUnicodeStrings+c3
Followup: MachineOwner
---------
