Windows 7: BSOD playing wow/gw2 - dxgmms1

davidfitz · 06 Sep 2012

Hello all,

I've been getting these dxgmms1 BSOD's recently and, all though they appear to be common, I've not seen a permanent fix anywhere.

The latest minidump is below, any help would be great.

Quote:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff880055ace6e

Debugging Details:
------------------

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800032e4769 to fffff800032e51c0

STACK_TEXT:
fffff800`00ba4d28 fffff800`032e4769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`032e2c32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`055ace6e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
dffff880`0428f8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x1a2

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2
fffff880`055ace6e 807c245000 cmp byte ptr [rsp+50h],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1

FAILURE_BUCKET_ID: X64_0x7f_8_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

BUCKET_ID: X64_0x7f_8_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

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

Maguscreed · 06 Sep 2012

It's a basic direct x fault.
Install the latest dx redistributable.
Then WIPE and reinstall graphics drivers.
That's really about the best you can do.
I usually use this for wiping display drivers.
http://phyxion.net/Driver-Sweeper/Dr...Version-3-2-0/

davidfitz · 06 Sep 2012

Thanks for the reply. Since posting I've crashed again. I think its the same error

Quote:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff880055ace6e

Debugging Details:
------------------

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800032e4769 to fffff800032e51c0

STACK_TEXT:
fffff800`00ba4d28 fffff800`032e4769 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`032e2c32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`055ace6e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
dffff880`0428f8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x1a2

STACK_COMMAND: kb

FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2
fffff880`055ace6e 807c245000 cmp byte ptr [rsp+50h],0

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1

FAILURE_BUCKET_ID: X64_0x7f_8_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

BUCKET_ID: X64_0x7f_8_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+1a2

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

davidfitz · 24 Sep 2012

I'm still getting crashes every now and then so I decided to use verifier to test my drivers. Enabling verifier resulted in the PC being unable to boot as that, it self would cause a Blue Screen.

I have three dumps which (i think) are the dumps from startup. Two are dxgmms and the last (below) is a HIDCLASS

Quote:

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff88006ca1710, fffff9802e7a2cf0, 0}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023b, The caller has changed the status field of an IRP it does not understand.
Arg2: fffff88006ca1710, The address in the driver's code where the error was detected.
Arg3: fffff9802e7a2cf0, IRP address.
Arg4: 0000000000000000

Debugging Details:
------------------

BUGCHECK_STR: 0xc9_23b

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23b

FAULTING_IP:
HIDCLASS!HidpMajorHandler+0
fffff880`06ca1710 48895c2410 mov qword ptr [rsp+10h],rbx

FOLLOWUP_IP:
HIDCLASS!HidpMajorHandler+0
fffff880`06ca1710 48895c2410 mov qword ptr [rsp+10h],rbx

IRP_ADDRESS: fffff9802e7a2cf0

DEVICE_OBJECT: fffffa8006fa99a0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: System

CURRENT_IRQL: 2

LOCK_ADDRESS: fffff800034c9b80 -- (!locks fffff800034c9b80)

Resource @ nt!PiEngineLock (0xfffff800034c9b80) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff800034c9b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff800037543dc to fffff800032ce1c0

