Sign in with
Sign up | Sign in
Your question
Solved

Is my BSOD a CPU problem?

Tags:
Last response: in CPUs
Share
October 8, 2012 5:27:54 PM

CPU: Intel Core i5-3470 3.2GHz Quad-Core Processor
Motherboard: Gigabyte GA-H77M-D3H Micro ATX LGA1155 Motherboard
Memory: Corsair Vengeance 8GB (2 x 4GB) DDR3-1600 Memory
Storage: Western Digital Caviar Blue 500GB 3.5" 7200RPM Internal Hard Drive
Video Card: HIS Radeon HD 7870 2GB Video Card
Case: Rosewill Challenger-U3 ATX Mid Tower Case
Power Supply: Corsair Enthusiast 650W 80 PLUS Certified ATX12V / EPS12V Power Supply
OS: Windows 7 Professional 64 Bit

Long story short, built a new computer a week ago, started crashing a handful of times while using onboard graphics; would crash on windows updates, light usage like streams and skype video chat. Other times, it would stay stable for hours, allowing me to watch downloaded movies (although they weren't hd, but still). Got a 7870, things still didn't improve.

I get both kinds of errors: blue screen saying uncorrectable hardware error, and other times my computer will just shut off with nothing. If I did something like, update my windows experience index, which tests the graphics and such, it would always shut off during that. Ran memtest for 2 hours, memory came up clean. I can get around in the bios just fine. When I try to go through safe mode, it will always blue screen after a minute.

Any ideas?

More about : bsod cpu problem

October 9, 2012 8:47:43 AM

tap f8 and select directory restore mode and restore back to a date when u know it was working, maybe a graphics card driver, have u overclocked anything?
Related resources
a b à CPUs
October 9, 2012 12:02:35 PM

^^ Last option. Find out what the problem is before taking half baked steps to maybe fix the problem.
October 9, 2012 12:06:57 PM

gamerk316 said:
^^ Last option. Find out what the problem is before taking half baked steps to maybe fix the problem.


half baked lol its surely quicker than looking up error codes.
October 9, 2012 12:28:45 PM

this will definetly fix this issue, your pc makes restore points, restore back to a date when you know it was working, this will work and fix 100%

Best solution

a b à CPUs
October 9, 2012 5:24:57 PM
Share

^^ Unless its HW, which 90% of the time it is. And 75% of the time it is HW, its RAM, 20% GPU, and the rest usually the mobo/PSU.

Hell, I have 90% of the common error codes memorized, because we see three or four every day in the Windows section of the forums.
October 9, 2012 5:35:57 PM

u mean damaged hardware then? not the software that runs it?
October 10, 2012 11:03:37 PM

I can't restore back to a point when it was working. It will crash early on when I've reinstalled my OS. I don't have the error logs anymore but one of the crashes was hal.dll.

I ran memtest on my memory for 2 hours. I'm downloading my windows straight from the site and putting it on a usb to install. It crashes with or without my graphics card. I'm not sure if it could be my psu because it has more than enough power and is not a cheap one.

Is there anything else I can troubleshoot?

The only thing I've used to "stress" test it is WEI because it has a function that tests the cpu and the graphics, etc. It will always crash on that. But if I'm doing light usage, like just browsing the internet like I am now, I can get by for hours without crashing.
October 11, 2012 1:24:03 AM

I'm also now seeing blue screens that say "machine check exception".
a b à CPUs
October 11, 2012 12:10:20 PM

Post a screenshot of what BSOD's Bluecreenview reports. That will help a bit, especially if various BSOD messages are being generated.

Anyway, a Machine Check Exception BSOD (0x9C) points to a HW problem, probably mobo or PSU related. Normally, 0x124 [WHEA_Uncorrectable_Error] would be generated for a generic HW problem, but if a crash occurs before WHEA gets initialized, a MACHINE_CHECK_EXCEPTION BSOD gets thrown instead. The fact HAL.dll is crashing [the HW Abstraction Layer] farther points to a HW related problem.

For the most part, I treat this BSOD similar to the WHEA BSOD's when it comes to debugging. First thing to check is temperatures, to make sure nothing is overheating. Next thing would be the voltages that are being reported, to ensure they remain within ATX spec. After that, you start going to a barebones configuration [one RAM stick, etc] to try and lessen the number of potential HW factors [for instance, some low-end mobos are unstable when using 4 sticks of RAM with certain agressive timings].
October 11, 2012 5:35:00 PM

It's solved. It was an improperly installed cpu heatsink/fan. It was running too hot, I just didn't realize the temperatures were wrong/too high because I've never monitored temperatures before. Reseated the fan and put a little more thermal paste in, and there are no more crashes.

Thanks a ton for the replies gamerk.
October 11, 2012 5:35:32 PM

Best answer selected by ffooby.
!