Windows 7 x64 Blue Screens on a new build

Radracer256 · 20 Aug 2010

Hey guys, new member here. Any who, I installed Windows 7 Ultimate x64 (legit) onto this computer I was building (first build) Well I've been having some blue screen errors, initially using windbg I had thought I had traced it back to a driver error; So I thought that just for the sake of stability doing a clean format. The windows image itself was downloaded through msdn and burned on a dvd at 4.7x if i recall; There were no errors or problems during the initial re-set up and update of this copy of windows, until I started moving files back onto the hard drive; it crashed about 2 minutes into the transfer. Then, while trying to register for this site to post the first crash dump, the computer crashed again. Looking at the first dump, it tells me that it was a hardware error, and looking at the second; i honestly couldn't make heads or tails of it. Can somebody out there lend me a hand? I'm pulling my hair out here.

ive ran memtest 86+ on the ram already, it was one pass on each stick, in each slot; then two passes on two sticks in alternating slots, then 6 passes on all 4 at once

no part in this machine is over 2 months old

Windows 7 Ultimate x64
Intel i5 650
EVGA p55 ftw motherboard
PNY 1333 2x2GB RAM (4 sticks for 8GB total)
EVGA 470GTX
stock cooling in a 65 degree room
Logitech keyboard/mouse
corsair 750W PSU
antec p180b case

Jonathan_King · 20 Aug 2010

Welcome!

The dumps appear to be caused by some sort of hardware failure.

What are your temps like? Test with Speedfan.

Test hard drive: HD Diagnostic

Test CPU: https://www.sevenforums.com/tutorials...t-prime95.html

Test video card: STOP 0x116: VIDEO_TDR_ERROR troubleshooting

If you get any more BSODs, please follow the BSOD Posting Instructions again.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 20 00:52:18.899 2010 (UTC - 4:00)
System Uptime: 0 days 0:28:12.024
BugCheck 1A, {5003, fffff70001080000, cd0d, e08e00019a0a}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  MsMpEng.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 20 00:23:17.431 2010 (UTC - 4:00)
System Uptime: 0 days 0:52:13.509
BugCheck 3B, {c0000005, fffff9600013b5f0, fffff88006421070, 0}
Probably caused by : hardware ( win32k!xxxSleepThread+58 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  RocketDock.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Radracer256 · 21 Aug 2010

Well I haven't had any bluescreens today, but I ran Prime95 for 12 hours; two of the four threads failed before the end of the 12 hour mark; ive attached a final prime95 screen shot(Prime95.png), and screen shots of speed fan at the half mark (6hours(halfsnap.png)) and the end mark (12 hours(endsnap.png)) of the test. Is this a simple heat issue or something more? I don't know what my next step should be here. I was thinking about re-seating my heat sink on the processor; but I thought that two of my processor cores were only logical cores; and if i looked at the readout correctly, those are the two that failed. Well I'm a little confused to say the least, can somebody help me out of this? Thanks for the help guys and gals.

Id also like to add that my cpu's temp on idle is usually 20-25, and when im gaming or something intensive like that, the temp is 35-40. Ive NEVER seen my cpu temp ever go as high as it did while running prime95; but looking on intel's web site, the max temp of my cpu is somewhere around 76, so i suppose im within the limits. Another thing I would like to add are the readouts during the test the two temperature readouts that are simply labeled "test" in speedfan I think are wrong; because at no point before,during,or after the test did those values change. Also, I think the +12v reading is wrong, saying that its around 9v, because i also checked that level in pc wizard 2010 and it said that the voltage was around 46v! So i think there's some issue with a few of the sensors as well