ASUS Z97-A Surge warnign

wolfie138

wolfie138

wolfie138

Soldato
Joined
8 Jun 2013
Posts
4,571
Hi all,
just looking for thoughts on an issue i got yester and today.
built my system in March;
Z97QA mobo
980 Strix
16gb Kingston HyperX Savage
Corsair RM750 PSU
system is plugged into a surge-protected multiplug along w/ my Clip+/Speakers for music.

Have done long days on it so i know stability seems good, and it's not being taxed as i'm only Photoshopping etc.
anyway, yester i was PSing, and the thing just went off, rebooted, adn there's a message saying ASUS anti-surge had detected an issue on a previous boot ~ which is odd, cos the thing had been up and running about 90 mins or so, not just booted. had a look at some settings, nowt unusual, carried on, same thing happened about 40 mins later.

this morning, it happened w/in about 20 mins of starting up. i switched off my Clip/speaker sockets to see if i could hear any sounds that might indicate anything, and abot 2 hours later nothing had happened so i put the music back on, tried a bit MS Word and Blender, and was still ok.
nothing else (lights/music etc) seemed to blip, that i could see so i'm wondering what you all think? the obvious choice would be the PSU but it's brand new and quality, and isn't making any noises etc. Had no other issues at all since i started using it.
Can't find anything about a log that might give more info, on thread on techsupportforusm says ASUS just advised turning the surge protection off. i believe the Corsair has it's own surge protection in it.
TIA
 
Just turn AntiSurge off in the BIOS. It causes more issues when enabled. I have had several Asus boards over the years and it is one of the first settings I disable.
 
I had this with my Asus board last month. Was fine for the 5 months I had it. Sent it back for a replacement.

Didn't feel happy disabling AntiSurge when my other computers are running fine with it enabled.
 
Cheers guys, i'll monitor it over a few days and see if it keeps up. i'm veering more to the disable side of things though, if it was an old PSU etc i#d definitely err on the side of caution but as it is, and given number of disable-it advices on other boards, some from ASUS themselves, it seems the way to go.
 
happened again tonight so i've switched off the option, but i was wondering if there's a monitor software thing i could run while i'm working that would log the power and allow me to see if there is actually anything going on?

have to say i'm utterly hacked off w/ ASUS "help" though, goddamn form wants every damn detail of my system, i filled all the cac in and it pops up "cannot be blank!" even to everything is filled in >:-(
 
Okay, ran an hour last night, had it on about 90 mins today and the thing shut down. i have a dmp file and an xml file thing that windows pointed me too but since the machine isn't hooked up to the net i couldn't check them out.

what's my next step, just return the PSU to OC? i've read stuff about using multimeters to check but i've not got one and haven't a clue how to use one, and if i did would i have to sit looking at it for an hour or more until something happened? would CPUID's HWMonitor be any good?
is there anyhting else i can check? some forum said to check for loose connections but the puter hasn't been moved since i put it in the room so nothing should have dislodged.is there any way of telling what part of the PSU is causing the issue, ie what item might be causing the prob?

TIA
 
Last edited:
so no replies to my last post, bit further update, i'm still getting the issue;
i ran a few things last week, a Fur shader test thing and Prime 95 for a bit - both seemed to do ok and didn't cause any issues. i then left the machine running with CPUID's hardware monitor thing running, and 4 hours later it was still going, nothing untoward seems to have happened as regards power etc, the voltages etc all seemed ok.
however, i fired up today and have been doing about 45 mins of Blender, nothing stressful, and the thing shut off again. so i've unset the auto-restart thing but and still no further forward as to what to look for.
i checked the PSU connections and cables to the mobo, all seemed tight etc, nothing gave obvious movements.
Any thoughts/pointers? a guy on another forum said to switch off the auto restart in advanced system properties, how would that help?


quick edit - i did have a look at event logs, teh only thing noted was something about AS Disk Unlocker reporting an invalid current state 11 ~ no idea if that's a red herring or not, google isn't helping much.

TIA
 
Last edited:
Could be the ram I guess. Is this the ram you are using?

Kingston HyperX Savage Red 16GB (2x8GB) DDR3 PC3-19200C11 2400MHz Dual Channel Kit (HX324C11SRK2/16)
https://www.overclockers.co.uk/showproduct.php?prodid=MY-204-KS

Look in the bios to see what the DRAM voltage is set to. Apparently it needs to be between 1.50-1.65v. Have you enabled the XMS profile?

*edit* just noticed you built in March. Has it been stable up until now?
 
Last edited:
hi,
yeah that's the RAM.

i'll admit my ignorance in not knowing what an XMS profile is (or XMP, if you meant that?) :-(
everything on the BIOS will be out-the-box, most of the stuff i've looked at is set to Auto etc.
and yeah, as i mentioned the machine was all good up to a couple weeks ago. it's my Blender/Photoshop machine so it's use is only when i have something to work on; ie, there's times when it won't be on for a few days/couple weeks, then when i'm working on a pic/model it'll be on for a good number of hours a day at the weekends, a couple hours a day during the week. nothing that's stressing/thrashing the machine though.
 
