hi
I have a number of different VMs which were running under VirtualBox 5.1.20 hosted on Windows 7 Pro 64bit
I upgraded to 5.1.30 applied the 5.1.30 extension pack to a guest VM of Windows 7 Pro 32bit which started up then crashed with a BSOD after perhaps 10 minutes or so
The error pointed to ataport.sys
I disabled sound and the VM is working fine
Any thoughts please?
thanks
Rod
w7 32bit guest blue screen after upgrading to 5.1.30 on w7 64bit host
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: w7 32bit guest blue screen after upgrading to 5.1.30 on w7 64bit host
These are two completely unrelated systems; the first has to do with your hard disk controller, the second, well...rodc wrote:The error pointed to ataport.sys
I disabled sound and the VM is working fine
We're going to need to see a VM log from a complete VM run:
- Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM.
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: w7 32bit guest blue screen after upgrading to 5.1.30 on w7 64bit host
thanks for responding
>..These are two completely unrelated systems
I appreciate what you say, sounds like "clean the windscreen and the car starts", but my response was driven by various search results, and regardless of correlation, once sound was disabled the VM ceased to fail.
This posting was an enquiry to see if anyone else had had a similar issue.
the two images attached show details of the BSOD and the post reboot message.
Prior to upgrading to 5.1.30 this VM was working normally - with sound
I'll turn it back on - I expect this time it will be ok
thanks
Rod
>..These are two completely unrelated systems
I appreciate what you say, sounds like "clean the windscreen and the car starts", but my response was driven by various search results, and regardless of correlation, once sound was disabled the VM ceased to fail.
This posting was an enquiry to see if anyone else had had a similar issue.
the two images attached show details of the BSOD and the post reboot message.
Prior to upgrading to 5.1.30 this VM was working normally - with sound
I'll turn it back on - I expect this time it will be ok
thanks
Rod
- Attachments
-
- VB5.1.30_windows_recovery.JPG (38.96 KiB) Viewed 1546 times
-
- VB5.1.30_blue_screen.JPG (96.24 KiB) Viewed 1546 times