DPC Watchdog viloation from Creative Sound cards

2

[27]

n00b
Joined
Apr 16, 2008
Messages
59
Soo I am at my wits end here. I have tried three different Creative sound cards on Windows 8.1 and they keep giving me intermittent DPC WatchDog Violation BSOD's!

Cards tried thus far:
X-Fi titanium
X-FI titanium HD
X-fi Recond 3D Fatality


It really is strange, I will be playing a game, and this generally only happens in games, and the sound will cut out. I can keep playing for a few minutes, but then the system comes to a complete crawl and sometimes I have to do a hard reset of the power.

When I pulled the cards (only 1 was in at any time), uninstalled the drivers, and proceeded to only use a USB headset (Astro A50) the problem went away.

the DPC watchdog violation tends to be a SSD issue, but from what I can tell its more related to the sound cards (as the problem went away after removing them).

Anyone have any ideas on how to proceed in finding a solution to this so I can use the Titanium HD?
 
Might wanna go check out memory dump after the BSOD. There are a few tools out there for analyzing it.
 
Silly question maybe, but have you tried the new X-Fi Titanium drivers that were just released earlier this year? I know the X-Fi Titanium series in Windows 8.x was a mess before that driver update, and one of the reasons I was sticking with 7.

Since the new drivers came out though, i've upgraded to 8.1 and have not had a single issue with my X-Fi Titanium HD.
 
[sarcasm]/Creative drivers causing problems? I've never heard of such a thing!/[end sarcasm].

Maybe try a Xonar?
 
Reviews show Xonar cards have just as many issues, in fact most of the updates are a few years old and do not appear to even include 8/8.1
 
StoleMyOwnCar said:
Might wanna go check out memory dump after the BSOD. There are a few tools out there for analyzing it.
Click to expand...

@gotnorice, I tried both the creative drivers and the PAX drivers, same issue on both.

@stolemyowncar, this is the dump file, it looks to be for ha20x22k.sys which is a creative driver.


Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff801`a5e13000 PsLoadedModuleList = 0xfffff801`a60dd2d0
Debug session time: Sun Apr 27 22:19:00.928 2014 (UTC - 5:00)
System Uptime: 0 days 0:16:28.625
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
.............Page 14b4ec not present in the dump file. Type ".hh dbgerr004" for details
..................................Page 19cd15 not present in the dump file. Type ".hh dbgerr004" for details
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.

Probably caused by : ha20x22k.sys ( ha20x22k+95ae5 )

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

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***


ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff801a5e13000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 52dc9374

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff801a5fa6b2c to fffff801a5f66fa0

