VMware Communities: Message List - Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Tue, 04 Nov 2008 05:48:05 GMT

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

I apologize, and all I asked was to help me get it back up and running (which you did) and I thank you for the quick and simple response.

There was no need to "bang on the bees nest" or go back and forth turning this into a nice long discussion (or justification) on why he feels he was correct. I agree, I do firmly believe that the Windows Update caused the problem. I do agree that Microsoft must have updated something, that did somehow cause a problem with the drivers possibly (the how/what/why I have no clue). I honestly don't have the time to waste hunting and poking, and messing around with it to even find out, or even care. My point is, that I'm just a user who depends on Fusion (former Workstation 6.0/6.5 user) but now that we've moved over to Mac's, I'm depending on Fusion.

So I am very new to this arena, and I thank-you again for the quick and VERY helpful response (it worked, it solved the problem, and it got me back up and running fairly quickly which is all that I was asking for). I honestly don't have the time (or resources) to be spending hours and hours hunting and poking for solutions (or reading Microsoft's vast knowledge base of hundreds and hundreds of thousands of pages related to specific errors), and it would be unlikely that an update that just got pushed out that day would already have a KB article written specifically to fix/address the issue. It would probably be weeks or months before Microsoft actually published a fix (if ever) since it's related only to VMWare Fusion, and Microsoft would have more than likely pointed me directly to VMWare and asked that I talk to them about the problem.

So yes, something Microsoft did (during the update) boinked the VMWare Fusion install. Yes, deleting those two files, and restarting Fusion did cause Fusion to reinstall the drivers (or whatever else it does in the background) and yes... it worked perfectly. Other than having to go back and reinstall VMWare Tools I was up and running in minutes/seconds. (I was incredibly happy to see the Vista login screen again).

So again, thank-you.

If you want to take it out on someone, try me - I am a Fusion developer.

Nah, my intent is not to attack the developers. You guys did a GREAT job designing a GREAT product, and my only other option is Parallels, and to be honest... Parallels is a "sub par" product compared to VMWare Fusion. You guys are doing an INCREDIBLE job, and every feature I have ever wanted (or asked for) is in Workstation 6.5 (and Fusion 2.0). My only last request is Direct X 10 support (that would be great!).

Again, thank-you for the hard work on this, and VMWare has come a very long way. I've been using it all the way back to GSX Server 2? and 3.1? So it's been awhile. I remember in the early days I had lots of gripes with it but the VMWare products have REALLY come a long way. Keep up the good work, keep improving your product (it still has a long way to go, and don't give up). The "Unity" feature is wonderful. You guys really are amazing.

I purchased two copies already, and I would almost purchase another copy or two (just to help fund the continued development of a great product). I do a lot of work for churches and various organizations, and the first thing I recommend is purchasing VMWare.

* If you want to take it out on someone, try me - I am a Fusion developer.*

I apologize, for some reason I thought "Woodyz" was senior to you or something. That's the only reason I was bothered because I saw a gold trophy next to his name, and didn't see one next to your name. (So I thought he was just upset that you had the correct answer). I was also bothered that he said something to the effect that "if you would only do a search, and do your own searching, then you could have solved the problem yourself" (or something to that effect).

Well, I hate to burst his bubble, but I've NEVER posted a post, without searching Google first, and without searching the forums as well. Google seems to be a much better search engine (and does a much better job of indexing key words), and the reason I was descriptive in my posts (listing the operating system, and the particular version of Fusion) is so that this page will probably get indexed by Google hopefully, and I'm hoping that if anyone else is looking for a solution (to an IDENTICAL problem after a Microsoft update gets pushed out) then maybe they will try this solution.

I would have rather had this post stay as short (and clear/concise as humanly possible), but there was no need for an additional response (after the question was already correctly answered and points were already awarded).

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.

I agree, but just try to keep things simple for us users, and give us the easiest solution possible first. If that doesn't work, then slowly move on to giving us step by step instructions on expanding CAB files, or running/unzipping scripts, or whatever else (but I'm very leery of reading a 3-4 year old post on Windows XP/Fusion 1.1) and running a script designed for an older operating system (and older version of Fusion). I don't want to "compound my problems" by making a situation even worse (and then possibly having to completely rebuild my whole Vista installation).

So I was very leery of those much older posts and I was just looking for something simple, quick and fast (and that works).

I was just upset that Woodyz seems to forget who his "audience" is. Take a look at the little "black pawn" next to my name. May as well print the words "Newbie" right underneith. Yes, I'm new to Fusion 2.0, and I'm NOT a Fusion 2.0 developer, and I don't design Fusion on a daily basis (nor do I understand or even care to learn all the ins and outs of Fusion).

If something breaks, I just want an answer (and a solution on how to fix it). That's it. Sure, bugs happen. Sometimes Microsoft does something stupid to patch 2 or 3 of their own bugs/security vulnerabilities, etc. Those 2 or 3 patches, can often cause or introduce 8 or 10 more bugs or problems. It happens. Fix one thing, break another.

That's why I HATE installing updates or fixes. If it's working, I prefer to leave it alone (don't fix what isn't broken). I was stupid for installing the Windows Updates. I was working late on a project, and I clicked the button, and POOF... now Fusion stopped working. I was more angry than anything. I've dealt with Microsoft for decades (since 1986?) so I've had my fair share of upsetting moments. I remember one year they went around deactivating volume license keys (apparently a Dell key had been leaked?). Who knows. But it sent about 30 of our workstations into endless reboots. This was around 2002 or 2003. Who knows, a long time ago, but I'll never forget it. Our IT guys were running around in circles and we had days of lost productivity while Microsoft "played dumb" about the problem and denied any wrongdoing. Later we found out that it was Microsoft that INTENTIONALLY did this (to thwart piracy) but apparently they didn't realize that maybe they should have issued Dell a new VLK first (which they did) but Dell never made any effort to recall the thousands and thousands and thousands of computers that were using that Key (that they had manufactured/rolled out). So while Microsoft may have stopped 50 or 100 pirates, they also took down about 20,000 or 30,000 legitimate users.