Sorry yes I did mean XMP, whoops :)

I thought you had already tried another PSU in the system but can't see any mention to it. Have you got another one that you could test it with and see if that removes the issue?
 
nah, not got another PSU. a guy on another forum has suggested turning off auto-restart in order to get a BSOD instead, mebbes that'll give a bit more info, so i guess that's my next step.
 
hi again. update, from the machine crashing twice on me just now. the first time was about a couple minutes after booting, after i was checking my Comtrol Panel etc, and it went straight into reboot, as i'd neglected to turn off the ASUS surge protector as well as the Auto-restart thing in Win7. after 20 mins or so, it happened again. there was no BSOD, machine went black, and appeared to go into sleep mode rather than full off, as the Noctua was still spinning until i pressed the power button adn shut down. after rebooting, i had a look at the Event log, and there seems a couple more things that i never noticed from last time; hopefully they make sense to you as they mean little to me.
the first couple that i noticed said
"ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 323K
_AC3 = 318K
_AC4 = 313K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data."

"ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.
_PSV = 0K
_TC1 = 0
_TC2 = 0
_TSP = 0ms
_AC0 = 353K
_AC1 = 328K
_AC2 = 323K
_AC3 = 318K
_AC4 = 313K
_AC5 = 0K
_AC6 = 0K
_AC7 = 0K
_AC8 = 0K
_AC9 = 0K
_CRT = 378K
_HOT = 0K
_PSL - see event data."

seemingly tied to these were
"Processor 0 in group 0 exposes the following:

2 idle state(s)
16 performance state(s)
0 throttle state(s)"

"Processor 2 in group 0 exposes the following:

2 idle state(s)
16 performance state(s)
0 throttle state(s)"

etc etc, one for each of the 8 cores. as far as i can tell from a quick goog, these are ok (? at least, the "ok" bit seems to suggest it, as on another forum the guy was getting temps listed in the PSV bits that they said meant he was overheating).

two others are:
"kernel p-p
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&1."

and
"driver frameworks user node
The UMDF reflector was unable to complete startup because the WUDFPf service was not found. This service may be started later during boot, at which point Windows will attempt to start the device again."

not a clue what that means but file.net says it's not essential and causes few probs.

aside from all that, when i booted back up i got the pop-up saying Win had recovered etc, (i've saved off the dmp file again and the xml report thingy) and it gave a couple more details. it said the event name was Blue Screen (even though as i said i didn't actually get one), and there was a bit below saying it had recovered from a bugcheck and mentioned 0x00000116 and a load of hex stuff i didn't copy down.
some goog stuff points to a GPU driver, i have the 344 version on the discs whcih came w/ the card in March, which were, IIRC the up-to-date ones. if this is the issue, however, i'm unsure as to why i wasn't getitng this from the get-go.

the only other odd thing i noticed was that the puter time was five minutes fast, so i rest it. this might mean nowt.

ta for reading.
 
was hoping someone might have been able to suggest something :-(

anyhow, in case anyone's still reading, i've been pushing on a bit trying to sort this issue.

i installed the nVid 353.62 drivers and the IRST mobo drivers yest, and ran for about an hour with no issue until i powered off to do something else. i was running OCCT and HWMonitor and all seemed ok, except (as mentioned on someone else's thread) my 12v was showing a Min of 11.04v in the summary thing.

today i ran DXDIAG, it shows DX11 and no issues.

i ran SFC/SCANNOW, and got the message that there's some corrupt files it couldn't repair ~ what's the best way forward, a repair install? the (possible) issue with that is i don't think my Win7 disc has SP1 on, will that cause probs? i've got a crap net connection which would take forever to d/l an ISO.
i saved the CBS thing off in case it's of any use. don't know how or why these are corrupted, i scanned this machine and had no issues, and it's a far older one.

i'm still getting the messages mentioned above, re the UMDF and temp enumerators, they're not marked as Warnings etc so i'm assuming they're ok.
on this that is curious (or maybe a problem??) is i noticed the starting event says "The operating system started at system time ‎2015‎-‎09‎-‎13T09:43:33.610798500Z." ~ now, this event was logged at 10:43, is the hour difference an issue or just because the Daylight Savings or whatever hasn't been applied? i've noticed other events say things like "The previous system shutdown at 10:41:41 on ‎13/‎09/‎2015 was unexpected." in other words, showing the correct hour.
when i crashed today, i got the black screen/standby ting. seemed to take a couple seconds from pressing the button to it starting up, and after i got to the desktop i had no pop-up about the recovery/mention of the BSOD like i did last time.

is any of this meaning anything to anyone?
 
You must log in or register to reply here.
Back
Top Bottom