Mother board power surge protection reseting my rig?

[Typolo]

So I don't see any signs of a power surge in my home and my power is relatively reliable.

My system has reset to a black screen with with white text. it tells me that the motherboard has reset the system to protect it from a power surge.

The first time I thought it was because I kicked the power strip that my power supply is plugged into, but the 2nd time I know it wasn't that.

I have an HX650 from corsair. Calculators rated my systems max power draw as ~625 watts with a 4770k and r9 290. I realize that amd recommends 700 watts. Should I use the HD4000 graphics from intel until I upgrade to something around 700-800watts?

Also I was going to give my psu to a friend when I upgrade, but now i'm not sure if it will work properly /:

My motherboard is the maximus vi hero.

So how could I find out if this is power supply, my power use, motherboard, or something else I'm unaware of?

 

[gokul36]

Full system specs

 

[Typolo]

4770k
R9 290
Maximus VI Hero
2x4 gigs cl 7 @ 1600 corsair vengeance ram
HX 650 psu
Windows 7 home premium 64-bit on a Samsung 840 evo ssd
WD 1 TB Black HDD

On cooling I have stock with tx-4 thermal paste and 4 case fans.

My power supply is plugged into a strip with my monitor. The strip is then plugged into an older surge protector along with my wifi/ethernet modem. I'm using the bus strip because only two plugs on my surge protector will power stuff.

 

[Typolo]

I was gone for awhile so I couldnt experiment with this the past few weeks.

I have removed the surge protector and bus strip from the equation and the problem persists.

So now my primary concern is wether it my psu is the actual source of the problem. I have found others with the same problem under Related resources: that I see below on this page. One end of the 20+4 pin connector seemed loose, so I pushed it in.
I don't want to try disabling the surge protector like others suggested in other posts in case it actually is a psu problem.

Ill try out my machine again today. If it happens again I'll see if any of my friend's PSUs are sufficient to work in my rig. If the surge protector goes off with theirs as well I will try disabling the surge protector in the bios. (In which case I will need to buy a new far beefier surge protector to protect my system).

If it does not go off with theirs plugged in then I'll try returning the psu to corsair under warrenty since I can't RMA through newegg now.

If anyone reads this can you please leave a response to see if this looks like a solid plan of action? this was my first build and first time having a serious problem. Its very scary

 

[Typolo]

PS: i figured I'd leave a picture of the screen that came up.

 

[ko888]

The the problem happen when the CPU isn't overclocked?

 

[toyftw]

PS: i figured I'd leave a picture of the screen that came up.

Hi - You have a fairly common issue with Asus mobo's that contain the anti-surge feature, even Asus
phone support has advised some users to disable the anti surge detection in BIOS.

 

[Y0GI]

I would try removing the R9 290 and see how it does with the integrated graphics for a while.

Yogi

 

[Typolo]

The the problem happen when the CPU isn't overclocked?

At first I was overclocked to 4.2GHz with AI suite 3. I was stable using this, but after adding the 290 into the rig I had thermal issues so I replaced the thermal pastes on cpu and gpu. I lowered it later to 4.0 using AI suite 3 before I decided to uninstall it since people have said it can lead to instability issues and such. After unitstalling I tried the cleaner from ROG but it kept reporting an error.

when I entered bios from the screen I posted I manually changed it to 3900MHz by changing the 40 to a 39. I entered windows and then powered down. I'll check now if its stable at the 3.9GHz with the power pushed in further. (it wasn't disconnected, just loose).

 

[Typolo]

Hi - You have a fairly common issue with Asus mobo's that contain the anti-surge feature, even Asus
phone support has advised some users to disable the anti surge detection in BIOS. [/quotemsg]

Thanks, I'll try that after I determine nothing else is causing a problem. It would be a real shame if I disabled it and everything got fried because it was actually working properly.

 

[Typolo]

PS: i figured I'd leave a picture of the screen that came up.

Hi - You have a fairly common issue with Asus mobo's that contain the anti-surge feature, even Asus
phone support has advised some users to disable the anti surge detection in BIOS.

I would try removing the R9 290 and see how it does with the integrated graphics for a while.

Yogi

I have it running at the moment. I don't think that I'm drawing to much power with the 290. I also know that it runs fine without it as I had it running without the 290 for 2-3weeks. I didn't have any problems (except thermal issues I fixed) for several more weeks (nearly a month) after I added the 290.

 

[Y0GI]

If it runs fine without the R9 290, but sounds the alarm with it, then it would seem that the MB is alerting to an actual problem and not just giving a false alarm.

Your plan to try other PSUs seems like a good one!

Yogi

 

[ko888]

ASUS Anti-Surge doesn't detect voltage surges on the AC power line. It only monitors the DC output rails voltages' for anything that goes out of spec.

Have you monitored the PSU's output voltages to determine if this is happening?

 

[Typolo]

ASUS Anti-Surge doesn't detect voltage surges on the AC power line. It only monitors the DC output rails voltages' for anything that goes out of spec.

Have you monitored the PSU's output voltages to determine if this is happening?

I have not. Would I do it like this?

http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html

I'm doing some basic stuff right now and it seems to do fine. I'll run BF4 in about half an hour to see how it does under load. If it doesn't act up today I'll assume it was just the lose 20+4 connector.

 

[Typolo]

If it runs fine without the R9 290, but sounds the alarm with it, then it would seem that the MB is alerting to an actual problem and not just giving a false alarm.

Your plan to try other PSUs seems like a good one!

Yogi

It just is that it worked fine with it as well. I might try that next weekend if I can't find a better solution.

 

