Windows 7 embedded starter crashs

[Belalugosi]

I've virtualized a Windows 7 embedded starter from a PC used in Control Numeric machine.
I tried to use it in VB but it crashs always. The best thing I had, is to see the desktop (before the crash) setting it as unknow OS.
The BSOD comes with 0x0000008E (0xc0000005, 0x8342E5E3, 0x9B9DD7D4, 0x00000000) error.

Someone has found the solution for this damned OS?
Thanks.

[scottgus1]

Embedded OSs often have only the drivers for the hardware the OS is installed on. If drivers for Virtualbox-simulated hardware or for the host OS CPU are not available, then the OS may not work.

That said, Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Attachments tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)

[Belalugosi]

I hope this is the log you need to see.

[scottgus1]

Thanks for the log. It shows what looks to be properly-running VM "hardware" and an OS that is BSODing but restarting correctly.

One thing that might help is to set the VM;s type to Windows 7:

Guest OS:
00:00:04.506203 Guest OS type: 'Other'
Paravirtualization:
00:00:04.562394 GIM: Using provider 'None' (Implementation version: 0)

See the VM's General settings, Basic tab, Type & Version.
Also System settings, Acceleration tab, Paravirtualization Interface > Default.

If these changes do not solve the BSOD, try reinstalling the OS. If that doesn't solve the BSOD, then this embedded OS may not be compatible with Virtualbox. See a web-search on some causes of BSOD 0x1000008e:

00:00:32.026451 VMMDev: Guest Log: VBoxGuest: BugCheck! P0=0x1000008e P1=0xc0000005 P2=0x830f9847 P3=0x91ded7d4 P4=0x0

[Belalugosi]

Thanks for the answer.
If I set the VM in win7, it crashs before to load the desktop.

Anyway, I don't have the iso for install it.
Sometimes all become so frustrating. So many Windows OS with many problems.
Thanks again.

[scottgus1]

Please refrain from using expletives on this forum. The F word is expression non grata here. Official warning.

Embedded OS's are not designed to be installed everywhere willy-nilly. They are designed to be used only on the hardware they were released for. For example, an ATM maker may want to use Windows 7 for their ATM OS, and would contract for an embedded OS at likely less cost than a full desktop version. The OS would only have drivers for the ATM's computer & peripherals. One can hack other drivers in, but such a setup is not supported.

Regular Windows works wonderfully in a Virtualbox VM. So get a regular Windows instead of the embedded version and you'll be OK.

[Belalugosi]

How I've ritten in the initial post, I virtualized a Windows embedded. It is been not my choise the version.

[scottgus1]

Ah, yes, I forgot that part. Sorry about that!

So this was a P2V (physical to virtual). There's probably not much that can be done then, especially if the install ISO isn't available. The Virtualbox "hardware" looks like it's working, so you can try to troubleshoot the BSODs directly in Windows using Microsoft help channels, as if this was still happening on the original PC.

[mpack]

I doubt that "Microsoft Help Channels" will be totally interested in helping out with a non-licensed Win7 embedded user struggling on the wrong hardware.

[scottgus1]

Very true, Mpack!

And Belalugosi, if it is your intent to use the VM to run the "Control Numeric machine", then this will likely not work well, even if you can get the Windows Embedded to stop BSODing. Virtual OS's have a hard time keeping up with real-world hardware, especially in a CNC environment.

You may do better buying an older but working PC from the early 2010's that could still run Windows 7, and try to clone the existing PC's disk to the new older PC, see if Windows Embedded works there.

[mpack]

I would go for a small form factor PC such as the Elitedesk 800 Mini. It would still be the wrong hardware, so I very much doubt that P2P migration of Win7 stands any chance of working. What might work is identifying the main CNC application and transferring that to a standard OEM Win7 system.