jeff_abbot
Contributor
Contributor

Bluescreen stop on Vista 64 bit host

I've been trying to evalute VMWorkstation. I've tried using version 6.0.1-55017 and 6.0.2-59824. Both cause a Blue Screen stop error as soon as I try to start a Virtual Machine. I can create the machine but not start it.

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffa80026f2dea, 0x0000000000000000, 0xfffff8000245db11, 0x0000000000000000).

I'm using Vista Ultimate 64 Bit on an Intel DP35DP motherboard with VT technology turned on ( I've tried it turned off and it still crashes). I have a Core 2 Duo 3.0GHZ processor and 4 GB of ram. I'm using the motherboards on-board Raid 0.

I've tried having UAC turned off during the install and running but still get the same crash.

Any one got any idea's why my systems crashes as so far I have not got anywhere.

Jeff

Tags (2)
0 Kudos
10 Replies
jonaska
Contributor
Contributor

Try the Processor Check for 64-Bit Compatibility tool.

You'll find it here: http://www.vmware.com/download/ws/drivers_tools.html

0 Kudos
jeff_abbot
Contributor
Contributor

I downloaded the processor check program and it tells me "This host is capable of running a 64-bit quest operating system this VMware product"

I'm not even trying to us a 64-bit OS as a guest. I dont get that far as to installing any OS. I cant even start a VM under the Player. I get the same Crash as above.

0 Kudos
Steve_Ferraciol
Contributor
Contributor

Try taking 2Gb of RAM out of the machine and see if that works. I'm having a similar problem with the DP35DP. I believe the solution is a future BIOS update from Intel and a hotfix in Vista SP1 thats not available as of yet.

0 Kudos
jeff_abbot
Contributor
Contributor

Thanks for the reply Steve, but I've already tried removing ram but it didn't help; same Bluescreen stop error. I think it must be something thats clashing between vmware and the intel bios. I have a similar PC excepts its a DG31PR motherboard but still with the P35 chipset. It only has 2GB ram.That PC is running Ubuntu Linux and VMware manages to crash that too. Except it crashes when running a guest OS. I dont get as far as installing any guests on vista.

Jeff

0 Kudos
rsa911
Virtuoso
Virtuoso

can you post your virtual machine config file (.vmx file) and the vmware.log file (also to be found in the VM directory)

0 Kudos
jeff_abbot
Contributor
Contributor

Config file:-

config.version = "8"

virtualHW.version = "6"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "512"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Ubuntu.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.wakeOnPcktRcv = "FALSE"

usb.present = "TRUE"

ehci.present = "TRUE"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

svga.autodetect = "TRUE"

pciBridge0.present = "TRUE"

mks.keyboardFilter = "allow"

displayName = "Ubuntu 7.10"

guestOS = "ubuntu"

nvram = "Ubuntu.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "useGlobal"

ide1:0.autodetect = "TRUE"

floppy0.fileName = "A:"

extendedConfigFile = "Ubuntu.vmxf"

