Hello . Firstly some background info:
BSOD occurs on virtual machine (VMware 7) running windows 32 bit.
Never attempted windows update (trying now)
BSOD has occured twice, both dump files & bsodviewer files has been uploaded. SF diagnostic files also uploaded in same zip
thank you for your kind attention
Hi nuker22110.
It appears to be a display related issue.
And the display driver is too old.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 0, 82872f95} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+51 ) Followup: MachineOwner ---------
This display driver is a part of VMWare tools. You need to update it.Code:0: kd> lmvm vm3dmp start end module name 9b5c3000 9b5da000 vm3dmp (deferred) Image path: \SystemRoot\system32\DRIVERS\vm3dmp.sys Image name: vm3dmp.sys Timestamp: Sat Jul 30 06:05:38 2011 (4E3351DA) CheckSum: 0001E5A3 ImageSize: 00017000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Let us know how it runs after the update.
hello and thank you for your reply.
I have updated VMware and vmware tools to the latest version (10.1). However the crash till occurs.
Note that i have edited the registry of the virtual machine in order to stop the lag (editing the driverdesc string and changing it to a video card name). could this be causing the crash? im told its not possible.
steps taken so far:
updated vmware 7 to vmware 10.1
made new copy of guest machine with windows 7 ultimate
installed directx
applied all windows updates
updated to latest gpu drivers on host machine
i have attached the latest crash files. Please advise on what i should do, its really frustrating.
edit: i just looked at the files, and it seems like the cause for the crash is different now?! blast it
A lag of three weeks cuts the continuity of thought.
Anyway, today's BSOD is display related. The display driver is an element of VMWare tools.
So the possibility is mere that it is the main reason behind the BSOD, though it is prima facie.Code:Driver Name: vm3dum64.dll,vm3dum,vm3dgl64.dll,vm3dgl
As a test, downgrade teh display driver of the host. Install the http://www.nvidia.com/object/win8-wi...river.htmlonly.
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).- Now follow Drivers - Clean Left over Files after Uninstalling
- Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
Let us know the results.
thank you for the swift reply
i have completed your instructions. now awaiting bsod again.
also, editing the registry causes vmware tools to not start, could that be the problem?
adding
monitor_control.restrict_backdoor = "true"
to the vmx config file causes vmware tools not to start as explainedSince VMware Tools accesses the backdoor port from ring 3, this setting (which only allows the backdoor port to be accessed from ring 0) effectively disables VMware Tools.
so far have not crash again. what was the significance of the older driver? will update if crash occurs again
here you go, kind sir. another crash occured
perhaps i should downgrade back to vmware 7, where it did not lag and i could enable vmware tools.
The same BSOD.
I think you should not have edited that registry. At least you should have made a registry backup before editing it.
I have decided to give up trying to find a fix for this issue. my idea now is to make the vmware to restart and auto run the applications for maximum uptime. however the bsod does not auto restart even with the box auto restart checked. is there another way to force restart on bsod?
Quote