Ticket #10328 (closed defect: obsolete)
VirtualBox Crash -- MSVCR80.dll
Reported by: | shawnsumin | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.1.10 |
Keywords: | crash | Cc: | |
Guest type: | Windows | Host type: | Windows |
Description
My OS: Win 7 64 Bit Virtual OS: Win XP SP3 32 Bit
I have also attached the VBox.log file.
Here is the details from Action Center of Windows 7:
Source Oracle VM VirtualBox Manager Summary Stopped working Date 3/14/2012 1:08 PM Status Report sent Description Faulting Application Path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Problem signature Problem Event Name: APPCRASH Application Name: VirtualBox.exe Application Version: 4.1.10.0 Application Timestamp: 4f5f41ab Fault Module Name: MSVCR80.dll Fault Module Version: 8.0.50727.6195 Fault Module Timestamp: 4dcdd833 Exception Code: c0000005 Exception Offset: 000000000001e250 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional Information 1: bc40 Additional Information 2: bc405b991258bef423db948774abc41f Additional Information 3: 4c5b Additional Information 4: 4c5b89eecfe1aa4d603883ff2bbebdd0 Extra information about the problem Bucket ID: 59476407
Attachments
Change History
comment:1 Changed 9 years ago by bdmeyer
I have this same error. Host OS win 7 Home Premium 64 bit. Fully patched. Attempted a repair install, and reboot. 6 different VM's. All ran fine until updating to VB 4.1.10.0. VirtualBox crashes ons tartup. Excerpt from EventViewer: Application Log. Error: Faulting application name: VirtualBox.exe, version: 4.1.10.0, time stamp: 0x4f60d455 Faulting module name: QtGuiVBox4.dll, version: 4.7.3.0, time stamp: 0x4e12cccb Exception code: 0xc0000005 Fault offset: 0x00000000002707ec Faulting process id: 0xca0 Faulting application start time: 0x01cd053cf2e3da48 Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe Faulting module path: C:\Program Files\Oracle\VirtualBox\QtGuiVBox4.dll Report Id: 34d92b10-7130-11e1-8ca0-005056c00008
Details (XML View)
- <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event">
- <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-03-18T19:26:06.000000000Z" /> <EventRecordID>21594</EventRecordID> <Channel>Application</Channel> <Computer>zt</Computer> <Security /> </System>
- <EventData> <Data>VirtualBox.exe</Data> <Data>4.1.10.0</Data> <Data>4f60d455</Data> <Data>QtGuiVBox4.dll</Data> <Data>4.7.3.0</Data> <Data>4e12cccb</Data> <Data>c0000005</Data> <Data>00000000002707ec</Data> <Data>ca0</Data> <Data>01cd053cf2e3da48</Data> <Data>C:\Program Files\Oracle\VirtualBox\VirtualBox.exe</Data> <Data>C:\Program Files\Oracle\VirtualBox\QtGuiVBox4.dll</Data> <Data>34d92b10-7130-11e1-8ca0-005056c00008</Data> </EventData> </Event>
: Information: Fault bucket 59585682, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0
Problem signature: P1: VirtualBox.exe P2: 4.1.10.0 P3: 4f60d455 P4: QtGuiVBox4.dll P5: 4.7.3.0 P6: 4e12cccb P7: c0000005 P8: 00000000002707ec P9: P10:
Attached files: C:\Users\bdmeyer\AppData\Local\Temp\WERDDB1.tmp.WERInternalMetadata.xml
These files may be available here: C:\Users\bdmeyer\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_VirtualBox.exe_fd73ba65a7a14c925fc8fd7572fdcc31ddf1118_0307558e
Analysis symbol: Rechecking for solution: 0 Report Id: 34d92b10-7130-11e1-8ca0-005056c00008 Report Status: 0
Details (XML)
- <Event xmlns=" http://schemas.microsoft.com/win/2004/08/events/event">
- <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-03-18T19:26:37.000000000Z" /> <EventRecordID>21595</EventRecordID> <Channel>Application</Channel> <Computer>zt</Computer> <Security /> </System>
- <EventData> <Data>59585682</Data> <Data>4</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>VirtualBox.exe</Data> <Data>4.1.10.0</Data> <Data>4f60d455</Data> <Data>QtGuiVBox4.dll</Data> <Data>4.7.3.0</Data> <Data>4e12cccb</Data> <Data>c0000005</Data> <Data>00000000002707ec</Data> <Data /> <Data /> <Data>C:\Users\bdmeyer\AppData\Local\Temp\WERDDB1.tmp.WERInternalMetadata.xml</Data> <Data>C:\Users\bdmeyer\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_VirtualBox.exe_fd73ba65a7a14c925fc8fd7572fdcc31ddf1118_0307558e</Data> <Data /> <Data>0</Data> <Data>34d92b10-7130-11e1-8ca0-005056c00008</Data> <Data>0</Data> </EventData> </Event>
comment:2 follow-up: ↓ 3 Changed 9 years ago by misha
Please attach a minidump for the crash here. See https://www.virtualbox.org/ticket/9267#comment:36 on how to make the minidump generated on app crashes.
comment:3 in reply to: ↑ 2 Changed 9 years ago by shawnsumin
Replying to misha:
Please attach a minidump for the crash here. See https://www.virtualbox.org/ticket/9267#comment:36 on how to make the minidump generated on app crashes.
I did not get your reply, in my email. Not sure why, maybe I am supposed to add myself to cc. But I can't modify anything in the original ticket.
Anyways, I was able to crash VirtualBox again with Win XP SP3 32 Bit guest.
This time I used the steps mentioned over there to create a minidump.
I filed the new bug/ticket here with the new VBox.log and minidump file: https://www.virtualbox.org/ticket/10368
comment:4 Changed 4 years ago by aeichner
- Status changed from new to closed
- Resolution set to obsolete
Please reopen if still relevant with a recent VirtualBox release.