Where exactly should the log files be? A search of the VMware directory ( or the virtual machine directory shows NO logs.

The last bugcheck:-

Log Name: System

Source: Microsoft-Windows-WER-SystemErrorReporting

Date: 28/10/2007 11:42:55

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: SATURN

Description:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffa80026f2dea, 0x0000000000000000, 0xfffff8000245db11, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />

<EventID Qualifiers="16384">1001</EventID>

<Version>0</Version>

<Level>4</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2007-10-28T11:42:55.000Z" />

<EventRecordID>75932</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>System</Channel>

<Computer>SATURN</Computer>

<Security />

</System>

<EventData>

<Data Name="param1">0x00000050 (0xfffffa80026f2dea, 0x0000000000000000, 0xfffff8000245db11, 0x0000000000000000)</Data>

<Data Name="param2">C:\Windows\MEMORY.DMP</Data>

</EventData>

</Event>

0 Kudos
rsa911
Virtuoso
Virtuoso

stop the vm and try to simplify as much as possible your VM config: remove USB, Sound, Floppy,...

the log is simply called vmware.log and should be present in the virtual machine directory on your host (next to the .vmx file)

0 Kudos
jeff_abbot
Contributor
Contributor

Stop the machine?? I wish I could!. I've never got as far as starting one.

I tried as you suggested amd removed all the devices except for HD and CROM. I still cannot start the machine, I get the same bluescreen crash. Oh and there is no log file, anywhere. It never gets as far as creating one.

It seems VMware just doesnt work here.

Jeff

0 Kudos
jeff_abbot
Contributor
Contributor

I found a log in the temp directory:-

Oct 30 09:23:23.798: vmui| Log for VMware Workstation pid=2704 version=6.0.2 build=build-59824 option=Release

Oct 30 09:23:23.799: vmui| Hostname=saturn.galaxy.local

Oct 30 09:23:24.068: vmui| HostDeviceInfo: Failed to enumerate host parallel ports via the registry. Could not open device map parallel port registry key.

Oct 30 09:23:24.156: vmui| HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

Oct 30 09:23:24.156: vmui| HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Oct 30 09:23:24.784: vmui| Foundry Init: setting up global state (0 threads)

Oct 30 09:23:24.784: vmui| Foundry Init: version 3, hostType 1, hostName (null), hostPort 0, options 0x203

Oct 30 09:23:32.272: vmui| Reloading config state: E:\vmware_machines\Ubuntu 7.10\Ubuntu.vmx

Oct 30 09:23:33.221: vmui| UpdateMenuState failed for item: 40046: Access violation - no RTTI data!

Oct 30 09:23:33.221: vmui| UpdateMenuState failed for item: 40730: Access violation - no RTTI data!

Oct 30 09:23:33.222: vmui| UpdateMenuState failed for item: 40721: Access violation - no RTTI data!

Oct 30 09:23:33.222: vmui| UpdateMenuState failed for item: 40723: Access violation - no RTTI data!

Oct 30 09:23:33.222: vmui| UpdateMenuState failed for item: 165: Access violation - no RTTI data!

Oct 30 09:23:33.222: vmui| UpdateMenuState failed for item: 40078: Access violation - no RTTI data!

Oct 30 09:23:33.223: vmui| UpdateMenuState failed for item: 417: Access violation - no RTTI data!

Oct 30 09:23:33.223: vmui| UpdateMenuState failed for item: 40058: Access violation - no RTTI data!

Oct 30 09:23:33.223: vmui| UpdateMenuState failed for item: 40010: Access violation - no RTTI data!

Oct 30 09:23:33.223: vmui| UpdateMenuState failed for item: 40048: Access violation - no RTTI data!

Oct 30 09:23:33.224: vmui| UpdateMenuState failed for item: 40047: Access violation - no RTTI data!

Oct 30 09:23:33.224: vmui| UpdateMenuState failed for item: 41960: Access violation - no RTTI data!

Oct 30 09:23:33.224: vmui| UpdateMenuState failed for item: 513: Access violation - no RTTI data!

Oct 30 09:23:33.224: vmui| UpdateMenuState failed for item: 40060: Access violation - no RTTI data!

Oct 30 09:23:33.224: vmui| UpdateMenuState failed for item: 40067: Access violation - no RTTI data!

Oct 30 09:23:33.225: vmui| UpdateMenuState failed for item: 40051: Access violation - no RTTI data!

Oct 30 09:23:33.225: vmui| UpdateMenuState failed for item: 40059: Access violation - no RTTI data!

Oct 30 09:23:33.225: vmui| UpdateMenuState failed for item: 40021: Access violation - no RTTI data!

Oct 30 09:23:33.225: vmui| UpdateMenuState failed for item: 40020: Access violation - no RTTI data!

Oct 30 09:23:33.226: vmui| UpdateMenuState failed for item: 40019: Access violation - no RTTI data!

Oct 30 09:23:33.226: vmui| UpdateMenuState failed for item: 40062: Access violation - no RTTI data!

Oct 30 09:23:33.226: vmui| UpdateMenuState failed for item: 166: Access violation - no RTTI data!

Oct 30 09:23:33.226: vmui| UpdateMenuState failed for item: 429: Access violation - no RTTI data!

Oct 30 09:23:35.696: vmui| CVMUIApp::MenuButtonClicked: 0 E:\vmware_machines\Ubuntu 7.10\Ubuntu.vmx

Oct 30 09:23:35.720: vmui| Unhandled C++ exception: class 'class __non_rtti_object', details 'Access violation - no RTTI data!'

Oct 30 09:23:38.378: vmui| Exception caught; trying to exit app.

Oct 30 09:23:38.415: vmui| Exited abnormally.

BTW My PC does not have parallel or serial ports,nor does have PS2 ports. Its usb only.

0 Kudos
jeff_abbot
Contributor
Contributor

I completely re-installed Vista and VMware is working fine now. I've no idea why I was getting crashes before. My vista installation must have been completely messed up for some reason. Pity my trial key expired before I had time to give it a fair go.

Jeff

0 Kudos