I know things are done differently over at Dell now, and at Microsoft as well. But you have no idea how angry these people were when they purchased a legitimate product, and got screwed like that. I swore on my life that I would never buy another Microsoft product again after that... and here we are with Vista. But I can assure you, that our "IT Guys" are working hard to ween ourselves of Microsoft. After something as horrid as that, we have begun looking at other options (Ubuntu, and OS X). So that's why I'm working on a brand new Mac Pro right now, and my Dell 1330 laptop and Dell 1530 laptop are both headed to the trash can as they begin to get us some new MacBook Pro's.

Sure, we'll have to run VMWare Fusion until we can completely ween ourselves of any and all Microsoft software (and products that ONLY run on Windows XP/Vista). As more and more Mac stuff comes out (that runs natively in OS X) our IT guys are working hard to purchase that stuff.

All it takes is one REALLY REALLY bad experience to lose a customer. They would get rid of our exchange server, and everything (if they could) but we're currently dependent upon SharePoint services, and Exchange, so it might be another couple of years before we can dump all that stuff, and maybe Apple will begin developing a much more advanced SnowLeopard OS X server (that will compete head to head with Windows Server 2008) and Exchange Server 2007 with Communicator. Who knows, it could happen. I'd love to see it, just so we can dump Microsoft.

As for right now, we're glad to have VMWare (and Fusion). Fusion 2.0 was "god sent" and our IT guys have been waiting for this new release so they could begin moving more and more of us over to Macs. We got 20 new Macs in the past month, and the IT team is pulling their hair out with migrations. (moving proprietary data/proprietary applications).

* There have been a number of cases in the past where deleting the Boot Camp partition has not worked.*

Trust me, if it wouldn't have worked, I would have been back with a new post... saying "It didn't work... now what?" I just believe in keeping things as simple as possible for the end user (which you did).

I have to say, I really thought it was going to be a long/hard/complex solution, and when you suggested deleting 2 files, and restarting it... that was what I was praying for. Something simple. I kept my fingers crossed, I deleted the two files, and I restarted it, and boy was I dancing around the room when the Vista login page showed up.

Thanks again.

One more thing... thank the VMWare management (and owners/president) for hiring American. We are so tired of dealing with Microsoft Support (in India) and Dell Support (in India or China) that we've had enough.

We'd rather spend twice or three times as much (and buy an Apple made in California by American developers) and be able to pick up the phone, or talk/type to an American worker. So my hat goes off to you guys, and tell your upper management that if VMWare "got stupid" and tried to outsource their development to a foreign country, we would dump them in a heartbeat.

As an American, we are SICK AND TIRED of the shoddy development and SHODDY support that comes out of these third world countries. When I have a problem, I don't want to sit on hold for 3 hours, while some monkey that barely speaks any english is reading something from a screen (and has no clue what it even means). I want to talk to a REAL LIVE DEVELOPER/ENGINEER (that is an AMERICAN) and I'm proud to support (and purchase) a product made here in America, and developed by an American company, here in the United States, and that employs American workers, and American developers.

The day VMWare turns into outsourcing jobs, is the day I dump VMWare. So just pass that message along to your bosses/supervisors/owners. We're done with Microsoft, until they bring all those jobs back to America (and even then, I'm not sure that we would forgive them). We're tired of their shoddy products, and shoddy support. Microsoft products were decent when they were made in America. At least the support was good when it was here in America. Those third world countries could really care less when you call them (it's like we are annoying them or bothering them, because we are having a problem with their BROKEN product). If the product worked, we wouldn't be calling. The Customer service is terrible, and when I have a problem I want to talk to an American. I want someone that can speak my native tongue, and someone that understands how I feel. If my boss is breathing down my neck, I want an American (that understands what that is like) and has a sense of urgency to help me and get me going again.

* it doesn't help your position for your accusation to be about 16 times longer than the thing you're replying to.*

We're just upset over the economy, and the lack of good engineering jobs (and the number of good engineering jobs that have been outsourced overseas) and we're just angered by these companies that lay off American workers (and developers and engineers) just to save themselves a few dollars (because in the long run, it doesn't work out for them). All these companies that have outsourced overseas, are beginning to realize they never realized ANY cost benefit. The damage it has done to their reputation, to their product line, to the quality of their products (and quality of their support), plus the stigma of taking away American jobs and "going foreign" has really destroyed their name.

The only reason I would even think of buying a Honda is if it's made in Ohio by American workers, here in America. So my hat goes off to you gentlemen, thank-you for your hard work, thank-you for a great product, and tell your bosses/upper management do NOT screw this up. You have a good company, a good product, good engineers, good developers (now just don't screw this up or do anything stupid, or attempt to "go foreign" on us). If they do, I will "vote" with my wallet.

As more and more Americans begin to "vote with their wallet" it will affect the profitability (and bottom line) of these companies that attempt to outsource jobs. If American engineers are not working, and not making good money, then these same people are NOT buying cars, NOT buying new shiny cell phones, NOT buying toys, and NOT spending their hard earned money. As more and more Americans are put out of work (and those good jobs go overseas) by GREEDY companies that want to increase their profits, then suddenly you see the shape our country has gotten into. Soon the economy collapses. Outsourcing does NOT work. You can't compete with a third world country (economically) with "FREE TRADE" and think that you will survive. I believe in FAIR TRADE, but NOT free trade.

