Sign in with
Sign up | Sign in
Your question
Solved

ASRock Extreme3 behaving extremely eratically

Last response: in Motherboards
Share
February 18, 2014 12:10:47 PM

I built a gaming computer about two months ago. It survived a move just fine, and last night I played on it with everything running smoothly. I updated AVG's free security suite and shut down with Windows updates before I went to sleep. When I woke up this morning, the computer started behaving at almost a hundredth of its normal speed, with severe lag and speed issues with even the BIOS. I can't access the BIOS menu, and System Restore is failing to operate. Any recommendations on what else I can do, or will I need to get a new motherboard?

More about : asrock extreme3 behaving extremely eratically

Best solution

a b V Motherboard
February 18, 2014 5:39:01 PM

It's slow to BIOS... That's pretty strange. Since you haven't gotten an answer yet, I'll try to help out!

Do you get any POST error messages?

Check that the power connections are well seated, specifically the ATX and CPU-power connections.
Also, check that the CPU is well seated.
Do you have a motherboard speaker? If so, take note of the "beeps" it makes. They have a significance, and can signal an error.

I find it strange that the PC boots to BIOS up in the first place.
Try removing all unnecessary hardware (HDDs/SSDs, video cards, all but one stick of memory) running MemTest86 to test the memory, one stick at a time.

Keep us posted.
Share
February 18, 2014 6:06:54 PM

No motherboard speaker, and no beeps. I left it alone for about an hour and it finally booted up. When I said BIOS, I was referring to the boot screen, not necessarily the menus and such. That said, thanks for the tips. I'll look them over when I get the time.
m
0
l
Related resources
February 18, 2014 6:08:49 PM

Also, I had Microsoft's diagnostic tool run a scan on the RAM. It reported back just fine. Still, checking all the cards can't hurt.
m
0
l
February 18, 2014 6:57:29 PM

Yeah, getting all the power connections resecured, as well as carefully removing and placing back in the memory sticks seems to have fixed it. Thanks!
m
0
l
!