• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Moved to another case, now getting internal cpu error code

Thought this is apropos:
its-alive.jpg
 
That was my reaction when the monitor kicked on
 
BarbaricSoul said:
another update, it appears one of the sticks of vengeance Blue RAM went bad, tested both stick individually, one worked, other produced the errors from earlier.
Click to expand...

This could be a good thread to quote in future for people with similar problems. Everyone should keep this in mind for future! Unfortunate barbaric had to deal with the panic associated with expensive borked hardware though!
 
Panic never really kicked in. I guess because I just couldn't accept that I fried the board some how. Replacing RAM, PFFFFT, I'll waste more money than that tonight at the bar.
 
It's so easy though to get caught with the "new" problem and try to fix it, without returning to a "known good state" and taking one step at a time. We've all done it. We get tunnel vision. The wise ones turn to TPU. ;)
 
BarbaricSoul said:
another update, it appears one of the sticks of vengeance Blue RAM went bad, tested both stick individually, one worked, other produced the errors from earlier.
Click to expand...
Unfortunately I didn't run across this thread soon enough, or I could have told you that's likely the problem.
The RIVE threw error 5A at me when I put in the 4930K and put in my backup RAM to test, perpetual boot cycling, all of that. Turns out the BIOS didn't like that RAM, so I had to run my precious Samsung HYK0s for the initial OC. When I updated to a more recent BIOS, the RAM in question worked just fine.
On these Asus X79 boards, it seems 5A has to do with the IMC specifically.
Sorry it turned out you had a bad stick, but I'm glad your rig is back up and running!
 
RAM errors.... it reminds me of any old DFI Lanparty old board... it could boot any default setting. :D

Nice, didn't the RAM OK button help? It usually kills off bad RAM slots?
 
BarbaricSoul said:
Panic never really kicked in. I guess because I just couldn't accept that I fried the board some how. Replacing RAM, PFFFFT, I'll waste more money than that tonight at the bar.
Click to expand...
One stick? Wow could have been allot worse. RCoon is right about this thread. I would never have thought about it. How was the bar?:toast:
 
You must log in or register to reply here.
Back
Top