Fresh install of Windows 7 x64 Ultimate. I'm actually getting a No Screen of Death and have to hard reset. The following is from the minidump:
My first guess was the RAM, but I had previously done a 24hour memtest on them...
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\Windows\Minidump\122910-8626-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Wed Dec 29 19:02:37.408 2010 (UTC - 5:00)
System Uptime: 0 days 1:23:34.468
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff880012178cb, fffff8800a92b938, fffff8800a92b1a0}
Probably caused by : Ntfs.sys ( Ntfs!NtfsRemoveClose+a3 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: fffff880012178cb, The address that the exception occurred at
Arg3: fffff8800a92b938, Exception Record Address
Arg4: fffff8800a92b1a0, 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:
Ntfs!NtfsRemoveClose+a3
fffff880`012178cb f08380e4000000ff lock add dword ptr [rax+0E4h],0FFFFFFFFh
EXCEPTION_RECORD: fffff8800a92b938 -- (.exr 0xfffff8800a92b938)
ExceptionAddress: fffff880012178cb (Ntfs!NtfsRemoveClose+0x00000000000000a3)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800a92b1a0 -- (.cxr 0xfffff8800a92b1a0)
rax=93b4fc8ef752c917 rbx=fffffa800a5646a0 rcx=fffff88001271220
rdx=fffff88001271220 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880012178cb rsp=fffff8800a92bb70 rbp=fffff80002c635a0
r8=00000000ffffffff r9=0000000000000727 r10=fffff8800126f700
r11=fffff8a0013b5960 r12=fffff88001271000 r13=0000000000000000
r14=fffff8800a92bc08 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
Ntfs!NtfsRemoveClose+0xa3:
fffff880`012178cb f08380e4000000ff lock add dword ptr [rax+0E4h],0FFFFFFFFh ds:002b:93b4fc8e`f752c9fb=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
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 fffff80002cf60e0
ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsRemoveClose+a3
fffff880`012178cb f08380e4000000ff lock add dword ptr [rax+0E4h],0FFFFFFFFh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88001297286 to fffff880012178cb
STACK_TEXT:
fffff880`0a92bb70 fffff880`01297286 : fffffa80`0b7a2a90 00000000`00000000 fffff8a0`013ba670 fffffa80`08148180 : Ntfs!NtfsRemoveClose+0xa3
fffff880`0a92bba0 fffff800`02acb961 : 00000000`00000000 fffff880`01216200 fffff800`02cc5100 fffff880`00000005 : Ntfs!NtfsFspClose+0x56
fffff880`0a92bc70 fffff800`02d62c06 : fffff880`00000001 fffffa80`0b3a6040 00000000`00000080 fffffa80`06d07040 : nt!ExpWorkerThread+0x111
fffff880`0a92bd00 fffff800`02a9cc26 : fffff880`009ee180 fffffa80`0b3a6040 fffffa80`08d62770 fffff880`01224a90 : nt!PspSystemThreadStartup+0x5a
fffff880`0a92bd40 00000000`00000000 : fffff880`0a92c000 fffff880`0a926000 fffff880`0a92b6c0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Ntfs!NtfsRemoveClose+a3
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
STACK_COMMAND: .cxr 0xfffff8800a92b1a0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_Ntfs!NtfsRemoveClose+a3
BUCKET_ID: X64_0x7E_Ntfs!NtfsRemoveClose+a3
Followup: MachineOwner
---------
Verbose mode ON.My first guess was the RAM, but I had previously done a 24hour memtest on them...