Tax the living crap out of companies that outsource more than 1% of their labor/workforce (and level the playing field for American workers and American companies). Ok, well go vote tomorrow, and hopefully we'll see what happens during the next 8 years when the next clown becomes president. Hopefully the next person that is in office will care a little bit more about the American people, and the American workers, and the American jobs.

I don't want to hear any silly nonsense about telling people to "go back to school and get trained". Heck, I have people that lost manufacturing jobs, trying to go to school for computers. Heck, there are NO JOBS in computers! There are no jobs period! So training is NOT what we need, JOBS is what we need!

Bring the jobs back to America, pay American workers an honest and decent salary, and you'd be surprised at how quickly this economy turns right back around. When hardworking Americans have jobs, and are making money... they are spending money. The more we make, the more we spend. The more we spend, the more we fuel the economy.

Laying off Americans, and putting them out of work, and then wondering why nobody can afford to buy your products (because everyone is out of work) only compounds the problem. Our company stopped buying Dell (just to let Dell know that we would rather spend 4 or 5 times the amount of money per machine and buy an American product, then support the outsourcing to India and China).

If the government (under the next president) would begin taxing these imports (from China and India) and begin taxing the living crap out of companies that outsource, suddenly it would "level the playing field". American companies could finally compete. If you had the choice of buying a $900 computer from an American company (made in America) or buying a $900 computer made in China (that may only cost $400 to be built in China, but $500 in IMPORT TAXES) then suddenly more and more Americans will buy American.

Thank your owners for their patronage to America. I'd gladly pay twice as much to buy American just to know that a product was PROUDLY BUILT IN AMERICA (by American workers). Thank-you guys.

* Oh dear, where to begin.*

Let's just call it a day. The rant is over. Go vote tomorrow, and as an American begin VOTING with your wallet. Sometimes it's the only way to show companies their support. If Microsoft wants to outsource their Labor pool, and send jobs overseas, then we'll just stop buying Microsoft (plain and simple). That's why we're purchasing so much VMWare (so we can slowly wean ourselves of Microsoft). Someday we'd love to run Ubuntu if we could, but we need developers to begin releasing their software products for OS X or Ubuntu (so we can dump Microsoft). If a company becomes "unamerican" then Americans will begin revolting and tossing the tea in the water (think about the British and Boston Tea Party). Americans are upset, and we just want those jobs brought back to America. We want the engineering, developing, and even the manufacturing to all be done here in America.

Just pay the workers and honest and decent working wage, give them medical and dental, and Americans will gladly support their products (and buy American). I'm pretty happy when I'm given the choice to buy American. I swore I would never buy a Honda, but when I see American workers buiding these cars (in Ohio) and see that 87% of the vehicle is made/manufactured in America, by Americans... I guess that's good enough for me. When I see American engineers working there, and I can shake hands with them, it makes me happy.

The engineers at Ford and GM really need to step it up a notch, and start developing cars that get 80+ miles to a gallon, and run on alternate fuels (such as water). Yes, it wouldn't be hard to develop a car that would run on water. Just take a current hybrid (like the Prius) and put a hydrogen fuel cell in it (so the vehicle can run on electricity for the most part, but use hydrogen when necessary), and then toss a solar panel roof on the vehicle (so that the car is "charging" its batteries during the day while you are at work, and the car is sitting outside in the parking lot soaking up sun). So the car is charged and ready for the commute home. We need better battery systems (Lithium Ion), and with the Hydrogen Fuel cell, we need a much smaller Hydrogen cell, and instead a small "Hydrogren generator" (that splits a 10 gallon tank of water into Hydrogen gas that will get stored in the Hydrogen fuel cell). As the hydrogen generator splits the H2O water molecules (into 2 atoms of hydrogen gas, and 1 atom of Oxygen) the Oxygen is released back into the environment (as clean pure oxygen) and the Hydrogen is stored into the fuel cell (to be burned as a clean fuel) and the byproduct/waste is nothing more than water. So Americans can drive around getting hundreds (or even thousands) of miles to a full tank of water (with a solar panel roof, and advanced lithium ion batteries) and water doesn't cost us anything.

Just get a 55 gallon drum and connect it to your gutter. If you have 3 or 4 downspouts, you can have 3 or 4 of the 55 gallon drums, and that's enough water to power your whole house. Yes, clean and renewable energy is the way to go. Slowly we can rid ourselves of these big greedy oil companies (and the global terrorism that many of these foreign countries fund and support with their oil sales).

All it takes is some good American engineering and a few Americans to put their "thinking caps" on. The Honda FCX is the perfect car to "convert" into a water fueled vehicle. It's about the size of a Honda Accord, and it runs on Hydrogen (it's a Hydrogen Hybrid vehicle) and it's full size vehicle. So all it takes is a couple of engineers to get off their tail, and create an "aftermarket upgrade" (that costs less than $3,000 in parts) that can be installed in the Honda Prius or Honda FCX, and run the vehicle completely on water.

It's coming, we just need someone to step forward and do it. Hopefully it will be an American company, with American engineers. I'd gladly support ANY American company that started doing this (and started manufacturing these cars that work 100% on water). We've demonstrated that hybrid vehicles do work, and once they are produced on a global scale (mass production) the costs will drop significantly.

