BSOD Starting Windows Virtual PC Machines (any machine, always bsod)

[seantomas]

Hello All,

I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last two crashes are from trying to start virtual machines, the most recent one is when I try to start a newly created vmcx, and the one before it is when I try to start/create the windows xp mode virtual machine. The errors are very consistent and happen every time at the exact same time. My setup:

Windows 7 Professional x64
i5-2500k CPU
ASROCK P67 Extreme4 with Bios v2.1
2x4GB RAM
c300 solid state 128MB OS drive
1TB samsung spinpoint data drive
ATI Radeon 4800 graphics card

I've never tried posting to a forum before, but I'm at my wit's end on this one and the people here seem to be quite knowledgeable and helpful. Any help on this would be greatly appreciated!
Shaun

 

[zigzag3143]

Hello All,

I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last two crashes are from trying to start virtual machines, the most recent one is when I try to start a newly created vmcx, and the one before it is when I try to start/create the windows xp mode virtual machine. The errors are very consistent and happen every time at the exact same time. My setup:

Windows 7 Professional x64
i5-2500k CPU
ASROCK P67 Extreme4 with Bios v2.1
2x4GB RAM
c300 solid state 128MB OS drive
1TB samsung spinpoint data drive
ATI Radeon 4800 graphics card

I've never tried posting to a forum before, but I'm at my wit's end on this one and the people here seem to be quite knowledgeable and helpful. Any help on this would be greatly appreciated!
Shaun

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[seantomas]

Thanks for the quick response. I will work on performing the tests you mentioned and post the results here.

Shaun

Hello All,

I've been getting consistent BSODs while trying to start Windows Virtual PC (not Microsoft Virtual PC 2007) machines on my computer. I've tried various driver updates and a bios update and several system restores along the way, but to no avail. In the attached dump files, the last two crashes are from trying to start virtual machines, the most recent one is when I try to start a newly created vmcx, and the one before it is when I try to start/create the windows xp mode virtual machine. The errors are very consistent and happen every time at the exact same time. My setup:

Windows 7 Professional x64
i5-2500k CPU
ASROCK P67 Extreme4 with Bios v2.1
2x4GB RAM
c300 solid state 128MB OS drive
1TB samsung spinpoint data drive
ATI Radeon 4800 graphics card

I've never tried posting to a forum before, but I'm at my wit's end on this one and the people here seem to be quite knowledgeable and helpful. Any help on this would be greatly appreciated!
Shaun

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[seantomas]

Okay, here's my update so far:

I have run memtest (and previously windiag) on each of my 4GB sticks, and tried them in each memory slot on the motherboard individually. They never generated any errors. I tried to start up a Windows Virtual PC machine with each stick individually and in different slots as well... every time I got a BSOD at the same time as before... as soon as I double click on the vmcx file.

I also tried running verifier as indicated. I rebooted several times while trying to start a virtual machine. Every time I got the BSOD as soon as I double clicked on the vmcx file. It did cause the driver for my smartphone to throw an error after one of the bootups, but not every time, and the BSOD upon vmcx start continued regardless of whether the phone driver was loaded or not.

I've attached the latest crop of dump files.

Thanks again for your help,
Shaun

 

[seantomas]

This update doesn't add much except to say that I have fully tested the memory now and neither stick in any slot generates errors with memtest.

Using the computer regularly does not result in blue screens. The blue screen only happens when I try to start a windows virtual pc machine - within a second or two after I try to start the virtual machine. The older version - Microsoft Virtual PC 2007 can start virtual machines just fine. The issue definitely seems to be directly related to something the system is doing when trying to start a virtual machine using the windows 7 version of virtual pc... I just wish I could find out what it was.

Shaun

 

[zigzag3143]

This update doesn't add much except to say that I have fully tested the memory now and neither stick in any slot generates errors with memtest.

Using the computer regularly does not result in blue screens. The blue screen only happens when I try to start a windows virtual pc machine - within a second or two after I try to start the virtual machine. The older version - Microsoft Virtual PC 2007 can start virtual machines just fine. The issue definitely seems to be directly related to something the system is doing when trying to start a virtual machine using the windows 7 version of virtual pc... I just wish I could find out what it was.

Shaun

Try a different VM. The new bunch is more of the same.

 

[seantomas]

I've tried 4 different VMs so far. They all blue screen as soon as I try to start them.

 

[zigzag3143]

I've tried 4 different VMs so far. They all blue screen as soon as I try to start them.

Have you tried with just 4 gigs ram?

 

[seantomas]

Yes, I've tried with each of the 4GB sticks in various motherboard slots.