Windows 2000 in VM Under Win 7??

[Jeffs]

@zzz

Ok!

Monday's project.

Thanks

 

[Jeffs]

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?

 

[zzz2496]

When exactly did it blue screen on you? When you install the Virtual Box?

zzz2496

 

[Jeffs]

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.

 

[zzz2496]

Hmm...

I install virtualbox many many times over many computers... Never had BSOD ever...
Looking at your spec, it looks normal (I've installed VirtualBox on a P55 mainboard before, and it ran perfectly).

Jeffs, what do you mean by "When I restored the image, they got over written."? Are you restoring your Windows partition? Can you do a clean install on your computer, use another harddisk, see if clean install can clear things up a bit, and please... next time when you hit BSOD, retrieve the crash dump... It'll help you a lot.

zzz2496

 

[Jeffs]

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.

 

[huisinro]

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.

 

[zzz2496]

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.

Ahhh, sorry I forgot that we are "playing" with a production system...
Ok, all I can do is to wait for your crash dump then... I'm curious as what brought your system down hard... I [personally] never see VirtualBox causing BSOD...

Anyway, if you still want to fix this, can you try again on the "sister" machine? If it fails with a BSOD, upload the crash dump... we'll see what brought it down. Anyway, did you install/update every device driver in the machine? (just making sure that the drivers are all OK and up to date).

zzz2496.

 

[huisinro]

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
---------

 

[Jeffs]

Yes, everything is up to date as far as I can tell. Windows Update is reporting nothing to update (no mandatory or optional).

That sister machine is in use now, so no I can't use it. What I can do is try another install on this machine, and this time remember to copy any logs related to the crash. I'll have to do an image restore again after this, so this cycle takes about an hour, and I have to do it first thing in the morning before I get started for the day as that is when the image is current. Before I start, and to prepare me, what exactly am I looking for after the BSOD? I assume there is a file I'll copy after it reboots? Something in windows\minidump, right?

 

[huisinro]

Jeff, what you can try is to install VirtualBox without installing the network components. You can select on one page. I am pretty sure it won't BSOD if you don't install network components. Without them, network will still work, as NAT, instead of bridged network. That means, your vm won't get a physical IP address. instead, vm shares the ip as host.

 

[huisinro]

another note, do you have other network apps in your host? such as Cisco VPN

 

[huisinro]

do you have TrendMicro AV?

 

[huisinro]

there is a ticket here reporting same BSOD:

#5519 (Virtualbox fatal BSOD installation) - VirtualBox

 

[Jeffs]

I attempted an installation of VirtualBox again. As suggested, I modified the networking section. I turned "Bridged Networking" OFF, and left "Host Only" ON.

The install BSOD again.

The error was DRIVER IRQL NOT LESS OR EQUAL

I copied the dump file from windows\minidump: 011910-18096-01.DMP

This file does not appear to be in text. How do I convert it so it's content can be posted here?

[I tried to attach it, but it's an "invalid file type". It's 142k]

 

[zzz2496]

I attempted an installation of VirtualBox again. As suggested, I modified the networking section. I turned "Bridged Networking" OFF, and left "Host Only" ON.

The install BSOD again.

The error was DRIVER IRQL NOT LESS OR EQUAL

I copied the dump file from windows\minidump: 011910-18096-01.DMP

This file does not appear to be in text. How do I convert it so it's content can be posted here?

[I tried to attach it, but it's an "invalid file type". It's 142k]

Zip the file, then you can upload it. It's a Binary file, you can't open it as text.

zzz2496

 

[Jeffs]

OK - attached.

However, what program will this be run through to convert it to human readable information?

 

[zzz2496]

Windbg.exe, there's a guide around here about Windows Debugger, dig around Jeffs

Edit: http://www.sevenforums.com/crash-lo...intermediate-configuring-debugging-tools.html

zzz2496

 

[Jeffs]

Let me know what the dump says!

 

[zzz2496]

Here:

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000001f0, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 93401bb0, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from 82975718
Unable to read MiSystemVaType memory at 82955160
 000001f0 

CURRENT_IRQL:  2

FAULTING_IP: 
decndis+1bb0
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8078aab0 -- (.trap 0xffffffff8078aab0)
ErrCode = 00000000
eax=00000007 ebx=8589f0e0 ecx=00000000 edx=00000001 esi=00000000 edi=93406978
eip=93401bb0 esp=8078ab24 ebp=8078ab28 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
decndis+0x1bb0:
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1   ds:0023:000001f0=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 93401bb0 to 828537eb

STACK_TEXT:  
8078aab0 93401bb0 badb0d00 00000001 80788000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ab28 934039c3 00000000 00000007 8078ab54 decndis+0x1bb0
8078ab40 934023db 8078ab54 86907ebc 86908008 decndis+0x39c3
8078ab78 93402af0 93406700 86945eac 00000000 decndis+0x23db
8078ab8c 8ae7720d 93406700 86907ebc 00000000 decndis+0x2af0
8078abac 8ae7709c 00908008 86907ebc 00000000 ndis!ndisSendCompleteWithPause+0xaf
8078abd0 8ae758a6 86908008 00000000 00000001 ndis!ndisMSendNetBufferListsCompleteToNdisPackets+0x7c
8078ac1c 8ae115e2 00000000 873ae3d8 00000001 ndis!ndisMSendCompleteNetBufferListsInternal+0x217
8078ac30 8ef30848 85fcabd0 873ae3d8 00000001 ndis!NdisFSendNetBufferListsComplete+0x3a
8078ac54 8ae115e2 85fca858 873ae3d8 00000001 pacer!PcFilterSendNetBufferListsComplete+0xb4
8078ac68 8ef4bb35 85fc9008 873ae3d8 00000001 ndis!NdisFSendNetBufferListsComplete+0x3a
8078ac8c 8ae75f0a 85fca008 873ae3d8 00000001 vpcnfltr+0x1b35
8078acb0 8f1d71d9 8589f0e0 873ae3d8 00000001 ndis!NdisMSendNetBufferListsComplete+0xa4
8078ad08 8f1d7e07 873ae3d8 00000000 85f9e000 k57nd60x+0x2b1d9
8078ae60 8f1d606d 85f9e000 00000000 00000000 k57nd60x+0x2be07
8078ae84 8f1ae9d5 85f9e000 00000000 00000000 k57nd60x+0x2a06d
8078aeb0 8f1aef9d 00000001 8589f0e0 85f88578 k57nd60x+0x29d5
8078aec8 8f1af147 00000000 00000000 8078af10 k57nd60x+0x2f9d
8078aee0 8ae63301 85f9e000 00000000 00000000 k57nd60x+0x3147
8078af20 8ae0e9f4 85f8864c 00f88578 00000000 ndis!ndisMiniportDpc+0xda
8078af48 828753b5 85f8864c 85f88578 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 82875218 82936d20 85cc7020 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 828749dc 8e9152cc 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 8e9152cc 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
828749dc 00000000 0000001a 00d6850f bb830000 0x8e9152cc


STACK_COMMAND:  kb

FOLLOWUP_IP: 
decndis+1bb0
93401bb0 6683bef001000001 cmp     word ptr [esi+1F0h],1

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  decndis+1bb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: decndis

IMAGE_NAME:  decndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  3d8305c8

FAILURE_BUCKET_ID:  0xD1_decndis+1bb0

BUCKET_ID:  OLD_IMAGE_decndis.sys

Followup: MachineOwner
---------

zzz2496