STACK_TEXT:
ffffd001`5fda2c98 fffff801`a5fa6b2c : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
ffffd001`5fda2ca0 fffff801`a5ec7678 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!CcTestControl+0x328e0
ffffd001`5fda2d30 fffff801`a65a467f : ffffe000`e50e9008 fffff801`a5efd426 ffffe000`e10003b0 ffffe000`e50e9008 : nt!KeClockInterruptNotify+0x788
ffffd001`5fda2f40 fffff801`a5ee2363 : ffffe000`e1000300 fffff801`a5f1a73b ffff4c25`4cc50d51 00000000`00000000 : hal!HalPerformEndOfInterrupt+0x6f
ffffd001`5fda2f70 fffff801`a5f6842a : ffffe000`e1000300 00000000`00000000 00000000`00000000 ffffe000`e4c65110 : nt!RtlInterlockedSetClearRun+0x38f
ffffd001`5fda2fb0 fffff801`a5f6880f : 00000000`00000000 ffffe000`e41fce68 00000000`00000000 00001fa0`00000901 : nt!KeSynchronizeExecution+0x83a
ffffd000`24ef1b80 fffff800`e8151ae5 : ffffe000`e41fce68 00000000`002fb600 ffffe000`e3bcc010 ffffe000`e506d0c0 : nt!KeSynchronizeExecution+0xc1f
ffffd000`24ef1d10 fffff800`e813efba : ffffe000`e41fce68 ffffe000`e3bcc010 ffffd000`24ef1d68 00000000`00000018 : ha20x22k+0x95ae5
ffffd000`24ef1d40 fffff800`e8173d3a : ffffe000`e506d050 ffffe000`e5de8f40 ffffe000`00000000 ffffe000`00000000 : ha20x22k+0x82fba
ffffd000`24ef1d70 fffff800`e81715da : 00000000`00000000 00000000`00000000 ffffe000`e5de8f40 ffffe000`e506d050 : ha20x22k+0xb7d3a
ffffd000`24ef1da0 fffff800`e817151f : 00000000`00000000 ffffe000`e506d050 ffffe000`e5de8f40 00000000`00000000 : ha20x22k+0xb55da
ffffd000`24ef1de0 fffff800`e81499ea : 00000000`00000001 ffffe000`e14cd180 00000000`00000000 ffffe000`e5f0f040 : ha20x22k+0xb551f
ffffd000`24ef1f60 fffff800`e80eb505 : ffffe000`e5f0f040 ffffe000`e5f0f040 ffffd000`24ef2038 ffffe000`e5f0f010 : ha20x22k+0x8d9ea
ffffd000`24ef1fa0 fffff800`e8180d46 : ffffe000`e14cd150 ffffe000`e14cd158 00000000`00000000 00000000`00000001 : ha20x22k+0x2f505
ffffd000`24ef1fe0 fffff800`e810ca81 : ffffe000`e77bccb0 00000000`00000001 00000000`00000001 00000000`8000100b : ha20x22k+0xc4d46
ffffd000`24ef2020 fffff800`e810c41d : ffffe000`00000000 fffff800`00000004 ffffe000`00000002 ffffe000`eb5b2010 : ha20x22k+0x50a81
ffffd000`24ef20b0 fffff800`e81809b1 : ffffe000`e7a06fc8 00000001`01000000 ffffe000`e77bcd00 ffffe000`eb5b2010 : ha20x22k+0x5041d
ffffd000`24ef2100 fffff800`e818084a : ffffe000`e77bcd00 00000000`00000000 ffffe000`eb5b2010 00000000`00000000 : ha20x22k+0xc49b1
ffffd000`24ef2130 fffff800`e81867de : 00000000`00000000 fffff801`a60a7ae5 00000000`00000000 fffff800`774e6350 : ha20x22k+0xc484a
ffffd000`24ef2160 fffff800`e8261400 : fffff800`e82851b0 fffff800`e82613be ffffe000`e41f8e58 ffffe000`e7687010 : ha20x22k+0xca7de
ffffd000`24ef2280 fffff800`e825c8c8 : ffffe000`e41f8e60 ffffd000`24ef26e8 ffffd000`24ef2440 00000000`00000000 : emupia2k+0x8400
ffffd000`24ef22f0 fffff800`e8006479 : ffffe000`e7665160 fffff800`e82712c0 fffff800`e82712c0 00000000`82d872e0 : emupia2k+0x38c8
ffffd000`24ef23c0 fffff800`e8261400 : fffff800`e8285130 fffff800`e82613be ffffe000`e41f8e58 ffffe000`e5d18010 : CTHWIUT!DllGetDefaultStringVersion+0x4da1
ffffd000`24ef2550 fffff800`e825c8c8 : ffffe000`e41f8e60 ffffd000`24ef26e8 ffffe000`e9dc4e48 00000000`00000000 : emupia2k+0x8400
ffffd000`24ef25c0 fffff800`e825c5d8 : ffffc001`00000000 00000000`00000000 ffffe000`e9db7000 00000000`0000de00 : emupia2k+0x38c8
ffffd000`24ef2690 fffff800`e826b6c3 : 00000000`00000000 00000000`20206f49 fffff680`00000000 00000000`00000001 : emupia2k+0x35d8
ffffd000`24ef2720 fffff800`e826971a : 00000000`000bafa4 00000000`00000001 ffffe000`e9db7000 ffffd000`24ef2aa8 : emupia2k+0x126c3
ffffd000`24ef27f0 fffff800`e829f4c1 : 00000000`00000010 fffff801`a620ea55 00000000`00000d00 fffff801`00000000 : emupia2k+0x1071a
ffffd000`24ef2820 fffff801`a620f8f2 : 00000000`00000001 ffffd000`00000010 ffffe000`e54b9ee0 00000000`00000001 : emupia2k+0x464c1
ffffd000`24ef2880 fffff801`a62101c6 : 00000000`00000000 fffff801`00000080 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandleWithTag+0xe92
ffffd000`24ef2a20 fffff801`a5f727b3 : ffffe000`e7d3cde8 ffffe000`e7d36670 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtDeviceIoControlFile+0x56
ffffd000`24ef2a90 00000000`00020002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x34b3
00000000`0008ee08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x20002


STACK_COMMAND: kb

FOLLOWUP_IP:
ha20x22k+95ae5
fffff800`e8151ae5 8b4b70 mov ecx,dword ptr [rbx+70h]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: ha20x22k+95ae5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ha20x22k

