virtualbox.org

Hello. I hope I can get help here. I'm running Windows 10 64-bit with a Windows 10 64-bit Guest. Occasionally, the Win10 Guest bluescreens. The Windows event log has this error:

"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff998e71af7060, 0xfffff803b72428d0, 0xffff998e70bdd480). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e1064618-e29f-4158-abe6-6bb3333bde9c."

I've tried the following VirtualBox versions (both Stable and Test Builds) but all seem to bluescreen the same way:

VirtualBox-5.2.10-122406-Win.exe
VirtualBox-5.2.12-122591-Win.exe
VirtualBox-5.2.13-122890-Win.exe
VirtualBox-5.2.13-123115-Win.exe
VirtualBox-5.2.13-123149-Win.exe

Anyone know of a fix for a random bugcheck-bluescreen problem like this?

(Dmp is attached as zip file)

ckong3309 wrote:The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff998e71af7060, 0xfffff803b72428d0, 0xffff998e70bdd480).

According to the Microsoft documentation, bug check 0x9F is defined as a DRIVER_POWER_STATE_FAILURE and the first parameter being 0x03 says that device object has been blocking an IRP (I/O Request Packet) for too long.

In English, it probably means that there is a buggy driver that isn't handling some power management related event properly. I would start by disabling all the power management related bits within the guest and see if the situation improves.

-Andy.

Andy, thanks for the reply. Here's things I've tried:

- custom power plan and shut off everything I could find
- running with and without Guest Additions
- Uninstalled/rebooted/then installed version 5.1.38
- set USB to 2.x
- unchecked 3D then 2D display support

Random reboots continue. I'm currently back on the latest 5.2.13 test build as the 5.1.38 build had funny audio problems.

I do have an Ubuntu 18.04 LTS Guest running and that seems to be fine. Just the Windows 10 Guest is randomly rebooting.

I'll continue to test & research online.

The Memory Dump is not as useful as the VBox.log from the VM. With the VM shutdown, right-click on it in the VirtualBox Manager, "Show Log". ZIP only the VBox.log and attach it to your response.

Thank you for looking at this. VBox.log in a zip file is attached.

Something's not right with the timing in the VM. What are you doing exactly? I have a vague idea, but I'd like confirmation.

Can you change the VM Settings » System » Acceleration » Paravirtualization Interface, to "None"?

The Windows 10 64-bit Guest normally is sitting idle when it randomly reboots (i.e. no game or music running).

I set the Paravirtualization Interface to None and re-tested. The Windows 10 Host rebooted on the first try, Windows 10 Guest didn't pass boot test (MIcrosoft?) on the 2nd try, but the Guest finally did launch on a 3rd and 4th attempt (each time randomly rebooting while sitting idle).

I've attached the latest VBox.log file in zip file.

Try to download a pre-made VM from Microsoft: Internet Explorer compatibility VMs. See if that reboots randomly.

I downloaded and imported "MSEdge - Win10.ova". I left the machine set the way it came (no settings changes; no Windows updates; etc). There are of course some settings differences between my Windows 10 Guest and the "MSEdge - Win10" Guest, but it behaves the same. Random reboots still occur.

Some differences (not all):
- My "Windows 10" Guest: System->Chipset= PIXX3; System->EFI=un-checked; Guest Additions=5.2.13
- The "MSEdge - Win10" Guest: System->Chipset=ICH9, System->EFI=checked; Both 2D and 3D video acceleration un-checked; Guest Additions=5.2.8

VLog file after one of the "MSEdge - Win10" Guest reboots is attached.

When I said to try a pre-made VM, I didn't say to change the settings. Especially the ICH9 chipset. Do you mind hovering over that and watching the tooltip? It's experimental, OSX guests only!!! Delete that VM (including all files), start from scratch, do not modify the settings. AT ALL!!!

ckong3309 wrote:Guest Additions=5.2.8

5.2.14 is out, please update before re-importing the OVA to a new VM.

Hello. I'm confirming I didn't change the any of the settings as previously mentioned.

I left the machine set the way it came (no settings changes; no Windows updates; etc)

The downloaded image comes with Guest Additions 5.2.8 already installed. The VirtualBox settings for "MSEdge - Win10" Guest were the settings that were imported (including Chipset=ICH9).

Since my last test, I've upgraded my PC's BIOS (it was about a year old) and upgraded the video drivers to the latest (they were only weeks old since I had upgraded them last month). I also installed 5.2.14 as suggested (uninstall 5.2.13; reboot; install 5.2.14). Initially it looked promising but eventually my "Windows 10" Guest and the "MSEdge - Win10" Guest rebooted. Here are some notes:

- The "Windows 10" Guest crashed to a state where it actually needed to be shut down. The running state was "Aborted". I grabbed the VLog.log file right there.

- The "MSEdge - Win10" Guest acted a bit more strange. On a first run, my Host machine hung. I left it in that state for 10 minutes hoping it would recover but it didn't. I eventually had to press my PC's reset button and start over. On a 2nd run, the Guest stayed stable for about 15 minutes, then I launched a CMD prompt in it and let it sit. Then after about another 10 minutes it rebooted. I shut it down without logging in and saved the VLog.log file.

Since I don't see a lot of posts in this forum about a random reboot issue, I'm guessing it's something to do with the combination of Windows 10 with the hardware I'm currently using (Ryzen 1800X processor; EVGA GTX 1070; Asus X370 not over-clocked to avoid issues like these; etc). At this point, I'm probably going to try Windows 10's included Hyper-V. It's been a over week of troubleshooting for myself so I need to move on and try something else. I understand turning on Hyper-V for Windows 10 is incompatible with other Hypervisors (at this time) so I won't be able to test VirtualBox when I turn the Hyper-V option on.

I'm attaching the VLog files. I hope the logs can help with future versions. Thanks for your support.

ckong3309 wrote:The VirtualBox settings for "MSEdge - Win10" Guest were the settings that were imported (including Chipset=ICH9).

They use a clearly marked experimental feature, they boot with EFI, and yet they chose the PS/2 mouse emulation, no 2D/3D acceleration, the AC97 audio card, and no USB controller (not even USB1.0)! Unbelievable!

ckong3309 wrote:On a first run, my Host machine hung.

That's definitely not a good sign...

[color=#A00000]Windows 10[/color] wrote:

00:33:39.725435 GIM: HyperV: Guest indicates a fatal condition! P0=0x9f P1=0x3 P2=0xffffc288bf443060 P3=0xfffff803b4c63c20 P4=0xffffc288bf67eb40
...
00:33:43.709398 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago

I have a feeling that if you disable Hyper-V in the VM Settings » System » Acceleration » Paravirtualization interface = None, might make a difference. If you're still interested, give it a shot.

ckong3309 wrote:I'm guessing it's something to do with the combination of Windows 10 with the hardware I'm currently using (Ryzen 1800X processor...

It's true that Ruzen 1800X is not a very common processor around, so that could very well be a limit case.