Win 10 Guest crashing after upgrade to 6.1.32

[deepzigzag]

(mod edit: topic title changed from "Win 10 Guest crashing after new monitor")

I have been running Win 10 Guest VM for 2 years.
Changed my monitor and now the VM keeps crashing (sometimes within minutes of booting).

I have attached VBox.log.

Not sure how monitor is related.

But is happening to all Win 10 VMs.

Installed a new Ubuntu Guest and seems to be working fine for the last hour.

Any suggestions would be appreciated.
Thanks,

[mpack]

The log doesn't show any VM problems that I can see. Is the crash inside the guest OS?

In fact I see that it is.

00:03:08.112968 GIM: HyperV: Guest indicates a fatal condition! P0=0x9f P1=0x3 P2=0xffff93859bb0d050 P3=0xfffff80452c71850 P4=0xffff93859bb1e8a0
00:03:08.113102 GIMHv: BugCheck 9f {3, ffff93859bb0d050, fffff80452c71850, ffff93859bb1e8a0}
00:03:08.113103 DRIVER_POWER_STATE_FAILURE

I assume the new monitor offers higher display sizes? That would be the only relevance I can think of. Perhaps look for updated host graphics drivers.

[deepzigzag]

Crash is inside guest OS.
Mouse and keyboard stop working.
CPU usage spikes up
I have to "power of the machine"

New monitor has same display/resolution as one of the existing monitors.
I have update graphic drivers for both monitors.

Host runs on a NVME. Did a chkdsk and no issues with the drive.

Any other suggestions?

Thanks,

[fth0]

Please try if VirtualBox 6.1.30 exhibits the same problem.

[deepzigzag]

Yes 6.1.30 also has the same issue....

Tail of new log file below....

<deleted by moderator - no partial or pasted logs please>

[fth0]

Thanks for trying. Partial log files are of no use, BTW (unless you know which log messages are the important ones). In this case, the log messages seems to indicate disk I/O problems, though.

In the VBox.log file from your original post, I didn't see any indications of problems other than the BSODs reported by the guest OS. I'd therefore suggest to investigate them inside the guest OS as if they had happened on a physical PC.

[deepzigzag]

Rebooted Host PC after install of 6.1.30.
3 Guest VMs are running fine so far.

Will post another update after a day of running

[deepzigzag]

Working fine on 6.1.30.
Will upgrade again next weekend to 6.1.32 and see if issue reoccurs

[AndyCot]

When you get to trying 6.1.32 can you grab a log for 6.1.30 just before the 6.1.32 upgrade so that if 6.1.32 plays up you have a log just before the upgrade that can then be used by other people of the forum to compare to see if they can spot anything.

[scottgus1]

+1 on what Andy asks. Please provide a 6.1.30 log from a working VM and a 6.1.32 log from whatever happens then.

For each version, Start the VM from full normal shutdown, not save-state. Run until you can log into the desktop or see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.

Right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip it, and post the zip file, using the forum's Upload Attachment tab.

[deepzigzag]

Attached log files for both 6.1.30 and 6.1.32 log file.
Issue still persists in 6.1.32
Reverting back to 6.1.30

[AndyCot]

Did going back to 6.1.30 resolve your issue or not? This helps with diagnosing the issue by other forum users.

[deepzigzag]

Yes. 6.1.30 is working fine.

Maybe need to change subject. don't think its related to monitor. Just a coincidence that I changed monitor and upgraded to new version at same time.

Thanks,

[scottgus1]

Maybe need to change subject.

'Tis done!

[snn-richard]

Seeing the same behavior. Windows 10/11 run fine in 6.1.30 but unusable in 6.1.32. Can't even get to a login screen after almost an hour.

Thanks,
Richard