• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

System doesn't resume normally - hardware?

O

Objekt

Limp Gawd
Joined
Apr 6, 2012
Messages
302
Only about a month ago, I built a brand new system using a Gigabyte GA-Z77-DS3H. Almost all is well, but it exhibits some weird behavior related to sleep/resume.

The problem is that resuming from sleep takes 3 presses of the power button, or mouse buttons, or keyboard (the latter two are optional ways to resume from sleep). On the first and second attempts, the system powers up briefly, then shuts off immediately.

Is this the way it's supposed to work? It seems very strange. Both the manual and Gigabyte's website are silent on the topic. In contrast, a system I built 4 years ago on an Asus motherboard, wakes on the first press of the power button.

I'm using Windows 7 Ultimate 64-bit, with the hardware listed in my signature.
 
Could be the operating system as I have experience the same issue with ulrimate OS, after sleep mode, it wont wake up at all, so I just have to turn it off. But I could be wrong.
 
Does it wake up with three fast taps on the keyboard? If you can just tap 3 times fast that would be a nice feature since it's not hard to do and it would prevent unintended wake-ups. If it's really 3 tries that's a bug/bad feature.
 
Actually it's completely unresponsive to keypresses. That may be normal behavior, because I have the keyboard connected via the PS/2 port rather than USB. I'm pretty sure the "wake on input" thing only works if the input is from a USB device (such as mouse or USB keyboard).

Quite by accident, I discovered that I was misdiagnosing the "resume from sleep" problem. It actually is not taking 3 presses of the power button to wake up. Here's what really happens: I press the power button. System briefly powers up, then shuts down. If I leave it alone, it will again briefly power up, then shut down. Occasionally, it will stay on after the second attempt, and eventually resume Windows 7.

As of yesterday, I've been getting bluescreens and other bad behavior. It started while I was playing Crysis 2. First there was a sudden freeze-up, with "stuck" audio, then bluescreen and the system rebooted itself.

Sometimes it will restart normally. Other times, the system powers up, issues a long string of fast beeps, then shuts down again. It will repeat that process for a while (maybe as long as I let it?).

So I have some big problems going on here. I think I'll file a trouble ticket with Gigabyte, because I don't know what else to do for now.
 
Last edited:
It has the latest one, F5, released just a couple of weeks ago.

I installed that last week. Good thing I did. In the state the system's in, I wouldn't want to try flashing BIOS.
 
Might be a power supply issue.

I had a spare PSU, though only 430 W, so I swapped it out (existing one was rated at 520 W).

That didn't really help at all. I'm still getting bluescreens or the repeated power cycling when I try to resume from sleep. Something is very messed up, and it isn't just the power supply.

Shortly after I wrote the above, the system stopped powering up at all. Had to RMA the motherboard. How disappointing. Guess I'll post about the RMA experience if it's especially notable.
 
Last edited:
Got the motherboard back today. Got the system back together, seems to work.
 
I've traced the original problem with resume-from-sleep down to one of my two pairs of RAM modules. By swapping RAM with another machine, I eventually determined that one of the two sets of G.Skill RAM I bought (part no. F3-10666CL9D-8GBRL) prevents resuming from sleep. The bad modules caused pretty much the same symptoms in a much older system (X38 chipset, Core 2 Duo CPU) as they did in my new system.

So it seems I actually had TWO bad pieces of hardware to start with.

The good part is, I can RMA the bad RAM without having to tear my system completely apart, and I will be able to use the computer while I wait for warranty service.
 
Ouch sorry to hear about the bad luck man. Good to see you were able to diagnose the issue with our unfortunately limited help.
 
Further good news, G.Skill issued my RMA number by the end of the day yesterday. So I'll send my (apparently faulty!) RAM out today and probably have a replacement by the end of next week.
 
When I tried to turn my system on this morning, it wouldn't. Just a long string of fast short error beeps, as occurred a few days before the motherboard died completely.

