[wdmaudiodev] Re: HCT 11.0: problems with verifier test, help please
- From: "David Miller (MULTIMEDIA)" <davmil@xxxxxxxxxxxxx>
- To: <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Wed, 13 Nov 2002 22:39:19 -0800
This is a known issue. We have a QFE in the works now that addresses
this problem.
-----Original Message-----
From: Jeff Pages [mailto:jeff@xxxxxxxxxxxxxxxx]=20
Sent: Wednesday, November 13, 2002 8:43 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: HCT 11.0: problems with verifier test, help
please
I am having the same problem with Driver Verifier under HCT 11.0. The
bugcheck code is 0x8E (0xc0000005, 0x80db8806, 0xf4db13d0, 0x00000000)
and the debugger traces it back to CPortFilterDMus__NewIrpTarget+0xd1 in
portcls.sys.
Now my hardware has no DMusic or MIDI support at all and all of this
stuff goes through the Microsoft emulator. Also the driver passed HCT
10.0 without any dramas.
Can anyone shed any light on this?
Jeff
----- Original Message -----
From: "0x0" <pagefault0x0@xxxxxxxxxxx>
To: <wdmaudiodev@xxxxxxxxxxxxx>
Sent: Friday, September 27, 2002 7:55 AM
Subject: {SPAM DETECTED: [wdmaudiodev] HCT 11.0: problems with verifier
test, help please
> Hi. A driver which was previously WHQLed is failing the driver=20
> verifier
test under HCT 11.0. Now I know that the test is more stringent now in
that it seems to verify all unsigned drivers on the system (outside of
MEDIA class even), but the crash which I keep on getting is within
portcls.sys.
>
> The last intelligible part of the stack trace (see below for the full
trace) shows a thread in portcls!CPortPinDMus::Init+0x4cb. Now I do
have a UART device, but not a DirectMusic device. I believe that the
port is the same for both, however. But even when I do not install the
UART subdevice, I get this error!
>
> Would anyone have any ideas whatsoever as to what may be the cause? =20
> Did
anyone else have a similar problem? Note that I have attached the full
stack trace below. Thanks in advance.
>
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp1.020828-1920
> Kernel base =3D 0x804d4000 PsLoadedModuleList =3D 0x8054be30 Debug =
session
> time: Sat Sep 14 12:19:56 2002 System Uptime: 0 days 0:24:30.321
> Loading Kernel Symbols
>
........................................................................
....
..............................
> Loading unloaded module list
> .................
> Loading User Symbols
> PEB is paged out (Peb =3D 7ffdf00c). Type ".hh dbgerr001" for details
>
************************************************************************
****
***
> *
*
> * Bugcheck Analysis
*
> *
*
>
************************************************************************
****
***
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 8E, {c0000005, 82dce176, f10793d0, 0}
>
> Probably caused by : portcls.sys ( portcls!CPortPinDMus::Init+4cb )
>
> Followup: MachineOwner
> ---------
>
> kd> !analyze -v
>
************************************************************************
****
***
> *
*
> * Bugcheck Analysis
*
> *
*
>
************************************************************************
****
***
>
> KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
> This is a very common bugcheck. Usually the exception address=20
> pinpoints the driver/function that caused the problem. Always note=20
> this address as well as the link date of the driver/image that=20
> contains this address. Some common problems are exception code=20
> 0x80000003. This means a hard coded breakpoint or assertion was hit,=20
> but this system was booted /NODEBUG. This is not supposed to happen=20
> as developers should never have hardcoded breakpoints in retail code,=20
> but ... If this happens, make sure a debugger gets connected, and the=20
> system is booted /DEBUG. This will let us see why this breakpoint is=20
> happening. An exception code of 0x80000002=20
> (STATUS_DATATYPE_MISALIGNMENT) indicates that an unaligned data=20
> reference was encountered. The trap frame will supply additional=20
> information.
> Arguments:
> Arg1: c0000005, The exception code that was not handled
> Arg2: 82dce176, The address that the exception occurred at
> Arg3: f10793d0, Trap Frame
> Arg4: 00000000
>
> Debugging Details:
> ------------------
>
>
> EXCEPTION_CODE: c0000005
>
> FAULTING_IP:
> +ffffffff82dce176
> 82dce176 008078e1dc82 add [eax+0x82dce178],al
>
> TRAP_FRAME: f10793d0 -- (.trap fffffffff10793d0)
> ErrCode =3D 00000002
> eax=3D85830f28 ebx=3D00000000 ecx=3D82ea1680 edx=3D8275e088 =
esi=3D85830e80
edi=3D85830fac
> eip=3D82dce176 esp=3Df1079444 ebp=3Df1079468 iopl=3D0 ov up ei =
ng nz
ac po
nc
> cs=3D0008 ss=3D0010 ds=3D0023 es=3D0023 fs=3D0030 gs=3D0000
efl=3D00010a96
> 82dce176 008078e1dc82 add [eax+0x82dce178],al
ds:0023:085ff0a0=3D??
> Resetting default context
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> BUGCHECK_STR: 0x8E
>
> LAST_CONTROL_TRANSFER: from f22bbf0e to 82dce176
>
> STACK_TEXT:
> WARNING: Frame IP not in any known module. Following frames may be=20
> wrong. f1079440 f22bbf0e 82ea1680 f22aed38 85830f28 0x82dce176=20
> f1079468 f22ba6a5 00000000 00000188 00000000
portcls!CPortPinDMus::Init+0x4cb
> f1079490 f22b2998 82f37f68 85b14ff4 85b14ff8
portcls!CPortFilterDMus::NewIrpTarget+0xd1
> f10794d8 f22b2abc 85b7afd0 82e98030 85b2cf48=20
> portcls!xDispatchCreate+0x8e f10794e8 bad8cfd9 82e98030 85b2cf48=20
> 82e98030
portcls!KsoDispatchCreateWithGenericFactory+0x28
> f1079510 bad8cced 82e98030 85b2cf48 f1079568 ks!DispatchCreate+0xce=20
> f1079520 f22b2863 82e98030 85b2cf48 82e9a220 ks!KsDispatchIrp+0x124=20
> f1079534 804eca36 82e98030 85b2cf48 806c8214=20
> portcls!DispatchCreate+0x31 f1079544 80647111 85b2cf58 85b2cf48=20
> 82ebf0f8 nt!IopfCallDriver+0x31 f1079568 80582ebb 82ed5f90 82922fa0=20
> f1079748 nt!IovCallDriver+0x9e f107964c 8057cc7c 82e98030 00000000=20
> 82e9d4d8 nt!IopParseDevice+0xa4d f1079684 805852f5 82ed5f90 00000000=20
> 82e9d4d8 nt!IopParseFile+0x44 f1079708 80581aba 80000138 f1079748=20
> 00000240 nt!ObpLookupObjectName+0x117 f107975c 80583172 00000000=20
> 00000000 ffffff00 nt!ObOpenObjectByName+0xe9 f10797d8 8058324e=20
> e10d5b70 40000000 f107986c nt!IopCreateFile+0x407 f1079820 bad8cbdc=20
> e10d5b70 40000000 f107986c nt!IoCreateFile+0x36 f107989c bad8d9d1=20
> 80000138 bad91af8 e1111900 ks!KsiCreateObjectType+0xd4 f10798b8=20
> f1bc9301 80000138 e1111900 40000200 ks!KsCreatePin+0x32 f10798dc=20
> f1bc9502 e1d2bff4 e1062e48 e1d2d4d8
sysaudio!CPinNodeInstance::Create+0x69
> f1079918 f1bcf44e 00000000 e1d2bff4 e27917d8
sysaudio!CConnectNodeInstance::Connect+0xd7
> f1079934 f1bc963b 00000000 82f1f138 00000000
sysaudio!CStartNodeInstance::Connect+0xa6
> f107995c f1bc8dd9 e1ea3468 e1d35900 82f1f138
sysaudio!CStartNodeInstance::Create+0x17f
> f107998c f1bc8aa5 c0000010 82f1f138 00000000
sysaudio!CPinInstance::PinDispatchCreateKP+0xa6
> f10799a8 f1bc833d 85a90e90 f1bc8d4d 82f1f138
sysaudio!CInstance::DispatchCreate+0x61
> f10799dc bad8cfd9 82ea4408 85a90e90 82ea4408
sysaudio!CPinInstance::PinDispatchCreate+0xbf
> f1079a04 804eca36 82ea4408 85a90e90 806c8214 ks!DispatchCreate+0xce=20
> f1079a14 80647111 85a90ea0 85a90e90 82dbe6d0 nt!IopfCallDriver+0x31=20
> f1079a38 80582ebb 82ed2a48 82e0ed98 f1079c18 nt!IovCallDriver+0x9e=20
> f1079b1c 8057cc7c 82ea4408 00000000 830d6cb8 nt!IopParseDevice+0xa4d=20
> f1079b54 805852f5 82ed2a48 00000000 830d6cb8 nt!IopParseFile+0x44=20
> f1079bd8 80581aba 000001e0 f1079c18 00000040=20
> nt!ObpLookupObjectName+0x117 f1079c2c 80583172 00000000 00000000=20
> 82e08101 nt!ObOpenObjectByName+0xe9 f1079ca8 8058324e 00769ae0=20
> c0000000 0099f7cc nt!IopCreateFile+0x407 f1079cf0 8058b1f0 00769ae0=20
> c0000000 0099f7cc nt!IoCreateFile+0x36 f1079d30 804da140 00769ae0=20
> c0000000 0099f7cc nt!NtCreateFile+0x2e f1079d30 7ffe0304 00769ae0=20
> c0000000 0099f7cc nt!KiSystemService+0xc4 0099f7f8 00000000 00000000=20
> 00000000 00000000
SharedUserData!SystemCallStub+0x4
>
>
> FOLLOWUP_IP:
> portcls!CPortPinDMus::Init+4cb
> f22bbf0e 894508 mov [ebp+0x8],eax
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: portcls!CPortPinDMus::Init+4cb
>
> MODULE_NAME: portcls
>
> IMAGE_NAME: portcls.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de2ca
>
> STACK_COMMAND: .trap fffffffff10793d0 ; kb
>
> BUCKET_ID: 0x8E_portcls!CPortPinDMus::Init+4cb
>
> Followup: MachineOwner
>
>
>
> ******************
>
> WDMAUDIODEV addresses:
> Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
> Subscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe
> Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe
> Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
>
> URL to WDMAUDIODEV page:
> http://www.wdmaudiodev.de/
>
>
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: =
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dsubscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=3Dunsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.de/
Other related posts:
