error code 0x000000C4 Windows Server 2008 64bit

[dme12]

Hi, I am having problems installing windows 2008 server in virtual box, getting error code 0x000000C4. Please help

I compressed the log file because it is too big to upload here.Attached is the log file.

[Perryg]

Code: Select all

00:00:02.996634 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=32 \Device\HarddiskVolume2\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll
00:00:02.996730 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll' (C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll): rcNt=0xc0000190

00:00:18.935326 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=64 \Device\HarddiskVolume2\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll
00:00:18.935397 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll' (C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll): rcNt=0xc0000190
00:00:20.909794 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=4096 \Device\HarddiskVolume2\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll
00:00:20.909863 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll' (C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll): rcNt=0xc0000190
00:00:20.938194 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cHits=128 \Device\HarddiskVolume2\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll
00:00:20.938276 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll' (C:\Program Files (x86)\Stardock\ObjectDock Plus\Dock64.dll): rcNt=0xc0000190

You have several unsigned apps on the host that are stopping VirtualBox from running your guest/s Fix those and it should work.

[dme12]

How can i fix those? Thank you.

[loukingjr]

You either have to uninstall them or fall back to VB 4.3.12.

[dme12]

I installed 4.3.12 and i got this error log. Please Help.

[mpack]

I suspect the problem is shortage of RAM. Your host only has 4GB RAM to begin with (which begs the question of why it needs to run a 64bit OS), so it isn't ideally suited to running a 64bit server as a VM. You have 2.5GB free, so you could try increasing the guest RAM to, say, 1.8GB. That would still be less than MS recommends, but better than 768MB.

[larrystanle]

I have ever run into the same problem and here is the workaround:
1. Open an elevated Command Prompt, type the following command to list your virtual machine's name:

Code: Select all

"c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" list vms

2. Next paste following command followed by Enter:

Code: Select all

"c:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "virtual_machine_name" VBoxInternal/CPUM/CMPXCHG16B 1

Replace virtual_machine_name with the name of the virtual machine name which you find in the step above.

I hope this will help others!

[mpack]

Well, thanks for trying to help, but I'm afraid that simply isn't correct.

The "CMPXCHG16B" extradata trick was a short term temporary workaround which was briefly needed, by Windows 8.1/Win2012 guests only, in the short interval of time after the release of the Win8.1 preview, but before VirtualBox had a Win 8.1/2012 template. The workaround enables a special CPU instruction used by the Win 8.1 installer.

The "workaround" will do nothing much for a Windows 2008 server guest, whose installer does not use that instruction.

VirtualBox added Windows 8.1 and Windows 2012 templates in v4.2.16, and the workaround has been unnecessary for all guests since then.


NOTE: I'm assuming that the OP has accurately identified his guest OS, since this error is what you would get if you used a Win2008 template with a Win2012 server guest. The OS name should be printed on the install DVD label, so it's hard to see how such a mistake could be made.

[noteirak]

The screenshot is definitly 2012, not 2008 - or maybe the SP1 of 2008 changed the BSOD screen? But I doubt it.
@OP - Select the appropriate OS template in the VM config (says 2008 in the logs)