Reply to thread

Message

Did anyone find an answer to the blank screen on auto resume issue? I've looked through the thread, but didn't see an answer.

I'm having the same issue with MST installed, but no problem if it is not installed. I have also noticed the same problem if I have Girder installed and running, even if Girder is configured to do nothing at all. Specifically, if the PC automatically resumes from S3 standby (not tried S1 or hibernate) to do a recording, the screen stays black, and after 5 minutes (my idle time in Powerscheduler, although that may be a coincidence) the PC goes back into standby having done nothing. During this time I cannot connect to the PC using VNC, but if I press a key on the remote everything springs into life. Starting the PC from the power button on the front or on the remote works as expected.

I'm thinking it must be a hardware related issue - until recently I was running an elderly AMD 3500 cpu with Asus/Via mobo and an AGP ATI 1650XT, and everything worked fine (both MST and Girder). Due to the old mobo going toes-up I upgraded to a Core 2 Duo 4600 with Gigabyte/Intel P35 mobo and PCIe ATI HD2400XT, and now I'm having these blank screen problems.

Any clues gratefully received.

<blockquote data-quote="nfox" data-source="post: 231439" data-attributes="member: 24296">Did anyone find an answer to the blank screen on auto resume issue?&nbsp; I've looked through the thread, but didn't see an answer.I'm having the same issue with MST installed, but no problem if it is not installed.&nbsp; I have also noticed the same problem if I have Girder installed and running, even if Girder is configured to do nothing at all.&nbsp; Specifically, if the PC automatically resumes from S3 standby (not tried S1 or hibernate) to do a recording, the screen stays black, and after 5 minutes (my idle time in Powerscheduler, although that may be a coincidence) the PC goes back into standby having done nothing. During this time I cannot connect to the PC using VNC, but if I press a key on the remote everything springs into life.&nbsp; Starting the PC from the power button on the front or on the remote works as expected.I'm thinking it must be a hardware related issue - until recently I was running an elderly AMD 3500 cpu with Asus/Via mobo and an AGP ATI 1650XT, and everything worked fine (both MST and Girder).&nbsp; Due to the old mobo going toes-up I upgraded to a Core 2 Duo 4600 with Gigabyte/Intel P35 mobo and PCIe ATI HD2400XT, and now I'm having these blank screen problems.Any clues gratefully received.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /></blockquote>

[QUOTE="nfox, post: 231439, member: 24296"] Did anyone find an answer to the blank screen on auto resume issue? I've looked through the thread, but didn't see an answer. I'm having the same issue with MST installed, but no problem if it is not installed. I have also noticed the same problem if I have Girder installed and running, even if Girder is configured to do nothing at all. Specifically, if the PC automatically resumes from S3 standby (not tried S1 or hibernate) to do a recording, the screen stays black, and after 5 minutes (my idle time in Powerscheduler, although that may be a coincidence) the PC goes back into standby having done nothing. During this time I cannot connect to the PC using VNC, but if I press a key on the remote everything springs into life. Starting the PC from the power button on the front or on the remote works as expected. I'm thinking it must be a hardware related issue - until recently I was running an elderly AMD 3500 cpu with Asus/Via mobo and an AGP ATI 1650XT, and everything worked fine (both MST and Girder). Due to the old mobo going toes-up I upgraded to a Core 2 Duo 4600 with Gigabyte/Intel P35 mobo and PCIe ATI HD2400XT, and now I'm having these blank screen problems. Any clues gratefully received. :thx: [/QUOTE]