|29 May 2011||#1|
| || |
Clean Install BSOD
Just did a clean install of Win 7 pro edition, 64 bit on my machine. Came home to find, 'my system has recovered from an unexpected shut down...'
On the clean install I have made sure to update all mobo drivers as well as graphics card drivers so I think I am up to date there.
System specs are :
Case: COOLER MASTER COSMOS 1000 RC-1000-KSN1-GP Black/ Silver Steel ATX Full Tower Computer Case
Mobo: MSI NF980-G65 AM3 NVIDIA nForce 980a SLI HDMI ATX AMD Motherboard
Graphics Card: SAPPHIRE Vapor-X Radeon HD 4870 2GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready CrossFireX Support Video Card
Hard Drive: Western Digital Caviar Green WD10EADS 1TB SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive
CPU: AMD Phenom II X4 955 Black Edition Deneb 3.2GHz Socket AM3 125W Quad-Core Processor HDZ955FBGIBOX
Memory: 8 Gigs of G.SKILL 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Dual Channel Kit Desktop Memory Model F3-12800CL9D-4GBNQ
Op sys: Microsoft Windows 7 Professional 64-bit 1-Pack for System Builders
Power: 600 Watt unsure of brand.
Attached is my crash file per BSOD posting instructions....
Can someone please help me out.....Thanks all....
|My System Specs|
|30 May 2011||#2|
| || |
Welcome to Seven Forums.
The dump files indicate the crash is from:
STOP 0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Which is the same as STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
With the exception 0xC0000005: STATUS_ACCESS_VIOLATION
This indicates a memory access violation occurred.
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Is this a new build?
If not what OS did you previously have installed?
Any new components?
Let's start with memtest86+ and test the memory:
RAM - Test with Memtest86+
Follow the instructions on this tutorial, for the first test leave all RAM cards installed.
You need to run it for a full 7 passes, this will take several hours, best to let it run overnight.
You have 8GB RAM DDR3 1600, if you have RAM settings at (800Mhz) 1600 in the BIOS, this will likely be causing the crash.
There is a known issue with AMD CPUs integrated memory controllers having problems running RAM at 1600 MHz and above.
VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's and RAM SPEEDS
Q&A for the topic VERY IMPORTANT INFORMATION REGARDING AMD AM3 CPU's & RAM....
First, change the RAM frequency to 1333MHz, then run memtest86+.
******************************************************************************* * * * 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: fffff80002f647d2, The address that the exception occurred at Arg3: fffff880031cb968, Exception Record Address Arg4: fffff880031cb1d0, 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: nt!CmpDereferenceNameControlBlockWithLock+aa fffff800`02f647d2 488b02 mov rax,qword ptr [rdx] EXCEPTION_RECORD: fffff880031cb968 -- (.exr 0xfffff880031cb968) ExceptionAddress: fffff80002f647d2 (nt!CmpDereferenceNameControlBlockWithLock+0x00000000000000aa) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter: 0000000000000000 Parameter: ffffffffffffffff Attempt to read from address ffffffffffffffff CONTEXT: fffff880031cb1d0 -- (.cxr 0xfffff880031cb1d0) rax=ff7ff8a008b26c98 rbx=0000000000000000 rcx=0000000000000e00 rdx=ff7ff8a008b26ca0 rsi=fffff8a008b26c98 rdi=fffff8a008b26c90 rip=fffff80002f647d2 rsp=fffff880031cbba0 rbp=0000000000007000 r8=000000009ca3430e r9=000000002cebfc39 r10=fffff8a00d9a5948 r11=fffff8a00013a140 r12=0000000000000001 r13=0000000000000001 r14=0000000000000000 r15=0000000000000001 iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!CmpDereferenceNameControlBlockWithLock+0xaa: fffff800`02f647d2 488b02 mov rax,qword ptr [rdx] ds:002b:ff7ff8a0`08b26ca0=???????????????? 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 fffff80002ea90e0 ffffffffffffffff FOLLOWUP_IP: nt!CmpDereferenceNameControlBlockWithLock+aa fffff800`02f647d2 488b02 mov rax,qword ptr [rdx] BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from fffff80002f646c8 to fffff80002f647d2 STACK_TEXT: fffff880`031cbba0 fffff800`02f646c8 : fffff8a0`102ee258 fffff880`031cbc5c 00000000`00000004 00000000`00000001 : nt!CmpDereferenceNameControlBlockWithLock+0xaa fffff880`031cbbd0 fffff800`02ec8f4e : fffff8a0`102ee258 fffff880`031cbc44 00000000`00000004 00000000`00000002 : nt!CmpCleanUpKcbCacheWithLock+0x34 fffff880`031cbc00 fffff800`02c7e961 : fffff800`02ec8c14 fffff800`02e165f8 fffffa80`06a1bb60 00000000`00000000 : nt!CmpDelayCloseWorker+0x33a fffff880`031cbcb0 fffff800`02f14bc6 : 0000056e`00000000 fffffa80`06a1bb60 00000000`00000080 fffffa80`06a0b040 : nt!ExpWorkerThread+0x111 fffff880`031cbd40 fffff800`02c4fbc6 : fffff880`02f64180 fffffa80`06a1bb60 fffff880`02f6efc0 0000056e`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb900 00000000`00000000 : nt!KiStartSystemThread+0x16 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!CmpDereferenceNameControlBlockWithLock+aa FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34 STACK_COMMAND: .cxr 0xfffff880031cb1d0 ; kb FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa BUCKET_ID: X64_0x7E_nt!CmpDereferenceNameControlBlockWithLock+aa Followup: MachineOwner ---------
fet6x64.sys Thu Jun 19 19:40:18 2008
Looks like your system crashed while doing a Windows Update.
The event viewer is showing many updates have failed.
Event: Log Name: System Source: Service Control Manager Date: 2011-05-28T22:55:02.863 Event ID: 7043 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Kennedy-PC Description: The Windows Update service did not shut down properly after receiving a preshutdown control.
This is a Secure Channel error, What anti virus do you have installed?
Event: Log Name: System Source: Schannel Date: 2011-05-28T19:01:02.668 Event ID: 36888 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Kennedy-PC Description: The following fatal alert was generated: 10. The internal error state is 10.
D/L and run Western Digital Lifeguard– Quick Test and Extended Test, on both HDDs.
Event: Log Name: System Source: Disk Date: 2011-05-28T09:45:36.244 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Kennedy-PC Description: The driver detected a controller error on \Device\Harddisk1\DR1.
|My System Specs|
|Similar help and support threads for2: Clean Install BSOD|
|BSOD 41(63), Second clean install||BSOD Help and Support|
|Please Help Clean Install BSOD's||BSOD Help and Support|
|BSOD on a clean install sys||BSOD Help and Support|
|BSOD's during clean W7 install||Installation & Setup|
|BSOD on 7 Pro clean install||BSOD Help and Support|
|BSOD on clean install||BSOD Help and Support|