Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: bobwadd on February 25, 2011, 11:38:01 am
-
Hi, I have a GA-H55-USB3 (rev. 2.0) in a new build with no video on resume. Latest BIOS ver F7. I have tried both S1 and S3 BIOS settings. Have same problem with both Standby and Hibernate. Monitor is hooked up to 15-pin D-Sub connector. System appears to come out of both as there is hard drive activity, just no video. I have searched the web and tried many suggestions but nothing works.
Thanks in advance, Bob
-
Sorry, forgot to mention I am running WinXP Pro.
Thanks
-
Gigabyte wants me to RMA the MB. I really don't think this is a hardware problem.
Still waiting for suggestions, Bob
-
Hi and welcome to the Gigabyte Forum.
Sorry that nobody answered you so far, you must have slipped through the net.
It is possible that it is your monitor that is at fault in that it is not switching back on when receiving the returned signal. Try switching it off and then back on after you have resumed from a sleep state.
-
The system wakes the monitor bach up. There is just no video.
I tried something new this morning. I set up a remote access server on the Gigabyte system. I suspended it then I woke it up. It appeared to wake up (hard drive activity) but I could not access it through remote access. I made sure the RA worked before I placed the system in S3 mode. The RA software could find the system but could not connect.
Bob
-
In that case it sounds like the system isn't waking fully from S3 sleep. I take it that it responds ok in other sleep modes ?
-
Just tried S1, same issue. Monitor is set to turn off after 15min. It wakes up fine from that.
-
These power saving modes are a pain quite often. I would advise you to take out a ticket with GGTS in case nobody on the forum can help you as they take a while to answer often.
Just enter your email address and click on the language of choice.
GGTS http://ggts.gigabyte.com/
-
Took out a ticket on Friday. They want me to RMA the board. I really don't think it's a hardware problem though.
Bob
-
Personally, Bob I would have to agree with you. Sometimes I think they use this as a stock answer when they don't know what else to say. I would have thought it was more likely a BIOS issue.