[wdmaudiodev] Re: HCT 11.0: problems with verifier test, help please
- From: Xu Wen Bin <skeeter_xu@xxxxxxxxx>
- To: wdmaudiodev@xxxxxxxxxxxxx
- Date: Thu, 14 Nov 2002 17:44:06 -0800 (PST)
Hi Guy,
Is the QFE released ? Where can I download it ?
Thank you.
--- "David Miller (MULTIMEDIA)" <davmil@xxxxxxxxxxxxx>
wrote:
>
> 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
> >
>
=== message truncated ===
__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com
******************
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:
