Boot camp with xp can't go into stand by

Exact same problem for me. I've seen similar problems in other threads that have come and gone without reply.

My problem is that if I close my laptop when XP is running, it will (more often than not), get hung up on the "Preparing to Standby" screen (without actually going into Standby mode ... often getting my machine very hot in the process). If I run on battery power and leave long enough for it to go into Standby mode on it's own, it simply hangs on that screen, with my only option to hold down the power key to shut it down.

Anyone out there know why?

Having an issue not quite like either, but something like this. I may start a new thread as I have not been able to find this problem anywhere in the discussions. I can run windows fine, but when my MBP goes to sleep (I guess) in windows, I get a black screen and it won't wake up. I have to power down and restart to get anything. Then today I thought I had powered it down after this happened, and when I pulled it out of my bag 20 min later, it was hot and the fan was running continuously. Have you guys seen anything like this, personally or in a thread somewhere ? Let me know, I'll be watching this thread. Thanks Steve

Full OEM version of XP SP2, installed fine.

This is happening to me as well. I can't remember if I could sleep and wakeup properly previously (I don't use boot camp too often on my first gen MBA), but it's been hanging and heating up once I close the lid lately.

I have no solution.
Just wanted to note that I am having the same issue as flyersfan.
Using XP SP3.

I have the exact same problem using a MacBook Pro
1. It won't go into standby.
2. It won't go into hibernate

The problem recurs constantly.

There allegedly was a solution on this page:

http://discussions.apple.com/message.jspa?messageID=6467897
But it is no longer accessible.

I am concerned for the longevity of the computer.

Also, it raises all kinds of issues ranging from overheating of the unit to safety of its operation.

I did find one clue, that the running of certain programs increased the likelihood of the standby problem to occur. However, even without that program running, it now occurs constantly.

I had this problem reported by several others here. I fixed it yesterday by disabling (within Windows XP Pro SP3) the Apple OS Switch Manager service called AppleOSSMgr.exe. Now standby, hibernate, restart and shutdown all work fine, multiple times. If you are not sure how to disable a service in Windows, read the advice here: http://www.overclockersclub.com/guides/windowsxpservices/

Unfortunately disabling the Switch Manager service did not fix the problem for me. I've been having the same symptoms as others on this thread with my MB Pro.

I can go into standby fine, but about 75% of the time, I can't wake it up (screen stays black no matter what you do until you force a power off and turn it back on). I would very much like to know how to fix this. Anyone at Apple read the forums? If so, we sure could use some advice! Thanks.

(My Apple OS Switcher service is disabled)

Same problem here, the computer can go in sleep mode, the power light flashes slowly, and hard disk stops. BUT!Q But but but when I press a key to wake it up, everything but the screen seems to wake up.

I've tried disabling the OS Switch Manager, checked and unchecked "password Required", even reformatting XP since it was a new computer. No,luck, and no further ideas. Same thing with BootCamp 2.0 and 3.0. (I upgraded to Snow Leopard) to get the latest drivers.

Sometimes, when I play with the power options, I can get the screen to turn back on but the mouse (and everything else) freeze about 20 seconds later...and then I have to do a hard restart.

Anybody encountered this problem?
And most importantly, anybody fixed it?

Same for me. I shall watch this thread for a fix

Yessssssss! It works!!!!!!!

I had the smae problem. When waking up from stand by, XP screen would be completely black, or turn back on for a few seconds with artifacts on the screen, before freezing again, thus needing a hard reboot by holding the power button for a few seconds.

*Here's how I fixed it* : *Disabled Bluetooth radio in device manager*.

+chriswilliams : "i had this same problem on my old macbook pro, the solution i found was turning off the power management for the apple built in bluetooth device in computer management in XP, try it and see, it works for me" === found on === http://discussions.apple.com/thread.jspa?messageID=8672991+

So! To do this:

Click on:
- My Computer
- System Properties
- Hardware
- Device Manager".

Then right-click on the bluetooth devices and click disable on the Bluetooth radio if you never use it. It worked for me.

IF YOU USE BLUETOOTH, try to just disable the power management options of this device. It might work just as well, but I didn't test it.

I hope it helps.

Thanks chriswilliams and everyone on the forum!

fwiw,
i have the same problem on a fresh win xp bootcamp install (windows updates installed as well). After initiating stand-by the screen goes black, backlit keyboard still on , and fan still spinning. need to force shutdown to get out of this.
I tried disabling the bluetooth and the Apple OS Switch Manager, but this didn't resolve the problem for me.

Hi,
I seem to have fixed it at least for my case. Here is how:

I went to control panels -> Administrative Tools -> Event Viewer -> System

There i saw an error listed caused by "nv" which happened during attempting to go into stand-by. Here the description from the log:
" The driver nv4_disp for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates."

I checked with Nvidia and downloaded their latest driver package
http://www.nvidia.com/Download/index.aspx?lang=en-us
( used Option 2 to automatically detect the graphic driver)

Installed, rebooted, and now i can get in and out of stand-by mode. Wohoo!

Hope that helps someone else as well

Message was edited by: SebastianV

Hey all,

I'm having the same problem here: I can always successfully stand by at least once after a fresh restart. But usually by the second or third stand by, it progresses to that light blue "Preparing to stand by" screen and just hangs until I do a hard shut down.

I have tried several things fruitlessly:
-Disabling bluetooth radios.
-Turning off wireless before standby.
-Even though I have never received the "nv" error in my Event Viewer, I followed SebastianV's procedure for updating the NVidia drivers, and it seemed to work for a bit--I had a streak of about 15 successful stand bys in a row immediately after the update, but then the stand by failed once, and ever after, my stand by hangs again on the 2nd or 3rd try after a fresh restart.


So I tried something else:

I tried what SebastianV suggested by going to the event viewer (Control Panel -> Administrative Tools -> Event Viewer -> System). I do not receive an "nv" error. Instead, I get an error whose Source is DCOM and whose Event designation is 10010. The error repeats every 2 minutes for the duration of the time I allow the computer to hang on the "Preparing to stand by" screen.

I did some googling about the DCOM error, and followed the instructions on this page:

http://blogs.msdn.com/distributedservices/archive/2009/01/21/dcom-error-10010-in -the-event-logs-and-sluggish-server-performance.aspx

So I created a restore point and then went ahead and edited the permissions on the HKCR\CLSID registry key to look like those presented on the above site. Upon restart, Windows operated absolutely glacially. However, it seemed to fix the standby problem: I managed 5 stand bys in a row without the computer freezing up. Windows was moving so slowly though that it was basically worthless, so I reverted back to the restore point I had created.

After having reverted back to the restore point, the stand by problem occurs just as it did before. Except now, the Event Viewer doesn't log a DCOM error when there's a failed stand by. In fact, now it doesn't log any error at all in association with the failed stand by.

Does this ring a bell with anybody? Do you think I was on the right track by editing those registry permissions?

Thanks much