'Mute' multimedia key BSODs

iont · Mar 4, 2006, 02:26 PM

When I check the 'Settings->Multimedia Keyboard Enabled' option and press the mute key on my keyboard it causes the following bugcheck:

Code:

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: srv*\\Screamline\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Mar  4 15:12:17.031 2006 (GMT+2)
System Uptime: 0 days 0:16:47.623
Loading Kernel Symbols
...........................................................................................................................................
Loading unloaded module list
..............
Loading User Symbols
.............................................
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D3, {ba169f6c, 2, 0, 804da447}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for kx.sys - 
*** WARNING: Unable to verify checksum for kxapi.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for kxapi.dll - 
*** ERROR: Module load completed but symbols could not be loaded for kxmixer.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for MFC42D.DLL - 
Probably caused by : kx.sys ( kx+169c9 )
---------



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

DRIVER_PORTION_MUST_BE_NONPAGED (d3)
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers marking code or data as pageable when it should be
marked nonpaged.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ba169f6c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804da447, address which referenced memory

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


READ_ADDRESS:  ba169f6c 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!strncmp+1f
804da447 f3a6			 rep	 cmpsb

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD3

LAST_CONTROL_TRANSFER:  from ba1159c9 to 804da447

TRAP_FRAME:  afc5b730 -- (.trap ffffffffafc5b730)
ErrCode = 00000000
eax=00000000 ebx=00000080 ecx=00000005 edx=82638cc8 esi=ba169f6c edi=82638cd4
eip=804da447 esp=afc5b7a4 ebp=afc5b7b0 iopl=0		 nv up ei pl nz na po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010207
nt!strncmp+0x1f:
804da447 f3a6			 rep	 cmpsb		 ds:ba169f6c=65 es:82638cd4=50
Resetting default scope

