Tip: After you have installed a screensaver, you can select it and customize its settings via the Personalization Control Panel Right-click on your desktop, select Personalize, then click the blue link Screensaver on the bottom right. There are 12 comments for this article. WoW, nice installer. I love the Mario and Matrix screensaver!
Definitely, the screensavers rock! What about a black ops screensaver. THEY are good i need window 7 to run my pc. I am having the same problem but found if my task bar is in hide mode, I leave the mouse on it so it is always up and it eliminates this problem. Message sent last week. Sorry for the delay as I don't seems to be getting notifications on replies to my messages. I've had this problem since day 1 win32, enterprise with my laptop.
I have a few different issues, but generally it's just failure to offer the login screen after the computer has been 'locked' sometimes I just see "locking your computer" and in this case a hard reboot is necessary. Seems to me that the logonui.
After anywhere from a few seconds to perhaps as much as 20 seconds, the mouse becomes frozen and won't move anymore. At no time from when the system was "woken up" by the mouse, can you do anything with the mouse or keyboard, e. Right click on "Computer" select "Properties" select "System Protection"select "Configure" select "Turn off system protection". Hi everybody ,. I had the same problem of video freezing after resume. Just a few weeks ago everything was ok but suddenly it started after a few modifications and software upgrades.
I knew that it was not related to any of drivers or hardware issues because my laptop HP Pavilion DV6 was working smoothly with no problem. After searching tons of blogs and forum sites with no success I decided to use system restore to roll back to very last good situation, and I did it many times cycling through every restore point but nothing changed! At last I tried to uninstall every program I recently modified or upgraded and at last I found the guilty one.
Exiting from Babylon, not uninstalling! Every time I use it I have the same problem of freezing after resume or blank screen. May be useful for somebody J. I'm simply astonished how many people are having this issue, and yet so many different variables as to what could be causing the problem.
I posted on another thread relating to this issue, and I figured I'd post here too. Originally I thought I had my issue of freezing after screens go blank by simply removing that setting. It seemed to of fixed the problem for a whopping two weeks or so, and the issue has returned. But the problem seems to have gotten worse being that I'm getting freezes during use on the computer and not just when the screens go blank.
I feel for everybody that is experiencing this issue. Has anybody else come across a valid solution or an idea as to what is really causing the problem? Office Office Exchange Server.
Not an IT pro? Windows Client. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Windows 7 Performance. Sign in to vote. I have observed this behavior on several builds using X64 versions of Ultimate and Home Premium; have not observed with X32 versions or with Professional, although I have little experience with these versions. The symptoms are that the system is left at idle for a period of minutes to hours, during which the screen s are turned off by the power management software.
There appears to be the need for a process to be operating in the background, such as a disk defragmenter, antivirus scanner, whatever, be it a MS service or a third party application. If a service is active in the background when the user returns to the computer, after the monitor s have been blanked, moving the mouse appears to "turn the system back on," with the monitor s coming back on and the mouse being initially responsive, e. After seconds, when the system freezes, nothing the user can do will have any impact other than a hard reboot of the system.
If the user is willing to wait, the system will ultimate become responsive once again after varying periods, from as little as 5 seconds to much more typically several minutes up to half an hour later. Once the system revives itself, it will function normally. Reviewing system logs will reveal exactly ZERO, other than if one did a hard reboot one will see the signs of that, or, one can find that some service or application was working in the background at about the time when the user tried to resume using the system from idle.
The bug clearly seems related to screen blanking "turn off display" in power options , not to hibernation or "sleeping. I'm currently testing this out myself. I believe that his observation is correct; the triggering factor is screen blanking when the machine has been left at idle, something related to the code used to implement that function, probably combined with any of a large number of possible applications or services working in the background at a time when the screen s have already been blanked and when the user then comes back to "revive" the machine.
Wednesday, January 27, AM. Additionally, you configure the computer to go to sleep. However, the computer may not go to sleep after the screen saver starts. Instead, a black screen is displayed. This problem causes the operating system to stop responding. You must restart the computer by holding down the power button. Edited by passionfly1 Wednesday, January 27, PM.
Hi, This update has already been installed on my system. I can't tell from the linked page when this update was released, although the current build I have on my machine was put back on the disk from an old image from December yesterday so the update shows as having been installed yesterday, when I did a "Windows Update" right after putting the image back on the system disk. I was having the issue up until yesterday, shortly before I made my post, when I disabled the ability of Windows 7 to turn off the monitors on the system.
The description of the problem on the linked page does not match what I am observing; for one thing, I have the screen saver disabled, and I never got or get a black screen. Rather, my normal desktop on both monitors becomes "frozen" e. I have only observed this behavior on one system, but have observed it with 3 different "builds" I've done with this machine, with X64 Home Premium on one "build," and with two different builds of Ultimate X I have initially left the power settings at default, as installed by the Win 7 install disk, although have also played around with them once the problem presented itself to try to see if any changes in these settings would resolve it.
The problem does not seem to occur, or at least is not anywhere as common or annoying due to length of "freezing period" when the only software installed has been Office and Win 7 itself. Once I start to install additional programs such as Antivirus AVG Free most of the times or a disk defragmenter Perfect Disk 10 , the problems begin and become progressively worse.
The common thread is that these are applications that work in the background when the system is at "idle. I have tried disabling various services through task manager, and this does seem to work, but then of course it results in a crippled system.
The MS native service I've seen that can also "cause" this behavior is the disk defragmenter service, another "background service. Resuming from idle with the screens blanked, the screens come back on but the system is unresponsive other than for a few seconds of possible movement of the mouse cursor, and nothing else. The period of unresponsiveness varies from several seconds to many minutes. No errors are noted in the various windows or other "event" logs, although one generally can see that some application or service was active in the background just before the mouse was moved to "reawaken" the system.
Details of this system are that it is a Lenovo ThinkCentre K desktop with an Intel Q quad core processor, 8 gb of DDR2 RAM in 2 banks with 2 matched sticks different types in each of the 2 banks however the same in each bank, all downclocked by the bios to the next speed down would have to go into the Bios to look at this again, I forget for the moment what that is. Have tried moving the RAM around with no changes.
Had the same problem when the system had 6gb as suppled by the Mfr. Swapped out one of the 3 original sticks so that I'd have 2 matched banks of 2 identical sticks each.
Slow video card, EGA dual headed 1gb Nvidia No problems whatever in device manager on any of the hardware in this system. And, as I've indicated before, I don't get blue screens and exhaustive review of system logs reveals nothing including looking at services for ALL users. I did however find several other posts in various threads from people who seemed to be having exactly the same problem I'm reporting here.
The only suggestion I have read that has worked, at least so far, was to turn off the ability of the system to blank the screens after a preset period of system idling. By turning this function off in the power manager service, and turning off the screens myself, manually, when I leave the system for a period of time, the problem seems not to occur.
Wednesday, January 27, PM. Do you have this problem if u ran the computer with only 1 stick inserted and the other one out for troubleshooting purposes. I understand this is not how you want to run it but does this error happen with only 1 stick? If the memory sticks are of different brands or same brand but different timings, they will work ideally with, some motherboards may be very very picky which timing is optimal for the pair and cause harrowing havoc on your system.
Let us know Hi, Thanks for your response. As I said before, I had this same problem with 3 identical sticks 2gb each; as sold by the mfr as the system was sold with 6gb of RAM from the factory occupying 3 of the 4 slots.
When I added the additional 4th stick, I elected to remove one of the 3 so as to have a bank of 2 sticks vacant, which I then replaced with 2 new, identical sticks. I have also moved the sticks around so that the pair that was in a bank of two is now in the other bank of two. For some reason this mobo with this bios will only run 3 sticks of 2gb each total 6gb at the faster speed, and defaults backwards when 8gb are in place.
I've had a fair amount of experience with bad RAM over the years, and it is generally fairly obvious. Given how much I have already moved stuff around on the Mobo, including the memory, I am extremely reluctant to remove RAM sticks yet again for testing that to me appears to have about a 0. To use your term, nothing is causing "havoc" on my system; it just freezes when coming out of an idle state when the system has blanked the screens. The problem has not recurred after I turned off screen blanking in power options as suggested by another user with an identical problem on a different system.
This is way way way way way too specific and repeatable of a problem to be due to the RAM, and suggests some sort of software incompatibility either among different pieces of code or possibly between the OS code controlling power usage and some specific sets of hardware components.
Edited by champignon Wednesday, January 27, PM typos. This isn't a memory issue per se its my hunt to find a commonality in terms of hardware devices that can be attributed to all ppl having this same sort of issue. Join our crusade for an answer here instead. Its a more livelier discussion: Windows 7 crash and reboot automatically kernel-power error. Thursday, January 28, AM. Its a more livelier discussion: Windows 7 crash and reboot automatically kernel-power error I'll have a look in on the other thread that you referenced.
I did skim it before I made my own post, however it doesn't seem to be referencing the same set of "symptoms" that I have observed, even if the cause in the code may be the same. I have a natural tendency to continually open up computer cases and to move stuff around and to change components.
This behavior has done a lot of damage to my systems over the years, and I am trying to avoid opening up the case when there is no real likelihood of benefit. So, I'm sorry to not have participated in the search for a common cause, but at least I still have a working system:- On the plus side, I have not had a single freeze from Idle since I changed the power settings to never turn off the monitors. The monitors are still, however, getting blanked when the desktop puts itself to "sleep" after 30 minutes even though I have turned them off physically beforehand.
When the machine reawakens due to a mouse movement, I am now getting prompted to put in my password, something that often did not happen even though the system was set up to do that.
This leads me to believe that the patch from yesterday, , has solved both problems, the freezing problem I was having and also problems with not asking for the PW on reawakening. It could well be that changing my power options to never blank the screen has done nothing at all and simply been a coincidence with release of this patch. Thursday, January 28, PM. I spoke too soon.
The patch has not corrected this bug. I changed the power management settings to again allow the monitors to be turned off, and the freezing has resumed. And as before, the freezing ultimate stops without user intervention if one is patient enough the most recent episode lasted for more than 20 minutes, after which I went out for lunch and returned to a system that was once again working. I'm not at all sure that the bug I am reporting here is related to other "freezing" issues with this OS 64 bit Windows 7.
The symptoms are certainly different. Friday, January 29, PM. I have nothing to add because you've described the issue perfectly. I'll be following this thread for a resolution. Friday, February 5, PM. I would narrow your cause down to it being purely OS or your memory chips and how they relate to the OS. These are the 2 possible causes I can see. One of em may be the correct avenue. I can only help you extensively in the hardware side of thing as this is my forte. OS issues I can give clues to but Microsoft, knowing its own code, has to do the brunt of that technical work.
Its also not so much that you have bad ram. Far from it. How the timings are set and then represented by the OS can be quite staggeringly different.
If the timings of your memory chips are off in their actuality under load then from what they are set to in the BIOS this could cause sluggishness and lockups and reboots.
A BIOS patch should correct this sort of discrepancy. Setting timings of 2T in the BIOS for instance and having Memtest running the tests at 2T would be an example of a timing discrepancy. This could cause huge consequences if the actual memory starts running at speeds over mhz. The faster the memory runs the more catastrophic the system error will be. Running into a wall at 2mph won't be as fatal as say 70mph, for example. But again I ask, have you had this problem with only ONE memory stick inside your computer for troubleshooting purposes?
I did not see this in your last post. You just mentioned you ran 2 out of 3 of the chips not specifically 1 out of 3 only. I think I might have the same issues I do use multiple users, and it seems to happen only if one users was logged in. Either black screen, or login screen, but turning black and staying black as you try to login. I had this behavior before and after applying patch Two days ago I uninstalled Norton Internet Security and Genie Backup Manager, which made my machine stable, potentially because there are fewer backup jobs running now.
No freezes since then. But it's been only 2 days, and I want both backup and virus protection running. I'll look at my power settings. Maybe if I no longer let windows turn off monitors, that will help. Saturday, February 6, PM. I don't know for sure if multiple monitors are necessary to have this problem, however my effected system has 2 monitors.
I can say that after turning off screen blanking in the power settings that the problem has disappeared. Even though Win 7 x64 has been instructed not to turn off the monitors, they still get turned off, perhaps because the sleep function has not been disabled.
After the system has been left on a while, typically a day or two or 3, the system will cease blanking the monitors even though it was not "told" to blank them in the first place. If the monitors do get turned off, then a password prompt appears when I resume using the system.
After the system has been booted up for a while a day or 2 or 3 and it has ceased screen blanking or asking for a password on being resumed, it still does not have the freezing problem I reported earlier. I am not the first person to document this behavior. As I reported in my first post, I found a couple of posts on other forums documenting this behavior which they described as "freezing" in the same situations as I have described it.
To Passionfly1, I am not insensitive to your request but I am very uninterested in reopening my computer case for the umpteemth time to remove Ram to follow up on your theory.
For one thing, I am using this system in various ways and distractions like that I don't need. For another, it would take some time to document whether or not the problems had resumed and if they did it would be a bit PITA for me to deal with in a system that is now working, albeit with the screen blanking function turned off in the power settings I agree that this is a bug, as I said in my initial posts.
This is not the first MS bug I have had to deal with in my life, and I'd rather have them inconvenienced by this than me! Sunday, February 7, AM. For now, I'm just leaving on the monitor continuously and setting the screensaver to blank. Monday, February 8, PM. Hi, I too am having the exact same symptoms as this. The only problem I seem to have with my setup is this freezing issue once I move my mouse to bring my screen back after it's been blanked. I'd love to know the solution but for now I guess I'll use the work around of disabling screen blanking, just use the screen saver, screen blanking is of no use to me on this particular PC as my LCD TV doesn't turn off, just sits there with "No Signal" flashing across the screen.
As I noted earlier, the system still blanks the screens, at least for a couple or 3 days after having been rebooted, in most instances, apparently when the system is due to go into "sleep" mode due to inactivity, and a password prompt screen comes up when I resume the system. Occasionally the screens are not blanked, but usually they are. I can't explain this behavior but it is really obvious that it is a bug, that may be hardware dependent, and something that MS has yet to address with any patches.
Perhaps it only effects a small percentage of Win 7 x64 users, and as I indicated, is hardware dependent. I can live with this current fix, but it would be better if MS would fix it once and for all. Tuesday, February 9, AM. Please describe with specificity what you mean by "turning off the monitor blanking function in the power settings".
What steps did you do to get this done? I do not see this setting there. It's simple. Go to control panel, select "power options," choose the power plan which is selected, by default it is "balanced," on the top. Click on "change plan settings. Select "NEVER" for when to turn off the monitor, then save your settings and exit out of the dialogs and control panel. That's it. Tuesday, February 9, PM. I didn't notice such behavior under Vista x64 I had run earlier.
I tried several things, different VGA drivers and settings, disabling bluetooth - first I was suspecting BT mouse to cause the problem since I usually "wake up" display by moving a mouse The only "solution" is what you already use, disabling system to power off display. I will be monitoring this thread in case sbd finds a solution. However I agree that this smells like Windows bug and should probably be addressed by MS.
I know ATI has some special power management features that I haven't investigated yet. It's a long shot but it may help if we find common denominator to all reported cases. I have an EVGA? This is a fairly slow, low power draw video card that is not used in high performance systems. I have video "wake-up" problems on two Win7 bit systems. In my case, I find that on resume, the display never wakes up, but the system does. I can access file shares on it through the network even while the display is "dead".
I have not tried using an RDP client to get a remote screen, but I suspect that would work even with the console not working. This is definitely not a screen saver issue, and the computer is definitely not in full sleep or hibernation mode. Apparently the keyboard controller portion of the chipset will generate an appropriate interrupt when it gets a request for such a 3-finger salute.
I'm wondering if it's the RAM that is not waking up. Friday, February 12, AM. Try locking your computer before you leave. Sunday, February 14, AM. Monday, February 15, PM. I have the exact same problem as the OP. After I leave my laptop, brand new HP DMus, long enough so that the screen saver and turn off monitor power options kick off.
My systems appears to come back to life. But just seconds after I move my mouse either touchpad or external mouse, it will freeze. Eventually the OS will become responsive.
It could take a few minutes to 30 minutes to come back to normal. What is weird though, it seems the longer the computer is inactive, the longer I have to wait for it to become responsive. I checked event viewer and I don't see anything out of the ordinary. They also said what the OP suspected, something with the background tasks running. I am going to try disabling the screen saver and let the monitor shut off. I will let you know how that works out. If anyone else comes up with something please post.
Tuesday, February 16, AM. Disabling the screen saver did not fix the problem. I just changed my power settings to disable monitor shut off. It sucks though because I am on a laptop so the screen saver is just going to run the whole time if I can't remember to shut the lid.
I will let everyone know if that fixes my issue. Tuesday, February 16, PM. After more internet searching I found that this is quite a popular problem. The problem may stem from the auto hide feature of the task bar. I had it set to auto hide.
After disabling the auto hide feature it hasn't froze after idle. I will continue to monitor the problem. So for those out there with this problem, try disabling auto hide if you have it enabled.
I have seemed to find a workaround. If I disable the autohide feature it does not lockup, freeze or become unresponsive.
I opened a case with MS to hopefully find an actual fix for the problem. Thanks for reporting on this and for contacting MS about it. I really like the autohide feature and would prefer to leave my system as is, without automatic screen blanking rather than lose autohide.
I should say, however, that I have never found the screen blanking function to be reliable in any recent version of Windows XP, Vista, or 7. Quite often when I expected it to work, I would come back to my computer hours later and find the monitors still on. So, it has become a habit of mine to turn my monitors off manually anyway, most of the time. Thursday, February 18, PM. I'm getting the same issue.
I do NOT have auto-hide enabled. Any idea? I have a second system that has now exhibited this problem. It is a micro ATX system with a dual core Intel Atom processor in it, being used as a media center box. The only software installed on it other than a few small utilities is Windows 7 Home Premium X There were no issues using the onboard video. I put a Radeon card I think it is a chipset but I'd need to look at it to verify this into the vacant video card slot.
After doing so I have had some instability issues with the system and ultimately removed the card, reverting to using the onboard video. I did check the Bios to be sure it was set to use the discrete video card and there was nothing else I could change at a bios level that would have made any difference. When the Radeon card was in the system, I had the freezing issue, as described in my initial post.
I have since removed the card, as above, and so far, the freezing issue hasn't returned. I don't think this problem has anything to do, per se, with ATI Radeon video chipsets. In fact, my main system is using a discrete Nvidia card. But both systems have integrated video which at least when exhibiting this behavior was over ridden by a separate discrete PCI-E video card. Most likely this is only one of a number of hardware or software configurations that can lead to this problem, but the similarity vis a vis the video in the two effected systems caused me to post this update.
My main desktop has no problems at all as long as I leave the screen blanking turned off in the power settings, as above. Friday, February 26, PM. Good news! In my case the problem went away on two of my systems. Your "wake up" problem may be different than mine. I just updated the ATI drivers from Catalyst I also installed the optional Catalyst One of those did the trick. The ATI Catalyst Saturday, February 27, PM. Monitor turning off feature used 2. AutoHide Taskbar used If Disabling either of these 2 fixs this problem then this serously flaw that MS failed to fix cause it been around since the RC build they made public, on side note this feature worked fine for me in XP for years, IF this the case and that the cause, where would i go to open an case or report this bug to MS cause like said I first noticed this in the RC build of Win 7.
Monday, March 1, PM. Now I'm seeing this issue on two different computers. I've had Win7x64 installed on my Mac Pro for about 4 months now, and this issue just appeared last week. At first I thought maybe my RAM was going bad until I researched it and saw how many other people were having the identical problem. It had previously been running a pre-release version with no problems, but as soon as I installed the RTM Pro version I started getting the freezing.
The most annoying thing is that even though I have changed the power settings to NOT turn the display off, I still come back to my desk and find it turned off. Then have to wait 5 minutes for Windows to unfreeze itself. Two wildly different platforms, different versions of the OS, installed at different times--this is not a hardware issue. Friday, March 5, PM. Saturday, March 6, AM. Nvidia here too. Monday, March 8, PM. I have the same freeze issue after the display turns off due to power options.
I have Windows 7 x64, with an Asus motherboard, and a nVidia graphics card. I do use the auto-hide toolbar. Sometimes the system will come back again after about 1 minute of freeze. Other times it requires a hard reset. I hope this bug gets fixed soon. Thursday, March 11, AM. I had the same random freezing problem for more than a month after installing W7.
Tried many solutions - updated drivers, tweaked screen savers, etc. I finally found what I believe is the solution regardless of your video card or system. Mine has been running now for three weeks without freezing after making this change: 1. Click on the "Boot" tab, then click on "Advanecd Options". Check both boxes at the top "Number of processors" and "Maximum memory".
Do not change the default values that appear. Click "OK" twice to exit, and reboot. I'm not sure why this works, but it has for me. Monday, March 15, PM. At first you can move the mouse but after a click or two, the mouse freezes and a hard boot is necessary. I do not get a black screen. However, I have got the black screen a couple of times when I switched users. A hard boot was necssary for this second problem. Since I purchased my computer from Staples with 14 days ago, I am returning it today.
Sounds like they are going to swap it out with a new one rather than try to fix it. Let's see if the problem is consistant with the machine. I'll keep you posted. Tuesday, March 16, PM. The device may be a sound device or a modem.
You also may see an "X" character appear on the speaker icon in the notification area. To resolve this issue, re-scan the device in Device Manager by performing the following: Click Start , enter device into the search field, and then select Device Manager from the list when it becomes available. Highlight and right-click Sound, video and game controllers.
The high-definition audio device will detect hardware changes and the "X" character should no longer appear on the speaker icon. Thursday, March 18, PM. I am running Win 7 with all patches installed. Friday, March 19, PM.
Tuesday, March 23, PM. I have never had Mcafee and I see the reaction. Thursday, March 25, PM. I'd sort of ruled out McAfee quite quickly too :. Friday, March 26, AM. Seymour Initially I blamed a background defragmentation program, Perfectdisk, but it became clear after a while that the bug is with the Windows OS itself and the way that it handles power saving activity when a machine is left idle.
With the amount of reporting that is available via Google etc, it is very evident that it is not limited to X64 code. Also this has been reported with Vista also. It is definitely an MS-induced problem Seymour. Friday, March 26, PM. When you have encountered this problem, did you have the taskbar set to auto-hide?
I had my taskbar set to auto-hide, and i think i read something in this forum which implied that might be involved. Saturday, March 27, PM. If so, then I used it there also. I have never had this particular problem with versions of Windows before Windows 7, even though I have used Autohide for many years. Sunday, March 28, AM. I am also having the same problem. The issue only occurs when I let my PC idle into screen off mode.
Hi, I use a Dell Inspiron 64bit laptop. I only got it in August and it initially had Vista on it. I then upgraded to Windows 7 and unfortunately this appears to be killing the machine. The problem manifests when the laptop is left idle, with only a web page open, and the screen saver comes on, you then return and try to exit the screen saver, the image appears again but the machine is then frozen.
You cant close the internet, you can't launch task manager, you cannot shut down, you cannot end task, essentially the machine becomes completly unresponsive.
At which point you have to switch off the power, then when you turn back on it has to check for inconsistencies on your disks. This is terribly inconvenient. I ran the upgrade as advised in the installation guidelines, running the upgrade assistant prior to the upgrade.
I have been advised to turn off Aero to increase performance, this has not helped. I don't have much on this machine, GB free space, the only external hardware I connect sometimes is an Hp printer, which is not connected when the machine crumbles.
0コメント