BSOD Booting Ubuntu 14.04-2 under vmware player 7

[matthewk]

This is not the first time this has happened. I had the same issue with vmplayer 6 and an older version of Ubuntu, but I did not care about that VM and just moved on to the latest version. Now the same issue is popping up. Right after Ubuntu starts to book under the VMware player, Win 7 bluescreens. I believe the error code is 0x000000D2 on the bluescreen.

The zip with the dump's etc is attached. Thank you for any ideas you might have.

 

[Arc]

It is a stop 0xD1 BSOD, which is typically a driver caused issue. Apparently we are seeing two drivers as failing, one is the touchpad driver and the other is the storage controller driver.

Update the touchpad driver from Drivers ? Synaptics.

Get rid of intel rapid storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.

But that may not be enough. I am suspecting some HP drive encryption programs are also playing a role there in the issue, though I dont have anything finite to blame it. For now, you do one thing more. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now see how it goes. Let us know.

____________________________________________________

BugCheck D1, {0, 2, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

fffff800`00b9a7a8  fffff880`05071249Unable to load image \SystemRoot\system32\DRIVERS\SynTP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
 SynTP+0x36249

fffff800`00b9a868  fffff880`0109b9d5Unable to load image \SystemRoot\system32\DRIVERS\iaStor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStor.sys
 iaStor+0x5c9d5

 

[matthewk]

Thank you for your reply! As soon as I have a few minutes I will go and have at it. The only odd thing I should mention is that the other night I learned how to mount a virtual disk as a second disk on a second virtual machine and I was able to install another instance of the exact same Ubuntu OS, under the exact same VMware player and that installed and worked fine for helping me get my files back. I also have been using a WinXP VM right along in the same VM player. Now I know at some time in the future, that the "new" Ubuntu VM will also start bluescreening the notebook upon startup.

As an aside, HP has been telling me that there is a new touchpad driver for some time but it consistently fails to install it. Ditto with the video driver. I can also get rid of the rapid storage, and start up stuff.

I am really intereged by how this can work just fine for a while and than start BSODing as soon as the Linux install starts to boot. If you are used to Ubuntu, it crashes right after grun starts the OS. I think I get the first line on the top of the screen about the cache and thats all she wrote.

Thank you again for your time!!!! I will get back to you.

 

[Arc]

Now I know at some time in the future, that the "new" Ubuntu VM will also start bluescreening the notebook upon startup.

No, probably it will not. Let us wait and see.

I am really intereged by how this can work just fine for a while and than start BSODing as soon as the Linux install starts to boot. If you are used to Ubuntu, it crashes right after grun starts the OS. I think I get the first line on the top of the screen about the cache and thats all she wrote.

Thank you again for your time!!!! I will get back to you.

I used to use Ubuntu, as physical machine and as virtual machine. When a virtual OS starts booting (GRUB in this case), it starts some services there like virtual disc, virtual network, etc; and it integrates with the hardware components like touchpad under our discussion. All those things are integrated components of the VMWare software. So if there is a scope to upgrade the version of VMWare, please try it.

As an aside, HP has been telling me that there is a new touchpad driver for some time but it consistently fails to install it. Ditto with the video driver. I can also get rid of the rapid storage, and start up stuff.

Now thats not good. Try this method? http://www.sevenforums.com/tutorials/97061-driver-install-device-manager.html
It may be helpful to install the drivers.

 

[matthewk]

Howdy!

This turned out to be less of a pain than I thought. I had not tried the HP update program in a while. That was failing, but this time I went through and got each update one at a time and found where it put the SP's on the disk and saved them. The updater installs the SP's in quiet mode so if they failed I could re-install them interactively. Anyway, a new video driver, a new touchpad driver, and a new version of the BIOS, and poof, it still bluescreened on that one VM...

Next I took out the Intel rapid storage program, and that did the trick. The VM started up with no issues. Very odd.

BTW, I had been around the block with this a few times before and there is no question in my mind that the "new" vm that I set up to rescue the "old" one would have started doing the same thing at some point in time. The "old" one lasted about a month, and through assorted windows updates and reboots etc. The one before that did about the same. Hopefully the root cause is now resolved.

Thank you very very much for your help.

 

[Arc]

Sounds nice. At least till now.

Now give it a time, as long as you think you should observe it. Report us for any further BSOD.