If the government would step in, and say that by 2012 all vehicles MUST get 100 miles to a gallon (sure, it may seem unrealistic, but it's not). We can easily hit 80 miles to a gallon right now, and in 3-4 years we should easily be able to squeeze 100 miles to a gallon (and yes, even water) using hybrid battery technology (an electric car, that only uses water/hydrogen as an alternate fuel source if the batteries are running low and need to be recharged).

Then slowly build solar homes (and homes that have lithium ion battery cells, that can be powered/heated in the winter by Hydrogen). Then have a Hydrogen fuel cell that splits rain water, into hydrogen gas, so that homes can be heated with Hydrogen gas in the winter months (free heat), and air conditioned by solar panels (on the roof) during hot summer months. Help eliminate the cost of expensive energy on the American people.

The technology exists, we only need to start using it (and developing/improving it). Begin manufacturing these products here in America, and hire American workers, and the government can give loan subsidies (0% interest loans and tax breaks to people who want to purchase/invest in clean energy). That way Americans can buy a "zero emissions" vehicle (that runs solely on hydrogen/water/electricity) and get a $8,000/yr tax break on their income taxes. It will help offset the costs of the technology. Plus it would be great for the economy (and the environment).

In a few years, maybe the government can back "clean energy" (zero emissions) homes that are 100% solar/hydrogen/water powered. Any excess electricity/energy that is produced could be pumped backwards back into the electric grid (and the homeowner can get a CHECK each month from their electric company, and use that money to help pay their mortgage). That excess energy can be sold (at very cheap rates) to businesses that need lots of power (i.e. manufacturing companies, large businesses, corporate companies, etc.). At least these companies can be purchasing very cheap (and CLEAN energy). Many of these companies could be given "tax breaks" for installing large solar panels on their roofs (to help reduce their dependence on the power grid) and help produce energy during "peak usage" hours. Any additional energy they need could still be purchased from the local power grid (at cheap prices, since the surplus clean energy would drive prices down). Also any energy produced by these large solar panels on weekends (when the company is not working) would be pumped directly back into the power grid (to give the company a "credit" for the energy they produce). Slowly as a country we can eliminate our dependence on foreign oil, and foreign energy, and fossil fuels.

The sun and water can easily give us all the energy we could ever want or need. The ocean is pretty big, and 80% of this planet is nothing but water. It wouldn't be hard to harness that energy, and split that water into Hydrogen and Oxygen. The byproduct (Oxygen) and even after the fuel is "burnt" the end product is just water vapor (which goes up into the sky, and causes clean rain).

So as it rains, we gather up the rain water, and use it to fuel our cars, and heat & power our homes. Hopefully the engineers are reading this, and listening. It's not rocket science my friends. Trust me, if we can put a man on the moon, we can eliminate our dependence on foreign oil, and also stimulate the American economy. If the government steps in, and mandates it... then its' guaranteed income for ALL Americans.

The engineering and manufacturing will create millions of jobs here in America (since every home in America would need to be "upgraded" by a set date, such as January 2015). So manufacturing companies here in America would need to begin producing the panels (and products) in mass production scale.

The layed off trades workers (due to the housing bubble burst) will now be installing solar panels, and rewiring homes (installing a main electrical backfeed that will tie into the main electrical panel in a home, and upconvert the 12 vole solar/battery power back into 110/120VAC current). Then the electric company will have to start replacing the old analog meters (that spin) with newer digital meters (that can read electricity used, as well as electrical current that is "backfed" into the power grid) so homeowners get credit for the surplus energy produced.

It's not hard to do. Quite simple really. The number of jobs that would be created would be in the hundreds of millions (as you look at how many homes in America would need to be upgraded to "energy free" homes).

Ok, way off topic, but go vote tomorrow in your local election, and hopefully someday after the "regime change" our new president will listen, and do what's right, and do what's best for America.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

etung — Mon, 03 Nov 2008 17:21:33 GMT

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.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Mon, 03 Nov 2008 14:14:14 GMT

+*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.*+

That's about the most INCORRECT answer I've ever seen. If it had nothing to do with Fusion "per-se" (as you like to claim) then I guess Etung's very simple solution of deleting two files, and restarting Fusion wouldn't automatically fix the problem now would it?

So just give Etung credit for the correct answer, humble yourself a bit and accept that you were wrong (it happens to all of us) and just accept the fact that Etung's answer was the most correct (and the SIMPLEST answer that works is the one that is correct).

Suggesting that I check Microsoft KB's, or rebuild my system wasn't even a real answer. That was just someone trying to get out of doing any work (and trying to pawn a user off on someone else). Hoping that I would waste time messing with KB's, or completely rebuilding a system that didn't need to be rebuilt (or researching KB's that didn't need to be researched).

Something as simple as deleting two files, and restarting fusion was by far the easiest and most simple solution (and best of all it worked!). Etung, thank-you for the solution.

Woodz, don't take it personally. We strike out sometimes, it happens. It happens to the best of us. I've been stumped before, and someone has come along and give a better answer (and one that works) and it happens to the best of us. So don't take it personally. Not a big deal. I was just giving Etung the credit that was due because he posted the correct answer. No reason to get upset about it (or take it personally).

This was no personal attack on you, I was just giving Etung the credit for a correct answer (and I gave him a pat on the back for coming up with the correct answer, and I just posted a simple reminder to reinstall VMWare tools, just in case anyone reads/finds this article in the future). No reason to turn this into a selfish rant, just because Etung posted a correct answer. Thanks mate for the solution!

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Mon, 03 Nov 2008 13:49:51 GMT

Well, I would assume that if it was a problem that it would have been FIXED, and addressed (and people wouldn't need to come to the forums to find out/figure out why Fusion 2.0 is suddenly crashing, and won't boot up).

Sure, there are hundreds of posts describing various blue screen of death issues with Fusion 1.1, 1.2, and various different versions, and all seem to be unrelated to my post (various idesys files, sound driver issues, etc.).

I've seen hundreds of different solutions, to include your idea of expanding cab files, and hunting/searching Microsoft KB pages (to search for an answer), and yet Etung posted something extremely simple (that I haven't read or found anywhere else), and I was just surprised that something so simple worked.

