Windows 8.1 (released) host Critical Structure Corruption

[Lance Cleveland]

+1

Any word on a patch?

[andrevmc]

Same problem here. Windows 8.1 64 with Ubuntu 13.10 64.
Seems that VMware is having the same problem.
Maybe this can help. Follow your considerations:

Windows 8.1 virtual machine fails with a blue screen and reports the error: CRITICAL_STRUCTURE_CORRUPTION (2060019)

Symptoms
Windows 8.1 virtual machines fail with a blue screen
You see the error:

CRITICAL_STRUCTURE_CORRUPTION
Resolution
This is a known issue affecting ESXi 5.0.x.

To work around this issue, manually create a CPUID mask for the affected virtual machines:
1. Power down the virtual machine.
2. Right-click the virtual machine and click Edit Settings.
3. Click the Options tab.
4. Select CPUID Mask under Advanced.
5. Click Advanced.
6. Under the Register column, locate the edx register under Level 80000001.
7. Paste this into the Value field:

----:0---:----:----:----:----:----:----

8. Click OK.
9. Click OK to close the virtual machine properties.

[Navare]

Upgraded to Windows 8.1 on the 19th of October.
Experience the bridged network adapter issue, so uninstalled my old version 4.2 of VirtualBox and installed version 4.3. This allowed me to bridge the network cards again. However, the host machine now fails (BSOD) with a CRITICAL_STRUCTURE_CORRUPTION error.
I am about to begin a series of diagnostic steps to see if I can get some stability back in the platform, as going back to Windows 8 does not appear to be an option.
I am trying two things initially 1) Run the VMs with NAT only, and 2) Reinstall earlier version of VB.
Will let you know how things track. Hopefully this will help with root cause analysis.

Update: Changing to NAT only had no effect - failed with the same error after 27 mins. I will try setting # of CPUs to 1 as recently suggested, before I downgrade VB.

Update 2: Likewise, have reduced the number of CPUs to 1 and it has been running for over and hour now .

[Steve Prior]

As mentioned above, see if limiting the guest OS to one virtual CPU helps.

[ketan]

Same issue here. Tried to install hcm peoplesoft image and it crashes. Hopefully oracle releases patch soon.

[lukethegeek]

So far so good with regards to limiting the VM to one virtual CPU.

I've not (yet) experienced a BSOD after around 6 hours of use.

Thanks for the suggestion

[freshbiology]

I am facing the same problem with my XP guest. My host is Windows 8.1 (released) and guest is Windows XP. This guest was running fine on VBox 4.2.18 (and prior versions of VBox) and Windows 8.1 Preview. But after I upgraded my Windows 8 to Windows 8.1 (Released) and installed VBox 4.3 it won't boot. Mostly XP reboots or hangs when the word WELCOME appears on the screen. Somtimes BSOD appears showing something wrong with intelppm.sys and that CRITICAL_STRUCTURE_CORRUPTION error. Any ideas?

[gtirloni]

Same here on a freshly installed Win8.1 Pro 64-bit. It happened with a 64-bit Fedora Linux guest when I increase the CPUs from 1 to 2.

I have been using a Win7 64-bit guest on it with 2-4 CPUs just fine.

I've the memory and minidumps in case a developer needs it.

[aknutson]

Same problem here.

The bridge network adapter wasn't working after updating Windows 8 to 8.1. So I Installed Virtualbox 3 (which fixed that issue) and now I'm having to limit the CPU to 1 Core so I don't crash with the described "CRITICAL_STRUCTURE_CORRUPTION" error.

Running Ubuntu 12.04 Guest.

[Ramshankar]

I have a fix with a testbuild here, would be good if someone provides feedback if it fixes this problem:
http://www.virtualbox.org/download/test ... 98-Win.exe (link auto. expires in ~14 days). Please reboot your host after installing the new build just to start with a clean state.

[j-frost]

Just installed the fix. What a weird thing. It changed my Debian VM to a Ubuntu one and my pointing device from PS/2 mouse to USB tablet. Also, it does not detect VT-x:

Failed to open a session for the virtual machine <name>.

VT-x is not available. (VERR_VMX_NO_VMX).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

(and has thusly only one processor enabled, down from two that I gave the machine), and when trying to fix these things, I didn't come further than having the VM now stop right after loading the initramfs. I wonder if this machine's kernel is confused now.

What am I doing wrong?

(Rebooting host did not help)

edit: Microsoft have issued an update that fixes this issue for me (in combination with Ra's fix).

[sch1zo]

The testbuild seems to fix the bsod issue. At least I have not got one since I installed it around two hours ago while having virtualbox running. Before I had the same CRITICAL_STRUCTURE_CORRUPTION as mentioned by others

[Abjerk]

Test build has also fixed the BSOD issue for me as well.

[ws6formula350]

Was anyone getting crashes, even when NOT running Virtual Box? Going to try installing the test build before I roll my laptop back to Windows 8. I was running VBox 4.2.18 with an XP guest as well as an Ubuntu 10.0.4LTS guest. My crashes were random and happened whether I was running VBox or not...

I should've known not to update a mission critical machine to a new OS release, but after a smooth upgrade on my HTPC box I decided to try it out.

[Steve Prior]

I installed the test build and did not get any more BSOD's even after bumping up the configured virtual CPU count for the guest machine up to two.