I tried all the usual tricks: BIOS update (to F6), swapped power supply, running on internal video instead of video card. None of it helped.

Occasionally the system will boot and load Windows 7...but then it will shut off at random while just sitting there (not as part of a power saving scheme), then upon trying to reboot, it will do the error beeps again. So it's pretty much useless.

This is the worst product experience I have ever had. I've had components die or malfunction before, but one RMA always fixed it. Either that or the mfg. gave me a new or refurbished replacement, which then at least lasted through the warranty period.

I'm not really even interested in doing another RMA; I'd rather have my money back and buy a different brand motherboard, like the MSI one I originally planned to buy (Newegg went out of stock on Ivy Bridge Launch day, is the only reason I didn't get that one). But a second RMA is probably the path of least resistance, so, meh, whatever.
 
Yeah a second RMA is probably your best bet. Though you could always eat the costs and get a different motherboard altogether.
 
Danny Bui said:
Yeah a second RMA is probably your best bet. Though you could always eat the costs and get a different motherboard altogether.
Click to expand...
And this is what I've done.

Ordered an ASRock Z77 Extreme4 this morning. It should be here tomorrow afternoon. So I'll either be jumping for joy that I finally get to use all that expensive hardware that's been sitting around, or crying because there was some hidden problem with the case/SSD/who knows what.
 
Got a response from Gigabyte's Newegg "VIP" service. They think I still have bad RAM. I explained that I already tried switching out the RAM entirely. Instead of the G.Skill which I bought for the new system, I installed some OCZ DDR3 that I've owned for years, which I know works. Had the same problems. Which is why I think the motherboard is still faulty.

We'll see what they say. My new ASRock motherboard should arrive within the hour, so it's not as if I'm in a gigantic hurry to do another Gigabyte RMA iteration.
 
Objekt said:
It has the latest one, F5, released just a couple of weeks ago.

I installed that last week. Good thing I did. In the state the system's in, I wouldn't want to try flashing BIOS.
Click to expand...
Check what version you have and tt least check the release notes on all versions released after yours. Often time 'resume' issues are caused by motherboard problems.

Also run Windows Update and make sure you have SP1 and any recommended updates that affect resume/sleep installed.
 
You're late to the party. It's understandable, though - I've had about half a dozen threads about this or something similar, so it's probably really hard for everyone to keep up.

As stated above, I figured out that my original resume-from-sleep issues were caused by one or more bad sticks of RAM. I RMA'd the pair and have been using the other pair (two, 4 GB) since.

As a separate issue, the Gigabyte board then began failing to boot. It wouldn't even POST - rather, it would power up, emit error beeps, power off, then do the whole thing over again a few seconds later. I RMA'd it, Gigabyte fixed it, sent it back. I used it for not quite a week, when it started doing exactly the same thing again.

Gigabyte thinks the remaining 2 sticks of RAM are somehow causing my GA-Z77-DS3H to fail to POST (note that it's impossible to do anything in Windows when the system won't POST, let alone boot...).

That doesn't seem to be true. For one thing, the board did work for almost a week after it got back from repairs. For another, I just got another motherboard, an ASRock Z77 Extreme4, and it's working fine and dandy with the 2 sticks of G.Skill RAM that Gigabyte thinks may be faulty.

Sleep/resume works normally on the new new board, and it's astonishingly fast! Perhaps because I'm using an SSD for the OS drive, that sucker "sleeps" within seconds of clicking the command, and "wakes" just as quickly.

I didn't even have to reinstall Windows 7. It booted right up on the new motherboard (the ASRock), automagically detected some devices & installed drivers. I do need to install a few others (for e.g. the wired NIC), but so far no bluescreens or boot failures.

Meanwhile, I think I'm going to have to apply for a second RMA for the Gigabyte board. What a cluster f@&* that's turned out to be.
 
Last edited:
You must log in or register to reply here.
Back
Top