Page 1 of 1
Win 10 Tech Preview
Posted: 21. Jan 2015, 22:35
by brianx
I appear to have installed the latest version of VirtualBox v.4.3.20 on my Win8.1 64bit system to the point where I Start it and install an OS on it. I have Win10 Tech Preview ISO and on DVD. When I point VirtualBox at the DVD drive, it seems to start installing Win10 but after a minute stops with an error and the DVD drive stops.
Your PC Needs To Restart ...
Eorror code 0x0000005D
parameters 0x00000000078BFBFF
0x0000000028100800
0x0000000000000001
0x0000000000000000
Allocated 20Gb to the virtual drive and half of my 16Gb system RAM
Any help please?
Re: Win 10 Tech Preview
Posted: 21. Jan 2015, 23:28
by loukingjr
You should use the .iso. Normally you only want to assigned 50% of the available host RAM, not 50% of the total RAM. My w10 runs fine in 2GB. You should choose the Windows 8.1 template. EFI should be disabled.
Re: Win 10 Tech Preview
Posted: 22. Jan 2015, 16:02
by PaulvdWal
What I did was assigning more video memory and enabling 3d accelleration....
brianx wrote:I appear to have installed the latest version of VirtualBox v.4.3.20 on my Win8.1 64bit system to the point where I Start it and install an OS on it. I have Win10 Tech Preview ISO and on DVD. When I point VirtualBox at the DVD drive, it seems to start installing Win10 but after a minute stops with an error and the DVD drive stops.
Your PC Needs To Restart ...
Eorror code 0x0000005D
parameters 0x00000000078BFBFF
0x0000000028100800
0x0000000000000001
0x0000000000000000
Allocated 20Gb to the virtual drive and half of my 16Gb system RAM
Any help please?
Re: Win 10 Tech Preview
Posted: 22. Jan 2015, 16:12
by mpack
Speculation could go on forever. It would save a lot of time if you provided definitive diagnostics, in particular a VM log file: Right click VM in GUI, select "Show Log", save "VBox.log" (only) to a file, zip file and attach here. Make sure the VM is shut down before you collect the log of the session.
Re: Win 10 Tech Preview
Posted: 5. Feb 2015, 16:35
by CentralCoastMike
I encountered this error until I browsed to a location to create the virtual hard drive. It is possible that the location that the operating system was pointed to was someplace like Program Files which can be hard to write to under some conditions.