Volmgr Transaction Corruption Event 57

"The system failed to flush data to the transaction log. Corruption may occur."
"\Device\HarddiskVolume#"

I have a strong feeling it relates to readyboost.

The thing is that the HarddiskVolume number has been shown as 6 and another
series of errors has shown it to be 10. I have 3 physical drives plus an
all-in-one memory card reader giving a total of 6 volumes. Readyboost is
using my SD card on volume 5.

When these errors come up, it comes up every 5 seconds and consumes computer
resources. I am unable to "safely remove hardware" as it says something to
the effect that an application is using the device.
When I go to my SD flash drive, it shows nothing in there.

It is just pure nastiness that I just reboot and it goes away until whatever
instigates it. This last series I noticed occurred after my tv card app
failed for the second time.

Nathan

Another instance of this occurance occurred after waking from a hibernating
state.

Though looking back a little earlier, it would seem it started around the
time it woke from a sleep state to go into the hibernating state.

It was an Event 137 that stated: "The default transaction resource manager
on volume <readyboost drive>: encountered a non-retryable error and could not
start."

Nathan

"Nathan" wrote:

> "The system failed to flush data to the transaction log. Corruption may occur."
> "\Device\HarddiskVolume#"
>
> I have a strong feeling it relates to readyboost.
>
> The thing is that the HarddiskVolume number has been shown as 6 and another
> series of errors has shown it to be 10. I have 3 physical drives plus an
> all-in-one memory card reader giving a total of 6 volumes. Readyboost is
> using my SD card on volume 5.
>
> When these errors come up, it comes up every 5 seconds and consumes computer
> resources. I am unable to "safely remove hardware" as it says something to
> the effect that an application is using the device.
> When I go to my SD flash drive, it shows nothing in there.
>
> It is just pure nastiness that I just reboot and it goes away until whatever
> instigates it. This last series I noticed occurred after my tv card app
> failed for the second time.