virtualbox.org

I am trying to run Windows 10 in a VM using Oracle VM VirtualBox Manager on my Windows 10 PC. I am able to load into the VM fine but after 4-10 mins I get a blue screen. The error says Driver Power State Failure. I have done all solutions I have found for Driver Power State failure which includes updating drivers both inside the VM and on my PC, and editing power saving features both inside VM and PC. I have attached the logs of the VM to this post if that helps in finding a solution. If you could help me I would be very thankful!

00:00:00.327315 File system of 'C:\Users\jainr\Downloads\Windows10_PC_Clonex64.iso' (DVD) is ntfs

This doesn't seem like a standard Win10 ISO... Where did you get this from? How about if you try the official Microsoft Win10 iSO? Custom, bootleg ISOs aren't exactly supported here...

I used the Microsoft media creation tool to create that ISO. I also initially used one which was linked by my professor but still had the same outcome.

I see... It's the trick that Microsoft is playing to anyone accessing the ISO page with a Windows OS. What's your preferred language for the ISO? I'm going to get a 24-hour-left-to-live link for you. If it's English or English International, here are the links:

• Win10 1809, 64-bit, English
• Win10 1809, 32-bit, English
• Win10 1809, 64-bit, English International
• Win10 1809, 32-bit, English International

Links expire: 2019-04-11 05:53:16 UTC

I see the following missing from your log:

00:00:01.319540 [/USB/HidMouse/] (level 2)

Are you using the "PS/2 Mouse" option, instead of the default "USB Tablet"? Not a big issue, more like an inconvenience.

Then at the 1'46" mark, and within 20 ms, you get these messages:

00:01:46.937931 AHCI#0: Port 0 reset
00:01:46.939000 VD#0: Cancelling all active requests
00:01:46.941100 AHCI#0: Port 0 reset
00:01:46.942148 VD#0: Cancelling all active requests
00:01:46.944136 AHCI#0: Port 0 reset
00:01:46.945194 VD#0: Cancelling all active requests
00:01:46.946721 AHCI#0: Port 0 reset
00:01:46.947764 VD#0: Cancelling all active requests
00:01:46.949972 AHCI#0: Port 0 reset
00:01:46.951023 VD#0: Cancelling all active requests
00:01:46.953083 AHCI#0: Port 0 reset
00:01:46.954155 VD#0: Cancelling all active requests
00:01:46.956978 GIM: HyperV: Guest indicates a fatal condition! P0=0x9f P1=0x3 P2=0xffff8083a27a8b40 P3=0xfffff8010d65e8d0 P4=0xffff8083a28618a0
00:01:46.957012 GIMHv: BugCheck 9f {3, ffff8083a27a8b40, fffff8010d65e8d0, ffff8083a28618a0}
00:01:46.957012 DRIVER_POWER_STATE_FAILURE

That looks to me like a problem with the hard drive, the host's hard drive. Did you / can you run a "chkdsk" on your hard drive?

Can you get more information about the BSOD? Can you use the BlueScreenView from Nirsoft to get more info?

Yes I was using the PS/2 option but I have since changed that back. I have attached a screenshot of the output of running "chkdsk" in the command prompt and also my Blue screen view output. Thank you for those links, I will try to use the 64-bit English version.

So... what makes you think that this BSOD is due to VirtualBox? All I can see from the info is that the culprit is:

Bug Check Code    : 0x0000009f
Caused By Driver  : mrxsmb10.sys

Oh well I just assumed since the BSOD is happening in the Windows 10 VM that it would be a Virtual box problem. Not sure how to fix it otherwise. I was running the ISO that you linked fine for a while longer than I had gotten before but this time got a BSOD due to "driver irql_less_or_not_equal".

Do you think I would be able to use a Windows 8 or 7 VM without getting these problems or would they still arise?

No, I do not think that it has anything at all to do with VirtualBox. mrxsmb10.sys is a Windows OS driver.

https://www.file.net/process/mrxsmb10.sys.html

Eddy Arji wrote:Oh well I just assumed since the BSOD is happening in the Windows 10 VM that it would be a Virtual box problem.

Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn't make it a VirtualBox problem necessarily. You're having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.