Opened 13 years ago
Last modified 9 years ago
#9360 closed defect
VBox 4.1.0 BSoDs a Win2k3 32bit guest after upgrading from 4.0.4. — at Initial Version
| Reported by: | kumba | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.6 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Windows |
Description
Something is not right with VirtualBox 4.1.0. I have an existing Windows Server 2003 guest that, when I upgraded to 4.1.0, would receive the infamous STOP 0x0000007B error code. I tried fiddling with several settings, but could not get it to boot. I finally had to downgrade back to 4.0.4, and it worked fine.
I then tried removing the guest additions, re-upgrading, and still the same problem. Gave up, and went to 4.0.12 instead, which works fine. Appears to be an issue with 4.1.0 and something on my guest machine.
Details: Host: Windows Server 2008 (NT 6.0) 64bit 4x CPUs (Intel Core2 Quad). 8GB Main Memory. RAID-5 array for storage.
Guest: Windows Server 2003 32bit 2x Virtual CPUs, PAE, VT-x, Nested Paging. 1,280MB Main Memory. 64MB Video Memory, @D and @D support enabled. LSILogic, SCSI Port 0 for storage (Boot Volume). IDE, PIIX4 for CD-ROM/IDE. Bridged Networking, PCnet Fast-III. No Audio or Serial VBox USB 2.0 extension pack.
BSOD: STOP 0x0000007B (0xF78A6A94, 0xC0000034, 0x00000000, 0x00000000)
No logging available. I was unable to find the feature to do this and didn't really feel like mucking around in the command line.