STACK_TEXT:
fffff880`033b60e8 fffff800`037543dc : 00000000`000000c9 00000000`0000023b fffff880`06ca1710 fffff980`2e7a2cf0 : nt!KeBugCheckEx
fffff880`033b60f0 fffff800`0375e47a : fffff800`037529f0 fffff880`06ca1710 fffff980`2e7a2cf0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033b6130 fffff800`0375f483 : 00000000`0000023b 00000000`c0000010 fffff980`2e7a2cf0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`033b6180 fffff800`0375fb42 : fffff980`2e7a2f28 fffff880`06ca1710 00000000`00000000 00000000`00000000 : nt!VfErrorReport1+0x63
fffff880`033b6220 fffff800`03754071 : fffffa80`06fea330 00000000`00000001 00000000`00000000 fffff980`2e7a2f28 : nt!ViGenericVerifyIrpStackUpward+0x62
fffff880`033b6250 fffff800`03760b2d : fffffa80`07018a80 fffffa80`06fea010 fffff980`2e7a2cf0 fffff980`2e7a2cf0 : nt!VfMajorVerifyIrpStackUpward+0x91
fffff880`033b6290 fffff800`0377250d : fffff980`2e7a2f28 fffff880`033b6480 00000000`c0000010 fffff980`2e7a2f28 : nt!IovpCompleteRequest2+0xad
fffff880`033b6300 fffff800`032d1bc1 : fffff980`2e7a2f2b 00000000`00000000 00000000`000000ff fffff800`03755eea : nt!IovpLocalCompletionRoutine+0x9d
fffff880`033b6360 fffff800`0376a19f : fffff980`2e7a2cf0 fffff880`06cab400 fffffa80`06fa9a00 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`033b6450 fffff800`032b3116 : fffff880`00000013 fffff880`033b6578 fffff980`2e7a2f28 fffffa80`06fa9af0 : nt!IovCompleteRequest+0x19f
fffff880`033b6520 fffff880`06ca1a0f : 00000000`00000000 fffffa80`06fa9af0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`033b6550 fffff880`06ca17fb : 00000000`00000000 fffffa80`06fa9af0 fffff980`2e7a2cf0 fffff880`033b6600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`033b6590 fffff800`03770c16 : fffff980`00000002 fffff980`2e7a2cf0 00000000`00000002 fffff800`0376c37e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`033b6600 fffff800`0376fc42 : fffff980`2e7a2f70 00000000`00000002 fffffa80`070cf9e0 fffffa80`06108180 : nt!IovCallDriver+0x566
fffff880`033b6660 fffff800`03770c16 : fffff980`2e7a2cf0 00000000`00000002 fffffa80`070cf890 00000000`00000000 : nt!ViFilterDispatchPower+0x62
fffff880`033b6690 fffff800`0376fd58 : fffff980`2e7a2cf0 fffffa80`070cf890 00000000`00000000 fffffa80`07073d30 : nt!IovCallDriver+0x566
fffff880`033b66f0 fffff800`0376fe42 : fffffa80`071b7040 fffffa80`035e5210 fffffa80`071b7040 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`033b6760 fffff800`0375cfaf : fffffa80`070b6820 00000000`000007ff fffff800`034045b8 fffff800`03660b49 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`033b6800 fffff800`03377d52 : fffffa80`070b6820 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`033b6830 fffff800`036b512c : fffffa80`070b6820 fffffa80`035e5210 00000000`00000001 01535242`00000007 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`033b6860 fffff800`036b6d24 : fffffa80`070b6820 fffffa80`070b6820 fffffa80`035e5210 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`033b6950 fffff800`036b720c : fffff800`034c7500 00000000`00000000 00000000`00000001 fffff800`035335d4 : nt!PipProcessDevNodeTree+0x264
fffff880`033b6bc0 fffff800`033c7eb2 : 00000001`00000003 fffff800`0346b2d8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`033b6c10 fffff800`032d7841 : fffff800`033c7bb0 fffff800`035c0601 fffffa80`035ceb00 00000000`0000055a : nt!PnpDeviceActionWorker+0x302
fffff880`033b6cb0 fffff800`03564e6a : 00000000`00000000 fffffa80`035ceb50 00000000`00000080 fffffa80`035ab890 : nt!ExpWorkerThread+0x111
fffff880`033b6d40 fffff800`032beec6 : fffff880`031d5180 fffffa80`035ceb50 fffff880`031dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

SYMBOL_NAME: HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME: HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a665

FAILURE_BUCKET_ID: X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

BUCKET_ID: X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0

Followup: MachineOwner

Can anyone suggest the next step?

Arc · 24 Sep 2012

Post it following the Blue Screen of Death (BSOD) Posting Instructions . We are to check the dumps at our own.

davidfitz · 24 Sep 2012

See attached. Thank you.

Arc · 24 Sep 2012

Sorry to say, but it is Norton Internet Security that is causing the problem here.

Code:

fffff880`033b6c48  fffff880`02e179efUnable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_20.1.1.2\Definitions\IPSDefs\20120921.001\IDSvia64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
 IDSvia64+0x179ef

Had I been your place, I would have uninstalled NIS, and would have used Microsoft Security Essentials - Free Antivirus for Windows.

But, it is hard to recommend, as you paid for it.

In my best opinion, if the change is done, the situation will change.

davidfitz · 24 Sep 2012

Thanks Arc. I assume that NIS is causing the boot problems when verifier is enabled? NIS is not responsible for the dxgmms blue screens?

Arc · 24 Sep 2012

Quote: Originally Posted by davidfitz

Thanks Arc. I assume that NIS is causing the boot problems when verifier is enabled? NIS is not responsible for the dxgmms blue screens?

When verifier is enabled, then in most of the cases it crashes. Verifier itself crash the system. The dump I have checked (the latest one), I got it as NIS.

For a test, you uninstall NIS for the time being, say when we are troubleshooting, and then let us find the other dimensions of the problem one by one. When all will be done, We will employ NIS again and observe our system's stability, ok?

SO, uninstall it for the time being, and ley us know if there are more crashes with verifier on. If those are there, upload the dumps for us.

davidfitz · 25 Sep 2012

thanks Arc. I uninstalled NIS and set the verifier up again.

Another Blue screen on start up im afraid.

Thanks

Windows 7: BSOD playing wow/gw2 - dxgmms1

BSOD playing wow/gw2 - dxgmms1 problems?