1 of 1 people found this helpful
I am also having the same issue on an Acer 3935 and again the only way to get rid of the problem is to restart the laptop. Although upon start-up windows loading up screen and boot screen etc... there does not seem to be any artifacts/screen distortion, making me think that it may be a driver issue but i have the latest drivers.
Any help would resolving this problem would be appreciated.
1 of 1 people found this helpful
I've been having this identical problem after integrating driver version 18.104.22.1681 into my Windows 7 Ultimate 64 bit installation DVD (and installing it obviously). I encounter the problem when I put the computer to sleep while on battery, wait some time, plug in the computer, and resume. The problem can be fixed by restarting, or by sleeping again, unplugging the power cord, resuming, then plugging it back in. It's almost certainly a driver issue since the cursor and some windows can appear on top of the artifacts, although the artifacts are not captured in screenshots. My hardware is a Sony VGN-FW270J with the latest Intel drivers for my 4500 MHD.
So does the issue relate to changing between mains and battery power when going to and coming out of sleep? Or is it down to the drivers Power Plan for the chipset. By this I mean that if it wakes on mains and tries to implement a Full Speed power plan when the chip and driver originally went to sleep on the Balanced or Max Battery plan.
It's a weird one. I still think this is a driver issue, but may be a chipset bug. Either way thanks for the advice.
Rather than Reboot simply put the laptop back to sleep, changing power from Battery to Mains, or Mains to Battery - basically away from the power type that corresponded to scren distortion. Then wake from sleep. If this works you can then revert to the power source of your choice.
Answered - in terms of a working solution that doesn't require a full restart.
Not answered - in terms of Intel actually fixing their chipset/driver
But I don't blame them, they have been useless at this for years. /sigh
I would suggest that if you are having this issue that you work with your OEM since this kind of issue sometimes has SBIOS dependencies. I have not seen this issue with the systems I have available for testing so it very well may be SBIOS related or some other factor related to the build on your system.
Three different OEMs are affected, and the problem only occurs with Intel's latest driver (i.e. the driver before this worked fine). That would imply a correlation of zero between having the issue and laptop manufacturer thus making it a very illogical approach in finding the bug. Plus it's inefficient, since an OEM isn't going to look into something until enough users complain, and then you'd have three teams duplicating their efforts. Furthermore, the most obvious first step would be to look into what changed regarding standby between the two releases, which would require looking at driver source, which Intel is most qualified to do.
OTOH, it's understandable that Intel would have difficulty investigating a bug they can't reproduce. Personally I'd just wait and see how many more complain of this issue as the update trickles down to the masses and see if there are any commonalities between the aflicted. Plus, knowing my OEM, suggesting that they spend money fixing something in a laptop they already sold is remarkably futile.
Same issue on Acer Aspire 1410. No problem until the Intel driver update (22.214.171.1241) which I performed last week - since then, the problem occurs frequently on awaking from sleep and/or hibernation.
I greatly appreciate the workaround (assuming it really will work) but it is not a solution, as most users will not find their way to this forum - indeed, will not even realize that the problem is associated with an Intel driver update.
As for the chance that Acer would do something about this... maybe in an alternate universe.
Simple simple simple solution. Discovered this morning after finding a garbled screen.
Remove the power lead (your screen will flicker and restore itself) then replace the power lead. Obviously do the opposite if you initally wake on battery.
No need to go in and out of sleep as previously suggested. Clearly this chipset has issues relating to going in and out of sleep with different power sources.
For the record, removing / replacing (or vice versa) does not work for me on the Acer 1410, but the sleep / change power / wake solution workaround does work.
I am having the same problem on a Gateway NV5814 laptop running Windows 7 Home Premium. This NEVER happened prior to updating to 126.96.36.1991. Since the "update," most of the time when I close the computer without shutting down (don't know if this is "sleep" or "hibernate" mode) the screen is garbled when I return. The computer is on electrical power when I close the lid, though sometimes I might unplug as it's going to sleep. I always plug in before turning the computer on again.
I don't believe "simply" unplugging and replugging (which I haven't tried) is a solution. A software update should not dictate our physical interaction with our machine. It may work--I haven't tried it--but it's not a solution; if an update to your car required that you unplug the battery cables every time you start it up, you would demand a repair. I demand a repair to this update!
Hurrumph, follow the link and get this: "The file that you are trying to download has either been moved, renamed or archived.
Please go to http://downloadcenter.intel.com and choose your product to find your download."
Follow that link and get the same thing again.
Definetly seems to be an issue there,, thanks for pointing it out, I will have it fixed. In the mean time, you can use the "zip" version of the driver. Just extract it and run setup.exe.
Here is the link: http://downloadmirror.intel.com/18788/a08/WinVista7_15169.zip
Attempted install. Got "This computer does not meet the minimum requirements for installing the software."
Acer 1410, 2 GB RAM, lotsa free hard disk space, Win 7 Home Premium.
Enough. I'll let others play guinea pig for a bit.