Opened 14 years ago
Last modified 10 years ago
#7245 closed defect
Windows 7 Pro 64 bit crashes periodically with BSOD — at Initial Version
Reported by: | Joan Ramon López Gillué | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.2.6 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description
Have had periodical BSOD in Windows 7. After examining the memory dumps it seems that the cause is VirtualBox. I have uninstalled VirtualBox and the crashes have stopped so far.
The crashes occur randomly and don't depend on whether I am actually executing VirtualBox or not.
Basic WinDbg output for memory dump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072710-18844-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`042c0500?
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff80002c18000 PsLoadedModuleList = 0xfffff800
02e55e50
Debug session time: Tue Jul 27 21:19:49.045 2010 (UTC + 2:00)
System Uptime: 0 days 4:50:52.169
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
................
*
- *
- Bugcheck Analysis *
- *
*
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800619f660, fffff800042c0518, fffffa8009bc7d60}
Unable to load image \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys, Win32 error 0n2 * WARNING: Unable to verify timestamp for VBoxNetFlt.sys * ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys Probably caused by : ntkrnlmp
Followup: MachineOwner
windbg output for memory dump