BSoD on VM reboot - PLEASE HELP!

[climbCO]

I have a new laptop with Windows 7 as the host OS. I had installed VirtualBox onto the machine and after installing 4 guest OS's (Linux Ubuntu, OpenSolaris, FreeBSD, and XP pro) everything worked absolutely fine until I had to reboot or restart my host OS which it then gave me the BSoD as it attempted to restart.

This occurred over and over until I booted into safe mode and restored my system to pre-VirtualBox which fixed the problem. I had a feeling it might be the guest OS's causing the issue so I unmounted all of them and reinstalled the VitrualBox program again fresh (after deleting the .vdi files etc.) and the problem persisted.

I attempted to switch virtualization software to VMWare and before decided to load a guest OS to that, I attempted to reboot and restart and I got the BSoD again at start up.

PLEASE HELP! The memory allocated for each guest OS was that which was recommended but it seemed to be taxing my memory a bit. Any suggestions?

 

[usasma]

Please re-upload the memory dump files - the download seems to be corrupted.

FWIW - I can't find anything that says that Virtual Box is compatible with Win7

 

[climbCO]

Sorry about the files. I guess I looked around to read on compatibility issues and I guess I have received different inputs. Here are the files if you wouldn't mind taking a look at them for me. View attachment 45789

I went to the Sun Microsystems home page and they did say that it was compatible with Windows 7. However I did find out that my T6600 Intel Core 2 Duo processor does not support VT-x but I didn't know if this applied to ALL Virtual systems. I attempted to upgrade Windows 7 home premium to Professional to install Microsoft Virtual PC but that wouldn't take either.

I'm probably out of luck. If you have any suggestions please let me know.

 

[usasma]

According to this article, you won't need it for Virtual Box: Should you Enable Intel’s VT-x in Virtualbox? | Tombuntu Have you checked to ensure that the VT-x support switch is turned off in Virtual Box?

Were you able to upgrade to Professional without issue? If so, then the failed attempt to install Virtual PC is to be expected (due to the lack of VT-x support).

Anywho, the dump files blame the crashes on athrx.sys - a component of your wireless networking adapter.
I'd suggest downloading a fresh copy of the Wireless networking drivers from the Sony support pages,
Then uninstall the currently installed version, then install the freshly downloaded version.

Also, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

Here's the older drivers:

SFEP.sys     Fri Aug 03 01:35:53 2007
mdmxsdk.sys  Mon Jun 19 17:27:26 2006
regi.sys     Mon Apr 16 11:19:10 2007

Post back if the BSOD's continue

 

[climbCO]

I was able to figure this out. I actually re-installed VBox without the bridge network utility and now everything boots up just fine. Not exactly sure why this caused the issue. If anyone could even speculate as to the reason I would be very interested as I do not know too much about network bridges. Thanks for eveyone's replies.

 

[usasma]

Network bridges are (from what I know) a device that links network devices together.
If the network devices can't talk to each other, then I'd suspect that there will be issues.

FYI - I had a network bridge on my youngest son's computer several years ago. It connected a dialup modem and a NIC card. Needles to say, we weren't able to connect with this computer until I deleted the network bridge.