If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
PC won't wake up
On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote:
Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later. The problem has just started happening without any changes being made by me. It only happens if the pc is allowed to sleep for 'too long' although I don't really know how too long is. If I put it to sleep and wake it shortly eg 5 mins later then all is fine. -- Jim S |
Ads |
#17
|
|||
|
|||
PC won't wake up
On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote:
Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. -- Jim S |
#18
|
|||
|
|||
PC won't wake up
On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote:
On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. |
#19
|
|||
|
|||
PC won't wake up
On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote:
On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. -- Jim S |
#20
|
|||
|
|||
Screen wake up (was: PC won't wake up)
On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote:
On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. -- Jim S |
#21
|
|||
|
|||
Screen wake up
Jim S wrote:
On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul |
#22
|
|||
|
|||
Screen wake up
On Wed, 14 Nov 2018 05:43:37 -0500, Paul wrote:
Jim S wrote: On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. -- Jim S |
#23
|
|||
|
|||
Screen wake up
Jim S wrote:
On Wed, 14 Nov 2018 05:43:37 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. When the system wakes from sleep, it needs to do a warm start of the hardware. When the computer dropped into sleep mode, the fans go off, and the main ATX power rails drop. Only the auxiliary +5VSB remains running (and powers the DRAM modules). The DRAM modules remain in autorefresh. On the next startup, the video card had been sitting there with no power. The video card is ice cold. Consequently none of the internal state is preserved. They choose not to "archive" the video card state. It's faster to warm start the driver and bring the card up the old fashioned way. If you start up the driver, it can reset the card, set up the command buffer and so on. The OS can choose to draw images after that, as required (indicating sleep is over). As far as the video driver is concerned, what's supposed to happen: 1) The monitor is connected via cable to the video card faceplate. 2) The monitor has termination resistors on the chosen input port. For example, 75 ohms to ground on VGA RGB. Or 100 ohms diff on the HDMI or DVI interfaces. 3) The video card can sense the effect these termination resistors have. It sends an "event" to the OS, stating something is hanging off the port. 4) The OS accesses the DDC/CI serial bus on the monitor cable. It reads the EDID ROM inside the LCD monitor. Information in there includes resolution settings, refresh rate, and so on. If the EDID was inaccessible, resolution will be capped at 1024x768. 5) Now the OS is in a position to check its records, and see what resolution it wants to drive out. Soon after this, the desktop is rendered on that port. If for any reason, the computer drives out a wrong refresh rate or scan rate, the OSD on the LCD screen responds with "Out of range". Out of range tells you there are signals on the cable, but the signals aren't right for the job. If a signal is present, like a DVI or HDMI clock, the monitor should "see it". Even without sync, it might display a gray screen indicating something is waking up. If it was "just an interface issue", some part of that sequence would need to be disrupted. If something more serious is wrong, it might not even be getting to step 1. Disabling Fast Start and seeing different symptoms, might suggest there is a problem before step 1 (the thawed kernel is corrupted - RAM test recommended). Paul |
#24
|
|||
|
|||
Screen wake up
On Wed, 14 Nov 2018 07:03:40 -0500, Paul wrote:
Jim S wrote: On Wed, 14 Nov 2018 05:43:37 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. When the system wakes from sleep, it needs to do a warm start of the hardware. When the computer dropped into sleep mode, the fans go off, and the main ATX power rails drop. Only the auxiliary +5VSB remains running (and powers the DRAM modules). The DRAM modules remain in autorefresh. On the next startup, the video card had been sitting there with no power. The video card is ice cold. Consequently none of the internal state is preserved. They choose not to "archive" the video card state. It's faster to warm start the driver and bring the card up the old fashioned way. If you start up the driver, it can reset the card, set up the command buffer and so on. The OS can choose to draw images after that, as required (indicating sleep is over). As far as the video driver is concerned, what's supposed to happen: 1) The monitor is connected via cable to the video card faceplate. 2) The monitor has termination resistors on the chosen input port. For example, 75 ohms to ground on VGA RGB. Or 100 ohms diff on the HDMI or DVI interfaces. 3) The video card can sense the effect these termination resistors have. It sends an "event" to the OS, stating something is hanging off the port. 4) The OS accesses the DDC/CI serial bus on the monitor cable. It reads the EDID ROM inside the LCD monitor. Information in there includes resolution settings, refresh rate, and so on. If the EDID was inaccessible, resolution will be capped at 1024x768. 5) Now the OS is in a position to check its records, and see what resolution it wants to drive out. Soon after this, the desktop is rendered on that port. If for any reason, the computer drives out a wrong refresh rate or scan rate, the OSD on the LCD screen responds with "Out of range". Out of range tells you there are signals on the cable, but the signals aren't right for the job. If a signal is present, like a DVI or HDMI clock, the monitor should "see it". Even without sync, it might display a gray screen indicating something is waking up. If it was "just an interface issue", some part of that sequence would need to be disrupted. If something more serious is wrong, it might not even be getting to step 1. Disabling Fast Start and seeing different symptoms, might suggest there is a problem before step 1 (the thawed kernel is corrupted - RAM test recommended). Paul Thanks Paul. Just tell me what I try next? -- Jim S |
#25
|
|||
|
|||
Screen wake up
Jim S wrote:
On Wed, 14 Nov 2018 07:03:40 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 05:43:37 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. When the system wakes from sleep, it needs to do a warm start of the hardware. When the computer dropped into sleep mode, the fans go off, and the main ATX power rails drop. Only the auxiliary +5VSB remains running (and powers the DRAM modules). The DRAM modules remain in autorefresh. On the next startup, the video card had been sitting there with no power. The video card is ice cold. Consequently none of the internal state is preserved. They choose not to "archive" the video card state. It's faster to warm start the driver and bring the card up the old fashioned way. If you start up the driver, it can reset the card, set up the command buffer and so on. The OS can choose to draw images after that, as required (indicating sleep is over). As far as the video driver is concerned, what's supposed to happen: 1) The monitor is connected via cable to the video card faceplate. 2) The monitor has termination resistors on the chosen input port. For example, 75 ohms to ground on VGA RGB. Or 100 ohms diff on the HDMI or DVI interfaces. 3) The video card can sense the effect these termination resistors have. It sends an "event" to the OS, stating something is hanging off the port. 4) The OS accesses the DDC/CI serial bus on the monitor cable. It reads the EDID ROM inside the LCD monitor. Information in there includes resolution settings, refresh rate, and so on. If the EDID was inaccessible, resolution will be capped at 1024x768. 5) Now the OS is in a position to check its records, and see what resolution it wants to drive out. Soon after this, the desktop is rendered on that port. If for any reason, the computer drives out a wrong refresh rate or scan rate, the OSD on the LCD screen responds with "Out of range". Out of range tells you there are signals on the cable, but the signals aren't right for the job. If a signal is present, like a DVI or HDMI clock, the monitor should "see it". Even without sync, it might display a gray screen indicating something is waking up. If it was "just an interface issue", some part of that sequence would need to be disrupted. If something more serious is wrong, it might not even be getting to step 1. Disabling Fast Start and seeing different symptoms, might suggest there is a problem before step 1 (the thawed kernel is corrupted - RAM test recommended). Paul Thanks Paul. Just tell me what I try next? When you Googled the make and model number of the LCD, did you find any similar reports of problems ? There have been monitors before, with marginal HDMI ports. The monitor could have some sort of "deep sleep" power saving mode, like an "ErP". There are some modern standards that decree that "vampire power wastage" be below 1W. You could review the OSD using the buttons on the monitor, to see if it has any menu items that mention power or power saving. My monitors here don't have any power saving options. Yes, they go to standby (disable backlight on loss of sync), but the power source likely doesn't do anything special. Especially the one on the monitors, which uses a brick. A AC brick design, the adapter runs in the same state all the time. The other monitor has AC power conversion in back of the panel, so some trickery would be possible there. Paul |
#26
|
|||
|
|||
Screen wake up
On Wed, 14 Nov 2018 08:28:19 -0500, Paul wrote:
Jim S wrote: On Wed, 14 Nov 2018 07:03:40 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 05:43:37 -0500, Paul wrote: Jim S wrote: On Wed, 14 Nov 2018 00:04:56 +0000, Jim S wrote: On Tue, 13 Nov 2018 10:56:52 -0600, Char Jackson wrote: On Tue, 13 Nov 2018 10:39:02 +0000, Jim S wrote: On Mon, 12 Nov 2018 22:26:32 -0600, VanguardLH wrote: Jim S wrote: My sojourn so far seemed to work, but tonight I left it for two hours and it would not start. If the fast startup option was still disabled after a reboot, test with ALL sleeping disabled. My guess is the 2 hour idle was longer than whatever sleep time you configured in whichever plan (scheme) you used in Power Options. Go into the power options and configure to leave the computer on ALL THE TIME. Then test. Maybe the problem was not with fast startup mode (a type of hibernate mode) but with the low-power saving mode (sleep or standby). As mentioned, some drivers or hardware won't deal well with getting slept. Test with no sleeping enabled. I'll try that later because it only displays this behaviou if I leave it in sleep a long time eg overnight. Short sleeps are no problem. It's a recent fault and I have changed nothing. What are your Power Profile settings for turning off the monitor and putting the PC to sleep? One of my colleagues recently had an issue similar to yours and what threw him was his assumption that the PC was going to sleep when it was only blanking the monitor. Actual sleep didn't happen until sometime later. In his case, the usual methods of doing almost anything (press a key, move the mouse, etc.) would appear to wake up the PC (during the period when the monitor was merely blanked), but once the PC actually entered the sleep state he was unable to wake it. He says he 'solved' it by unplugging a USB-connected hard drive, but he was short on the details. Thanks. I have one of them. I'll try it next time. The problem seems to happen when I let it sleep too long. Much like my children when they were teenagers. Took me long enough to realise that it's just the monitior screen that won't wake up. The USB Hard-drive trick didn't work either. So toggling the power on the monitor always brings it back ? Paul If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. When the system wakes from sleep, it needs to do a warm start of the hardware. When the computer dropped into sleep mode, the fans go off, and the main ATX power rails drop. Only the auxiliary +5VSB remains running (and powers the DRAM modules). The DRAM modules remain in autorefresh. On the next startup, the video card had been sitting there with no power. The video card is ice cold. Consequently none of the internal state is preserved. They choose not to "archive" the video card state. It's faster to warm start the driver and bring the card up the old fashioned way. If you start up the driver, it can reset the card, set up the command buffer and so on. The OS can choose to draw images after that, as required (indicating sleep is over). As far as the video driver is concerned, what's supposed to happen: 1) The monitor is connected via cable to the video card faceplate. 2) The monitor has termination resistors on the chosen input port. For example, 75 ohms to ground on VGA RGB. Or 100 ohms diff on the HDMI or DVI interfaces. 3) The video card can sense the effect these termination resistors have. It sends an "event" to the OS, stating something is hanging off the port. 4) The OS accesses the DDC/CI serial bus on the monitor cable. It reads the EDID ROM inside the LCD monitor. Information in there includes resolution settings, refresh rate, and so on. If the EDID was inaccessible, resolution will be capped at 1024x768. 5) Now the OS is in a position to check its records, and see what resolution it wants to drive out. Soon after this, the desktop is rendered on that port. If for any reason, the computer drives out a wrong refresh rate or scan rate, the OSD on the LCD screen responds with "Out of range". Out of range tells you there are signals on the cable, but the signals aren't right for the job. If a signal is present, like a DVI or HDMI clock, the monitor should "see it". Even without sync, it might display a gray screen indicating something is waking up. If it was "just an interface issue", some part of that sequence would need to be disrupted. If something more serious is wrong, it might not even be getting to step 1. Disabling Fast Start and seeing different symptoms, might suggest there is a problem before step 1 (the thawed kernel is corrupted - RAM test recommended). Paul Thanks Paul. Just tell me what I try next? When you Googled the make and model number of the LCD, did you find any similar reports of problems ? There have been monitors before, with marginal HDMI ports. The monitor could have some sort of "deep sleep" power saving mode, like an "ErP". There are some modern standards that decree that "vampire power wastage" be below 1W. You could review the OSD using the buttons on the monitor, to see if it has any menu items that mention power or power saving. My monitors here don't have any power saving options. Yes, they go to standby (disable backlight on loss of sync), but the power source likely doesn't do anything special. Especially the one on the monitors, which uses a brick. A AC brick design, the adapter runs in the same state all the time. The other monitor has AC power conversion in back of the panel, so some trickery would be possible there. Paul The thing that puzzles me is that it just started happening. It may be qa Windows 10 update of course. I just did a full systems image check and a sfc /scannow showed nothing. I'm off to the pub for an hour after deliberately putting it to sleep and see what happens. -- Jim S |
#27
|
|||
|
|||
Screen wake up
Jim S wrote:
If you mean switching the monitor power off and on then no it doesn't work. If I switch it off and back on I get the rectangle telling me it's in sleep mode (or WTTE) which then fades to black. Then I'd suspect a video driver problem. What happens if you alter your currently selected Power Options scheme to not sleep at all and instead just spin down the HDDs and power off the monitor? Those are the big power consumers (since, after all, if the CPU and other internals components are consuming power then they aren't idle and the computer shouldn't be sleeping, anyway). Note that even if you are on the latest version of the video driver, that may have bugs. New code can result in new problems. I had to test several versions of AMD's Catalyst driver finding the latest version that still worked with my old video games. The newest version caused the old video games to crash. They removed compatibility code for old games when they added compatibility code for newer games. Check what version of the video driver you have now and what is available from the video card maker's web site. |
#28
|
|||
|
|||
Screen wake up
Jim S wrote:
The thing that puzzles me is that it just started happening. It may be qa Windows 10 update of course. I just did a full systems image check and a sfc /scannow showed nothing. I'm off to the pub for an hour after deliberately putting it to sleep and see what happens. Did you configure Windows 10 to /*NOT*/ automatically your hardware drivers? If not, you're letting Microsoft change from working drivers to newer drivers, and new code brings new bugs. https://www.itprotoday.com/windows-1...tes-windows-10 From my experience, getting new driver versions from Microsoft is hazardous. I get the drivers from the web site of the maker of the hardware, or the OEM that used the hardware (some hardware drivers are just reference drivers and need to be modified to include however an OEM implemented the hardware). It can take a long time for a manufacturer to get Microsoft to publish a new version of their driver that is available via Windows Updates. If the driver author finds a bug in the driver, it can also take a long time to get the defective driver off of Windows Updates. Just because Microsoft's WU server has a new driver version doesn't mean it is the best one for you nor that it is bugfree. |
#29
|
|||
|
|||
Screen wake up
On Wed, 14 Nov 2018 14:50:01 -0600, VanguardLH wrote:
Jim S wrote: The thing that puzzles me is that it just started happening. It may be qa Windows 10 update of course. I just did a full systems image check and a sfc /scannow showed nothing. I'm off to the pub for an hour after deliberately putting it to sleep and see what happens. Did you configure Windows 10 to /*NOT*/ automatically your hardware drivers? If not, you're letting Microsoft change from working drivers to newer drivers, and new code brings new bugs. https://www.itprotoday.com/windows-1...tes-windows-10 From my experience, getting new driver versions from Microsoft is hazardous. I get the drivers from the web site of the maker of the hardware, or the OEM that used the hardware (some hardware drivers are just reference drivers and need to be modified to include however an OEM implemented the hardware). It can take a long time for a manufacturer to get Microsoft to publish a new version of their driver that is available via Windows Updates. If the driver author finds a bug in the driver, it can also take a long time to get the defective driver off of Windows Updates. Just because Microsoft's WU server has a new driver version doesn't mean it is the best one for you nor that it is bugfree. I think I might just set to 'never sleep' as it seems to be that which cuases the problem. If I set to 'turn off the display' and go back before the 'sleep' kicks in, there is no problem. I think I have tried all the other suggestions. I will then shut down at night. -- Jim S |
#30
|
|||
|
|||
PC won't wake up
"Jim S" wrote in message
news If I put my desktop to 'sleep' mode (or if it does it on timer) I cannot get it to wake up. If I move the mouse I normally hear the drive motor start then the screen, but now I hear the motor start, but whatever I do the screen remains black. The only solution is to turn off, wait 30 secs and start from scratch. Ideas please. I had the same problem with a Gigabyte motherboard. Consensus of opinion from all the experts that I asked (both online & locally) was that it was waiting for an input from Windows 10 which it never received. I reinstalled Windows 8.1 & it's worked without a hitch for the last couple of years. Display turns off after 1 hour. Computer sleeps after 2 hours. Any key press wakes it instantly. -- Regards wasbit |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|