| Member with 30 posts. THREAD STARTER | | Join Date: Aug 2012 Experience: Intermediate | |
Solved: BSOD 00000124 - Not RAM, not Software Hey guys, I'm having issues with a computer I recently built with parts suggested by and bought from MSY. I knew which CPU and GPU I wanted, and they suggested the rest based on my input as I'm not too great with all the compatibility stuff.. I know how a computer goes together, that's about it.
Gigabyte Z77-D3H
Intel i7-3770k
HIS Radeon HD7850
32GB DDR3 G-Skill RAM
600 Watt PSU
4 fans.
Windows 7 Pro x64
It worked perfectly at first, but then I ran a feature that came on a disk with the motherboard and I'm afraid it's destroyed either my CPU or Motherboard..
Anyway, I have Aspergers so I'll write a lot if I don't shorten it to an analysis or list/robot talk so for the sake of an easy assessment of my trials and errors for anyone who would be able to help me, here's everything so far with some relevant information along the way:
Accidentally ran EasyTune6's "AutoTune" function. It started over-clocking itself going up and up to around 4300mhz after 5 minutes.
BSOD.
Rebooted, showed BIOS error as it had previously mentioned would happen and reassured me that it was normal.
Ok, back into the system. It automatically re-opens the auto-tune and continues.
After 30 seconds, another BSOD, reboot, but no BIOS error this time.
Into system, autotuning reopens again, I close it. Another BSOD.
Since then, I get BSODs whenever the computer exerts itself.
I've tested this by Rendering in Autodesk Maya, which should work on any machine without causing a BSOD no questions asked.
Think of rendering as a stress test, just using all the juice available towards a lengthy process. It uses the CPU, but not the GPU as far as I'm aware.
It's standard in the CGI industry for computers to do this for days if not weeks non-stop.
My computer would now give me a BSOD after 2 minutes of rendering.
Tested rendering a different Maya scene from an older project just to make sure it's not that.. had to ramp up the render settings to make it a long enough render to prove it, and the problem still persists.
Same exact copy of Maya used on other machines has not had this issue over the past year, nor have I ever heard of anyone having this problem due to this software, which is used primarily for the CGI in most feature films, definitely not a random small time piece of software that could be the issue.
It's quite safe to say that modern games or benchmarking software would also get a BSOD, my CPU should be able to go flat out.
CPU reached roughly 75 degrees rendering, 28-35 idle.
Reapplying heat sync made that roughly 70 max, 23-32 idle.
It would not cut off while heat was still rising, but level out there after about 30 seconds.. after a few minutes it would give me a BSOD.
Restored BIOS to defaults.
No change.
Uninstalled EasyTune
Reset CMOS.
Could render for 40 minutes sometimes, 5 minutes other times, such was 50/50.. but still BSOD.
Tested with some old DDR2 RAM which definitely works on my other much older machine which can render the same thing (though slower) without any issues.
BSODs got more frequent (but still never while idle, just while rendering larger more intense scenes, couldn't render a single frame if it took more than 2 minutes (some frames can take up to an hour or longer to render)
Installed clean system on a clean drive, no software or drivers except Maya to test it.
Problem persists.
If you have any idea what's wrong with my computer, I'd really appreciate the input!
Do you know if it's either my Motherboard or Processor, and how should I go about claiming whichever it is on the warranty?
I am completely broke from buying this thing and can't afford another compatible CPU to test it with or any technical support in a shop or anything.. I'm completely broke, not eligible for financial support from this country's government, and need this computer to work to earn more money, so specialist help is quite out of the question, your advice here is pretty much my last resort. If I can't fix this I'm screwed.
Thanks for your time,
Tony |