If it was "your idea" then why did you suggest that I go check out the Microsoft KB website first, and begin expanding CAB files? When something as simple as this would solve the problem?

No disrespect, but I've found that sometimes the VMWare staff seems clueless as to why their software is crashing, or not working properly. I read about 30-40 different posts, on various blue screen of death issues, and every single one of them had several posts each (with many solutions that didn't work, as I could read from the various responses), but all I did was follow up with a quick response letting anyone else know that this was a quick and easy fix, and that etung's suggestion did work.

It was much easier than spending hours and hours hunting down KB articles and in the end after wasting hours and hours of time, I would have realized that none of those would have resolved the problem (and would have just been wasted effort).

It seems to be related only to Fusion, so it seems to be a VMWare issues (a bug that still hasn't been fixed).

+It's not like this is some big well kept secret... +

Well I would assume that if VMWare knew about it that they would have addressed the issue and FIXED IT (not just ignored the bugs, and left them). If VMWare Fusion is causing blue screens of death, then I would think that they would take the time to actually FIX the problem (instead of leaving it up to the users to hunt and poke through the forums and various other third-party websites to try to figure out why their software is crashing or why driver's aren't loading properly, or what all the other problems/bug fixes are.

I've never had to visit a vendor's website, and hunt the forums for 3-4 major "bugs" in less than a month. So instead of complaining that I didn't do a "good enough" job reading your mind (and it shouldn't be my job to hunt through hundreds of pages of various blue screen of death problems, system crashes, stop errors, and KB articles, just to figure out that VMWare has some major bugs that they choose to ignore and I wouldn't be in this forum if these problems weren't happening).

I've never had to join a forum before, just to hunt for solutions to try and figure out why a program isn't working properly, is crashing, or is causing blue screen of deaths. If I do a simple search there was nothing I could find concerning Windows Vista x64, and Fusion 2.0 errors.

So get off your high horse, and stop whining just because etung made a simple suggestion (that worked). That's all I asked for was a simple solution, to get this fixed. Etung made a simple suggestion, and I tried it, and I was merely responding that it worked (in case anyone else every runs into this same problem with Vista and Fusion 2.0).

I would think that you would focus more energy on FIXING the "known bugs" instead of just leaving the bugs in the program (as you've admitted that they've been around for quite some time I guess). Yes, I did see hundreds of blue screen of death posts, but it's hard to say what's related and what's not related. I'm not interested in spending thousands of hours reading each and every post in this forum, and trying thousands of solutions that don't work (every post I've read has had a different solution) and this was the first time I've seen a post as simple (and as concise) as etung's suggestion.

That's all I asked for was a SIMPLE and CONCISE answer. If you can't read a question, and give a simple and concise response, instead of yelling at users and telling them they should have sifted through the thousands and thousands of pages looking for an answer on their own, then what are you here for?

If you're not interested in helping, then just ignore my post. Plain and simple. If you can't give me a simple solution, and your answer is to expand cab files, or go check Microsoft's website, well neither of those were very helpful solutions. So just ignore my posts.

All I did was post a simple response that etung's solution worked, and it was a quick and easy fix.

If you can find an exact duplicate post to this one, then just post the link. I've searched hundreds of posts on various problems with the VMWare software, and tons of blue screen of death crashes (due to sound drivers, or some ide files, or various other reasons) but all of which were Windows XP related, or Fusion 1.1 related.

I didn't find a SINGLE POST about this stop error in Windows Vista, in Fusion 2.0, that was possibly related to a recent Windows Update. So quit whining like a baby, just because I gave Etung the simple "Thank-you" and "Correct Answer" to the question.

So just because your post about telling me to go find my own solution to the problem on the Microsoft Website wasn't very helpful, so next time just ignore my post. I'm glad I ignored yours, and didn't waste a whole lot of time searching KB articles (yes I did look at a few) but realized that it wasn't a Microsoft issue, because Vista was booting up just fine in the native partition (it was only a Fusion problem).

So if it's a Fusion problem, why would I continue to waste hundreds of hours sifting through all these thousands of pages when all I needed was a simple one or two line answer?

If you seem to be so smart, then why didn't you just suggest doing it in the first place? Why give me 3 or 4 wrong answers, and then get mad just because I give Etung the points for a correct answer?

If you saw that Etung posted the correct answer (and you posted 2 wrong answers AFTER his post) then why would you even make a post? You posts certainly weren't helpful or useful, so quit crying about it.

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

Well then why didn't you suggest it if it was such a simple answer, and why did you go on rambling about suggesting that I go check Microsoft's KB articles instead (after Etung already posted a correct response). So apparently you didn't know the solution to the problem (or the correct response) because if you did then you wouldn't have posted a suggesting that completely contradicts what Etung suggested.

