VirtualBox

Opened 12 years ago

Closed 8 years ago

#10782 closed defect (obsolete)

Windows 2008 R2 guest Blue Screen

Reported by: PRab Owned by:
Component: other Version: VirtualBox 4.1.18
Keywords: Cc:
Guest type: Windows Host type: Windows

Description

I have been getting a BSoD inside a VirtualBox VM. I was getting some help on the forum, but they sent me over here. https://forums.virtualbox.org/viewtopic.php?t=50210

Host = Windows 7 64 bit Guest = Windows 2008 R2

Here is the text from the "Windows has recovered from an unexpected shutdown" window.

Problem signature:

Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.274.10 Locale ID: 1033

Additional information about the problem:

BCCode: 1a BCP1: 0000000000041287 BCP2: 0000000000000000 BCP3: 0000000000000000 BCP4: 0000000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 274_3

Files that help describe the problem:

C:\Windows\Minidump\072312-27375-01.dmp C:\Users\Administrator\AppData\Local\Temp\WER-93703-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

I have also attached the .dmp file and the VBox.log.

Attachments (5)

072312-27375-01.dmp (262.6 KB ) - added by PRab 12 years ago.
VBox.log (57.4 KB ) - added by PRab 12 years ago.
BSoD.png (22.2 KB ) - added by PRab 11 years ago.
VBoxSVC.log (626 bytes ) - added by PRab 11 years ago.
VBox.2.log (104.1 KB ) - added by PRab 11 years ago.

Download all attachments as: .zip

Change History (12)

by PRab, 12 years ago

Attachment: 072312-27375-01.dmp added

by PRab, 12 years ago

Attachment: VBox.log added

comment:1 by PRab, 12 years ago

As a test, I switched from using a virtual NAT network adaptor to using a virtual Bridged network adaptor. I have always had both "installed", but before I had the virtual cable disconnected from the Bridged adaptor and connected the the NAT adaptor. This didn't make a difference; I still get the bluescreens either way.

Last edited 12 years ago by PRab (previous) (diff)

comment:2 by PRab, 12 years ago

The problem remained through version 4.1.20, but appears to be fixed in version 4.1.22. My VM has been running for 2 days now and it has not crashed or bluescreened. I'll report back if it dies again.

comment:3 by Frank Mehnert, 12 years ago

Thanks for the feedback!

comment:4 by PRab, 12 years ago

Looks like I spoke too soon. It just crashed again this morning.

Here is the text from the "Windows has recovered from an unexpected shutdown" window. Let me know if you would like any other logs/dumps.

Problem signature:

Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.274.10 Locale ID: 1033

Additional information about the problem:

BCCode: 1a BCP1: 0000000000003452 BCP2: 000000013FA40000 BCP3: FFFFF7000109D9B0 BCP4: 2A50000000000000 OS Version: 6_1_7601 Service Pack: 1_0 Product: 274_3

Files that help describe the problem:

C:\Windows\Minidump\091712-28875-01.dmp C:\Users\Administrator\AppData\Local\Temp\1\WER-1392718-0.sysdata.xml

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

by PRab, 11 years ago

Attachment: BSoD.png added

by PRab, 11 years ago

Attachment: VBoxSVC.log added

comment:5 by PRab, 11 years ago

Its been a while and I still get the BSoD. Here is a new screenshot and log. I have updated to 4.2.16 r86992.

by PRab, 11 years ago

Attachment: VBox.2.log added

comment:6 by Frank Mehnert, 10 years ago

Still relevant with VBox 4.3.2?

comment:7 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use