VMware
This thread is locked

This Question is Answered

2 "helpful" answers available (6 pts)
12 Replies Last post: Nov 3, 2008 9:48 PM by nextech  

Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0 posted: Oct 29, 2008 11:09 PM

Click to view nextech's profile Enthusiast 139 posts since
Sep 9, 2008

Everything has been working fine (and normal) until I installed a Windows Update. It said there were some updates to install, and after a reboot (in native Windows Vista) I noticed that I was unable to load Vista in Fusion 2.0 anymore.

I believe it may have had something to do with a language file update, because it was giving an error about NLS? (just before the first blue screen of death crash)

The weird thing is, I can boot directly into Vista (in my boot camp partition) just fine, and everything works normally. It seems to only be a Fusion 2.0 problem.

Anytime I load up Fusion 2.0, and attempt to start the Boot camp partition, it just begins loading and gets to a "*** STOP: 0x0000007B (0xFFFFFA60005AF9D0, 0xFFFFFFFFC000034, 0x000000000000000, 0x000000000000) error and says "A problem has been detected and Windows has been shut down to prevent damage to your computer, blah, blah, blah."

I've tried rebooting into Safe Mode (inside of Windows Vista from within Fusion), but it crashes with a blue screen of death as well as soon as it gets to the

I'm guessing that something in the latest windows update is causing Vista to crash (from within Fusion 2.0). If I boot directly into Vista there is no problem, but if I attempt to use Fusion, it just crashes continously, and I've tried installing the original DVD and pressing F8, hoping to find a way to repair the installation, but I just don't even see an option. As soon as it begins to try to boot to the menu (to even repair) it crashes from inside Fusion.

If I boot directly into Fusion, it works just fine. Any ideas as to what I can do to try and fix this? Since the update just appeared, and I just installed it tonight, any ideas what could be causing the problem/conflict with Fusion?

Apparently Microsoft "broke something" with Fusion, because whatever it is... Vista just will not run in Fusion anymore. Any ideas as to how I can remove Fusion, and delete the Fusion configuration files, and possibly reinstall Fusion, and reinstall a new "Virtual Machine" (using the Boot Camp partition) and maybe this will fix the problem?

Maybe Vista overwrote some files that Fusion/VMWare Tools uses or something? Is that possible? So maybe if I could remove VMWare complete, and attempt to do a clean install and readd the Boot Camp Partition to VMWare, maybe that will fix it and resolve whatever it is that Microsoft did?

Again, I'm not quite sure how to do this (I'm familiar with Workstation 6.5, but not with Fusion 2.0) so I'm still poking around and learning. I would greatly appreciate any instructions on how to remove Fusion 2.0 completely, and remove any configuration files, and attempt a clean install of Fusion 2.0 and import my Boot Camp Partion back into Fusion (and cross my fingers that the fresh re-install will overwrite or fix whatever it is that Microsoft has broken with their latest updates). Again, this is Windows Vista Ultimate x64 running on a native Boot Camp partition (using Fusion 2.0) in Leopard 10.5.5.

Thank-you so much.

Click to view etung's profile Guru 11,086 posts since
Oct 15, 2006
Frequently Asked Questions about Guest OSes: Boot Camp virtual machine has a Blue Screen of Death with error code 0x0000007b
Click to view etung's profile Guru 11,086 posts since
Oct 15, 2006
If you do a search for any significant part of the phrase "Boot Camp virtual machine has a Blue Screen of Death with error code 0x0000007b" in Frequently Asked Questions about Guest OSes (or Frequently Asked Questions about VMware Fusion), you'd see a very short section with a link to Re: Bluescreen trying to run Fusion 1.1.2 from Boot Camp partition on MacBook Air, which explains what's going on and how to fix it. I see you found this link on your own.

While you're wise to be cautious about OS differences, I believe in this case it doesn't matter if the guest is XP or Vista and that the problem and solution is the same for both. As Jim said in that post, "The Stop 7B bluescreen is always caused by a missing intelide.sys driver" - unless you have evidence this is not the case for you, I'm going to believe Jim. You need to locate the appropriate .cab files and extract the intelide.sys driver. While the various scripts may not work directly, you can hopefully get an idea of what they're doing and determine the analogous commands for Vista.

Alternately, assuming you haven't added extra references (such as adding another virtual disk or taking a snapshot), while Fusion isn't running, you could delete the Boot Camp metadata (the actual data should be on the partition and so be safe) and naos helper virtual machine (both are located in /Users/${USER}/Library/Application Support/VMware Fusion/Virtual Machines/). The next time you run Fusion, the Boot Camp virtual machine will be recreated; the next time you run that virtual machine, Fusion will re-prepare the Boot Camp partition, hopefully restoring the IDE driver.
Click to view WoodyZ's profile Guru 10,110 posts since
Apr 22, 2004
While I understand that you can boot the Boot Camp partition natively without any issues the fact that this is happening when running the Boot Camp partition as a Virtual Machine does not, in general, change how one has to troubleshoot the issue. This means the same methods and techniques one would use on a stand-a-lone physical machine apply and in that respect it has nothing to do with Fusion per-se. Which means in order to figure out what you're having an issue with in Fusion you have to apply the same information available at Microsoft to troubleshot BSOD's.