STACK_TEXT:  
afc5b7b0 ba1159c9 82638cd4 ba169f6c 00000080 nt!strncmp+0x1f
WARNING: Stack unwind information not available. Following frames may be wrong.
afc5b7d4 ba16a6bf 81da5000 ba169f6c ba169f5c kx+0x169c9
afc5b830 ba0ed94f 81a2b240 00000004 82bd6e90 kx!get_frame_size+0x1ed6f
afc5b848 ba0ed9a1 82bd6e90 81f72608 e1aab9f8 portcls!PcDispatchProperty+0x130
afc5b870 ba0c0f4c 00000004 ff6fe140 ff6fe138 portcls!PropertyItemPropertyHandler+0x2b
afc5b8d4 ba0c0ec9 82bd6e90 00000004 e1aab9f8 ks!KspPropertyHandler+0x616
afc5b8f8 ba0eb603 82bd6e90 00000004 e1aab9d0 ks!KsPropertyHandler+0x19
afc5b90c ba0eda85 82bd6e90 00000004 e1aab9d0 portcls!PcHandlePropertyWithTable+0x1b
afc5b940 ba0eb69d 81f725f0 81e95c88 82bd6e90 portcls!CPortFilterTopology::DeviceIoControl+0xb2
afc5b95c ba0c0f85 81e95c88 82bd6e90 afc5b9a0 portcls!DispatchDeviceIoControl+0x49
afc5b96c 804e37f7 81e95c88 82bd6e90 806ee2e8 ks!DispatchDeviceIoControl+0x28
afc5b97c 80669cc5 00000000 82bd6e90 00000006 nt!IopfCallDriver+0x31
afc5b9a0 f99a4774 00000000 00000000 82bd6e90 nt!IovCallDriver+0xa0
afc5b9f0 f99a618e 82bd6e90 ff6fe140 e1a094b0 sysaudio!ForwardIrpNode+0x1b2
afc5ba44 ba0c0f85 ff817548 82bd6e90 afc5ba88 sysaudio!CFilterInstance::FilterDispatchIoControl+0x14c
afc5ba54 804e37f7 ff817548 82bd6e90 806ee2e8 ks!DispatchDeviceIoControl+0x28
afc5ba64 80669cc5 81a2db58 82bd6e90 ff817548 nt!IopfCallDriver+0x31
afc5ba88 ba0c1c47 ad09aa20 afc5baf8 00000028 nt!IovCallDriver+0xa0
afc5bab4 ad0905fb 81a2db58 00000000 002f0003 ks!KsSynchronousIoControlDevice+0xbd
afc5bb18 ad093d8c 81a2db58 0000000d 00000006 wdmaud!kmxlAudioNodeProperty+0xb8
afc5bb60 ad093f11 ff64eb88 00000000 00000001 wdmaud!kmxlHandleSetUnsigned+0x168
afc5bb94 ad098b6c 81fd5b8c ff64eb88 ff882148 wdmaud!kmxlSetControlDetailsHandler+0x149
afc5bbe8 ad094d84 82bd2f48 81fd4000 ff64eb88 wdmaud!Dispatch_SetControlDetails+0xf4
afc5bc10 804e37f7 00000018 81fd4000 806ee2e8 wdmaud!SoundDispatch+0x418
afc5bc20 80669cc5 82b7cf58 806ee2d0 82bd2f48 nt!IopfCallDriver+0x31
afc5bc44 8056a101 82bd2fdc 81f8bf90 82bd2f48 nt!IovCallDriver+0xa0
afc5bc58 80579a8a ff81ace8 82bd2f48 81f8bf90 nt!IopSynchronousServiceTail+0x60
afc5bd00 8057bfa5 0000010c 00000354 00000000 nt!IopXxxControlFile+0x611
afc5bd34 804de7ec 0000010c 00000354 00000000 nt!NtDeviceIoControlFile+0x2a
afc5bd34 7c90eb94 0000010c 00000354 00000000 nt!KiFastCallEntry+0xf8
0006f11c 7c90d8ef 7c8016be 0000010c 00000354 ntdll!KiFastSystemCallRet
0006f120 7c8016be 0000010c 00000354 00000000 ntdll!ZwDeviceIoControlFile+0xc
0006f180 72d24523 0000010c 001d8314 000b0d58 kernel32!DeviceIoControl+0x78
0006f1c8 72d2379b 000b0d58 00000018 0006f534 wdmaud_72d20000!wdmaudIoControl+0x96
0006f1f0 76b4a88d 00000000 00000008 000a5b10 wdmaud_72d20000!mxdMessage+0x44e
0006f218 76b5046b 0009e378 00000008 0006f534 WINMM!IMixerMessageHandle+0x68
0006f240 0040dc51 00000000 00000001 00000000 WINMM!mixerSetControlDetails+0x166
0006f568 010115c6 00200000 00000001 00000000 kxapi!iKX::mixer+0x13c1
0006f5a4 01059a20 00000027 00000003 77d4d500 kxmixer+0x115c6
0006f620 0104418f 000000ad 006f0074 0000006e kxmixer+0x59a20
0006fc74 77d48734 000100ee 00000312 000000ad kxmixer+0x4418f
0006fca0 77d48816 01043340 000100ee 00000312 USER32!InternalCallWinProc+0x28
0006fd08 77d489cd 00000000 01043340 000100ee USER32!UserCallWinProcCheckWow+0x150
0006fd68 77d496c7 0006fda8 00000001 0006fee4 USER32!DispatchMessageWorker+0x306
0006fd78 0104470e 0006fda8 0006fd9c 0006fd9c USER32!DispatchMessageA+0xf
0006fee4 5f4335c3 ffffffff 00340034 00000000 kxmixer+0x4470e
0006ff04 0105cb88 01000000 00000000 00092332 MFC42D!Ordinal1190+0x83
0006ff1c 0105b284 01000000 00000000 00092332 kxmixer+0x5cb88
0006ffc0 7c816d4f 00350032 00340034 7ffd8000 kxmixer+0x5b284
0006fff0 00000000 0105b0fe 00000000 78746341 kernel32!BaseProcessStart+0x23


FOLLOWUP_IP: 
kx+169c9
ba1159c9 83c40c		   add	 esp,0xc

SYMBOL_STACK_INDEX:  1

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  kx+169c9

MODULE_NAME:  kx

IMAGE_NAME:  kx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  43dfeae0

STACK_COMMAND:  .trap ffffffffafc5b730 ; kb

FAILURE_BUCKET_ID:  0xD3_kx+169c9

BUCKET_ID:  0xD3_kx+169c9

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



