Build 10041 - Enabling Hyper-V Results in BSOD at Bootup

I did a clean install of Windows 10 - 9926.  I then upgraded to 10041.

When I enabled Hyper-V and rebooted I end up with a "BSOD", actually the error that there was a problem starting my computer.

Hyper-V worked perfectly in builds 9879 and 9926 but is a complete failure on 10041.

Anyone else having this problem?

March 28th, 2015 3:39am

MM

I suspect it is something local to your machine as it is working fine here.  We could use the DMP files to find why it is not working there

 

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

Free Windows Admin Tool Kit Click here and download it now
March 28th, 2015 9:58am

There is no DMP file generated.

It isn't hardware, as I can turn around and put build 9926 back on there and Hyper-V will work.

So, what changed in Hyper-V between builds 9926 and 10041?

March 28th, 2015 1:11pm

MM

Again it is local to your machine not to what changed in 9926>10041.  Not sure if you want to address the crashes or not.  In the wiki it tells you what is nec for DMPS to be created.  I have not seen a huge amount of hyper-v crashing in 41.

Free Windows Admin Tool Kit Click here and download it now
March 28th, 2015 1:21pm

I'm sorry but I followed those instructions and there is no DMP file generated.  I enable Hyper-V and when the system reboots I get that ":( Your PC ran into a problem and needs to restart." screen.  I boot into safe mode and there is no DMP file.

And it is something that changed between the two builds because why then can I install 9926 and enable Hyper-V without it crashing?  If it were my machine (faulty memory, unsupported CPU, etc.) then I would get the crashes regardless of what build I put on it.  

Now it could be as simple as a change to the hardware requirements or a particular instruction set that 10041 now requires that my CPU does not support.  But it is rooted in a change between the two builds.  Build 10041 is doing something different than build 9926.  I'm just looking for someone from Microsoft to tell me what that change was.  If support for my CPU had to be dropped so that some new feature could be added or improved so be it.

Same exact hardware, Hyper-V on build 9926 works while Hyper-V on 10041 crashes.

March 28th, 2015 2:04pm

Hi,

Since former Windows edition runs Hyper-V with no problem, your CPU should support Hyper-V. 

On the other hand, in my opinion, the reason why crash dump file couldn't be generated might be caused that system crash occurs before system load successfully, as crash dump file generate after user log on.

For your problem, it probably caused by driver compatibility problem with Windows 10 Technical Preview 10041.

Any other app or service startup with system can be also cause this problem, please try to make clean boo for test.

http://support.microsoft.com/kb/929135

In addition, if your computer has Bluetooth model, please disable it for test. According to my experience, sometimes Bluetooth can be cause this problem.

Free Windows Admin Tool Kit Click here and download it now
March 30th, 2015 8:27am

Hi Roger.

The drivers are all the native Windows 10 drivers, so that shouldn't be an issue.  There's no Bluetooth, so I'm safe there.

I'll try the clean boot test this evening after work.

March 30th, 2015 12:42pm

Hi,

How about your problem now? Is there any progress?

Free Windows Admin Tool Kit Click here and download it now
April 1st, 2015 3:08am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics