Windows 2000 in VM Under Win 7??

@zzz

Ok!

Monday's project.

Thanks

Well, I tried installing VirtualBox, and that also blue screened during installation. Upon reboot, I tried to install again, and noticed the text was missing from all buttons on menu boxes and such. The reinstall also blue screened, so I did an image restore.

So much for that.

So, VMLite, and VirtualBox both fail during install. And not just on this PC, but another PC bought at the same time from the same vendor (Dell). There must be something about these PCs. Give me a good old DIY system anytime...

So the only VM I'm left with is the VHD we created from Acronis, which runs under Microsoft Virtual PC, but has no virtual networking. This is quite useless as without the virtual network, the data is trapped in the VM.

I'm about to give up completely. Any last suggestions?

During installation of VirtualBox itself. It was going along, then I remember getting a prompt "did I want to install USB...?", then a prompt for "did I want to install network...?", then sometime shortly after that BOOM. Blue screen.

If you're going to ask for crash dumps, I won't have any. When I restored the image, they got over written.

I meant I restored my windows installation from the latest system image, which I made from last night. I need to make sure the BSOD doesn't leave any surprises behind for me to hit later. Since it's a work system, I need to know it's clean and in a known state. That "known state" is my system image prior to installing these VM programs before they fail.

Restoring my image file essentially overwrites everything that was on the drive. So any crash dumps written by the BSOD were lost. Yes, my fault for not making a copy of them before I did the image restore.

By the way, the spec you may have looked at is my personal Windows 7 machine at home, and not the one here at work. This is a Dell Optiplex 360, Intel E7500 processor, and and Intel chipset (G33/G31/P35/P31), 4gb ram (3 used).

By the way, I mentioned a "sister" machine is also failing the same way when trying to install these programs. It was essentially clean, so no need for me to make a new clean system.

we found the bsod is caused by the network filter driver's power handling routine. We are trying to fix.

Among our more than 30k users, there is only two crash cases, but it does happen.

I got one from one of our users, it's the VBoxNetFlt.sys causing the BSOD.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\vpxware\bugs\010710-43695-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`83329ad4?
WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\websymbols*Symbol information
;C:\virtualbox-dev\vbox\out\win.x86\debug\bin
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x83203000 PsLoadedModuleList = 0x8334b810
Debug session time: Thu Jan 7 08:49:01.115 2010 (GMT-8)
System Uptime: 0 days 2:55:27.660
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
...........
0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 89883590, Physical Device Object of the stack
Arg3: 83329ae0, Functional Device Object of the stack
Arg4: 8b064450, The blocked IRP
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for VBoxNetFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for VBoxNetFlt.sys
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: 8b064450
DEVICE_OBJECT: e5286028
DRIVER_OBJECT: 879ff7e8
IMAGE_NAME: VBoxNetFlt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4afb6d6d
MODULE_NAME: VBoxNetFlt
FAULTING_MODULE: c7154000 VBoxNetFlt
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 8323f054 to 832dfd10
STACK_TEXT:
83329a94 8323f054 0000009f 00000003 89883590 nt!KeBugCheckEx+0x1e
83329b00 8323e8e8 83329ba0 00000000 83336280 nt!PopCheckIrpWatchdog+0x1f5
83329b38 8326d04d 83344a20 00000000 50398a21 nt!PopCheckForIdleness+0x73
83329b7c 8326cff1 8332cd20 83329ca8 00000002 nt!KiProcessTimerDpcTable+0x50
83329c68 8326ceae 8332cd20 83329ca8 00000000 nt!KiProcessExpiredTimerList+0x101
83329cdc 8326b20e 000a4c1d 89807b48 83336280 nt!KiTimerExpiration+0x25c
83329d20 8326b038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
83329d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38

STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0x9F_IMAGE_VBoxNetFlt.sys
BUCKET_ID: 0x9F_IMAGE_VBoxNetFlt.sys
Followup: MachineOwner
---------