VirtualBox

Ticket #9360 (new defect)

Opened 3 years ago

Last modified 19 months ago

BSoDs a Win2k3 32bit guest after upgrading from 4.0.4 (ICH9 only)

Reported by: kumba Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.6 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description (last modified by frank) (diff)

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.

Attachments

VBox.log Download (83.8 KB) - added by kumba 3 years ago.
VBox.log from BSOD

Change History

comment:1 follow-up: ↓ 2 Changed 3 years ago by misha

Could you attach a VM log and a  minidump for you crash here?

comment:2 in reply to: ↑ 1 Changed 3 years ago by kumba

Replying to misha:

Could you attach a VM log and a  minidump for you crash here?

How do I enable the logging? I took a quick poke through the interface and didn't see anything stand out.

Minidump is impossible. The machine never gets to load enough of the NT Executive to make it very far. I can see NTLDR running, and if I enable boot logging, some of the drivers will load, but one of the drivers triggers the crash. I couldn't see which one that was because the crash happens before it actually prints the line of text to the screen. If it's one of the storage subsystems (as is apparently hinted at by STOP 0x0000007b), then there wouldn't even be a way for it to write minidump information out (unless there is some low-level, fallback driver it can use).

You can perhaps try building an XP or Server 2003 Image on 4.0.x, but use LSILogic, SCSI Port 0 for storage, ICH9 for chipset, enable the other CPU bits above, then try upgrading in-place (no uninstall of older version) to 4.1.0, and see if that will re-create. It's a guess, though. I didn't have time to try and isolate the flaw in greater detail, because I needed the image functional for work-related purposes.

Changed 3 years ago by kumba

VBox.log from BSOD

comment:3 Changed 3 years ago by kumba

Still happening in VBox 4.1.2. I got a log this time. The BSOD happens after this line in the log file:

00:00:13.234 Guest reported fixed hypervisor window at 0x000000008a000000 (size = 0xc00000, rc = VINF_SUCCESS)

BSOD is still: STOP 0x0000007B (0xF78A6A94, 0xC0000034, 0x00000000, 0x00000000)

I am going to try and upgrade the Guest Additions to 4.1.2 under 4.0.12, then upgrade back to 4.1.2, as this blurb on Technet suggests it is disk related (driver) in some form.

 http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/19402d17-3239-4e8b-b6c6-e06f45f3a123/

comment:4 follow-up: ↓ 5 Changed 2 years ago by frank

Does changing the chipset type from ICH9 to PIIX3 change anything?

comment:5 in reply to: ↑ 4 Changed 2 years ago by kumba

Replying to frank:

Does changing the chipset type from ICH9 to PIIX3 change anything?

Not sure. I last tried with 4.1.4, and still had the same BSoD. I'll try again later on and report. I usually default to ICH9 because it's a newer chip. Not real sure if there's a notable difference, seeing as it is all emulated anyways.

comment:6 Changed 2 years ago by kumba

Confirmed. 4.1.6 will boot Win2k3 R1 x86 if the chipset is changed to PIIX3 from ICH9. So it looks like there is a bug in the ICH9 support?

comment:7 Changed 2 years ago by frank

  • Priority changed from blocker to major
  • Summary changed from VBox 4.1.0 BSoDs a Win2k3 32bit guest after upgrading from 4.0.4. to BSoDs a Win2k3 32bit guest after upgrading from 4.0.4 (ICH9 only)

Yes, seems so. The ICH9 chipset is still experimental.

comment:8 Changed 2 years ago by frank

  • Version changed from VirtualBox 4.1.0 to VirtualBox 4.1.6

comment:9 Changed 2 years ago by kumba

Update: this is still an issue under 4.1.8 if using the ICH9 chipset. I am on a Core i7 now, but that has no effect on this issue.

comment:10 Changed 19 months ago by frank

  • Description modified (diff)

Recently we implemented some fixes for the ICH9 chipset emulation. Could you check if your problem is still relevant with VBox 4.1.22 / 4.2.0?

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use