Opened 14 years ago
Closed 9 years ago
#7445 closed defect (fixed)
host BSOD in Windows 7 x64
| Reported by: | Chris Jones | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.2.8 |
| Keywords: | Cc: | ||
| Guest type: | BSD | Host type: | Windows |
Description (last modified by )
My host is Windows 7 64-bit. I have two guests, 32-bit Windows XP and 64-bit FreeBSD amd64. When either guest uses the network, I'll eventually see a host BSOD. Windbg seems to think my network driver is at fault.
The most recent BSOD was with the FreeBSD guest. For that crash, I'm attaching minidump, windbg output, and VirtualBox log file.
I have 3 other minidump files, all associated with the XP guest. Let me know if you'd like to see those also.
Attachments (3)
Change History (10)
by , 14 years ago
| Attachment: | 090710-34055-01.dmp added |
|---|
by , 14 years ago
| Attachment: | windbg.txt added |
|---|
windbg output for host win7/x64, guest FreeBSD/amd64
by , 14 years ago
| Attachment: | FreeBSD-2010-09-07-13-39-23.log added |
|---|
VirtualBox log for host win7/x64, guest FreeBSD/amd64
comment:2 by , 14 years ago
I'm experiencing the same with Win7 x64 host / ubuntu 32b guest.
The guilty module is also e1k62x64.sys - and the BSOD occurs only if I have a wired connection, not wifi. I already tried to update to the latests Intel drivers, but the issue still occurs.
I experienced the issued with 3.2.6 so I had to uninstall VirtualBox, but on Friday I reinstalled 3.2.8 and updated by drivers, and I had 3 BSOD since Friday afternoon.
comment:3 by , 14 years ago
We have the same problems here. Two different Dell notebooks with Win7-64, but both with the same Intel 82577 Gigabit Network Adapter and newest version of e1k62x64.sys driver. With Virtualbox running (one guest PC Win XP Workstation, the other Win 2008 Server) and high traffic on the network card we quite often have a BSOD caused by e1k62x64.sys.
comment:4 by , 14 years ago
Seems to be a problem only of the Intel driver. Other persons experiance similar problems without using Virtualbox: http://communities.intel.com/thread/15350;jsessionid=FE025C563A5E32C987F223F01E88831A.node6COM
comment:5 by , 14 years ago
The solution proposed here :
http://communities.intel.com/message/102592#102592
seems to be ok. I hope I'm not talking too fast, but I'm running Virtual Box for 3 hours now without any BSOD, which was impossible before.
comment:6 by , 14 years ago
I used the last Intel driver (which should resolve this issue), but I still face this BSOD, but this only when VirtualBox 4.0 is running. I usually got at least one BSOD per day, now I'm running my PC since 3 days (without VirtualBox) and I didn't face a single crash.
Is there something I can do to help (providing logs? running some diagnostic tools)
comment:7 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Please reopen if still relevant with VBox 5.0.8.
minidump for host win7/x64, guest FreeBSD/amd64