Opened 7 years ago
Last modified 7 years ago
#16086 new defect
VBOX 5.1.8 is crashing
| Reported by: | Jaques | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.8 |
| Keywords: | crash | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
My Windows 10 box upgraded on Monday. I'm running Windows 10 Pro 10.0.14393 Build 14393 x64 now. My vbox did not work after the upgrade, so I downloaded the latest version (5.1.6) and upgraded vbox Since the upgraded, vbox is crashing. It crashed once on Tuesday, once yesterday, and already 5 times this morning. I've upgraded to 5.1.8 this morning, and disabled Audio, but it crashed again.
Is there something that I can do to prevent this?
Attachments (3)
Change History (9)
by , 7 years ago
comment:1 by , 7 years ago
I forgot to say the error msg, but I've attached the screen shot for it.
The error is referenced memory cannot be read
comment:2 by , 7 years ago
I've worked now for the last 2 hours without it crashing. Just before it crashed now I connected to a network resource, and opened a file in Notepad++. Right after I copied a line to the clipboard, I got the error and VBox crashed.
comment:3 by , 7 years ago
I'm rolling back to Windows 1511 from 1607. Hopefully that is where the error is, and not the vBox software.
comment:4 by , 7 years ago
Other people are experiencing this bug. For the bug ticket I'm on (15719), the crashes are being caused by Alt key combinations (Alt+Tab, Alt+NumberKeys, Alt+ArrowKeys, etc.). You need to generate a mini dump when the crash happens (see the comment 15719#comment:11 for instructions on how to generate the mini dump and what to do with it). I don't _think_ it's a windows issue (but let us know if it starts working again). My crashes started happening when I upgraded from virtualbox 5.1.2 to 5.1.4.
comment:5 by , 7 years ago
I also picked up it is when I use Alt+Tab to switch between Windows. I caused so much crap now with my rollback to 1511. Everything stopped working, and it seems that it is some kind of Permissions thing. My Windows is all of a sudden not activated etc.
comment:6 by , 7 years ago
The Alt+Tab bug was finally fixed in VBox 5.1.10. But the original reporter of this ticket apparently observed crashes due to a different reason. So any improvement with VBox 5.1.10? If VirtualBox still crashes: Under which conditions?
vbox log