VirtualBox

Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#8127 closed defect (fixed)

VBox Guest (WinXPx86 SP3) BSOD on Win7x64

Reported by: Alil Owned by:
Component: other Version: VirtualBox 4.0.2
Keywords: bsod, crash Cc:
Guest type: Windows Host type: Windows

Description

Guest just came to BSOD.
There was no big activity in guest before BSOD.
The only thing I noticed was guest hang and red strip on the top of guest video (it was in fullscreen). And BSOD.

Attachments (2)

VBox.20.01.2011_bsod.log (96.4 KB ) - added by Alil 13 years ago.
vbox20.01.2011_bsod.png (21.3 KB ) - added by Alil 13 years ago.

Download all attachments as: .zip

Change History (8)

by Alil, 13 years ago

Attachment: VBox.20.01.2011_bsod.log added

by Alil, 13 years ago

Attachment: vbox20.01.2011_bsod.png added

comment:1 by sunlover, 13 years ago

Can you also attach a minidump from the guest? The files are usually located in C:\Windows\Minidump directory.

comment:2 by Alil, 13 years ago

Sorry I don't have any minidump.
Also at this bsod there was not memory leak as #7966. So it seams to be caused by other things

comment:3 by sunlover, 13 years ago

Probably minidumps were disabled in the guest. Could you enable them? On XP it can be enabled via: Control Panel/System/Advanced/Startup and Recovery Settings/Write debugging information. Select 'Small memory dump' in the list.

BTW if you already had 'Kernel memory dump' or 'Complete memory dump' enabled, then please look for c:\Windows\MEMORY.DMP file. It is even better than a minidump.

comment:4 by sunlover, 13 years ago

diagiman, please check if VirtualBox 4.0.4 fixes this.

comment:5 by Frank Mehnert, 13 years ago

Resolution: fixed
Status: newclosed

No response, closing.

comment:6 by Frank Mehnert, 13 years ago

Actually this is a duplicate of #7930. Disabling nested paging should work around this bug. Or using a guest which does not run in PAE mode.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use