[ko888]

ASUS Anti-Surge doesn't detect voltage surges on the AC power line. It only monitors the DC output rails voltages' for anything that goes out of spec.

Have you monitored the PSU's output voltages to determine if this is happening?

I have not. Would I do it like this?

http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html

I'm doing some basic stuff right now and it seems to do fine. I'll run BF4 in about half an hour to see how it does under load. If it doesn't act up today I'll assume it was just the lose 20+4 connector.

You can use a utility to monitor and log voltages from the motherboard's sensors. The ASUS Anti-Surge feature uses the motherboard's sensors to monitor voltages so this is what you want to track.

You can download and run the freeware utility HWiNFO64. Set it to use sensors and turn on logging. You can also change the scan interval.

http://www.hwinfo.com/download.php

 

[Typolo]

Ok, I already have that and I started a log with the scan interval at 200ms (instead of 2000). How do I find the PSU output voltage from that? would I just add all the values measured in Volts together?

 

[ko888]

Ok, I already have that and I started a log with the scan interval at 200ms (instead of 2000). How do I find the PSU output voltage from that? would I just add all the values measured in Volts together?

You can set the utility to monitor only the motherboard voltages since that is all you're concerned with for troubleshooting this problem.

Since you set the utility to log an entry every 200ms you will have five lines of data created every second in the log file.

Run some testing with the R9 290 installed. When the system crashes and reboots, hopefully the log file remains. You want to check the log file for the +3.3V, +5V and +12V rails voltages to see if any of them went out of spec. The file is actually a .CSV (i.e. comma separated values) file meant for viewing and analyzing within a spreadsheet application like Microsoft Excel.

+3.3V must remain between +3.14V and +3.47V

+5V must remain between +4.75V and +5.25V

+12V must remain between +11.40V and +12.60V

Voltage values outside of these ranges are considered out of spec. That's what ASUS Anti-Surge would be detecting.

 

[Typolo]

Ok, I already have that and I started a log with the scan interval at 200ms (instead of 2000). How do I find the PSU output voltage from that? would I just add all the values measured in Volts together?

You can set the utility to monitor only the motherboard voltages since that is all you're concerned with for troubleshooting this problem.

Since you set the utility to log an entry every 200ms you will have five lines of data created every second in the log file.

Run some testing with the R9 290 installed. When the system crashes and reboots, hopefully the log file remains. You want to check the log file for the +3.3V, +5V and +12V rails voltages to see if any of them went out of spec. The file is actually a .CSV (i.e. comma separated values) file meant for viewing and analyzing within a spreadsheet application like Microsoft Excel.

+3.3V must remain between +3.14V and +3.47V

+5V must remain between +4.75V and +5.25V

+12V must remain between +11.40V and +12.60V

Voltage values outside of these ranges are considered out of spec. That's what ASUS Anti-Surge would be detecting.

Ok, I'm not sure where to find these voltages. In the Sensor status under 'GPU [#0]: ATI/AMD Radeon R9 290: CHiL/IR PMBus- GPU Core' there is the 'GPU VRM Voltage in (VIN/+12V)' it reads current 11.969V Minimum 11.938V Maximum 11.969V

That's all I find labeled as +12V

All I found labeled +3.3V was under 'ASUS EC' for 'VGA +3.3V AUX' it read current 1.769V minimum 1.750V Maximum 1.775V

I cant find the +5 reading anywhere and I'm not sure if I'm reading the right stuff for the others...

 

[Typolo]

well each core has a max values of 1.195V, 1.193V, 1.192V, and 1.192V, which totals to 4.772V Max
total of the mins are 2.789V which is way under the +4.75V

There are a bunch of voltage readings under Nuvoton NCT6791D such as Vccin alot are near .5 or 1V. 2 of them are just over 3V

Thanks so much for the help, I'm kinda lost on this haha

 

[ko888]

well each core has a max values of 1.195V, 1.193V, 1.192V, and 1.192V, which totals to 4.772V Max
total of the mins are 2.789V which is way under the +4.75V

There are a bunch of voltage readings under Nuvoton NCT6791D such as Vccin alot are near .5 or 1V. 2 of them are just over 3V

Thanks so much for the help, I'm kinda lost on this haha

This is an example from my system:

 

[Typolo]

Mine isn't listing a +12V, +5V, or a +3.3V.

Could you have possibly renamed yours?

I do have a 3VCC that 3.376V for all values except minimum which is 3.360V.
There is also the 3VSB that reads 3.424V for all values.
Then I have VBAT that reads 3.280V, 3.820V, 3.296V, and 3.280V

Those are the only things that look like they could be the +3.3V. Since I see VBAT and 3VSB on yours as well I'm guessing 3VCC is the +3.3V?

I have nothing close to 5V or 12V in that section. I do however have the readings just under 12V for my 'GPU VRM Voltage in (VIN/+12V)' as I said earlier.

 

[Typolo]

If it matters, I am using version 4.30-2060 of HWinfo64

Should I use 4.31-2065?

 

[ko888]

I haven't changed anything. Those are all the default names used by HWiNFO64.

The version I'm using is also HWiNFO64 v4.30-2060.

You can try the Beta version if you want to.

 

[Typolo]

Hmm well I've been on here most of the day now and I haven't been reset. This is much longer than I've had it ever run since the problem first occurred. I guess it was just the loose connector

I'm going to re-install ai suite iii because my fans are driving me crazy! I'll go into the bios later on to bump up the overclock to were it was. If it still works I think I can call this officially closed!