AMD Phenom seems to cause BSOD 0x0000008E -> update your BIOS

[Daniel]

Host : Windows XP x86 Service Pack 3 Guest : Windows XP x86 Service Pack 3

With an AMD64 Socket 939 (ECS Nforce4 motherboard) everything worked fine.

Upgraded (old motherboard died) to AMD AM2+ Phenom (with an Asus M2 motherboard) and got a 0x0000008E blue screen.

I see a pattern here, pointing to AM2+ Phenom.

This ticket

​http://www.virtualbox.org/ticket/1627

Looks awfully similar to my situation. But, as far as I understood, he manages to boot into the OS. I can't even do that.

The exact scenario is:

• When installing XP from scratch, on a new virtual HD, the first install phase (the one in Text Mode in which you choose the install partition and a first batch of file copying takes place) all goes through fine. When the system boots, for the second install phase, that one with an actual GUI, before the GUI appears the 0x0000008E happens.

Interesting facts:

• Microsoft's Virtual PC 2007 (with and without Service Pack 1) has the EXACT same behaviour.

• VMWare Workstation works fine! And thats exactly what I found out last night and used as a workaround. I created a vmware machine using a link to the "3rd party" virtual hard disk. And it managed to boot fine and I had my old vm back.

Sun and Microsoft need to do whatever magic VMWare does to coupe with whatever AMD Phenom is doing.

[mixmatch]

I am using virtualbox to run Windows XP x86 Service Pack 3 in Xubuntu 8.04 amd64 with a Phenom 9500 with no problems.

[Daniel]

Replying to mixmatch:

I am using virtualbox to run Windows XP x86 Service Pack 3 in Xubuntu 8.04 amd64 with a Phenom 9500 with no problems.

Therefore problem gets limited to a Windows XP Host. Problem still stands.

[WCarvalho]

As noted on bugtrack under my Login, have no success with v1.6.2 and Delphi 2007 for Win32...

Hava we success with Phenom???

Regards,

Wagner.

[Daniel]

I just tested out 1.6.2 and the bug persists. Then Phenom I'm using has the TLB Errata fixed. It's a 9550.

[Frank Mehnert]

Did you enable hardware virtualization? Try to disable it.

[Toney]

I think I am having the same issue. Proprietary VirtualBox, not OSE. AMD Phenom 9750 on an ECS A770M motherboard with 4 GB of RAM and 2x500 GB SATA drives running Ubuntu 8.04 64-bit. I copied the VDI file from another machine (AMD X2 5000+, 4 GB ram, 1x500 GB SATA drive running Ubuntu 8.04 64-bit), recreated the virtual machine, corrected settings (the old one was PIIX3), and now the virtual machine gives a BSOD every time right after the animated bar screen on startup. I have tried toggling each of the settings (APIC, IO-APIC, AMD-V, PIIX3/4, Shared clipboard, PAE) on/off with no success. I had installed 1.6.2 build 31466 but uninstalled it and tried 1.6.0 then 1.5.6 with no success. Anything else I can try? Your help is appreciated, this is a fine product!

-Toney.

[Toney]

Oops, I never stated what my Guest OS is. Clarification: Host is Ubuntu 8.04 AMD64, Guest is WinXPsp2 32-bit and the same VDI file is working on an Intel Core2Duo machine and was working on an AMD X2 machine (machine got retasked).

-Toney.

[Daniel]

Replying to frank:

Did you enable hardware virtualization? Try to disable it.

Yes, disabling it has no effect.

[Sander van Leeuwen]

Toney,

In general moving VDIs from an Intel machine to an AMD machine doesn't work, so I'm kind of surprised that you managed to do so. There's an Intel driver preinstalled in the Windows guests that typically freaks out when it doesn't find an Intel CPU.

Seventh: I'll try installing XP again on my two Barcelona systems (Phenom 9850 & Opteron) .

[ranger]

I am having the same issue. Proprietary VirtualBox 1.6.2 and phenom 9550 Host : Arch linux Guest : Windows XP x86 Service Pack 1, Windows XP x86 Service Pack 2, Windows XP x86 Service Pack 3. None of them works. I always get a BSOD during second install phase.

Windows 98 SE and various linux distributions have no problem.

[Toney]

Update:I have formatted and reinstalled my PC twice, once with Ubuntu 8.04 AMD-64 and once with Ubuntu 8.04 x86 32-bit. Installed all updates, nVidia display drivers, VirtualBox 1.6.2-31466, then tried to install XPsp2 in a VB. The initial install completes and then reboots and I get a BSOD (0x0000008e). Should I try another linux distribution? FC9?

Thanks, Toney.

[ranger]

Replying to toneyc:

Update:I have formatted and reinstalled my PC twice, once with Ubuntu 8.04 AMD-64 and once with Ubuntu 8.04 x86 32-bit. Installed all updates, nVidia display drivers, VirtualBox 1.6.2-31466, then tried to install XPsp2 in a VB. The initial install completes and then reboots and I get a BSOD (0x0000008e). Should I try another linux distribution? FC9?

Thanks, Toney.

I think this is not a distribution problem. Propably, this is a problem with the motherboard chipset. I have AMD 790 and I have the problem and a second PC with nvidia chipset has no problem. Both PCs with Arch linux as host.

[Toney]

You, Sir, are a genius! There was a BIOS update available for my A770M. <Blush> Don't know why I didn't think of that before. Got the BIOS update installed and everything seems to work! Thanks, everybody!

-Toney.

[Sander van Leeuwen]

Seventh: can you check if there's a newer bios available for your motherboard too?

[ranger]

Confirmed.

After BIOS update everything OK.

[Frank Mehnert]

I will close this bug. It can be still found for reference using the search function.

[jens]

confirm:

Have a ASUS M2A-VM board with Phenom 9650.

I also get XP boot stop error 0x0000008E with a very old BIOS version (v1501 from 2007) After Update to newer BIOS, the STOP error flows away ;)