Windows 10 enabling virtualization + running HTC VIVE Results in BSOD

[KenChowder]

Hi All!

 

This is my first time posting here but I was hoping someone out there would have some information on the issue I am having. I have a custom built gaming desktop with the following hardware:

 

ASUS Z170I PRO GAMING LGA 1151 Intel Z170 HDMI SATA 6Gb/s USB 3.1 USB 3.0 Mini ITX Intel Motherboard

ZOTAC GeForce GTX 1080 FE DirectX 12 ZT-P10800A-10P 8GB 256-Bit GDDR5X PCI Express 3.0 HDCP Ready SLI Support ...

Intel Core i7-6700K Skylake Quad-Core 4.0 GHz LGA 1151 91W BX80662I76700K Desktop Processor Intel HD Graphics ...

G.SKILL Ripjaws 4 Series 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3000 (PC4 24000) Intel X99 Platform Extreme ...

Crucial MX300 2.5" 525GB SATA III 3-D Vertical Internal Solid State Drive (SSD) CT525MX300SSD1

CORSAIR CS-M Series CS550M 550W 80 PLUS GOLD Active PFC Haswell Ready ATX12V & EPS12V Modular Power Supply

 

My goal is to enable virtualization on my MOBO for the purpose of running Hyper-V. I would build my computer with a clean install of Windows 10, do all Windows Updates, update all the drivers for the GTX 1080. And when I run the HTC VIVE setup, I would get a BSOD during the setup (specifically when the drivers for the Head Gear itself is installing) OR I would get a BSOD the next time I reboot/boot my computer. The BSOD does not give an error code or stop code, just a sad face. It would then prompt me to "Restore" to an earlier point. This will work 50% of the time and when it restores to an earlier point, it would be a point before Steam VR is installed.

 

Other times it would loop in diagnosing the error and not being able to resolve it. When this happens, I cannot boot into safe mode, cannot do a repair, and cannot recover from this. It would loop in a BSOD and have no actual stop code or error code. When viewing the event log, the error I get is error 0x0 "your computer unexpectedly shut down due to a crash, power loss, or error" ***paraphrasing***

 

My computer works fine if I have virtualization enable on the MOBO and running Hyper-V with multiple VMs

My computer works fine if I do not have virtualization enabled on the MOBO and running my HTC VIVE VR system

There always seems to be an issue if I have both configured at the same time.

 

Any advice would be greatly appreciated!!

[App4that]

Are you sure you have enough USB lanes? Have you tried uninstalling anything Steam related?

 

[vorticalbox]

14 minutes ago, KenChowder said:

The BSOD does not give an error code or stop code, just a sad face.

Not true that picture you posted stated the error at the bottom.

[App4that]

You scan the error code with your phone to get the break down.

 

 

[Guest Darth Revan]

It's Win10, what were you expecting?

[PlayStation 2]

I don't remember in particular if the 6700K supports virtualization. If it does, then it's Windows 10 being bitchy. If it doesn't, well that's your problem.

[KenChowder]

On 2/23/2017 at 9:33 AM, Dan Castellaneta said:

I don't remember in particular if the 6700K supports virtualization. If it does, then it's Windows 10 being bitchy. If it doesn't, well that's your problem.

 

Yeah it does support virtualization

[KenChowder]

On 2/23/2017 at 9:16 AM, vorticalbox said:

Not true that picture you posted stated the error at the bottom.

Yeah but that stop code can mean a number of things. When I look at the event logs, it doesn't give me anything specific. Something along the lines of "Windows experienced an unexpected shutdown due to power loss, a crash, or etc etc."

 

After BSOD I would disconnect all peripherals and even remove the GPU and the extra RAM stick. Still no luck. Doesn't seem to be a hardware issue, probably software (installing something from SteamVR?) Maybe its conflicting drivers?

[KenChowder]

On 2/23/2017 at 9:15 AM, App4that said:

Are you sure you have enough USB lanes? Have you tried uninstalling anything Steam related?

 

 

Sorry, this is the first PC build I've ever done. What are USB lanes and how do I check if I have enough? Usually when I run into this issue, I can't boot into the OS at all. Not even in safe mode.

 

I will check in the BIOS if I have turned off the onboard graphics. Maybe that's what is conflicting?

[vorticalbox]

7 hours ago, KenChowder said:

Yeah but that stop code can mean a number of things. When I look at the event logs, it doesn't give me anything specific. Something along the lines of "Windows experienced an unexpected shutdown due to power loss, a crash, or etc etc."

 

After BSOD I would disconnect all peripherals and even remove the GPU and the extra RAM stick. Still no luck. Doesn't seem to be a hardware issue, probably software (installing something from SteamVR?) Maybe its conflicting drivers?

google the error and most of the foxes are graphics drivers, remove them with DUU and try again.

[KenChowder]

On 2/25/2017 at 0:34 AM, vorticalbox said:

google the error and most of the foxes are graphics drivers, remove them with DUU and try again.

I can't get into the OS after BSOD. Can't recover from it when it happens

[Haythum]

I have the same computer sepcs

 

i faceing now  same  problem that you face    Any soultion you get ?

[KenChowder]

On 2/25/2017 at 0:34 AM, vorticalbox said:

google the error and most of the foxes are graphics drivers, remove them with DUU and try again.

I thought the same, that it may be a hardware issue. I removed each piece of hardware one at a time and tried to boot but still got BSOD. Removed everything until only 1 8gb stick of ram was left but still getting BSOD. Recovery options do not work and it will loop endlessly with BSOD.

[KenChowder]

Hi All,

 

Currently, I have been running the computer fine for the last month when I have Virtualization disabled on MOBO and I am not running Hyper-V.

 

I am using this computer just for gaming now and have no issues. I believe the issue will return once I do enable Virtualization. I will try it this weekend and provide updates.

 

Kind regards,

Ken

[vorticalbox]

1 hour ago, KenChowder said:

Hi All,

 

Currently, I have been running the computer fine for the last month when I have Virtualization disabled on MOBO and I am not running Hyper-V.

 

I am using this computer just for gaming now and have no issues. I believe the issue will return once I do enable Virtualization. I will try it this weekend and provide updates.

 

Kind regards,

Ken

seems weird that a feature you're mot using would cause this. It might very well be a bios issue? Maybe its just windows 10.