Opened 7 years ago
Last modified 7 years ago
#17009 new defect
Windows XP SP3 VM application error on VirtualBox 5.1.26 on Windows hosts
| Reported by: | Nick1 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.26 |
| Keywords: | 0x00007FFADAF76D43 0x0000000000000018 0x00000018 | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
Windows XP SP3 VM consistently causes application error within 10 minutes from startup on VirtualBox 5.1.26. This error happened on three different Windows host PCs. Error occurs with VirtualBox 5.1.26 running on Windows 10 64 bit host or on Windows 7 64 bit host. The error message from a Windows 10 host PC is "The instruction at 0x00007FFADAF76D43 referenced memory at 0x0000000000000018. The memory count not be read." (see attached image). Windows 7 host may of had a different instruction address but it still had the "referenced memory at 0x00000018" text. No special action was performed to cause the error. I downgraded to 5.1.24 on a Windows 10 host and the XP VM ran very stable with the error happening only once after days of use. I only tested on Windows hosts and not on Linux hosts.
Attachments (7)
Change History (13)
by , 7 years ago
| Attachment: | Windows XP with VS2003-2017-08-12-23-45-14.log added |
|---|
by , 7 years ago
| Attachment: | Windows XP with VS2003-2017-08-12-23-47-36.zip added |
|---|
Zipped up machine log (7-zip)
by , 7 years ago
| Attachment: | Image-Vbox-crash-with-XP.png added |
|---|
Screen capture of application error dialog box
comment:1 by , 7 years ago
Replying to Nick1:
Windows XP SP3 VM consistently causes application error within 10 minutes from startup on VirtualBox 5.1.26. This error happened on three different Windows host PCs. Error occurs with VirtualBox 5.1.26 running on Windows 10 64 bit host or on Windows 7 64 bit host. The error message from a Windows 10 host PC is "The instruction at 0x00007FFADAF76D43 referenced memory at 0x0000000000000018. The memory could not be read." (see attached image). Windows 7 host may of had a different instruction address but it still had the "referenced memory at 0x00000018" text. No special action was performed to cause the error. I downgraded to 5.1.24 on a Windows 10 host and the XP VM ran very stable with the error happening only once after days of use. I only tested on Windows hosts and not on Linux hosts.
comment:2 by , 7 years ago
Ticket description has a typo in error message. It should say "The memory could not be read".
comment:3 by , 7 years ago
We'd need a Windows minidump (see here for instructions on how to provide one) to be able to investigate that issue.
comment:4 by , 7 years ago
I also have the same error. the dump file size is over 150MB. Maximum file attachment is only 524288 bytes.
comment:5 by , 7 years ago
I have been having this error for while (on two separate x64 Win 7 hosts) and I have a couple of observations. First it seems that every time it occurs it involves Windows file access (and often - if not always - in directories which don't have blanket R/W permissions for all users, which is explicitly the case associated with the attached files). Second it seems like that this ticket and ticket #17026 reflect the same issues. (I might also mention Linux guest tickets #16959, #17001, #17047 and #17016 which sound suspiciously similar.)
I've attached a screen capture and a Windows mini dump. I have a full dump of this same event but it is 750 MB in 7z format. Contact me to arrange for a transfer of that file if it seems helpful.
Machine log files and Image of error message