Opened 12 years ago
Closed 8 years ago
#11617 closed defect (obsolete)
Windows Delayed Write Failed
Reported by: | Thomas Astleitner | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.8 |
Keywords: | dataloss mft bluescreen | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
During my work, Windows XP as a guest comes with a yellow exclamation mark in the tray and a balloon tip saying:
Windows – Delayed Write Failed: Windows was unable to save all the data for the file C:\$Mft. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. Panically, I try to save some data, but can't access them at all.
After a reboot, I receive a blue screen saying:
SESSION3_INITIALIZATION_FAILED
The drive is not startable anymore.
I had this before already since I guess 4.2.4 or so. Once the message came up, several data in the guest were unaccessible. I deleted the VDI file and restored a backup file, creating a new machine and mounted the VDI as master. A while it's always doing a good job, but after 1-2 weeks, problem's back.
This time, I'll keep the VDI file for further investigation, if someone needs more info. Don't know if a bluescreen will help anyway. Now I'm going up to 4.2.10. I'll restore my backup VDI and try it again and again and again until that's fixed.
Thanks! Tom
Attachments (2)
Change History (6)
by , 12 years ago
comment:1 by , 12 years ago
comment:3 by , 12 years ago
And the thrill goes on. Freshly installed WinXP guest on a WinXP host, using VB 4.2.10. Several programs installed, after two weeks: bang.
@ aeichner: VBox.log of the new machine attached (sorry for delay, didn't get noticed of your comment, please find Logs.zip containing all available files). Notice: on this machine no bluescreen occoured (yet)! The guest error occoured unexpected (as always) and I was able to perform a regular shutdown of the guest. The VBox.log has been taken after this shutdown.
The app version for this ticket must be changed to 4.2.10 now. How can I do this?
comment:4 by , 8 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
And again. Same crack with VirtualBox v4.2.10. see attachment (loss.png).