New
#1
BSOD Analysis Help Please!
Hey Guys and Gals. I am new here ad I am usually able to figure out something like this on my own, but I am bit stuck
I have Windows 7 Pro 64 Bit HTPC box. Built it myself and it was good for a few years. Had some BSODs before because of the video card. HD4770 was nagging like my wife and a few driver updates resolved that problem. Now I am having some BSODs quiet frequently. I did rebuild it a little while ago after I got a Ceton Card for Time Warner Cable installed. I don't think its the Ceton card that's causing BSODs, but who knows.
Anyway, I am attaching screenshot from the debugger analysis
Can't attache the memory dump file itself. I guess here is a size limit here!
Only thing I see that is LogMeIn and I have since disabled it plus its video mirror driver
Any help would be greatly appreciated
Thank you in advance !!!
==============================================
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0341d000 PsLoadedModuleList = 0xfffff800`03661670
Debug session time: Fri Nov 16 14:59:28.890 2012 (UTC - 8:00)
System Uptime: 1 days 15:22:03.622
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff800034ccd4f, 0, 8}
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockChainValid+1f )
Followup: MachineOwner
---------
0: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800034ccd4f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000008, Parameter 1 of the exception
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!KxWaitForLockChainValid+1f
fffff800`034ccd4f 488b07 mov rax,qword ptr [rdi]
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000008
READ_ADDRESS: 0000000000000008
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: LogMeIn.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008915440 -- (.trap 0xfffff88008915440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=0000000000000008
rdx=0000000000000088 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034ccd4f rsp=fffff880089155d0 rbp=fffff88008915c60
r8=000000006770534e r9=0000000000000001 r10=0000000000000000
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KxWaitForLockChainValid+0x1f:
fffff800`034ccd4f 488b07 mov rax,qword ptr [rdi] ds:8bf0:0000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800034e6d88 to fffff8000349c1c0
STACK_TEXT:
fffff880`08914bb8 fffff800`034e6d88 : 00000000`0000001e ffffffff`c0000005 fffff800`034ccd4f 00000000`00000000 : nt!KeBugCheckEx
fffff880`08914bc0 fffff800`0349b842 : fffff880`08915398 00000000`00000001 fffff880`08915440 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x48d3d
fffff880`08915260 fffff800`0349a3ba : 00000000`00000000 00000000`00000008 fffff880`08915500 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`08915440 fffff800`034ccd4f : 00020006`00020019 fffff880`0148d4e9 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`089155d0 fffff800`034afba7 : 00000000`00000000 fffff880`0148da1b 00000000`00000000 fffff880`01797358 : nt!KxWaitForLockChainValid+0x1f
fffff880`08915600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CcUnpinFileDataEx+0x577
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KxWaitForLockChainValid+1f
fffff800`034ccd4f 488b07 mov rax,qword ptr [rdi]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!KxWaitForLockChainValid+1f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4fa390f3
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KxWaitForLockChainValid+1f
BUCKET_ID: X64_0x1E_c0000005_nt!KxWaitForLockChainValid+1f
Followup: MachineOwner
---------
Quote