IMAGE_NAME: ha20x22k.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

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

2: kd> .symfix
2: kd> symfix
Couldn't resolve error at 'ymfix'
2: kd> .symfix; .reload
Loading Kernel Symbols
...............................................................
................................................................
.............Page 14b4ec not present in the dump file. Type ".hh dbgerr004" for details
..................................Page 19cd15 not present in the dump file. Type ".hh dbgerr004" for details
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............

************* Symbol Loading Error Summary **************
Module name Error
SharedUserData No error - symbol load deferred

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
 
Last edited:
[27];1040797523 said:
@gotnorice, I tried both the creative drivers and the PAX drivers, same issue on both.
Click to expand...

What version of the Creative Driver did you try?
 
asus p9x79 ws mobo

ive gone out to station-drivers and updated everything i could, i ran into an article that stated that asus suite ii was causing issues like this, but ive uninstalled it and the issue remains.
 
[27];1040797523 said:
@gotnorice, I tried both the creative drivers and the PAX drivers, same issue on both.

@stolemyowncar, this is the dump file, it looks to be for ha20x22k.sys which is a creative driver.
<snip>
Click to expand...

It's really hard to tell anything from the dump you did, because you didn't have the symbols path loaded correctly. Almost every message in your post was related to that.
 
I'm obviously doing something wrong, I am using the following commands in the debugger:

.sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
.ignore_missing_pages 1
.symfix; .reload

and I get the following errors:
2: kd> .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*f:\localsymbols*http://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
2: kd> .ignore_missing_pages 1
Suppress kernel summary dump missing page error message
2: kd> .symfix; .reload
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
..............

************* Symbol Loading Error Summary **************
Module name Error
SharedUserData No error - symbol load deferred

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.

When I tried as one command line of:

.sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols;.ignore_missing_pages 1; .symfix; .reload;

I get this:
2: kd> .sympath SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols;.ignore_missing_pages 1; .symfix; .reload;
Symbol search path is: SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols;.ignore_missing_pages 1; .symfix; .reload;
Expanded Symbol search path is: srv*f:\localsymbols*http://msdl.microsoft.com/download/symbols;.ignore_missing_pages 1; .symfix; .reload;
WARNING: Whitespace at start of path element
WARNING: Whitespace at start of path element
WARNING: Whitespace at start of path element
Error: Attempts to access '.ignore_missing_pages 1' failed: 0x2 - The system cannot find the file specified.

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*f:\localsymbols*http://msdl.microsoft.com/download/symbols
Error .ignore_missing_pages 1



any input as to what I need to do to get you the needed info?
 
I should also note that since I uninstalled the Asus Suite II that I can prevent the BSOD if I get out of whatever game I am playing when the audio stops/crashes. I wont be able to get any audio in that session though, and will have to reboot to get it back.
 
You must log in or register to reply here.
Back
Top