Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

After installing windows 10 anniversary update BSOD on virtual machine host


  • Please log in to reply
1 reply to this topic

#1 glenn600

glenn600

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:42 AM

Posted 11 August 2016 - 09:05 AM

Since ive installed the anniversary update everytime i try to start a VirtualBOX vm or any virtual machine for that matter my host pc gets BSOD ive tried reinstalling the virtualbox but that didnt help
 
This is my dump
 
 
==================================================
Dump File         : 081116-7562-01.dmp
Crash Time        : 8/11/2016 3:53:48 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000096
Parameter 2       : ffff9d01`2387d8b3
Parameter 3       : ffff9d01`22e27ce0
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+149f90
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.14393.0 (rs1_release.160715-1616)
Processor         : x64
Crash Address     : ntoskrnl.exe+149f90
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\081116-7562-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 14393
Dump File Size    : 571,356
Dump File Time    : 8/11/2016 3:55:35 PM
==================================================
 
==================================================
Dump File         : 081116-7125-01.dmp
Crash Time        : 8/11/2016 3:48:08 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000096
Parameter 2       : ffff9181`a123e8b3
Parameter 3       : ffff9181`a2cccce0
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+149f90
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 10.0.14393.0 (rs1_release.160715-1616)
Processor         : x64
Crash Address     : ntoskrnl.exe+149f90
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\WINDOWS\Minidump\081116-7125-01.dmp
Processors Count  : 8
Major Version     : 15
Minor Version     : 14393
Dump File Size    : 575,532
Dump File Time    : 8/11/2016 3:49:20 PM
==================================================
 
 
If you need anything more please let me know and thanks for the help in advance

Edited by Queen-Evie, 11 August 2016 - 09:25 AM.
moved from Windows 10 Support to BSOD


BC AdBot (Login to Remove)

 


#2 glenn600

glenn600
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:42 AM

Posted 11 August 2016 - 09:14 AM

Turns out removing Hyper-V as a feature resolves this issue thanks Microsoft






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users