VirtualBox

Opened 10 years ago

Closed 8 years ago

#12792 closed defect (obsolete)

VBox crashes in VBoxDD.DLL

Reported by: Rafcio Owned by:
Component: other Version: VirtualBox 4.3.8
Keywords: Cc:
Guest type: other Host type: Windows

Description

When booting OS/2 client that accesses optical drive on boot, and the optical drive is busy (say playing a DVD movie) the whole session crashes with error in VBoxDD.DLL. The crash report has been sent to Microsoft (mutiple times so far) and I'm not sure how much useful information about the crash is in the log file, but the crash is consistent, so I can recreate it on demand and collect more information if given instructions on what and how to collect. This is not new to the current version, it was there before.

Attachments (1)

VBox.zip (12.6 KB ) - added by Rafcio 10 years ago.
Log

Download all attachments as: .zip

Change History (6)

by Rafcio, 10 years ago

Attachment: VBox.zip added

Log

comment:1 by Frank Mehnert, 10 years ago

Can you provide a minidump?

comment:2 by Rafcio, 10 years ago

Sorry I missed your request. I usually get email when there is an update to the ticket, but somehow I didn't get one for this issue. Sure I can do that. I can probably find out online how to create a minidump, but if you have a link to good instructions page I'd appreciate that.

comment:3 by Frank Mehnert, 10 years ago

Please go here and scroll down to the Minidumps section.

comment:4 by Rafcio, 10 years ago

I don't know why, but a minidump is not created when the application crashes. I've changed kernel memory dump (which is being created when BSOD happens, so my config should be fine) to small memory dump (and even tried few different locations), but no dump file is created. I recreated the crash several times.
I will try to find a reason for no minidump, but I will be away from home for over a week, so this may not come any time soon. In the meantime, this is from Windows error report, but I'm not sure if it has any value.

Sig[0].Name=Application Name
Sig[0].Value=VirtualBox.exe
Sig[1].Name=Application Version
Sig[1].Value=4.3.10.0
Sig[2].Name=Application Timestamp
Sig[2].Value=533315cb
Sig[3].Name=Fault Module Name
Sig[3].Value=VBoxDD.DLL
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=533315fa
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000007c522
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=3487
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=3487f82fb7cff035f55cd539c176b3a4
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=6e08
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=6e0829928ffe482ce853711536547751

comment:5 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