Standby problem on Inspiron 9400/e1705 due to Bluetooth 350 update

I recently applied all the new patches for my Inspiron 9400 from dell, and since I installed the latest bluetooth 350 adapter software and the patch for it, my notebook behaves very strangely when told to go into standby:

It goes into standby normaly, but then turns back on staright away, and makes the sound which is played when a new hardware device is found - I think it is the bluetooth adapter because the update upgraded its firmware, and this probably made it behave slightly differently when it receives a command to power down.
Has anybody else faced this problem and is there any solution to it ?

P.S.: The bluetooth module has also been making high-pitched noises since the firmware update even when it is disabled.

 

I have not updated the software; however, have you rebooted your machine? Sometimes software will not fully kick in until after a full reboot. Putting the machine in Standby is not a full shut down.

 

Also, doesn't the E1705 use the 355 bluetooth adapter? Mine uses that one at least. You might want to verify what you have.

Good luck ...

 

Yes, I have rebooted several times and the problem persists. As for standby, I realise it is not a full shutdown but nonetheless, most devices, including wireless adapters shut down when the computer goes into standby. What remains powered are input devices such as mice, as well as RAM.

My e1705 uses a 350 bluetooth adapter because it was manufactured in january 2006 and the 355 appeared later that year.

 

You can try rolling the drivers back. Go to the device manager, right click on your BT module, and there should be an option under properties to roll back the driver.

 

I thought about that but since the device's firmware was upgraded, I am affraid that the problem will not be solved and even more conflicts may arise between the device and the old driver.

 

I have this exact problem too -- with bluetooth disabled in my E1705 BIOS, then I get the annoying Found New Hardware dialog after every S3 standby resume. I can see the bluetooth indicator light up for a split second when resuming, so I think it's a BIOS order issue, ie. the BIOS needs to turn off bluetooth before starting the resume process or something.

 

But your computer stays in standby? or does it fire back up like mine?

 

OK, I'm pulling this one down: today, it went into standby normaly - I guess its one of those irreproduceable errors. Thenks for your suggestions guys. Have a good year 2007!