Windows 10 Startup Freezes

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
russ_vb
Posts: 5
Joined: 9. Nov 2017, 23:46

Windows 10 Startup Freezes

Post by russ_vb »

I'm running VirtualBox v5.1.30 on macOS Sierra 10.12.6. When I start a Windows 10 client it freezes before I get to the login prompt.

It was working fine until yesterday. I didn't shutdown the VM client when I disconnected from an external display and closed my laptop. When I later opened my Mac, my mac wouldn't respond to any keyboard presses at all. The only option was to hold the power down and restart it.

When I launch my Windows VM, it freezes on launch. I have tried a few things in this forum without any success. I have attached a log.

It seems to be failing to load the condrv.sys service.
Attachments
VBox.log.zip
(27.59 KiB) Downloaded 165 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Windows 10 Startup Freezes

Post by mpack »

At present you have a 4-core host and assign all 4 cores to the VM. Ironically leaving none to run VirtualBox itself, nor the host OS. Lags and freezes are to be expected. I would allocate 2 cores to the VM.

Still, I doubt that that is your main problem. I suspect that your problem is OpenGL related. What happens if you disable 3D acceleration in the VM settings?
russ_vb
Posts: 5
Joined: 9. Nov 2017, 23:46

Re: Windows 10 Startup Freezes

Post by russ_vb »

Thanks for your reply.

I originally just had one core allocated. It was freezing with just one so I bumped it to 4 to see if it could get to the login screen. I dropped it back to one again but it didn't help.

I didn't have 2D or 3D acceleration on when it froze. I have tried turning 2D on (and 2D & 3D) but it didn't help. They are currently both off.

I have attached a new log (with one core and 3D/2D acc off).

It can startup in safe mode. I turned windows boot logging on and followed a Microsoft forum discussion titled Windows 10 Hangs on Startup to discover the last service the system tries to load (condrv.sys).

Steps to determine the faulty driver:
1. Run MSCONFIG again, click the Boot tab, and check the "Boot log" box
2. Reboot your PC. When your PC hangs, shut it down and turn it back on so you can log in.
3. After you log in, run MSCONFIG again and disable the "Boot log" option.
4. In the \Windows folder, you'll see a file named NTBTLOG.TXT. Open the file and scroll to the bottom of the file. Then scroll up until you see the date and time. The line immediately above that time stamp is the last driver it attempted to load.

The condrv service is a bit of a mixed bag.
I tried resetting the condrv service to manual (default) using SC but it didn't help. I also ran SFC /SCANNOW but it reported that no issues were found.

I tried repairing Windows using the installation iso but windows wouldn't allow the repair to begin.
Attachments
VBox.log.zip
(25.21 KiB) Downloaded 135 times
Post Reply