Vista - Error when removing ReadyBoost USB Flash Drive

Whenever I remove my ReadyBoost drive (you can't use the "Safely Remove
Hardware" feature) I get a warning error every 5 seconds in the Vista Event
Viewer(system events). I have to remove it before putting my laptop to
sleep otherwise
the system will wake up when I remove the flash drive(while it's sleeping).
I'd leave it in the usb port but it wont fit in my backpack with it in.
Stupid huh?

Here's the particulars:

Event ID: 57 (qualifier=32772)
"The system failed to flush data to the transaction log. Corruption may
occur."

Windows Vista Enterprise 6.0.6000.16386

If I reinsert the flash drive(into the same port) I still get the errors
every 5 seconds.

In order to stop the errors I need to reboot.

Does anyone know a fix for this? I hate having to clean out my event logs.

Thanks,

Mike

Go to the properties of the flash drive and select "Do not use this device"
in the ReadyBoost tab. Then click OK or Apply.
You can then unplug the USB flash drive without getting those errors.


"MiGKiller" <MiGKiller@xxxxxx> wrote in message
news:AE23B23A-E5FD-4939-BD9C-8E403DFF46A2@xxxxxx

You could Hibernate instead of standby. Then you might be able to unplug the
flash drive.

"MiGKiller" <MiGKiller@xxxxxx> wrote in message
news:AE23B23A-E5FD-4939-BD9C-8E403DFF46A2@xxxxxx

Thanks Gary, the hibernate option seems to be a good workaround. I was
hoping that there would a hotfix or update to the ReadyBoost feature.

Much appreciated.

-Mike


"Gary Mount" wrote:

I believe that because of security reasons, unplugging the ready boost flash
drive in standby mode will cause the cache to need to be rebuilt. When
hibernating, after coming out of hibernation the cache is rebuilt just in
case the cache has been compromised. Maybe version 2.0 would allow a user to
configure whether to rebuild the cache after coming out of hibernation.
Only ReadyBoost memory that is built into the motherboard does not present a
security problem (to a degree) and does not have to be rebuilt each time
after coming out of hibernation.
Service Pack 1 (available this month) might help with the problem that you
are having.

"MiGKiller" <MiGKiller@xxxxxx> wrote in message
news:626DC951-90B9-4725-A8C6-687AC07C97D4@xxxxxx

Thank you so much for providing some clarification to this issue. I'll
wait and see (and hope) if SP1 will provide a solution to this problem.

Regards,

-Mike


"Gary Mount" wrote:

Thanks again for providing the information and clarification about this
issue. I'll stand by for V2.0 and/or SP1. Hopefully either of those will
provide some kind of solution.

Regards,

Mike


"Gary Mount" wrote: