Installing Server 2012 R2 on Windows 8.1 Enterprise

[LyonAdmiral]

I'm running VirtualBox 4.3.28 on a Windows 8.1 Enterprise 64 host; Precision 690 with dual Quad Xeon's and 48 gigs of RAM.

The host crashes while trying to install Server 2012 R2 in a VM. Has anyone else seen this sort of behavior? I have searched the forum but not found this particular type of crash.

Thanks,
Daniel

[scottgus1]

How does the host crash? BSOD? immediate reboot? Are there any indications in the host's event viewer when the host reboots?

[LyonAdmiral]

BSOD. It does capture a memory dump but the memory dump is almost 700 megs.

[mpack]

A guest log doesn't tell us much about a host crash. VirtualBox itself may not even be relevant (beyond touching whatever faulty host resource caused the crash), never mind anything in the guest.

At the very least you would need to disable auto-restart on the host and record the BSOD info.

[scottgus1]

BSODs that auto-reboot (are supposed to) record the error info in such a way that the error can be read in the Event Viewer (probably System logs) after the PC reboots. Take a look in the Event Viewer after your last BSOD and see if shortly after the reboot time there is some info about the BSOD.

[LyonAdmiral]

It was running actually for a while without incident, and while trying to export the VM, I got another BSOD:

CRITICAL_PROCESS_DIED

[mpack]

A minidump is of no use to me (if the devs take an interest then they may feel otherwise). I would prefer that you just told me what the BSOD was, like I asked.

[LyonAdmiral]

A minidump is of no use to me (if the devs take an interest then they may feel otherwise). I would prefer that you just told me what the BSOD was, like I asked.

Attached is a pic of the host crashing. I appreciate your help, thank you.

The only thing that shows up in the system log is this at the time of the crash;

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

[mpack]

A 320x240 JPEG doesn't tell me an awful lot either! I can't read that text even with reading glasses on.

I can see that this doesn't resemble the BSOD screen from previous versions of Windows - in particular it gives no diagnostic info.

Why don't you just report what it says? If there's a button for detailed information then click that and provide the information.

[LyonAdmiral]

A 320x240 JPEG doesn't tell me an awful lot either! I can't read that text even with reading glasses on.
I can see that this doesn't resemble the BSOD screen from previous versions of Windows - in particular it gives no diagnostic info.
Why don't you just report what it says? If there's a button for detailed information then click that and provide the information.

There is no further diagnostic information, I guess that is one of the fallacies of the new vision for Windows is that it isn't tech friendly anymore. It just says "CRITICAL_PROCESS_DIED".

[scottgus1]

First crash was while installing the guest, second crash was while exporting the guest. Might indicate this is not caused by Virtualbox directly.

I'd suggest asking on a Microsoft forum how to diagnose the "Critical Process Died" failure. Once you get that figured out, it may tell you where the error started. If it's Virtualbox, let us know.

A thought - Virtualbox touches memory in higher-capacity systems that may never get used in other usual operations. Maybe you have a bad memory stick?