So just because I post a quick response that Etung's solution worked for me, and resolved the particular problem that I was having, why are you getting so bent out of shape and crying like a little baby just because I didn't waste my time with your ideas, and if you seemed to "already know" that Etung has posted the correct response (because you're a genius) then why are you complaining? Why would you even post AFTER Etung already posted the correct answer?

If there are hundreds of posts that all have the correct solution (as you so claim), because I didn't find a single one... then why didn't you just post a link (refering to a post with the correct solution). I haven't found a single post that has had this exact same problem on Vista Ultimate in Fusion 2.0.

As you've even said yourself, hundreds of things can cause a stop error. So why would you make an ignorant assumption that all of these hundreds of posts on one particular stop error are ALL EXACTLY THE SAME (or even related)? Why would there be hundreds of posts then? I guess everyone is a moron except for you my genius friend. So instead of crying that I'm wasting your time, trying to fix your broken software, why don't you spend more time FIXING THE BUGS in your software so I don't have to BOTHER the developers trying to find solutions to all these bugs/problems/blue screen of death, etc.

It certainly isn't a physical hardware problem, so it's something to do directly with VMWare Fusion. So instead of whining that I don't know the "ins and outs" of your software (like you do) just because I'm not a VMWare employee, or a VMWare developer, and I don't just happen to know thousands of solutions to various KNOWN BUGS and KNOWN PROBLEMS off the top of my head, all I did was post a simple question, and all I ask for was a simple answer.

It's not rocket science. Why waste my time with your silly nonsense, if you're not helping? If you are so smart and already "knew" the answer to the problem (as you so claim), then why not just post the correct answer, and then I would gladly give you credit for the post.

As far as I can tell, you have never posted a correct answer to the specific question I have asked, so just because Etung did, there is no reason to get your panties in a bunch or start whining about it.

Just because you have a shiny gold trophy next to your name (and Etung doesn't) that doesn't mean Etung's solution isn't correct. It was a simple solution, I tried it, and it worked perfectly. So quit whining.

Stop acting like a little child. This isn't some big "competition" to see who can be right or wrong.

Etung posted a correct answer, and all I did was post a response (and awarded him the credit for the correct answer). It worked, and it solved the problem. Not a big deal. Quit acting like a baby, just because someone else answered my question, and gave a simple (and correct) answer.

If you already "knew" that Etung's response was correct, then why did you post? Why did you post twice? I read your posts, but I don't think searching the Microsoft KB's was the correct answer, and I do think Etungs response WAS the correct answer.

So if you knew that was the correct answer, why are you suggesting to expand CAB files, or suggesting that I go search Microsoft's website, if you "knew" the correct answer all along? (Mr Smart Guy).

Post a correct answer, I award you the points. It's pretty simple. Etung posted the correct answer, I posted a simple reply (letting him and others know that the solution Etung suggested did work) and I awarded him the "Correct Answer" points.

No reason to get bent out of shape about it. This isn't a competition. Someone other than yourself can be right once in a while ya know. Apparently you don't know all the right answers, or you would have posted it.

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

Wow, you are a brain. Only a real genius would have figured that out. You contradict yourself even in your own posts.

First you tell me it was an "easy solution" and there are 80-100 posts that all have the same answer (but doing a simple search yielded not a single one). Then you tell me that I got "lucky" because "not all STOP 7B BSOD's are caused by the same thing.

Wow, you're a real genius brainiac. So why do you think I didn't just follow the instructions on ALL 100 other posts (especially since none of them were related to the specific problem I was having) and wasted weeks and weeks of my time playing stupid games, and trying things that don't work, that are completely unrelated to the problem that I'm having, and unzipping CAB files, and over writing system files (just for the heck of it) because someone else had a blue screen of death on a completely different operating system, running a completely different version of Fusion, and a completely different issue with sound drivers. Really doesn't make much sense, but after your ignorant posts, I guess that's your hairbrain explanation.

In the future, just ignore my posts Woody. Thank-you. I ignore yours (as most of the solutions you have suggested haven't worked for me). So it's just habit to read what you post, and ignore it.

So far Etung has posted some very useful and valuable information (and has solved my problems in a very clear and consise manner) and that's all I'm asking for. So if he posts an answer, and it works for me, and it solves my problem, then so be it.

I'll take a minute to at least thank him for his post, let him know that his solution did fix the problem, and I'll take the time to click the "Correct Answer" button.

Just because his solution worked, and yours didn't... doesn't mean that it's the end of the world for you. No reason to be so "competitive" and get upset just because Etung's solution worked (and yours didn't), that doesn't mean you have never answered a question correctly before. I see you have a gold trophy next to your name, so apparently you've answered your fair share of correct posts or whatever, but let Etung have his day. Ok, so Etung gave a simple and easy solution, so just let him have his day.

I gave the man credit (where credit is due) and just stop complaining that he gave me the correct answer. Apparently you didn't know the correct answer, or you would have suggested it earlier (right away), and wouldn't have wasted my time.

Etung got me back up and running fairly quickly, and that my friend is what is MOST important. I didn't have to waste several days hunting and poking, and Etung posted a solution that worked for my particular problem. Just like you said, it won't work for every single blue screen of death (Duh...), but if someone did a Microsoft Update 2-3 days ago, and just happened to have the EXACT SAME PROBLEM (100% exactly the same situation, and same exact problem) then yes, it might work for them as well. It seems to be a bug, and I was just making this bug known (and looking for a quick solution).

You didn't seem to know the answer, or have a quick solution (or quick and easy fix) but you did offer many ideas (and none of them worked). So don't be upset that Etung's solution worked (and was simple and easy) and it got me back up and running within seconds.

I'd venture to say

Well you don't need to "venture to say" much of anything. Your answer was wrong, Etung's was correct. That's all you have to "venture to say". Enough said.

That doesn't mean that you are always wrong and never right, it just means on this particular post, with this particular problem... your solutions didn't work, and weren't useful to me. Etung posted the correct answer (that worked). So I gave him credit for the correct answer. Not a big deal. No reason to cry about it.

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

I didn't ask for the hardest/longest solution possible, and if you really truely want to actually HELP someone, why not try the EASY and SIMPLE things first (especially if you supposedly "knew" the solution but just chose not to post the correct answer, because you were TOO SMART to post the correct answer, so you chose to post 3 or 4 wrong answers just to throw me off, right?) Your logic makes no sense at all.

If you didn't know the correct answer, then how should I have known the correct answer? Quit whining quit complaining. Etung gave a very simple solution, delete two files, and then restart Fusion. It doesn't get much simpler than that, and it worked.

Just because I didn't spend hours (or days) going back and forth with you doing some stupid crazy "low level" diagnostics and spending hours on the phone with Microsoft Technical Support (on something completetly unrelated to them) and then wasting hundreds (or even thousands of dollars) in support costs, then finally Microsoft would just tell me that it's VMWare related, and try contacting VMWare (which I did). So yes it was a VMWare Fusion problem, and yes Etung's incredibly simple solution fixed the problem. I have a hunch that it would probably fix 85% of the problems, but you would rather spend hours/days/weeks going back and forth with users (wasting their time) instead of just giving them a clear, and simple (and CORRECT) answer.

I don't need 10 or 12 posts/dialogs just to get a correct solution. If I post a question, just post an answer. It's that simple. If it's correct, and it works, then I'm gone. I'll respond with a "thank-you! It worked!" and then I'm gone.

Unfortunately you can't seem to respond with a clear, or concise, or a simple, or a correct soluton. Your answers all seem to be long complex time consuming things (and none of them worked), so I just finally tried the quick and simple (and easy) thing that Etung suggested, and it worked. So Etung gets credit for the correct answer, and he's my hero for today.

So get over it, quick crying, and just work on giving correct answers (and be clear and concise, with a detailed step by step explanation if the user asks for it).

Just remember that not all of us are Mac OS X (or Windows) pro's. (Or VMWare God's). If we were, then we wouldn't be in this forum asking for help. We're just people that need help, and every user in this forum has a different level of knowledge (and experience with VMWare).

Since I'm a VMWare novice, and I've owned a Mac for less than a month now, and I'm still pretty clueless when it comes to a Mac (and VMWare Fusion), I may need a bit more "hand holding" than you are accustomed to giving. So I suggest you go find some professionals to help, and leave the novices like me alone, because you don't seem to have the patience (or skill) to help a novice.

+* it will be less painful then having to rebuild from scratch.
*+

I hate to say this, but a VMWare novice like me, shouldn't know that your ideas have been incredibly dumb, and if Vista is working properly (natively) then there would be absolutely no reason at all to "rebuild from scratch" and if you had half a brain, you would know this.

You'd also know that if Windows Vista was functioning properly and loading up correctly (outside of VMWare Fusion) that it would be a Fusion/VMWare problem. (Basic troubleshooting 101). I guess you must have missed that class.

No reason to start banging your head against the keyboard, it's not that hard to figure out that all it would take is something as simple as a uninstall/reinstall to fix the problem (even I knew that, and I'm a complete novice). So it's ashame that such a "genius" as yourself was busy conjuring up a plan on how to rebuild a system, or expand CAB files, or do all the craziest things I've ever heard, when all it takes is something extremely simple (and easy) like what Etung suggested.

That's all I asked for, a simple way to uninstall/reinstall Fusion. Etung told me how, and that's all I needed, and it worked for me. Thank-you. If you can't give a simple answer to a simple question, (or a correct answer) then just don't respond. Etung did a fine job, and I was just giving him the credit for the correct answer. That's all. Nothing wrong with me singing Etung a little praise for giving me a correct answer, and getting me back up and running as quickly as possible (without wasting anymore of my time).

So just pat Etung on the back, and say "Good answer mate... wish I would have thought of that..." and let it all go.

Sure, you win some, you lose some. You don't need to always be 100% correct, and it's life... sometimes someone suggest something that is much easier (and almost seems TOO SIMPLE, but it works perfectly). So don't get bitter or jealous. I'm sure you'll get a correct answer someday, or get an answer to one of my posts that works, and when you do... I'll give you the proper credit for the correct answer, and I'll also give you the points for the correct answer. So just because you were wrong today, and Etung was correct, no reason to get upset (or jealous) over it.

I just thank him for getting me up and running as fast as humanly possible (and not wasting anymore of my time in the process). I don't have time to be wasting/spending reading KB articles when I should be working. So if Fusion is broken, that means I'm losing money (because I can't work). So your concern should be HOW to get me back up and running (as quickly as possible) without wasting my time asking me to hunt down CAB files, or KB articles, or send smoke signals to the man on the moon for answers.

If you know the answer thand post it, if not then quit complaining that Etung did know the answer (or at least he thought he did, because he posted a quick response to my last response) and his solution did seem work etremely well). No reason to get mad that his answer was much quicker, easier, and it WORKED (and your answers didn't).

It's all about posting a CORRECT answer. I'd rather see ONE simple correct answer, then 5 or 10 wrong answers (or a complex talk about expanding CAB files) which I would have saved for maybe a "stage 3" or "stage 4" troubleshooting (after I suggested something simple like deleting the two files and restarting Fusion). If that didn't work, then (and ONLY then) move forward with more complex testing/troubleshooting.

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

Well apparently it wasn't time to read the KB's or rebuild the system, and just something as simple as deleting two files and restarting Fusion fixed the problem (and I'm thankful for Etung's solution, or I'd be listening to your hairbrain idea of rebuilding a system that doesn't need to be rebuilt). So lucky for me, Etung came out with a better/faster/more correct answer.

In the future you may want to try the easiest and simple stuff first, and try to make things as easy as possible on the users/consumers of your products. Start with basic trouble shooting, and give a few quick things that a user can try first, and then (and ONLY THEN) if all else fails, then you suggest KB articles (if you are clueless and don't know the correct answer) or suggest rebuilding a system (again because you are clueless and don't know how to fix the problem).

So just because Etung knew the CORRECT answer (the one that WORKED), no reason to get upset over it. (a 10 second solution that Etung gave was by far the quickest and easiest and on top of that it was the CORRECT answer, because it worked!)

Thanks again...

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

WoodyZ — Fri, 31 Oct 2008 14:29:07 GMT

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.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Fri, 31 Oct 2008 07:14:43 GMT

Etung,

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.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Fri, 31 Oct 2008 07:00:00 GMT

Etung,

I deleted the files just as you said. Then started fusion, and it said something about "preparing the something or other for something" (I need a slower computer, so I can read this stuff). With 32GB of RAM, and 8 cores this Mac Pro does everything so quickly. Doesn't even give me time to read the screen.

Well it just booted up, and the Vista login is right in front of me.

You are the man!!

Big Kudos!

Well, for future note (in case anyone has Vista x64 Ultimate) and is running Fusion 2.0, and experiencing the same blue screen of death... all I did was delete the data in the boot camp folder, and delete the "naos" file (as etung said) and it worked for me! Yippie! Fusion works again!

I love you guys! (I'm still upset with Microsoft, for whatever in the heck they did) but I'm glad that it was a quick and painless fix. Thank-you guys again! Etung, you are my hero.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Fri, 31 Oct 2008 06:51:11 GMT

+*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/)*+

Etung, just to be a little bit more specifc. I went to the /Library/Application Support/VMware Fusion/Virtual Machines/ directory, and inside there are two folders. One folder is labeled "Boot Camp" and the second folder is labeled "Helper". Is it ok to delete both folders? Or just the files inside each folder?

I believe in the Boot Camp folder there is a folder called "%2Fdev%2Fdisk1" and in the other Helper folder there was a file called "naos-1.0.vmwarevm". So it's safe to just delete that "%2Fdev%2Fdisk1" folder completely? and it's safe to delete the "naos" file?

Ok, I will do both, and restart Fusion, and hopefully that will fix it. Thank-you! I'll let you know what happens.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

WoodyZ — Thu, 30 Oct 2008 20:14:12 GMT

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.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

etung — Thu, 30 Oct 2008 19:28:00 GMT

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.

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Thu, 30 Oct 2008 19:11:29 GMT

Etung,

Thanks for the quick response. I've clicked on the link you mentioned (about the Frequently Asked Questions about Guest OSes), and there is a myriad of information there. I did some hunting and poking, but cant seem to find ANYTHING related specifically to the problem I'm having.

Could you cut and paste (specifically) what you want me to do or try?

I've found absolutely nothing related to the error on the link you mentioned. I did find two other pages mentioning BSOD's (Blue Screen of Death's) after Windows Updates, but both were on Windows XP.

Located here:

http://communities.vmware.com/thread/173234?tstart=0&start=15

and here:

http://communities.vmware.com/message/931510#931510

One was related to a sound driver, and the other was some other unrelated issue. I'll need to look more into this (and try to find the exact problem, something a bit more detailed) because clearly neither of these are what is causing this blue screen of death. Plus my BSOD is on Vista, and not XP.

So I'm not sure that the other posts are even remotely related. I do believe it is definitely a "hardware driver" or something related problem (caused by a recent Microsoft update), but I'm not exactly sure how to get you the correct detailed information that you need to isolate the problem (and give me the detailed instructions that I need to fix it). Or even what files need to be fixed or replaced.

I'm in a crunch right now (and yes this is a work/development machine), so I'm under the gun right now, and won't be able to get you more detailed information till later tonight when I'm off work. Boss expects me to work, and not fix problems with the computer (even though these problems are preventing me from doing my work).

So when I get home, I'll do more research, and hopefully give you something a little more detailed so you can try and help me further. <<br />The attached file, Boot_Camp_partition_Virtual_Machine_BSOD_STOP_0x7B_Fix.zip contains three files:

ReadMe1st.txt
Expand_i8042prt.sys_and_intelide.sys_Drivers.cmd
Boot_Camp_Virtual_Machine_i8042prt.sys_and_intelide.sys_Driver_Entries.reg

+*The files contained in this .zip archive are to be executed while
running Windows XP under Boot Camp with the intension of then running
the Boot Camp partition as a Virtual Machine.*+

The .cmd Script was written and tested for Windows XP Only!

I saw a post by WoodyZ that mentioned the following in a post about the 0x0000007b error but again, everything seems to be Windows XP Only. Nothing Vista. So looks like I'm still in "new territory" here (stupid Vista Ultimate x64), but hopefully we can get this figured out, and keep this post as an "archive" so if anyone else stumbles across the same error, or similar problem at least it's documented and hopefully we can find a solution/fix soon.

I'll try to get you more detailed information later tonight. Please let me know where I can find the log files, or anything else that you may need to help give you more detailed information. I know when it tries to boot up in safe mode it gets to a particular file and then blue screen of death's again. Can't remember the exact name of the file, I'll have to go back and boot into it again, and jot down that file name, but hopefully that will help in the search for an answer.

I've googled, and hunted around the forums, but again I can't find ANYTHING that seems to be related to this error/problem on Vista. So let me get back to work (before boss sends me packing), and I'll be back a bit later tonight with more detailed information. Please just send me a short reply (no links to more FAQ's please) just give me a one or two line answer with what files (log files) or whatever I can try to get for you, or any information that either you (or WoodyZ) may need to try and figure out what is going on with my machine, and how to fix it.

Thanks guys,

Re: Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

etung — Thu, 30 Oct 2008 15:32:15 GMT

Frequently Asked Questions about Guest OSes: Boot Camp virtual machine has a Blue Screen of Death with error code 0x0000007b

Blue Screen of Death with Vista Ultimate x64 in Fusion 2.0

nextech — Thu, 30 Oct 2008 06:09:16 GMT

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.