kd> lm v m kx*
start	end		module name
00270000 002c9000   kxgui	  (deferred)			 
	Image path: C:\WINDOWS\system32\kxgui.dll
	Image name: kxgui.dll
	Timestamp:		Thu Jan 26 04:31:34 2006 (43D83486)
	CheckSum:		 missing
	ImageSize:		00059000
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0
00400000 00461000   kxapi	C (export symbols)	   kxapi.dll
	Loaded symbol image file: kxapi.dll
	Mapped memory image file: C:\WINDOWS\system32\kxapi.dll
	Image path: C:\WINDOWS\system32\kxapi.dll
	Image name: kxapi.dll
	Timestamp:		Thu Jan 26 04:31:50 2006 (43D83496)
	CheckSum:		 00000000
	ImageSize:		00061000
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0
01000000 01076000   kxmixer	(no symbols)		   
	Loaded symbol image file: kxmixer.exe
	Image path: C:\WINDOWS\system32\kxmixer.exe
	Image name: kxmixer.exe
	Timestamp:		Thu Jan 26 04:32:41 2006 (43D834C9)
	CheckSum:		 0007E0AF
	ImageSize:		00076000
	File version:	 5.10.0.3538
	Product version:  5.10.0.3538
	File flags:	   1 (Mask 3F) Debug
	File OS:		  4 Unknown Win32
	File type:		1.0 App
	File date:		00000000.00000000
	Translations:	 0409.04b0
	CompanyName:	  Eugene Gavrilov
	ProductName:	  kX mixer
	InternalName:	 kX mixer
	OriginalFilename: kxmixer.exe
	ProductVersion:   5, 10, 00, 3538 - debug
	FileVersion:	  5, 10, 00, 3538 - debug
	PrivateBuild:	 5, 10, 00, 3538 - debug
	SpecialBuild:	 5, 10, 00, 3538 - debug
	FileDescription:  kX mixer
	LegalCopyright:   Copyright © Eugene Gavrilov, 2001-2006.
	LegalTrademarks:  Copyright © Eugene Gavrilov, 2001-2006.
	Comments:		 Copyright © Eugene Gavrilov, 2001-2006.
018f0000 01935000   kxfxlib	(deferred)			 
	Image path: C:\WINDOWS\system32\kxfxlib.kxl
	Image name: kxfxlib.kxl
	Timestamp:		Thu Jan 26 04:32:03 2006 (43D834A3)
	CheckSum:		 missing
	ImageSize:		00045000
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0
ba0ff000 ba18a400   kx		 (export symbols)	   kx.sys
	Loaded symbol image file: kx.sys
	Image path: \SystemRoot\system32\drivers\kx.sys
	Image name: kx.sys
	Timestamp:		Wed Feb 01 00:55:28 2006 (43DFEAE0)
	CheckSum:		 0009998C
	ImageSize:		0008B400
	Translations:	 0000.04b0 0000.04e0 0409.04b0 0409.04e0
---------


// 0xba169f6c is the 'Memory Referenced' field in the above bug check params
kd> d 0xba169f6c
ba169f6c  65 70 69 6c 6f 67 00 00-4d 61 73 74 65 72 4c 00  epilog..MasterL.
ba169f7c  4d 61 73 74 65 72 52 00-65 70 69 6c 6f 67 00 00  MasterR.epilog..
ba169f8c  73 65 74 20 53 79 6e 74-68 20 4d 55 54 45 20 74  set Synth MUTE t
ba169f9c  6f 20 25 64 20 63 68 61-6e 6e 65 6c 3d 25 64 0a  o %d channel=%d.
ba169fac  00 00 00 00 21 21 21 20-73 65 74 20 4d 55 54 45  ....!!! set MUTE
ba169fbc  20 75 6e 6b 6e 6f 77 6e-20 6e 6f 64 65 3d 25 64   unknown node=%d
ba169fcc  0a 00 00 00 21 21 21 20-62 61 64 20 69 64 20 69  ....!!! bad id i
ba169fdc  6e 20 74 6f 70 6f 3a 3a-6d 75 74 65 0a 00 00 00  n topo::mute....
---------

Russ · Mar 4, 2006, 02:35 PM

Do your multimedia keyboard buttons work without that enabled?
I am not exactly sure what that settings is for, but my multimedia keyboard works just fine without that setting enabled (but, I do not having any problems if it is enabled).

iont · Mar 4, 2006, 03:55 PM

Quote:

Originally Posted by Russ

Do your multimedia keyboard buttons work without that enabled?
I am not exactly sure what that settings is for, but my multimedia keyboard works just fine without that setting enabled (but, I do not having any problems if it is enabled).

nope, the mltmdia keys do not work otherwise, probably because i'm using standart winxp drivers for the keyboard.

however the mute key crashes the machine even when that kx option is off. Still, the backtrace shows clearly that control flow ends somewhere in the kx core..

Maddogg6 · Mar 14, 2006, 04:29 AM

Same here - if not enabled in KX - MM keys stop working. Its a logitech wired KB and its shown in device manager as a standard 101/102 key or Microsoft Natural Keyboard Ps-2 KB.

It works fine for me btw..

**dj_stick** · Mar 14, 2006, 07:40 AM

are you using Russ's "hack?"

Russ · Mar 14, 2006, 03:25 PM

Quote:

Originally Posted by Maddogg6

Same here
...
It works fine for me btw..

Do you mean that it works fine for you, other than the BSOD problem, or do you mean that you do not have any problems?

