Hey guys, sorry to bother but I need some help assessing a problem I have been having. Machine is 2 weeks old and I keep getting random freezes no BSOD for since day 2 of the build. Today I got my first BSOD crash and this is what was in the dump file.
Code:++++Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\Mini123010-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*Symbol information Executable search path is: Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458 Machine Name: Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e21dd0 Debug session time: Thu Dec 30 12:02:10.751 2010 (UTC - 5:00) System Uptime: 0 days 0:00:59.423 Loading Kernel Symbols ............................................................... ................................................................ .................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffffa6000fb27d2, fffffa60026759d8, fffffa60026753b0} Probably caused by : ecache.sys ( ecache!EcCacheUpdateBufferCommit+86 ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffffa6000fb27d2, The address that the exception occurred at Arg3: fffffa60026759d8, Exception Record Address Arg4: fffffa60026753b0, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: ecache!EcCacheUpdateBufferCommit+86 fffffa60`00fb27d2 448b432c mov r8d,dword ptr [rbx+2Ch] EXCEPTION_RECORD: fffffa60026759d8 -- (.exr 0xfffffa60026759d8) ExceptionAddress: fffffa6000fb27d2 (ecache!EcCacheUpdateBufferCommit+0x0000000000000086) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffffa60026753b0 -- (.cxr 0xfffffa60026753b0) rax=fffffa8005b90000 rbx=ff00fa8004f99dc0 rcx=fffffa8005b90000 rdx=0000000000096a00 rsi=fffffa8004dbee48 rdi=fffffa8005a89ac0 rip=fffffa6000fb27d2 rsp=fffffa6002675c10 rbp=00000000000f2000 r8=0000000000000000 r9=fffffa8005a89ac0 r10=0000000000001fff r11=0000000000000000 r12=0000000000000368 r13=fffffa8004dbe4b0 r14=000000000000005c r15=fffffa8008b776f0 iopl=0 nv up ei ng nz na po cy cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010287 ecache!EcCacheUpdateBufferCommit+0x86: fffffa60`00fb27d2 448b432c mov r8d,dword ptr [rbx+2Ch] ds:002b:ff00fa80`04f99dec=32aa2fd8 Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 ERROR_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 fffff80002e84080 ffffffffffffffff FOLLOWUP_IP: ecache!EcCacheUpdateBufferCommit+86 fffffa60`00fb27d2 448b432c mov r8d,dword ptr [rbx+2Ch] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffffa6000fb2db2 to fffffa6000fb27d2 STACK_TEXT: fffffa60`02675c10 fffffa60`00fb2db2 : fffffa80`04dbe4b0 fffffa60`00fc1fd0 fffffa80`08a68480 00000000`00000001 : ecache!EcCacheUpdateBufferCommit+0x86 fffffa60`02675c60 fffff800`02ec1f57 : 00000000`0667bdaa fffffa80`04d46bb0 00000000`00000080 fffffa60`00fc1fd0 : ecache!EcCacheIoWorker+0x33e fffffa60`02675d50 fffff800`02cf4656 : fffff800`02dd0680 fffffa80`04d46bb0 fffff800`02dd5b80 fffffa80`039ba138 : nt!PspSystemThreadStartup+0x57 fffffa60`02675d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ecache!EcCacheUpdateBufferCommit+86 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ecache IMAGE_NAME: ecache.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e02c52 STACK_COMMAND: .cxr 0xfffffa60026753b0 ; kb FAILURE_BUCKET_ID: X64_0x7E_ecache!EcCacheUpdateBufferCommit+86 BUCKET_ID: X64_0x7E_ecache!EcCacheUpdateBufferCommit+86 Followup: MachineOwner ---------+++++++
I don't know anything about how to read this or what it means so any help would be appreciated, thanks in advance.



Reply With Quote




