Replaced every part, no improvement. Freezes and Restarts pre-and-post OS Launch

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
System:

MoBo: ASRock Z77 Extreme4 LGA 1155 Intel Z77 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard
GPU: GIGABYTE GV-R795WF3-3GD Radeon HD 7950 3GB 384-bit GDDR5 PCI Express 3.0 x16 HDCP Ready CrossFireX
CPU: Intel Core i5-3470 Quad-Core Processor 3.2 GHz
PSU: Corsair CX750 Builder Series ATX 80 PLUS Bronze Certified Power Supply
RAM: G.Skill Sniper Series 8 GB Dual Channel Memory Module
HDD: Seagate Barracuda 1 TB HDD SATA 6 Gb/s NCQ 64MB Cache 3.5-Inch Internal Bare Drive
OS: Windows 7 - 64 Bit


For some reason the system keeps restarting after "x" amount of time. System will be running just fine, and then without warning either freeze up and then restart, or just restart. Its usually a short amount of time - anywhere from immediately after POST to 7 hours later. But there's no warning, no BSoD, just... almost as if I hit the reset button. The freeze is the only warning I get when it occurs.

This will occur whether the system is running during OS operation, or just sitting in BIOS, or just running Memtest.

If I'm running memtest - just happens to be a way to monitor the uptime of the system to see how long until it does its reboot - then when it does freeze, the little "+" symbol in the top left will still blink for a short bit even after all else has stopped before the system reboots.

However, there is the Event Viewer log that clearly defines it as an error if it runs in OS - just non specific as it says power was lost.

I'd like to backtrack a bit by saying that I already dealt with this problem before. Had a mobo with slightly bent pins. Sent it back, got a new one and a new CPU just to make sure all good.Replaced the PSU because we figured "Hey, 600W might just not be enough, let's return it and get a 750"

Nothing is overclocked at all, it's all stock and default.

When I got the mobo back, the CSR had emailed me the following:
"Our technician tested the replacement under below conditions, and it passed.

Under Windows
BIOS version was updated to the latest version.
LAN, sound, and video
"

Updated all drivers, ran without the video card and swapped ram sticks. No improvement.

At one point, I figured that it might be the PSU still, so swapped my working one into it, and it still failed. Even went so far as to think that was just the wall socket so moved to the socket where my own build is connected, and it still failed.

Took the entire build to a computer shop for diagnosis. They found a bad stick of ram, but I told them to keep looking into it because issue happened with both sticks regardless but to toss the bad stick anyways. Ended up finding that the processor was bad - something about the northbridge connection.

Replaced the processor again.

Same issue.

As a last resort, thought that somehow that the harddrive itself might be messing up, almost impossible since crashes before it's used to my knowledge, but why not give it a try: removed harddrive. Still same issue.

I've literally replaced every single part on this build at least once, and its the same exact issue. I thought that when Asrock sent back a motherboard I got the same one that just had been repaired, but different serial numbers.

Anyone able to provide some insight or something I may be overlooking? Been trying to figure this out for over a month now. Asrock and Newegg gave me the runaround about the motherboard and took forever to replace, and I'm so tired of pulling my hair out trying to figure out whats wrong.

Thanks
 
Solution
I am now at a loss. I do see that there were suggestions regarding ram and the hard drive above. Is it possible for you to test the ram in a different rig? Do you have a different hdd that you could do a fresh install on?

The ram and hdd are the only areas to yet be eliminated. I would start with the hdd - if you can get the system up long enough to do a complete disk check. Also, if you can run a prolonged memtest on the ram, that might be helpful.

Last question - is your windows install coming from a store bought disc, or are you using a download on a usb? If you downloaded, did you do a checksum to insure the download was not corrupted? If you are using a store bought disc, try downloading the iso from HERE, do the...
It's possible that the faulty cpu caused issues with both motherboards. If I am reading your post correctly, you replaced m/b 1 with m/b 2 and used the original processor which you determined to be faulty after installing on m/b 2. When the issue returned with m/b 2, you then replaced the cpu.

