Windows XP guest terminates with fatal error after loading FASTFAT.SYS driver

[chriswyattuk]

Host: Lubuntu 13.10

After setting up a fresh Windows XP VM, I upgraded to SP3, then I installed the VirtualBox guest additions. When I reboot, VirtualBox crashes with a fatal error. There doesn't seem to be much of a clue in VBox.log as to why.

I enabled boot logging in Windows XP, and it's crashing after FASTFAT.SYS, I'm not sure what driver gets loaded after this, but that might help in figuring out what's going wrong.

Windows XP boots in safe mode, I tried diagnostic startup and /BASEVIDEO boot parameter in msconfig, it still does not boot.

Few more details:

• I'm using SAS for CD and hard drive, though I doubt it's related
• I'm using a paravirtualised network card, again probably unrelated, not installed the driver for it yet.
• I'm using a USB2.0 controller, but as this uses a generic Microsoft driver, that doesn't appear to be touched by VirtualBox guest additions, I'm guessing this is also unrelated.

[chriswyattuk]

VBox.log

[chriswyattuk]

I was wrong about the network adapter. I tried disabling it, and XP now boots!

I tried PCNet FAST III, Intel Desktop and virtio adapters to no avail. I also tried changing between, Bridged, NAT and Not Attached, again, to no avail. It seems that the only workaround is to disable the network adapter completely.

[chriswyattuk]

Worth also noting, I have 2 Ethernet cards and 1 Wi-Fi card:

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 20)

05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

08:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)

[chriswyattuk]

Well, for some reason the problem's come back, I think it may have been triggered by some Lubuntu updates that I'd installed.

[chriswyattuk]

Problem seems to be fixed in 4.3.2

[Frank Mehnert]

Great, thanks for the feedback!

[chriswyattuk]

Problem's come back again, aargh, sorry :\. I'm not sure what's causing it. I installed 4.3.2 and it worked fine, even with the network adapter enabled. Now suddenly I'm getting this error again, quite strange. Perhaps this is a seperate issue, it seemed to happen at the same point during boot-up, but I booted it a 2nd time and it happened when it got to the Welcome screen. Will carry on fiddling with it for a bit to see if I can get some idea of what might be causing it.

The first log has no error message, it just says that the VM has terminated, the 2nd log does have an error: E_ACCESSDENIED. I tried booting with the network card disabled a couple of times, no problems. Enabled the network card again, no problems. The issue I'm having in 4.3.2 seems to be intermittent, whereas the problem I was having in 4.3.0 was happening on every boot. Due to it being intermittent it's hard to say if it's related to the network adapter this time round.

[chriswyattuk]

2nd log, terminated at welcome screen instead, possibly seperate issue

[chriswyattuk]

Had the problem again, while I was in the middle of installing something.

Afterwards, I changed from Bridged to NAT, I've been running it for about an hour now without any problems.

EDIT: Got it again during the boot screen (with the progress bar), which is now making me think it's possibly the same (or a related) issue.

[chriswyattuk]

Terminated during boot screen, no E_ACCESSDENIED error this time.

[chriswyattuk]

I hadn't noticed that further up in the error log, there is a VERR_TRPM_DONT_PANIC error. This seems to be the same error that I was getting in 4.3.0 as well. 4.3.2 was stabler, but then for some reason ended up being much more consistent with the errors, to the point where I just couldn't get it to boot up any more.

I wouldn't be surprised if it also relates to me using software virtualisation, my laptop doesn't support VT-X :(. I'm probably going to be seeing more of these problems because my laptop is so old now, need to upgrade.

I've reverted to 4.2 for the time being.

[Frank Mehnert]

Could you re-test with VBox 4.3.6? Thank you!

[chriswyattuk]

VirtualBox 4.3.6 log

[chriswyattuk]

Unfortunately still have same problem, it crashed during startup, log attached.

1st boot - Was OK
Reboot - Guru meditation
2nd boot - Was OK

I'll continue testing with 4.3.6.

[chriswyattuk]

Log after XP crashed with glitchy graphics

[chriswyattuk]

Just had a crash, possibly unrelated. VirtualBox is still stable, but the actual virtual machine itself has crashed.

Wasn't doing anything except letting VM boot, Avast was doing it's usual updates as well.

[hwertz]

I don't think this is limited to Windows XP. My Host is Ubuntu 12.04 (running 3.5.0-45-generic kernel). VirtualBox 4.2.x has been rock solid, VirtualBox 4.3.x has been unstable for me and 4.3.6 continues to crash, Guru Meditation -2403 (VERR_TRPM_DONT_PANIC). For me it does it for all VMs guests... Windows 7, XP, Ubuntu 10.04, 11.04, 12.04, 13.04, and 13.10. My D620 does not support VT-X 8-( This is a [email protected] (Core Duo, not Core 2 Duo).

Please find attached my log from just a few minutes ago, in this instance 11.04 bailed during bootup.

[hwertz]

Ubuntu 11.04 guest crash.

[Frank Mehnert]

hwertz, your guest runs with software virtualization and I think that's the cause for your guest problems. Are you sure that VirtualBox 4.2 boots your Ubuntu guest without any problems? In that case please attach a VBox.log file from VBox 4.2 running your Ubuntu guest.

[ben huynh]

USB Enable in Setting cause the system lockup under Win 2012 guest, it happen under some hardware environment. I have Dell and HP Servers 2-Xeon, SAS, USB 2.0, 72G, host W2k8x64 and w2k12 host; if guest W2K12 has USB Enable, it automatically lockup after Install Guest Additions CD image. So, when I remove Vbox extension 4.3.xx and disable USB Enhancement; the system boot up normal and fast.

However, it may work on a desktop computers, MSI 9xx, or Laptop Lenovo.

Some how, the USB extension from version 4.3.xx recreates the USB blue screen/some kind lockup.

[Frank Mehnert]

BJvBox, I really don't know what your problem has to do with the original problem (FASTFAT.SYS driver). Please open a separate ticket for your problem.