While Windows Vista has a whole host of new features to offer, it has one major problem that just won't go away: it's totally FUBAR'd after you resume from sleep or hibernate. Unfortunately, many of these issues weren't present during the beta stage, and were somehow introduced in the RTM build of Windows Vista. This exclusive NeoSmart Technologies report describes some of the symptoms in detail, and we even provide links to possible fixes by Microsoft. All issues have been duly reported and confirmed by Microsoft, so this isn't just some figment of our imagination. A number of these patches are scheduled to be included in Windows Vista SP1 (Codename Fiji).
Few computer "enthusiasts" turn off their PCs. Even with Bill Gate's promised 6-second-boot (we've clocked an average of 42.6 seconds here on 8 different PCs), turning on a PC via a cold-boot requires waiting for all the various programs to load, the network to establish, the security policies to propogate; and you don't get to brag about never turning off your PC - plus your uptime restarts. The alternatives were either hibernation (for laptop owners) or "Deep Sleep" for the rest. (("Deep Sleep" is configured in the BIOS, and refers to the use of S3 power-saving mode instead of the default S1 setting. In S3, you're machine actually kills the power to everything but the memory, and uses up about as much power as a single, tiny light (like those powering up your Christmas lights). And you get to instantly turn your PC back on, with all your programs running and in a matter of seconds (for real!). At least, that's how it's supposed to work.))
Throughout the beta, Deep Sleep in Windows Vista went great. It's the default option (so long as it's configured in the BIOS) when you click the shutdown button. ((As opposed to using the shutdown menu, and selecting an option from there.)) It would put your computer in a low-power mode that recovered in a matter of 2 or 3 seconds, and didn't crash! But in the final version of Windows Vista, something is very, very majorly wrong. On 6 of the 8 tested systems, ((All systems are modern, 100% x86 ACPI-compatible systems running Windows Vista Ultimate Edition, RTM. No systems are using non-signed Vista drivers, and no buggy software is installed.)) recovering Windows Vista from a hibernate or Deep Sleep results in one of the following:
- When recovering from a hibernate: "Cannot find uxtheme.dll" appears whenever you attempt to run (almost) any program. No matter what you do, you can't even run Task Manager. What's worse, a restart doesn't fix it, and because Windows Explorer also fails to launch with this error, you need to boot from the DVD and use System Restore - Safe Mode won't work! ((We obviously didn't mess with uxtheme.dll, didn't patch it, nor did we try to install any of XP's theming software…))
- Failure to establish a network connection. Everything looks OK, but you can't connect to the internet. Your LAN signal will be there, but the internet just doesn't work. You must restart to fix it.
- Poor performance: though Task Manager will show normal CPU load, some of the drivers (they don't appear in TaskMan) will attempt to use 100% of the CPU, resulting in a very laggy PC. You need to restart to fix it.
- No DWM. For no reason, DWM just won't re-appear. This happens on ATi and nVidia, with or without the latest official drivers from the companies themselves. Manually running "dwm.exe" doesn't work, you need to restart to fix it.
- BSOD on recovery. This is usually caused by the video drivers, and may or may not indicate something wrong with the kernel itself.
- No sound. Vista goes mute. Nothing you can do about it, no way to revive it, you just have to restart and let the re-done sound-stack load-up the way it should.
All of the above errors and more occur randomly and make using hibernation down-right impossible (unless you're willing/eager to run System Recovery from the DVD!) and Deep Sleep a waste of time (seeing as you have to restart to "quick recover"). Most of the errors are indicative of a problem somewhere deep in the kernel, and it's not going to be easy to fix it. Some people are blaming this on the PC/Hardware/BIOS itself, but it's not the BIOS' job to support the OS, ((Assuming, of course, that the BIOS conforms to the basic standards already defined and used by BIOS manufacturers everywhere)) and the only thing to blame here is a buggy ACPI model.
We've notified Microsoft of each of these errors, we've been told they're real bugs and a fix is in the works for some issues, others are just as much of a mystery. Some of these can be solved when ATi and nVidia release their final (hopefully bug-free) drivers for Vista. Others may not be as willing to go away. Either way, an operating system that you have to shutdown in order to save on power isn't exactly the biggest business model. The only good news is, this bug only recently made its way into Vista, so that may just mean it won't be too hard to squash. For now, if you really need to keep your PC on all day and all night, check the list below for hotfixes that may work for you.
Patches by Microsoft (Updated 06/12/07)
Here's a list of patches by Microsoft related to Vista and wake/resume problems. You may have to call MS directly for access to some of these patches. Stop errors are blue screens (BSODs).
- [KB-928135] - Windows Vista hangs on resume/wake
- [KB-928135] - USB-Related crashes on resume/wake
- [KB-929734] - Many problems on resume/wake
- [KB-927341] - "Manage Discs" WMP feature slow to respond after resume/wake
- [KB-933872] - Default Gateway missing after wakeup
- [KB-933778] - Applications with HotStart fail to load after wakeup
- [KB-929685] - No (HD) audio upon resume/wake (possibly permanantly)
- [KB-929577] - No bluetooth on resume/wake
- [KB-929762] - Stop error 0x9F on machines with firewire (IEEE1394) upon resume/wake
- [KB-929909] - Intel 945GM Chipset PCs won't wake/resume
- [KB-930311] - No network with stop error 0x0000007E after resume/wake
- [KB-930495] - No firewire (IEEE1394) after resume/wake
- [KB-930570] - usbhub.sys stop error 0x00000044 on resume/wake
Talk about broken! What does Vista have to offer that isn't
Half-Baked Completely Broken Stolen from somebody else Useless
??????
Microsoft was going on and on about how Vista's power settnings have been totally revamped, I've seen the screeenshots in your gallery, then you guys came and claim it sucks...
Either MS is way worse off than anyone thought or you guys are talking about somehting else...
Lol, Michael, there is such thing as grammar you know ;)
But really, I don't see a conflict. It seems to me (took a quick look at the Vista gallery at NST really fast), that Microsoft has offered flexibility and customization and control, but they just left out stablitiy and speed, and that's what (to me at any rate) this article is all about.
Interesting article, scary reflections. Vista won't fail because Windows is already number 1, but let's just say if this was Linux 2.7 we're talking about, we could write off as a joke and say that Linux as we know it was over... But it's Vista, so we have to be nice. :-{
Odd - I'm running Vista Enterprise on about 30 machines and none of them have S3/S4 resume issues.
They're all bits of HP hardware though - several models of laptops & tablets, and d530, dc7100/7600/7700 business desktops. Maybe we're just lucky...
Now I'm no Microsoft fan boy (writing this on my Mac as we speak) but bow arrogant can one person be, making such a large blanket statement.
I have the final version of Vista running on every one of my companies workstation models (A mixture of 10 different models mixed between Dell, IBM, and HP). Not one of them has this issue. Either the author is completely ignorant and has no idea how to test a operating system (like installing on more then one machine, with different hardware configs and making sure that all the drivers are correct) or the author is just trying to generate traffic by writing a inflammatory article. Either way a complete was of time.. Be smart people get your information from a trusted source, not some random yahoo who clearly has no clue.
What a load of bullshit! There are so many things wrong with what you are saying, it is hard to know where to start. There is no credibility to this story as the footnotes are vague and largely incorrect.
Deep Sleep is not S3. Deep Sleep is S4. Look it up for yourself. Support for any hibernation mode relies on the hardware itself to be fully compliant.
"All systems are modern" - List the specifications, including the manufacturers of the systems tested. List the bios settings used, drivers, installation options, etc. etc.
There are a number of other recovery options, and it is not a reasonable assumption to associate the .dll problem with the hibernation.
That is a rather large assumption. Further, there is no evidence to suggest that this is a problem at the kernel level. With so many different manufacturers of motherboards, different hardware configurations, etc. etc. etc. it is not reasonable to assume that every configuration would be supported on the new O/S. Further, which of the tested systems was badged "Vista Ready" ?
Dear Dusty,
Did you RTFA?
Sincerely, Me
Actually, if it were Linux 2.7, "we" would write it off as being a part of the development series of the Linux kernel.
@Mike: We spoke with Microsoft, they told us the .dll with hibernation was a bug. The rest are also reported bugs. The machines don't have a Vista-Capable sticker, but Vista installed on them, didn't it? And they all receive above a 3.5 in System Rating. This is using the default S3 settings, except the default S1 sleep has been changed to S3. There's a reason why "Deep Sleep" is in quotes, we're talking about S3 - S4 is rather temperamental, and we didn't want that to bias our results.
The drivers installed don't matter, what does is that they're all signed and out-of-the-box (except the WDDM drivers, and we talked about that).
Maybe Vista doesn't support S3 on this hardware, is that any better? These are all modern machines that S3-Sleep just fine on XP, 2k3, and Linux - what more do you need?
Lol Antares, you know what he means ;)
If it's Linux, it's the end of the world. If it's Vista, it's just another small thing we're supposed to ignore. For how long!?
@CG "@Mike: We spoke with Microsoft, they told us the .dll with hibernation was a bug." Who at Microsoft did you speak to? What KB article is this documented under?
"The machines don’t have a Vista-Capable sticker, but Vista installed on them, didn’t it?" I can get Vista to install on just about any piece of 486+ hardware, that does not mean that it is supported, or that all functionality is available.
"There’s a reason why “Deep Sleep” is in quotes, we’re talking about S3 - S4 is rather temperamental, and we didn’t want that to bias our results. " Fair enough. I agree that S4 is very poorly supported, by both O/S and hardware manufacturers.
"The drivers installed don’t matter, what does is that they’re all signed and out-of-the-box (except the WDDM drivers, and we talked about that)." Unfortunately, drivers do matter. Study after study has concluded that the majority (as high as 99.xx%, and I apologize for not having a link to this information) of BSOD scenarios are a direct result of poor drivers. The fact that they get signed, well now that is a valid point for contention. Many drivers should never have been signed, and the testing process is not as open and conclusive as many IT professional would like.
"Maybe Vista doesn’t support S3 on this hardware, is that any better? These are all modern machines that S3-Sleep just fine on XP, 2k3, and Linux - what more do you need?" Better? No. But certainly more accurate than a blanket statement calling Windows Vista Wakeup Support hideous.
Fair point. I guess if Microsoft drivers with it's "Ultimate" operating system that shouldn't be there and shouldn't be even signed in the first place, that might explain the problems we're facing on our widely-varying hardware here. However, that's rather worse than just saying "Vista's wakeup-controller is borked" because it means a hell of a lot worse can go wrong.
About the hardware: I agree, that's why I pointed out that bit about all machines scoring > 3.5 on WinSAT.
I really think you should publish the list of hardware that failed, so in the least everyone can avoid that manufacturer. While it is easy, and possibly fun, to blame Microsoft and windows for every short coming of a OS the fact of the matter is that there are many shoddy hardware implementations. For instance the wireless connectivity issues detailed http://windowsvistablog.com/blogs/windowsvista/archive/2006/12/04/how-windows-vista-rtm-build-addresses-wireless-connectivity-issues.aspx they can be nailed down to shoddy hardware, which isn't, by a long shot Microsoft's fault.
Of course the line saying that simply because Vista installs on some hardware it should support all the hardware is quite horrible precedent to take. Take for instance the fact that people will use a microwave to dry their clothes (not recommended), simply because you can fit a baby in one doesn't mean that it is suitable for drying. While that is a very extreme example I think it gets the point across, there is no substitute for common sense even if the sense isn't so common.
Hey Lyme,
I just want to point out that the Microwave doesn't come with a list of "tested clothing brand names" to back that up - nor does it ship with "sample clothing" to try it with.
Vista does. They're called signed drivers, and their very definition is Microsoft-approved, tried, and tested. Some come in the box, some are available on Windows Update. If Microsoft explicitly says they're OK...
The ACPI S3 suspend mode is called Suspend to RAM ("STR"), not "deep sleep". S4 (Hibernation) is Suspend to Disk ("STD") and S1 is Power on Suspend ("POS").
I can concur with the myriad of sleep/wakeup issues in RTM. I have a homebuilt system using an Asus P5W DH board (latest 1607 Bios), Pentium D 805, and an Nvidia 7900GT. With Beta 2 and RC1 Sleep worked perfect, I couldn't be more thrilled. With both RC2 and RTM the machine goes into sleep (the power led blinks), it powers back up after moving the mouse, but the screen stays off and the hard drive led stays on solid. A reboot will bring it back to life (restoring from the hibernate file on disk), usually, although I've had a couple instances where it refused to boot and had to run the repair utilities.
So much for energy savings!
Thanks for the info, Ahti! I'll see what I can do about fitting that in :)
@Ed34: Yep. With a Pentium D and a nVidia 7900GT, you really do need S3 suspend whenever you can, that stuff doesn't run off of hydrogen! But with Vista, to suspend, you have to waste more time than to shutdown. And it wasn't like that in the beta! :@
If DWM dies, try 'net stop uxsms' and then 'net start uxsms' from an elevated cmd prompt. Manually running dwm.exe won't work because Vista launches it with said service.
Of course these features work on W2K and XP. They work because the hardware was developed with those operating systems and ships with those operating systems. No manufacturer is going to ship a computer with an operating system that isn't compatible with the hardware.
That's why there's this two-month gap between Vista RTM and public availability. The hardware manufacturers need time to get these bugs worked out with their hardware. Rest assured that companies like Dell and HP have been scrambling to fix all of the little inconsistencies so that when they ship Vista, everything (including hibernate) will work perfectly.
Vista isn't done yet. You spent a whole page groaning about a single bug in an unfinished application. RTM means Release To Manufacturing, not Release to the Public. This period between RTM and public release was added specifically to allow things like this to be fixed before the product gets to you. And your uninformed complaining is the perfect example of why they limit this release to developers only.
I'm a developer. It's really simply: if the drivers are broke, don't ship them with the Operating System.
The drivers that shipped with RTM in Nov. are the same that will ship with Vista (in the box) in Jan. Only OEM machines will have custom drivers, and that's not what this article is about.
My Mac goes to sleep flawlessly. Could this be a case of the 25+ year old BIOS holding back PCs?
*cough* dropped EFI support *cough*
Of course not, why would you ever imagine that Microsoft's refusal to leave BIOS could have anything to do with this kind of inherent system instability?
Oops! I forgot the /sarcasm tag!Even with buggy BIOSes full of out-of-specifications ACPI instructions designed for M$ Windows, it's harder to believe that this so expected windows version fails to do it's job when deep slipping or hibertating!
It looks like M$ standards never lasts too long.. You will see..
It's not sleeping. It's calculating how much money Microsoft made off you for your poor choice of Windows and Office software.
I can verify everything stated in the article is exactly what's happening on my Asus A8N32-SLI based system. S3 suspend works great on this system under XP. S3 worked great in the Vista beta. But Vista's S3 using 'out of the box' drivers got badly broken in the RTM.
The primary question in my mind is WHERE ARE THE NVIDIA PLATFORM DRIVERS FOR VISTA RTM??!! I check for them almost daily and not only is there no sign of them, there's almost no discussion going on anywhere on the internet about the lack of nvidia vista RTM drivers. What's up with that??
Until I can get the basics like this and PGP support working properly, I have to relegate Vista to getting run occasionally in a VM or multiboot.
Vista IS Windows ME, The Sequel.
Only it's worse.
It always scares me when developers confuse technical things. Like the difference between "inherit" and "inherent".
Oh, and this light blue on light gray textarea isn't doing much for me, either. : \
LoL..
You caught my “slipping" and "sleeping" misuse of words. Despite that, I think that windows sucks idea still remains there.
PS: This WYSIWYG html editor sucks too! It could have syntax highlighting to prevent scary confusions.
Thanks for installing a pirated version of Windows Vista, my friends.
You know the 'billgates release'? We made a tiny one-byte change in shell32.dll on the 'leaked' version, acutally we made several (to determine WHO leaked it), but the final internet-released version, it was just one change, a call to an invalid instruction by adjusting jump offset, it wouldn't affect anything unless some special condition triggered it.
In the future, please try to avoid using pirated software ^_^
Sincerely yours, Microsoft
Editor's note This isn't Microsoft, and he's kidding. At least, I hope this really isn't true :@ Doesn't matter to us, we have direct access to these builds from Microsoft, and it doesn't affect the integrity of our tests
um hello0000
sleep has been broken in xp forever, sometimes it works sometimes it dont, been this way forever! sheesh...
You can add unexplained screen resolution changes to your list.
I have Vista RC2 installed on my Thinkpad T42p, and after waking deep sleep, sometimes the screen resolution spontaniously changes to 800x600 for no reason!! Arrghh!!
I thought I'd weigh in in support of the author on this one.
I've been running RC2 on my Asus A6Ja (Centrino Duo platform, 4.2 Windows Vista rating) notebook since it was released and I've had a number of problems with both sleep and hibernate. Originally, the problem was that the wireless networking wouldn't re-acquire my access point. As of late however, I get the solid HDD light, no action scenario when coming out of sleep or hibernation.
Compared to Windows XP and Windows 2000 (both of which I've used for years on various platforms), Windows 2000 had the most robust hibernation and sleep of the three! I had very very few problems with hibernation under XP (on the same notebook even) but sleep didn't seem to work properly all the time.
So, count me as another user with Vista hibernate and sleep problems, desperately looking for a cure!
I have to confirm that for some machines power management is really a problem in Vista. My main notebook (a very recent Acer) won't sleep (it shuts the screen off but the cooler remains on at maximum speed, tha case becomes hot and just a forced powerdown will stop it). It won't resume from hybernate. The display remains black after a screen switch off caused by power management policy. Basically nothing power-related works as expected with ALL drivers comming from Windows itself or Windows Update, a fresh install and all the default settings. XP works perfectly for me while no matter how entusiastic I may be with Vista, I cannot use it. I read this tale over and over again and understand this is a real problem. It is absolutelly the oposite of what MS states about fantastic improvements of the power management in Vista. How unfortunate.
This is a general comment to the author(s), skip if looking for Vista specifics.
Dear Mr. Guru, thank you for this heads up. Most computer “enthusiasts”, well, they would eat there own young. A few years back in one of the ACM journals, there was an article on a first C++ programming assignment. There was a huge response on how flawed it was. Talk about over reacting. I liked this article. I thought your last article about Firefox was pretty much ^&*(hit. If anyone else gets down this far in the comments, I would take not of this and hope that my machine(s) did not have this problem and not be surprised if it did. FYI I think Mr Lopat makes a few good points, but perhaps he is being a bit too harsh. But take his points to heart. Be specific, precise and accurate. Do not generalize. You may have done a lot of work, however, with millions in the user base, odds are you won't cover everything. For example look at the title of this article. What you can say is " We have done xxx amount of work , with these machines, and this does not work" or something to that effect. Your mileage may vary.
12.6 seconds to boot your operating system! For the love of all that is good an holy! 12.6 seconds is just too long. I expect the 6 second boot that Gates promised. In that extra 6.6 seconds I could... uh... well... hmmm... scratch something I guess.
Drivers do matter- I have almost all the same issues after HP installs a new driver for one of my cards occasionally. I fall back to the old driver and everything is fine; sound returns, it will awaken normally, everything loads.
Get a mac!
Hey thanks for the feedback, Gary.
You have to understand the reason for the disparity this and our Firefox article. One is an article reporting the results of a study concerning an aspect of an operating system, the other is more of an editorial-type article, the sole purpose of which is to raise concern regarding something tangible. We didn't anyone to go You know what, they're right, because we were expressing our fear for something that looked inevitable, and we wanted to say You know what, be careful, this might not turn out so good. Hopefully the devs at Mozilla took note.
Anyway, NeoSmart Technologies is nothing without feedback from the readers and contributions from the members, glad to hear from you :)
i am just a random yahoo with no clue, but one thing i know:
if it is from MS then it is destined to suck big time in some or a lot of aspects.
and that's final!
i have no hope that MS will ever produce something truly good.
Soyo SY-P4I865PE Plus DRAGON 2 motherboard Intel Pentium 4 3.20 GHZ HT 2x1024MB pc3200 PNY RAM Windows Vista Home Premium PNY GeForce 7800 GS 8x AGP, 256MB (97.46 ForceWare) PCI Creative X-Fi XtremeMusic LG Flatron L1920P lcd monitor
My computer shuts down when going into sleep mode, but I get no video when resuming along with a single long bios beep. I am unable to do anything but hit the reset button. Vista then shows resuming but screen goes black with a flashing cursor and some junk on the screen. I then have to hit reset again and I am able to boot properly. Any ideas if this has to do with the nvidia drivers or some bios problem? Not sure what a single long bios post beep means. I have Pheonix Award Bios. Let me know please if anyone has any ideas. In the meantime I have disable all sleep options. Thank you!
mhajii210
February 14th, 2007 - Using the RTM version of Vista on my Gateway MP8708 laptop, and STILL no relief for the Sleep/Nightmare problem. I experience several symptoms: GUI freeze on resume though mouse still moves, or no network connectivity with the LAN LED solid but the Network Manager indicating no connection and then a BSOD after 4-5 minutes.
I strongly suspect that the problem is in my LAN driver, but Gateway says it's compatible. I've installed all of the other Vista driver updates from Gateway. Is everyone still having this problem, or is the public version different from the "RTM" version that I got from MSDN in December? All of the sources are quiet regarding this problem, and I'm starting to wonder if it was fixed. Ack.
Sorry Scott, it was never fixed. You can check if it is your LAN driver easily by disabling the onboard network crad from the BIOS, booting into Vista, and seeing if that fixes your problem.
Actually, you can even disable it from the device manager, it should have the same effect.
Good luck with it, whichever way you choose.
A few days ago, I bought a Velocity Micro E6400 machine at Bestbuy for about $1,400 with Nvidia 7600GS I think and it either did not sleep or hibernate or if it did, it would not come out. I called Velocity tech support and after two hours, he told me it was probably a bad motherboard. I returned it and bought the next Veloicyt Micro model up at Bestbuy for about $2,000 but had the so called "Geek Squad" check this new model before I left the store. They had the same problem with this model as well. So I returned it. I doubt any of the Velocitiy Micro computers will do sleep mode or the power saving mode. It was very disappointing.
My trackpad will not wakeup from sleep or hibernate in Vista (full version). I'm using bootcamp on a Macbook Pro. Everything else works, but the mouse doesn't work at all when I sleep or hibernate.
Anyone have a way to reinitialize the mouse upon wakeup?
--Neal
Neal, you either have to delete and reinstall the trackpad from Device Manager, or just reboot. It sucks, I know.
Computer Guru-- thanks for the heads-up. What a time consuming fix... especially since I have to do this all without a mouse, takes forever with the keyboard.
I think there was a solution out there... something about reinitializing the mouse each time it wakes-up. But I forgot the blog and can't find it now.
Neal :appl:
Well Neal, if you ever do find that blog again, do post back, 'k?
Thanks! :)
Most Odd...
Vista Ultimate on a Presario 1516 4 years old Laptop with P4 2GH, 512MB and radeon IGP 340 64Mb shared memory. I install in it to have a first look before use Vista on my Bussines.
All working right, suspend and hibernate if I use the desktop button, but if I suspend the system by closing the lid the screen don't resume.
Any sense on this?
Continued....
My Vista is not Rtm but final version bought at a store.
My Conclusion: It's not a driver problem, nor a Bios problem, it is just some kind of bug.
Well, RTM means final version.
Anyway, I think you need to install the latest ATi Drivers to take care of your problem: http://neosmart.net/blog/2007/final-ati-drivers-for-windows-vista-rtm/
Folks,
Make no mistake about it - it's a real problem. I have logged 16 hrs on with tech support on this and my problem still exist. I'm now waiting for research to call back - in the meantime I've been down for 4 days now.
INTEL® Core 2 Duo E6600
ASUS® P5W DH DELUXE
320GB SERIAL ATA II HARD DRIVE
512MB GEFORCE 7900GS
WINDOWS VISTA Ultimate
Just spent 2 days recovering a brand new PC with Vista ultimate, all caused by the sleep 'feature' killing Vista ! Could not even boot from a clean restore of Vista using the 1506 BIOS !
Following the crashes when using sleep, could not boot a clean install of Vista using BIOS 1506 and eventually needed to upgrade BIOS to 1901, this allowed me to boot and finally get Vista up and running with TV card and latest Nvidia drivers.
Vista/applications seem OK, but sleep mode is still a big no no and I've had enough of backup/restore over the last 2 days and nights.
Any news on a fix for this, as the general consensus appears to be that its a Vista, not a bios, problem ?
Woo hoo!! It happened again, but this time I received the following message (after "Check for a solution to the problem"). Please note the HUGE mea culpa ("my fault") offered by Microsoft in the message.
WOW. I'm giving it a try now.
Ack. No dice. After 40 minutes on the phone with MS Support to get the hotfix - Windows6.0-KB931671-x86.msu, I applied it. I rebooted, browsed the internet, clicked the sleep/suspend button with my mouse, waited a couple of minutes, pressed the power button on the laptop to power it back up, unlocked the screen, and... no network connectivity. The Network Sharing Center just showed a blank white window. Then, as I expected, Vista crashed with the same BSOD "DRIVER_POWER_STATE_FAILURE" or whatever. After rebooting, the problem resolution tool told me that there was a solution to this problem... but it was the solution I just tried.
So, I wait patiently for another "fix" while I consider getting a new Mac Powerbook.
doh you got me excited there for a minute, scott... I might try it just on the off chance that i get better results... thanks for posting the info...
Hey Scott,
Would you be willing to provide us with a copy of the hotfix so we can test it on a couple of machines and see if it even works at all for anyone?
If you're willing, just shoot us an email over at NeoSmart@NeoSmart.net
I am prevented from sending the file to you. The usage agreements, end-license-agreements, and support agreements clearly prohibit the redistribution of the file by me. That said, I'm sure that you'll have no trouble finding a source for the file. We all look forward to your findings.
I just did a bit of research of my own, my MS contact says he has absoloutlely no idea why they gave you that update for your problem.
This is a very specific hotfix, and it only addresses issues where you get this only when you are connected with a modem to the internet, and you put your PC to sleep. If you have this issue when your not using a modem, this hotfix doesn't apply.
I understand about the EULA, thanks anyway.
Here's the KB-article that clears up the hotfix and when its needed: http://support.microsoft.com/kb/931671
(damn!)
Major Update
I've received a list of related issues, patches, and hotfixes from Microsoft. You can see the entire list above, but there are many KBs involved. None of these can be had from Windows Update at the momement. You must manually download the hotfixes you need.
Some of these hotfixes can only be obtained over the phone. Just tell the Microsoft support representative you found this hotfix via the article on NeoSmart Technologies at http://neosmart.net/blog/2006/vistas-hideous-wakeup-support/ and describe your problem in detail to the support professional. They'll email you the update free of charge if they think it'll solve the problem you're experiencing.
These updates will later, upon further testing, find their way into Vista SP1 or a Windows Update release, if you're willing to wait it out.
FYI, the touch pad issue on wake-up occurs in my ACER (purchased with Vista pre-installed) about once a week (machine is put to sleep several times a day). The solution for this was: Control Panel|Mouse|Device Settings ... then press the "Reset Devices" button. The Device Settings tab appears to be a Synaptics tab so it might be different for other notebooks.
But it does work and you can get there all via keyboard. Annoying, but no reboot required.
I read your article about sleep/hibernation problems with Windows Vista and, quite frankly, I thought you were talking about another Windows Operating System entirely. I've used Windows Vista Home Premium (off the shelf software, not beta) now since its release and have had none of the issues you have discussed here, and I hibernate my Compaq Presario PV5119US laptop all the time.
this news is pure FUD because my Windows Vista works great on my PC
Paul, it's not FUD. If software development were as simple as "If it works on my machine, it's bug-free" then Windows would be the most stable piece of code ever. Don't think that MS makes it buggy on purpose, these bugs only appear when testing on different platforms with different software, settings, configuration, and hardware.
Anyway, as the Slashdot users were pointing out (thank you!), how can it be FUD if Microsoft admits to these sleep-related shortcomings, and ATM, 80% of all the SP1 patches are for sleep/hiberation-related issues?
Fiddling with your video driver usually solves it, apparently Nvidia still has a bit of work to do.
http://www.nvidia.com/object/vista_driver_news_022207.html
Try either the latest drivers maybe or removing the nvidia drivers and let vista install the default OS drivers.
I installed MS Vista Business 32-bit on my P4 3.2 Ghz, 1GB RAM, Asus P5GD1 (Intel 915P chipset), and I too am having issues with the Hybrid-Sleep function. Sometimes it work, sometimes it doesn't.
I have tried putting my computer into sleep maybe 30 times now, but every few attempts, the computer will completely FREEZE up either just BEFORE shutting down into sleep mode (computer still powered-on but frozen), or, if it does properly enter sleep, it freezes AFTER I try to restart the computer. This happens, on average, every 3rd or 4th sleeping procedure. It's random; it can freeze the first time, or the 8th time-- there doesn't seem to be any rhyme or reason. All I can do is hit the power or reset button the computer.
I have tried different many different settings-- both hybrid-sleep and just sleep, and other Device Manager Power settings for mouse, keyboard and LAN to no avail.
My computer refuses to wake up after Deep Sleep. Screen remains black.
I'm not having any of these issues you folks are having with Vista Home Premium on my Vista-Capable (designed for XP) laptop, a Compaq Presario PV5119US.
I have the sllep problem on my new Dell XPS that was loaded with XP then upgrade to Vista!!
I wish I could put Vista's ASS in a DEEP SLEEP forever!!!Vista sucks!!
E-mail sucks!!Speed sucks!!Sleep Sucks!! I ask Dell if I could just load XP back on my System and they told told me it would be a real pain to do so.
So why did they charge me an 30.00 for XP re-install?
Dell and Vista are both alike....GIMMIE YO MONEY AND *#$% YOU!!!
Hope yall check my &^%$#) GRAMMER!!!!
Well I am having big problems with suspend / resume on my Acer TravelMate 5620 with Vista Ultimate. This machine is "Windows Vista Premium Ready". On resume (every time) hangs for a while then prompts to boot into safe mode. The only way to get back into normal is to boot into safe mode then restart. So obviously I can't use suspend / sleep at the moment.
Also after booting (event on a normal start) - my dual monitor set up keeps swapping the screens around the wrong way - really annoying!
Sure hope SP1 is our quickly or I might just go back to XP!
I have a brand new Gateway system. Right out of the box, you boot it and everything works fine. I can access the internet using my DSL with no problem. If I put the machine to sleep or hibernate it, when awakened it will not access the internet. The system still sees the internet connection, I can go to command and ping my I.P. provider with no problem but to use my computer/internet explorer I have to restart my system. Gateway has been of no help, matter of fact saying that they have customer help is a joke. Based on this experience alone, I will never buy another Gateway.
Is there a workaround a non-professional I.T. person can use to make my system work from "sleep/hibernation" ?
Randy, your problem is EXACTLY like mine. In fact, if you wait long enough after resume, your computer might get a "blue screen of death" (BSOD) with a POWER_STATE_FAILURE message. After resuming from sleep, mine actually will hang while shutting down, and I have to press-and-hold the power button for 5 seconds to force a power-off. The bad news: There is currently no workaround that anyone (techie or non-techie) can do to fix it. I have a Gateway MP8708 and haven't bothered calling Gateway support. I am hoping that Visat SP1 will solve the problem, but I can't be sure!
Uh, correction: HOLY CRAP - I found a fix to my problem. I installed it and it worked! I have a Gateway MP8708 laptop and had a problem similar to the one Randy just described.
KB Article: 929734 - "You may experience problems after you resume a Windows Vista-based computer from sleep or from hibernation" -- http://support.microsoft.com/kb/929734
They sure didn't make it easy to identify, but my clue in the sea of clues was the phrase "...after this problem occurs, the computer may stop responding when you try to shut it down or to perform a restart." This is a hotfix, so I had to call MSDN tech support (and evade their insidious 'you must pay' mechanisms. Once I connected to a human, all I had to do was say "I need a hotfix" and give him the KD Article ID. Hotfixes are definitely available at no charge to MSDN subscribers, and maybe available free to everyone? The support rep warned me that this hotfix was not regression tested and that they recommend performing a full tape backup of the machine before installing the hotfix. (I, of course, did not do a full backup. I live for the adrenaline.)
Best wishes to all of you who have not yet found your fix. I felt your pain.
Wow, I'm really happy you got that working, Scott! 929734 is in our list up there, the very first one actually - if only they'd made them available on their site maybe one wouldn't need a very good reason before just downloading it and seeing if it works.
Scott, thanks for taking the time to post a possible fix for my "Vista" problem. I downloaded the hotfix and gave it a try but unfortunately it didn't solve my problem. Still I appreciate you trying to help me with this mess.
I have just about reached my maximum frustration point and will most likely return my new system to Best Buy where I bought it. I will then return to my trusty old XP system which has never given me a single problem.
In the big picture, after this experience and trying to get help from Gateway and Microsoft, if appears that they really don't care if I am a happy customer or not. There to big to care about one customer. If I return my system and leave dissatisfied, they apparently don't care.
Again, thanks for the information on the Hotfix. Good luck to you and all who "TRY" Window Vista.
There is a hotfix available for the issue that networking wont start up again after recovering from a sleep. Here is the hotfix:
https://premier.microsoft.com/default.aspx?scid=kb;en-us;933872
Hope this helps somebody.
Ronald
Thanks for the hotfix Ronald. Unfortunately the download link you provided is only valid for paid subscribers to Microsoft's software assurance program. However, I've added a link to the main knowledgebase article in the post above. Thanks!
I also added another KB article to the list: http://support.microsoft.com/kb/933778/en-us
my Acer (brand new, Vista ready, AMD64, cheap but decent) will not respond AT ALL, to any button push, after going to sleep. You computer geeks give me a headache....HOW DO I FIX THIS? ACER sent me to this web page, and I still am making zero progress.
Hey Mark,
The only work around is to go into the BIOS-> Power Options -> Standby Mode and change it from S3 to S1.
Good luck.
Should have bought macs...
I have a lappy badged Vista compatible, and Lenovo supports it as such, but it still freezes often on wake up. I'm installing Intel's AHCI driver right now, as the KB says the (945GM) problem doesn't occur with it. Sucks that they won't give me the patch. I don't feel like downloading it off some sketchy website, and I really don't feel like calling support right now.
One possible solution for systems with nVidia graphics:
[BUG] “On resume from hibernate or sleep, the monitor only shows black but the computer is powered on. This can be worked around by completely turning off your computer and then restarting it."
[FIX] nVIDIA believes this issue is fixed in v101.32. Please download the new driver and if you are still experiencing problems, please submit a bug report.”
http://www.nvidia.com/object/vista_driver_news_030207.html
The latest beta is what finally worked for me; and I did not use any hotfixes. But after I installed the driver, the HIBERNATE option disappeared. See this for more info:
http://bloggingabout.net/blogs/erwyn/archive/2006/11/25/Windows-Vista-Hibernate-Mystery.aspx
The comments that "if this were Linux, failures like this would be treated as the end of the OS" are hilarious, and couldn't be further from the mark. The latest supported distributions of Linux from Novell and Red Hat can't even sleep or hibernate on my new laptop (or my old one, from a different manufacturer) without adding unsupported patches from random sources, and even then it doesn't fully work. The difference is I don't really expect Linux to work with all my hardware, so I just shrug off the failures. With Vista, I expect it to fully support every piece of hardware in my computers, and if it doesn't, I'll complain. I think a lot of Linux + Windows users have similar expectations.
Whether it's Linux or Vista, the real problem is you need support from the hardware firms. If they don't write high quality drivers or provide specs for their hardware, there's nothing the OS can do to magically make it work properly. Where Microsoft have the advantage is in having the support infrastructure to report all of the various failures sent in from users to the hardware firms, with debug dumps and other details, as well as the market power to (usually) convince them they should actually fix their drivers.
...i too have wake up problems. New Acer desktop 1.8 duo with 2GB ram. Had Vista Home Premium installed on it, and bought Vista Ultimate and installed that - need remote desktop.
In Home version, sound would disappear and just get the default gong. Now with Ultimate, my Sidebar items don't function, like the weather/temperature.
As for booting up, from the login screen it is 20 seconds loading everything. Partially not MS fault, could be Kaspersky checking everything, but no different in boot up time from my old XP with TrendMicro with a P4 2.8 1GB.
Apart from that, my Corel PaintShopPro is dog slow now whereas on XP loved it.
I spent $300 for dang FPI - Fisher Price Interface, should have stuck with XP.
I FOUND THE FIX!!! without you having do change anything with ACPI LID. download http://thehotfixshare.net/download/download/Language%20Neutral/Vista/Windows6.0-KB929577-x86.msu and this should fix your problem. I now have had no more black screen problems after waking from sleep!
Yeah, it's listed above. I'm not sure if the distribution of these packs is legal under the Microsoft EULA, so we're not providing download links in the article.
Glad you found that works though :)
Finally resolved my issue: http://support.microsoft.com/kb/934237 But... MS requires you call or email for the hotpatch and they send it to you as a link to a password protected zip file.
My machine fails to wake (power comes back on, fans going etc but no windows) from sleep.
The weird part is that my motherboard, cpu, memory, graphics card (Core 2 Duo E6400, 2 gig of corsair xms-2, Abit F-I90HD MATX motherboard with onboard Ati x1250 graphics) worked fine in my antec sonata case with Vista Ultimate but when i moved the components to a new Antec NSK2400 case and did a fresh install of Vista Home Premium on a new hitachi hard drive i can no longer wake from sleep mode.
Thank you very much for this article! The first two hot fixes on your list fixed an issue I was having on my Dell Precision; I would put it to sleep at night, and at around 5am it had a task scheduled that would wake it up. 50% of the time the computer would freeze immediately after waking, and I'd find the login screen frozen on the screen. The two hotfixes seemed to have fixed it.
Ugh, my computer was frozen this morning after waking itself up. So I guess the patches I applied weren't the real solution to my problem. And the other patches don't seem to address my issues. I hope Microsoft fixes this soon.
my laptop does not have a problem with a usb, firewire, network or other kind of device, BUT the screen does not turn on after sleep mode. and the links below explain the problem to fix, and none is my case...
does nomeone knows anything else?
I have a brand new machine (Sony Vaio) with Vista pre-installed. Didn' have choice, Sony has switched to Vista first day. It has (or had) some of these sleep/wakeup problems. I think this definitely means that either Mircosoft or Sony are at fault, or probably both.
What I really don't understand is one thing: what are Vista's advantages? I am sure there are (or will be) some, but at the moment all it is giving me is a lot of headache, plus runs slower than XP would (ttat's hearsay, I didn't run XP on it) and eats battery more quickly.
If anyone knows any advantages, please let me know. Sorry I am not a professional (by a long shot).
Interesting thread. I just stuck my head up to see if there were any recent progress in this area for XP. My history of the problem goes like this. My old P III 1.13 Dell Inspiron with XP had no problems whatsoever. Then I purchased a Dell Inspiron 9400 Centrino Core Duo loaded up and Gold Technical Support. It's been through all new internal components once, that means MB, Video, hard drive 3 times, memory twice, Blue-Tooth twice, etc. Next was a complete system replacement. After that was a new video again. I have at least 60 hours working with tech support, and at least 240 hours working on the problem. The problem can be avoided entirely if the only thing on the computer is the OS, and no updates. I've proven that. However, even if you simply add Microsoft Office and do the critical updates to the operating system, the problem will return.
You will hear lots of theories on the KB about "some" process running that prevents etc. You can cross that decoy off your list. They had me chasing so many rabbits in this area that I lost track. If there is a process causing the problem, it's a Microsoft process. The only driver MS has a basis to do any finger pointing with is the video driver where they are only partially responsible. Everything else is under the control of HAL. I thought perhaps I should have gotten the nVidia instead of ATI. That's the the case either.
The dragon has many heads, and you will see a new one every time you change your power management settings and the amount of RAM. For instance, in my case, if I set it to hibernate when I close the lid, then when it goes into standby, it will not wake up. The way out of that is to close the lid, wait for it to hibernate, reopen the lid, and start it back up. If I don't set it to hibernate when I close the lid, then sometimes the hot key can make it hibernate, and sometimes not. It seems to be time related. The longer you use it before you ask it to hibernate, the less your chances are of it hibernating. When it fails to hibernate, it disables the hibernate function, it cannot be re-enabled, and the computer is unstable. The only cure is to reboot. I have a bag with an open top, so I put it into the bag on standby with fans facing up when I travel to a customer. If I cut my ram to a gig, I will have far fewer problems, but that's not near enough ram for what I do.
The problem has slowly gotten better over time due to updates. I don't see that BSOD anymore. That disappeared months ago. IMO this is squarely a MS problem. There are many different hardware and software combinations out there that manifest the problem. If it were due to one of those, the problem would be much less widespread and the offending elements identified. The MAC has no problems in this area running on essentially the same hardware.
Don't hurt yourself financially chasing this rabbit. Just stick your head up once in awhile to see if there are any finds in this area. Chances are it will go away on its own and no amount of fretting or pushing on your part will make any difference.
PS: Another such technology is Bluetooth. I have lots of mice and keyboards, and don't use any of them. I have about 60 hours in this area. If you want wireless, don't get Bluetooth. I've done Widcomm, Microsoft, and Toshiba. At length, they are all trouble.
I have a similar wake up problems on my HP Pavilion dv6000 notebook after long hours of sleep. It just doesn't accept a regular user password, though it does accept a password for an administrator. However, there's a difference in password complexity: administrative one doesn't use special characters, but for the regular user one I need to use AltGr+number combination in my local language keyboard... Maybe that is the problem...
We have a brand new Lenovo 3000 N100 shipped with Vista home ed. It also has had the blank-screen of death. First time, being a laptop I couldn't hard boot it without removing the battery (thus causing it to fail on restart and I had to rebuild it.) Second time, it decided to wake up at 3AM as Ron says, to do some routine "maintenance" and then decided to BSOD. This time, being wiser, I left it on and the let the battery run out such that it would shut down. I find it remarkable that an OS is released that causes a brand new (certified) laptop to crash. Isn't it like buying a car but if you turn the wheel it might suddenly stop when you are driving along?
The Linux kernel is already 100 times better than the Windows Kernel. That being said, it's what the Distros do with that kernel and how they use all the other FOSS and proprietary combinations that make it as good, or better or in many cases... worse than Windows. I still have yet to find an OS I would feel safe installing on my mother's computer. While Windows has it's problems, and their kernel sucks ass... they still manage to cobble together a better OS than all the other contenders. That is only for the desktop mind you.... and yes... I think that Windows is better than Mac OS X, which I've had only friggin nightmares with.
For servers, Linux cannot be beat as far as I am concerned... but on the desktop, Microsoft is King.
I need a patch for
[KB-928135] - Windows Vista hangs on resume/wake [KB-929734] - Many problems on resume/wake
I do not manage to get them on your website.
Thanks for providing me with the relevant program.
Best regards
well, at least i'm not alone with vista sleep problems. my gateway laptop gets the bsod about 3 of every 5 times i try to resume from sleep mode. sometimes i get the message that a wait, attach or yield process was detected from a drc routine, and THEN i get the bsod.
I have recently built a home-theater PC running windows vista ultimate edition and my PC hangs almost every time it is awoken from sleep/hibernation modes. The PC consists of:
Asus P5W DH Deluxe Socket 775 ATX motherboard.
Intel core 2 duo E6700 2.67Ghz CPU
Diamond Radeon X1950 Pro/256Mb PCI Express
Hauppauge WinTV-PVR 500 dual TV Tuners
Patriot Dual Channel 2048Mb PC6400 DDR2 800Mhz RAM
Seagate 500GB Serial ATA HD
I cant believe I paid $200 for Windows Vista and it doesn't even work properly. Ofcourse I'm not allowed to return this faulty software for a refund! How frustrating!!!!! Maybe I should have just downloaded a pirated version instead, atleast then I wouldnt feel bad about erasing it and installing some more reliable O/S!!!
I've tried installing a hot fix
[KB-928135] - Windows Vista hangs on resume/wake
but this didn't help.
I hope Microsoft releases SP1 soon and hopefully that will fix the problem. Otherwise, I wonder if we can file a class-action lawsuit to get our money back? :)
Nick
I have two problems, one with a Sony Vaio notebook that when resuming from sleep, the screen does not come back on and a Dell E520 desktop that will not go to sleep, pressing the sleep button simply turns the screen dark for a few seconds then pops back to life again. Any tips would be parreciated. I have installed latest graphics drivers and BIOS.
I have the same problem when waking up my laptop(ferrari 3400) from sleep..the screen is blank...i tried with different vista and worked fine...so vista is the problem..and hw could they make softwares only for new machines and also stop the support for xp at the end of this year. MS should learn from APPLE in releasing operating system, compatible with both very old pcs and new pcs aswell.
I don't yet see a hotfix (or many reports really) for the condition of an intermittent hang on sleep itself but never on resume, the condition I'm seeing with the below hardware and Vista Ultimate 32
Sometimes it sleeps fine, others not, but when it does sleep fine, I've never seen a problem on resume.
Based on another post http://www.superwasp.net/weblog/2007/05/solving-your-vista-sleep-problems.htm I plan to focus on the Creative card by disabling it and seeing if that seems to change anything.
I'm also toying with the idea of installing XP just to rule out the OS/drivers but since I would only run Vista regardless of sleep issues I'm not in a real hurry to prove anything there.
===
Asus P5W DH 1901 bios
Intel E6600 at stock speed
G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
EVGA 640-P2-N821-AR GeForce Nvidia 8800 GTS 640 MB (v160.04 WHQL drivers)
SAMSUNG SpinPoint T Series HD400LJ 400GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM
ATI TV Wonder 650
Creative X-Fi soundcard
CORSAIR CMPSU-520HX ATX12V v2.2 and EPS12V 2.91 520W Power Supply
A couple more salient bits:
http://thegreenbutton.com/forums/permalink/180530/180532/ShowThread.aspx#180532 Re: Sleep takes forever Check your Diagnostic-Performance logs, it will tell you exactly how long it took to enter sleep and what caused the delay.
You can get to the logs from either Control Panel\System and Maintenance\Performance Information and Tools and selecting Advanced tools then View performance details in Event log or by running Event log directly (eventvwr) and expanding to it under Applications and Services Logs\Microsoft\Windows\Diagnostics-Performance\Operational.
I would recommend using the Advanced tools option since it does a good job of recommending fixes and warning you of possible issues.
If the suggestions that the Advanced tools gives you doesn't help then in the Event log you'll see events similar to the below ... To enable the kernel power diagnostic event log:
Open the Windows Event Viewer. On the View menu, enable Show Analytic and Debug Logs. In the left tree view, navigate to Applications and Services Logs - Microsoft - Windows - Kernel-Power. Right-click Diagnostic and select Enable Log. Restart the system. ...
Sorry for my english!
I have FSC Amilo xi 1546 notebook with VISTA ULTIMATE. I had problems with wake up-black screen from sleep. But now I install Windows XP drivers for my chipset (intel mobile 945PM Express Chipset 7.2.2.1007) and the problem was gone in a second.
I hope that this will help somebody, because to me did.
<blockquote>I managed to get around the problem on the Vaio notebook by changing the power settings to enable hibenatw instead of sleep, it's not as quick to power down and boot back up but the screen does come back!
The Dell PC still has the sleep fault where clicking the shutdown button (set as sleep as default) tries to put the PC into sleep but then within a couple of seconds springs back to life again. I am still trying to get a fix for this!!
Regards
Ryan</blockquote>
I have a ASUS P5B, 8800GTS, 4GB RAM.
System goes into S3 state fine, but when it wakes I get a black screen then it automatically reboots.
S3 did work fine on this system, I don't know what has upset it, I'm think it must be the updated Nvidia drivers, or something has changed in Vista.
Honestly, the best thing you can do until SP1 comes out (hopefully, at any rate) is to set your BIOS to use S1 sleep mode instead.
Yep I think you're right, thanks ;)
Rather interesting stuff I've read on here. I had exactly the same problem with the sleep function. My HP D530 Would just crash everytime it went to sleep. But, a Microsoft Update has fixed this.
I'm not free of the problems yet though; I use a P4 2.8GHz/1.5GB RAM and a 40GB Hard Disk & Also a 80GB Hard Disk for all my downloads. Ive had enough of IE7 and Media Player, so I downloaded Fire Fox and WinAmp. But STILL, my machine runs like its a 486x, I check task manager and my CPU is constantly strained at 100%! Does anyone have the same issues ?
...sadly, this has been the second time I've removed an OS completely out of frustration. First was ME, now Vista.
Went back to XP Pro and no problems. Even went to desktopsidebar.com and get a sidebar for XP.
From bad recovery on sleep to playing some simple games (like Flight Sim 9 and X) there seemed always a "gotcha" with Vista.
Even the sidebar goes spazzy once in-awhile, have to reset the stock options or digital to analog clock. After 3 years of playing with Vista Beta, thousands of 'testers' or users trying it, and I am suppose to pay $400 Ultimate for what, an OSX knockoff? I'm missing something.
tomax7, I know a lot of people (here at NST and eleswhere) how did the same thing. We're all just hoping SP1 improves it or else we're in big trouble, because XP is getting more and more dated by the day.
Big Frank: in the Task Manager | Processes, which process is taking up all (or 50%) of the CPU?
...Big Frank. Do you have Office 2007 with Outlook Contact Manager? That was a culprit on my machine. Removed CM and things quiet down.
Also another villain is Vista Indexer. I turned it off and that helped. Check your Processes in Task Manager like CompGuru said.
Here's a question (I should ask MS).
Why in the "Business Edition" Bitlocker is not included? You'd think for laptops that would be a selling feature, ironically most laptops today are sold with Home Premium pre-installed.
Meaning people have to go out and buy another edition (thereby falsely increasing Vista's sold count) to make it more secure. Oh wait, don't get Business edition, but have to buy Ultimate.
Sadly one can't run all the bells and whistles they paid for with Ultimate because of the graphic's card and RAM installed (let alone HD space) on a laptop usually isn't enough.
Can't win.
Thanks for getting back so quickly.
There is nothing taking up over 50% CPU power as far as I can remember, I'l have to have a look when I get home. But I have had a good look through the processes recently and cant see anything unusual. I dont have Office 2007 installed yet so I can exclude that one. I'll have a look at the processes again tonight and see if I can find that indexing one. I have recently replaced a bad 512mb RAM Chip just last week. I thought that was the cause but obviously not as its still happening.
What about my torrent client 'Azureus'? Its a memory hogger but I have 1.5GB RAM and I havent heard of processor problems with it. I'll be able to explain the problem better when I'm using it. Will have to check back later on to give you a clearer idea. Can I upload screenshot on here?
Cheers guys and girls. :0
Big Frank, just open a new thread here: http://neosmart.net/forums/
You can upload as many screenshots as you like in our forums :)
Cheers Tomax, I just wrote 2 paragraphs back but IE crashed and I lost it. So I'll do what you said when I get back from work and report my findings back here later on.
Oh, I dont have Outlook 2007 installed yet. I dont think I will bother after what you said mate.
Cheers. :))
Opera: The one browser to rule them all.
Honestly, IE7 is great on paper, but it's performance is absoloutely dismal. Opera has yet to disappoint me even once.
I've read that there is a Microsoft hotfix for the black screen problem, but I've tried the files that have links here & they say they are not for my system.
Has anyone got the fix for Vista Home Premium 64 bit version?
Which KB?
It's this http://support.microsoft.com/kb/937500/en-us
Cheers people. Here is the link to my thread. i will sort out some screen shots later. Muchos Gracias http://neosmart.net/forums/showthread.php?p=5042
Overkill, you can download it here: http://thehotfixshare.net/download/index.php?dir=Language%20Neutral/Vista/
Thanks, but I can't find it, I can only see the x86 version.
The article number is 937500, so does that mean the patch is KB937500?
If you can't find it there, then you most likely won't get it anywhere else - just keep checking that page, I guess.
Must be my ASUS P5B bios, because it doesn't work in XP now either :(.
It was working in Vista, must be since I've updated my bios.
If you want to get down and dirty, there is the
powercfgutility which lets you decide exactly what happens.Start | Run | cmd.exe
powercfg /?If you need anything else, please ask in the forums.
Here's my experience, with a Toshiba Tecra m4 and an Acer Aspire 5610Z, both with non-OEM full retail Vista Ultimate installs:
The older Toshiba seems to work just fine, no issues at all. However, the Acer is awful. I estimate that about 9 times out of 10 if I close the lid, then it seems that just the screen blanks, and it will not resume afterwards. It doesn't matter if I set the