Problem with stand-by--help!!

bovinda

Senior member
Nov 26, 2004
692
0
0
A computer I just built has a problem with stand-by mode--sometimes it won't come out of it. When I push the power button to get it out of stand-by mode, the PSU comes on and I hear the fans start, but there's no video signal and the LEDs on the front of the case flash on for a moment then stay off. I can't get it to shut down by holding in the power button or anything else, I just have to reset it.

Is this a problem with AMD 64s? I had the same problem on another AMD 64 system, although less regularly. Has anyone had this problem?

Here are the specs for the machine its happening on now:

AMD 64 3200 (90 nm) socket 939
MSI Neo2 Plat
1 Gig Corsair Value Select RAM
BFG NVidia 6800 OC
Antec Sonata case with 380 watt Truepower
Viewsonic Optiquest 95 monitor
Windows XP MCE 2005

I have it set to S3 mode for stand-by.


The machine it used to happen on (hasn't happened since I switched the monitor to the one I just built):
AMD 64 3400 (130 nm)
Gigabyte NForce 3 150 Socket 754
1 Gig Corsair RAM (CMX?)
Radeon 9800 Pro 128
Antec 480 watt PSU
Windows XP Home

This machine is also set to S3 mode for stand-by.



Anyone have any experiences with this, know what's causing it, or have a solution?

Thank you,
Jeff
 

dataxpress

Banned
Jan 7, 2005
257
0
0
Set it for S1 standby mode. Works for me.

Also, it takes the power button to resume sometimes

unless you're doin it Keyboard98 style, which is pimp ;)
 

bovinda

Senior member
Nov 26, 2004
692
0
0
Is there any fix to this with S3 though? Or is it just an inherent flaw of S3 standby? I like S3 because all the fans shut off when it's on standby. Is switching to S1 the only fix?
 

drpootums

Golden Member
Oct 22, 2004
1,315
0
0
as soon as i installed my MX420 (old computer...dont like to think about those days...) my standby sounded like ur's did (went off, sure, but wouldnt come back on). I dont really have a fix, i just got a new one...
 

bovinda

Senior member
Nov 26, 2004
692
0
0
Hmmm...I've had the same problem on two computers now, but the only thing they've really had in common was the monitor (Viewsonic Optiquest 95) that was plugged into them both. Does anyone think that could in someway have something to do with it? And if so, is there some possible solution?