At this point, I would be leery of both the new cpu and m/b 2. If the problem originated with cpu 1, which caused both m/bs to die, it's possible that the failure of m/b 2 may have hosed cpu 2.

Mark

 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Harddrive I assume is fully functional. The issue occurs with or without the harddrive present. I actually removed it completely last night just as a last resort and planned to run diagnostics on it in the case that the build was active longer than a half hour, but it failed within a couple minutes.

And as far as the mobo/cpu failure: I thought that might have been the issue as well. However, I replaced mobo1 and cpu1 at the exact same time, so there was no crossover. I couldn't figure out which was bad, so just replaced both.

Mobo1 and CPU1 went together, then Mobo2 CPU2 together, and finally Mobo2 CPU3 went together. So, the only connection would be that of MB2 and CPU2/3. But, issue itself hasn't changed since the very first setup of the system.
 

ktolo

Honorable
Jul 19, 2012
457
1
10,960
It sounds like a memory problem to me. But in your original post you mention running Memtest, so i'd assume that any problems would have been picked up by this.
I'm yure you're already done so, but what about the memory settings in the BIOs, is it getting enough voltage? are the clocks right etc.?
Sorry i can't offer any more insight than this. I do feel sorry for you though!! I know what that's like. I built a system years ago, and it turned out my ram was incompatible with my MOBO, it gave me nightmares until i sent it back and got a diff brand.
Not saying this will also be the case here though.
 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Memory settings in the BIOS: I haven't checked since the first mobo, but settings were fine then. I don't assume that the second would be any different even though the second was updated to latest version and such by Asrock, but I'll look into it. RAM is compatible, actually checked that out last night as well just to make sure.

I have ran it completely outside the case, yes. I thought that it might have been the issue as well, but from what I've read (Which isn't much on this topic) that the case serves almost only to have a more available power/reset button, give you a casing, and provide fans.
 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Not sure how to boot via shorting the power pins, but there is a power/reset button actually on the m/b. I've removed all connections from the case itself. That the method you're talking about though? If so, will update when I know something.
 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Let it run for a while, and sadly, even without the switches, it restarted. I thought it was going great, but... alas, my hopes got too high and had to be shattered.

Anyways, ground switches apparently aren't the cause. Any thoughts?
 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Bit of an update, I do have the option from ASrock to rma the mobo again. I don't think it'll help any as I've had this issue with the previous m/b.

However, I can't think of anything else that might be causing this issue. Removing the switches from the case to m/b didn't change anything.

Help?
 
I am now at a loss. I do see that there were suggestions regarding ram and the hard drive above. Is it possible for you to test the ram in a different rig? Do you have a different hdd that you could do a fresh install on?

The ram and hdd are the only areas to yet be eliminated. I would start with the hdd - if you can get the system up long enough to do a complete disk check. Also, if you can run a prolonged memtest on the ram, that might be helpful.

Last question - is your windows install coming from a store bought disc, or are you using a download on a usb? If you downloaded, did you do a checksum to insure the download was not corrupted? If you are using a store bought disc, try downloading the iso from HERE, do the checksum and use that to install (this is perfectly legal - you would use the product key from your purchased dvd).

Mark
 
Solution

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
The ram was tested at the repair shop. Apparently it was under memtest and ran fine for them. From what I gather, they must've ran it under a different rig, but I will put it in my personal one later today and let you know.

Harddrive, I don't feel is the issue. Unless it could have damaged the m/b or processor. Had this issue occur without the harddrive even connected. I will run disk check when I get back to the build though.

Windows was downloaded from the Microsoft website I believe, and burnt as an ISO to a disc. Couldn't find my original install/repair disc, so had to make one.

Will update with my results later today.
 

alexoldshane

Distinguished
Mar 13, 2009
107
0
18,680
Update:
So, after trying everything I could think of, decided to replace the RAM with some in my own build.
Apparently Memtest can't catch everything. Has been up for about 12 hours now, running perfectly.
Out to go get some new ram today. Probably a heatsink too. Thanks all.