Opened 9 years ago
Closed 7 years ago
#14907 closed defect (obsolete)
Can't start Virtual Machines on older Hosts
Reported by: | kayk | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.0.10 |
Keywords: | memory, crash, windows 7, update | Cc: | |
Guest type: | all | Host type: | Windows |
Description
We use different Notebooks, and those that had Windows 7 installed longer than a year or two can't start Virtual Machines on Versions 4.3+
We need to update to 5.0.10 but can't do so with those older Laptops because they get all the same Error message. I attached a picture, translated it's something like "The instruction at XXX referenced memory at XXX. The memory could not be written"
If I reinstall a new Windows 7 on one of those Laptops, it seems to work fine but we got 20+ of them and it would be a real pain to back up everything when it's the same OS we already use.
I tried deactivating antivirus, so that doesn't seem to be the problem.
Thanks for your help.
Attachments (3)
Change History (13)
by , 9 years ago
Attachment: | Capture.PNG added |
---|
by , 9 years ago
by , 9 years ago
Attachment: | VBoxHardening.log added |
---|
comment:1 by , 9 years ago
Which version is currently running on these laptops? Just to double-check: Both VBox 4.3.34 and 5.0.10 show the same problem on these older laptops (hang during boot)?
We would need an application dump for debugging.
comment:2 by , 9 years ago
Right now 5.0.10 is running on them.
Since it didn't work I tried installing earlier versions. When I installed 4.2 it started working. Everything above 4.3+ doesn't. Don't know about the exact build number though since I haven't tried every single one.
Also, it doesn't create any dump files. Is there some setting I missed? I set it up like the wiki said but the folder stays empty, even after I restart everything.
comment:4 by , 9 years ago
I can create a dump with the TaskManager, but that's a 35MB .7z file which I can't upload here. What can I do?
comment:5 by , 9 years ago
Ok, I uploaded the compressed dump file to a Google Drive so I can share it here: https://drive.google.com/file/d/0B7prhRovC_CENlpjMkZxQXRPNkE/view
Hope that helps.
comment:6 by , 9 years ago
kayk, we analyzed your dump. It looks like some the VirtualBox kernel code is not properly loaded. This problem could be triggered by some software which is running on your host next to VirtualBox. Also, do you have a virus scanner installed on that host and is it up-to-date?
comment:7 by , 9 years ago
Ok, so now I've tried a Windows Clean Boot with no success. It is running McAfee which is up to date. I also already tried deactivating it, but that didn't help. Should I upload another dump with it deactivated? It seems odd to me that with the older version the kernel was able to load.
comment:10 by , 7 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Picture