Russ · Mar 14, 2006, 03:27 PM

Quote:

Originally Posted by dj_stick

are you using Russ's "hack?"

The OP posted about this problem before I made that.

DDRRE · Mar 14, 2006, 04:55 PM

It's the same error mentioned in this thread:

http://www.hardwareheaven.com/bug-reports/76171-kx-sys-blue-screen-kx3538h.html

only there the user tries to modify the volume level instead of just pressing "mute".

Maddogg6 · Mar 14, 2006, 05:21 PM

Quote:

Originally Posted by Russ

Do you mean that it works fine for you, other than the BSOD problem, or do you mean that you do not have any problems?

the MMkeys work as I would expect - and Ive never seen what the BSOD looks like in XP (yet??, knock on wood).

So, I guess Im just confirming that KX is at least capable of proper MM key operation / function. One then could sumize that it could be aither confilct with KX - or not kx at all - but that bugtracker screen sure makes it look like KX was at fault there.

?? I dunno - I use them keys ALOT - no problems ever.
Dis-ableing KX MM kB support - stops my keys from functioning - (AND no OSD happens either btw)

Russ · Mar 14, 2006, 05:49 PM

Thats what I thought you meant, but wasn't sure.
If you were using the right driver, it would probably would work without the kX setting as well.
The iTouch software that came with my keyboard does the OSD, and handles the other MM keys, but the volume keys work without it, and without the kX setting enabled.

In any case, it sounds like it is not really related to the MM keys, but with kxmixer updating Windows (i.e. from the info in the following thread: http://www.hardwareheaven.com/showthread.php?t=76171)

Maddogg6 · Mar 14, 2006, 06:00 PM

My KB didnt come with drivers - it was meant for XP only IIRC - I even looked for drivers so I could remap the other 5 keys - but found nadda - but then I found how to remap some keys with M$ TweakUI XP for 4 of the other 5 keys (I have a 'PLAY/PAUSE' key that isnt mapable for me - btw)

Maddogg6 · Apr 20, 2006, 11:47 PM

Sorry for re-viving an old thread but...

I just experienced for the second time - WinXP SP2 w/ KX V3538J - when pressing a MM key -XP went black and re-booted, but I didnt look at the debug/XP error report.

I guess Im not sure where to find these reports. Any tips ??

**dj_stick** · Apr 21, 2006, 03:26 AM

XP Pro SP2, 3538J, A ES & A2ZS -> no such issue here using volume up/down/mute and mm controls

Mar 4, 2006, 02:35 PM	#2
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,562 Rep Power: 62	Do your multimedia keyboard buttons work without that enabled? I am not exactly sure what that settings is for, but my multimedia keyboard works just fine without that setting enabled (but, I do not having any problems if it is enabled). Last edited by Russ; Mar 14, 2006 at 05:09 PM. Reason: typo

Mar 14, 2006, 04:29 AM	#4
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	Same here - if not enabled in KX - MM keys stop working. Its a logitech wired KB and its shown in device manager as a standard 101/102 key or Microsoft Natural Keyboard Ps-2 KB. It works fine for me btw..

Mar 14, 2006, 04:55 PM	#8
DDRRE HardwareHeaven Junior Member Join Date: Mar 2006 Posts: 37 Rep Power: 0	It's the same error mentioned in this thread: http://www.hardwareheaven.com/bug-reports/76171-kx-sys-blue-screen-kx3538h.html only there the user tries to modify the volume level instead of just pressing "mute".

Mar 14, 2006, 05:49 PM	#10
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,562 Rep Power: 62	Thats what I thought you meant, but wasn't sure. If you were using the right driver, it would probably would work without the kX setting as well. The iTouch software that came with my keyboard does the OSD, and handles the other MM keys, but the volume keys work without it, and without the kX setting enabled. In any case, it sounds like it is not really related to the MM keys, but with kxmixer updating Windows (i.e. from the info in the following thread: http://www.hardwareheaven.com/showthread.php?t=76171)

Mar 14, 2006, 06:00 PM	#11
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	My KB didnt come with drivers - it was meant for XP only IIRC - I even looked for drivers so I could remap the other 5 keys - but found nadda - but then I found how to remap some keys with M$ TweakUI XP for 4 of the other 5 keys (I have a 'PLAY/PAUSE' key that isnt mapable for me - btw)

Apr 20, 2006, 11:47 PM	#12
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	Sorry for re-viving an old thread but... I just experienced for the second time - WinXP SP2 w/ KX V3538J - when pressing a MM key -XP went black and re-booted, but I didnt look at the debug/XP error report. I guess Im not sure where to find these reports. Any tips ??