Solved Bluetooth doesn't work after resuming from S3

I have this exact issue:

A Bluetooth device stops working, and you receive error code 43 together with event 17 after you resume a computer that is running Windows 7 from sleep

It used to happen sometimes on Win 7 32 bit, I've now changed to Win 7 64 bit and I can replicate it everytime I put the machine in and out of sleep.

The only way to fix is to use a different USB mouse to go into Device Manager and disable/re-enable the bluetooth device.

The reason for my post is that I requested the hotfix, yet upon trying to install it, I get a message telling me that it's not applicable for my PC? :shock:

Win 7 64 bit Home Premium, SP1, with all available Windows updates installed.

Any further ideas?

Thanks

Usually power state errors like this can be resolved through driver updates too.
Have you pursued seeking driver updates via the company that provided the device?

Hi,

As per MS' own site, i'm using the default (possibly even generic) driver found via Windows update, which is stated to be Win 7 64 bit compatible

Windows 7 Compatibility for Belkin Mini Bluetooth Wireless Network Adapter: Belkin. Drivers, Updates, Downloads

I'm attempting to download an XP/Vista 32/64bit one from Belkin's site as a test. Will post back with results.

EDIT: Interestingly that seems to have worked and also taken the amount of time it takes to go to S3 sleep in the first place down from about 50 seconds to 10. Won't count chickens just yet but looking promising Just fingers crossed that the old AHCI issues with S3 have gone after redoing the AMD drivers!

They haven't really been 100% with that, as they generally take the manufacturer's word that it is updated. Unfortunately a massive number of manufacturers simply repackage vista drivers as win 7 drivers.
The primary difference in the two is power management.
It's something I see on a daily basis as a crash dump reader.
I can only offer input based on my own experience, but that's pretty much the jist of it.

If you encounter any future driver based issues
I we can always enable driver verifier and create some crash dumps I could read.

EDIT: spoke too soon, although it's helped to reduce the S3 time, the problems still happening (although not as frequently). When it happens, the device appears within device manager with the error code listed on the article. Also get the other error message in event viewer.

Might just be that these are crap dongles (never had much luck with anything from Belkin) however I'd sooner not buy one of the £1 no-brand ones as I doubt they'll be any better.

Only other concern I had was the last time I used AHCI the hard drive never used to wake up properly/in time after S3. I see there's a hotfix but again I imagine it's hopefuly been fixed as part of SP1.

The list of fixes for sp1 is so long I would be lying if I said I had it memorized. I wouldn't be surprised if it's in there though.

They shouldn't try to overwrite a driver that is newer than the one they have on record so hopefully you're okay there.

As I said most the power state issues you will have are generally a result of vista drivers being advertised as win 7 drivers.
In normal daily use for the average person the power state issue is not a problem.
For someone like you who is dealing with multiple power states, those vista drivers will likely have issues. As windows 7 does have a slightly different way of managing the system power.

At any rate since you are settled for now could you make the thread solved please?