Self-built desktop keeps crashing

[pmoon]

Hello, I just joined this forum and this is my first time posting.
I built my desktop in late December last year. Everything seemed fine until I installed Windows 7 Ultimate x64 (Korean) and started installing programs I regularly use. Then, BSOD hit me...I'd never had a self-built computer crash on me so fast after building, and I thought it might be a problem with Win7 installation, so I tried formatting and re-installing windows multiple times (probably 5~6 times), but BSOD kept happening. Win7 even refused to be installed at all twice or so.

I have been really busy with work since, so I just never got around to try fixing it until last week. I did a fresh installation, then everything seemed fine until two nights ago, when my computer failed to boot up. I get the usual bios messages, and even the windows logo that shows up before the mouse pointer appears, then BSOD. It happens every time I try to boot up. I managed to pull out minidumps, so I'm attaching them here.

It seems to me like a hardware problem. I have run windows' memory diagnostic tool, which told me there aren't any problems with my memory, but who knows. My amateur guess for the culprit is the motherboard, but I wanted to ask for professional opinions here and decide which components I should send in for after-service.

Thanks in advance!

oops I forgot to post my system specs and minidumps
Here they are.

Motherboard: ASUS P7P55D
CPU: Intel i7-860 Lynnfield
RAM: EKMEMORY DDR3 8G (4x2G) PC3-12800
Video: Rextech Xpert Radeon HD 4890 D5 1GB
Power: CORE Chungoong Bingsan 600W

 

[richc46]

I have examined your dump reports. Based upon my analysis you had 3 BSOD's recently.
The last Dump report was corrupted and I was not able to read or open it.

The other two reports indicated stop errors of 00000005 and 1000007E. Based upon those reports and the additional information contained in the files the following information was ascertained.

You have a corrupted driver which must be replaced, the ATI radeon Kernal Mode Driver

In addition memory problems were evident. You should download and use memtest86 to test the memory.

You should also check for any corruption by perfoming a System File Check.
On an elevated command prompt (type cmd in search, right click and then run as administrator) type the letters sfc /scannow.

It is often the case that after these repairs are made additional BSOD may occur, especially since I could not read the last report. If that occurs return and we will report the additional problems to you.

There is also an idication that csrss.exe was involved. This is a normal process but sometimes the hiding place of a virus. So perform a virus scan.

One of the reports mentioned pool corruption which points to memory. The problems could be many but one possiblity is mismatched ram. Since your compter is self built this is a potential problem. So be sure to perform the previoulsy mentioned memory test.
http://memtest.org/

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp2_minidumps[1].zip\060210-28532-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03058e50
Debug session time: Wed Jun  2 10:40:35.778 2010 (GMT-4)
System Uptime: 0 days 0:00:32.808
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880051fb07a, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+38f07a )
Followup: MachineOwner
---------
2: 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: fffff880051fb07a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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: 
atikmdag+38f07a
fffff880`051fb07a 410f2973e8      movaps  xmmword ptr [r11-18h],xmm6
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c30e0
 0000000000000000 
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1E
PROCESS_NAME:  csrss.exe
CURRENT_IRQL:  0
EXCEPTION_RECORD:  fffff88002a5fce8 -- (.exr 0xfffff88002a5fce8)
ExceptionAddress: fffff880051fb07a (atikmdag+0x000000000038f07a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000
TRAP_FRAME:  fffff88002a5fd90 -- (.trap 0xfffff88002a5fd90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000800
rdx=fffff900c07e1a50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880051fb07a rsp=fffff88002a5ff28 rbp=fffffa80091e2000
 r8=0000000000000000  r9=0000000000000004 r10=fffff8a0024a8d00
r11=fffff88002a5ffd0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
atikmdag+0x38f07a:
fffff880`051fb07a 410f2973e8      movaps  xmmword ptr [r11-18h],xmm6 ds:fffff880`02a5ffb8=000000000000ff0c000000000000008e
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ec5929 to fffff80002e8b600
STACK_TEXT:  
fffff880`02a5f518 fffff800`02ec5929 : 00000000`0000001e ffffffff`c0000005 fffff880`051fb07a 00000000`00000000 : nt!KeBugCheckEx
fffff880`02a5f520 fffff800`02e8ac42 : fffff880`02a5fce8 fffff880`02a60098 fffff880`02a5fd90 fffffa80`090e5000 : nt!KiDispatchException+0x1b9
fffff880`02a5fbb0 fffff800`02e8954a : 00000000`00000000 0000041a`00000690 00000000`00000000 00001fa0`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02a5fd90 fffff880`051fb07a : 00000000`0000a191 fffff880`051cfc55 fffff880`02a60468 fffff880`051e0573 : nt!KiGeneralProtectionFault+0x10a
fffff880`02a5ff28 00000000`0000a191 : fffff880`051cfc55 fffff880`02a60468 fffff880`051e0573 00000000`0000260c : atikmdag+0x38f07a
fffff880`02a5ff30 fffff880`051cfc55 : fffff880`02a60468 fffff880`051e0573 00000000`0000260c fffff880`051e0573 : 0xa191
fffff880`02a5ff38 fffff880`02a60468 : fffff880`051e0573 00000000`0000260c fffff880`051e0573 00000000`00000000 : atikmdag+0x363c55
fffff880`02a5ff40 fffff880`051e0573 : 00000000`0000260c fffff880`051e0573 00000000`00000000 fffff880`05208728 : 0xfffff880`02a60468
fffff880`02a5ff48 00000000`0000260c : fffff880`051e0573 00000000`00000000 fffff880`05208728 00000000`00000003 : atikmdag+0x374573
fffff880`02a5ff50 fffff880`051e0573 : 00000000`00000000 fffff880`05208728 00000000`00000003 fffff880`051fc09a : 0x260c
fffff880`02a5ff58 00000000`00000000 : fffff880`05208728 00000000`00000003 fffff880`051fc09a 00000000`0000a1e8 : atikmdag+0x374573
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
atikmdag+38f07a
fffff880`051fb07a 410f2973e8      movaps  xmmword ptr [r11-18h],xmm6
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  atikmdag+38f07a
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME:  atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4be0ccae
FAILURE_BUCKET_ID:  X64_0x1E_atikmdag+38f07a
BUCKET_ID:  X64_0x1E_atikmdag+38f07a
Followup: MachineOwner
---------

 

[Jonathan_King]

I agree with Richard. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Test your hard drive as well: HD Diagnostic

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 10:13:25.591 2010 (GMT-4)
System Uptime: 0 days 0:00:12.511
BugCheck 1000007E, {ffffffffc0000005, fffff80003007000, fffff88003985858, fffff880039850c0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+174 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 10:40:35.778 2010 (GMT-4)
System Uptime: 0 days 0:00:32.808
BugCheck 1E, {ffffffffc0000005, fffff880051fb07a, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+38f07a )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]