Since you have possibly tied the timing of this to the Windows Updates you just did then one place to start is to either uninstall the Windows Updates or use System Restore to roll back to a point prior to the Updates and then manually update one update at a time until you see which update effects the system when running it as a Virtual Machine. You can review your Windows Update History online or look in the Windows Update History Log File for exactly what was applied recently and information on this is available at Microsoft.

You can also look in the Event Logs for flags and the BSOD information and if necessary modify Startup and Recover preferences to insure this information is being gathered including a memory dump that can be analyzed. Again all this information is available at Microsoft.

This has also been covered before in this forum as I know I have provided direct links to MS KB Articles numerous times in the past as well as this information can be found on Goggle too.

A quick way to provide troubleshooting information from the Fusion side would be to use the Collect Support Information command from the VMware Fusion Help Menu and upload the .tgz file created on your Desktop.
Click to view WoodyZ's profile Guru 10,110 posts since
Apr 22, 2004
nextech wrote: Your solution of just deleting those two files, and starting up Fusion was by far the simplest (and easiest) answer I've read so far. Incredibly simple, and it worked like a charm. I would highly recommend it over any of the other things I have read (in any of those previous posts). Expanding CAB files, or any of that other stuff. Deleting those two files and restarting Fusion was by far the easiest possible solution.

Very quick, and very simple. Didn't have to hunt and poke, and spend hours dealing with Microsoft (and their hundreds of articles and KB's with solutions that usually never seem to fix a problem), but this one worked great!

It was simple and fast, and I would highly recommend trying this first over any of the other articles I have read so far concerning this issue. Nice and simple, very easy, and I was back up in running in seconds! Less than 10 seconds and wow... it works! Thank-you guys.

Fusion fixed itself, and I'm incredibly happy! (one more thing, for anyone that does this... please be sure to reinstall the VMWare Tools because it seems to remove the VMWare Tools, so just click the "Virtual Machine > Install VMWare Tools" menu option after Vista boots up and everything is back up and running perfectly! Thanks guys! Thank-you Etung for such a quick and simple fix.


It's not like this is some big well kept secret... as a matter of fact it's pretty much SOP with Boot Camp partition Virtual Machines issues as a first step in trying to correct the various issues that come about with Boot Camp partition Virtual Machines. Just this year alone I have suggest users delete the Boot Camp partition Virtual Machine to rebuild the meta-data no less then 60 to 70 times and if you what to add all the number of times Eric and several others regulars have also posted the same advice then it's probably in the hundreds. As a mater of fact searching for STOP 0x0000007B or BSOD 7B or STOP 7B would have yielded the delete the Boot Camp partition Virtual Machine advice enough times that I'd venture to say had you done a little searching and reading first you would not have even needed to post in the first place and there are plenty of other users that have posted that they didn't need to post their questions because after search the forum they found that the information such as in this case fixed their particular Boot Camp partition Virtual Machine issues much less the same type of replies to answers to other issues in general. So I wonder why you seem to have so much trouble finding answers to your issues when they have already been asked and answered more then enough times that others have no problem finding the answer without having to ask but apparently for some reason you just can't.

Anyway JSYK deleting the Boot Camp partition Virtual Machine to allow Fusion to rebuild the meta-data does not always work with STOP 7B BSOD's and you should count yourself lucky it worked for you this time as there are no guarantees it will work the next time because not all STOP 7B BSOD's are caused by the same thing and while deleting Boot Camp partition Virtual Machine does fix many of types of issues it doesn't fix them all and sometimes it does just come down to preforming the lower level diagnostics and following the MS KB Articles so I wouldn't discount or knock that advice because when the time comes that your only choice is going to be try what's in the KB or rebuild the system you'll be happy that there are some solutions that while not as easy as deleting Boot Camp partition Virtual Machine it will be less painful then having to rebuild from scratch.
Click to view etung's profile Guru 11,086 posts since
Oct 15, 2006
Oh dear, where to begin.

I merely skimmed your post, so I may have missed some things, but to clarify: WoodyZ is not a VMware employee, bur rather a (knowledgeable) user. He is not responsible for or involved with Fusion, so it's inappropriate to direct frustration with Fusion at him or to expect him to be able to do anything about Fusion's bugs. If you want to take it out on someone, try me - I am a Fusion developer.

Woody is completely correct about the possible need to have done all the things he suggested if the simple trick of deleting the Boot Camp metadata didn't work. It's common advice, so perhaps he assumed you had already done so. There have been a number of cases in the past where deleting the Boot Camp partition has not worked.

I also disagree that this is (clearly, at least) a bug with Fusion merely because it works in a native boot but not in Fusion. Removing the Boot Camp metadata causes Fusion to redo the preparation steps of poking Windows to get the right drivers. You had mentioned that you just applied a Windows update, and I think it's likely that doing so somehow upset Windows' drivers. Keep in mind that since virtual hardware is different from native hardware, we use different drivers than native boot, so it's entirely possible for one set to be damaged and have the other be fine. Nothing to do with Fusion.

Tip: If you accuse someone of ranting (and I don't think Woody was, nor do I think he took offense about who you gave credit to), it doesn't help your position for your accusation to be about 16 times longer than the thing you're replying to.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities