TechTalkz.com Logo Ask the Experts!

Go Back   TechTalkz.com Technology & Computer Troubleshooting Forums > Tech Support Archives > Microsoft > Microsoft Device Drivers > Microsoft Device Drivers - DTM

USBSer.sys causes BSOD

Microsoft Device Drivers - DTM

 
 
 
Thread Tools Display Modes
Old 12-01-2008, 12:34 PM   #1
Lono
Guest
 
Posts: n/a
USBSer.sys causes BSOD


I tried to pass the Windows Logo Test for the driver of USB modem product
of our company, however, the PnP Driver tests failed. A BSOD occued during
PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck code
is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was caused
by USBSer.sys which is a standard driver in Windows XP. Because we provide
nothing but an .inf file and the only driver is standard USBSER.sys driver,
the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
both Windows XP SP1 and SP2. Any ideas about how to fix this problem?

Thanks,
Lono Kao
 
Old 12-01-2008, 12:35 PM   #2
Leo Havmøller
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

"Lono" <Lono@discussions.microsoft.com> wrote in message
news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
>
> I tried to pass the Windows Logo Test for the driver of USB modem
> product
> of our company, however, the PnP Driver tests failed. A BSOD occued during
> PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck
> code
> is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was
> caused
> by USBSer.sys which is a standard driver in Windows XP. Because we provide
> nothing but an .inf file


What about your USB device and the firmware in it?

> and the only driver is standard USBSER.sys driver,
> the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> both Windows XP SP1 and SP2. Any ideas about how to fix this problem?


Make a USB bus trace of what happens when the BSOC occurs, then fix your
firmware.

Leo Havmøller.

 
Old 12-01-2008, 12:35 PM   #3
Leo Havmøller
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

"Lono" <Lono@discussions.microsoft.com> wrote in message
news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
>
> I tried to pass the Windows Logo Test for the driver of USB modem
> product
> of our company, however, the PnP Driver tests failed. A BSOD occued during
> PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck
> code
> is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was
> caused
> by USBSer.sys which is a standard driver in Windows XP. Because we provide
> nothing but an .inf file


What about your USB device and the firmware in it?

> and the only driver is standard USBSER.sys driver,
> the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> both Windows XP SP1 and SP2. Any ideas about how to fix this problem?


Make a USB bus trace of what happens when the BSOC occurs, then fix your
firmware.

Leo Havmøller.

 
Old 12-01-2008, 12:36 PM   #4
Lono
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

The WinDbg indicated that BSOD occured when USBSer.sys was unloading. I don't
know if BSOD was caused by USBSer.sys or my USB COM port device.

The detailed information is here:


Device description: A mobile device with a usb port. The USB port supports
only virtual COM port functionality. The

device conforms to USB CDCACM standard. The driver used on Windows is
standard USBSer.sys which is provided by

Microsoft.

Operating system: Windows XP SP2 English(United States)
Processor: x86Qualification program: Unclassified Qualification Level:
Unclassified signature
Windows Logo Kit Version: WLK 1.1
USBSer.sys Version: version: 5.1.2600.2180

I then tested the driver with PnpTest.exe with Verifier enabled.

Verifier.exe version: 5.1.2600.0
Pnpdtest.exe version: 3.4

Verifier Enabled Settings:
Special Pool
Pool Tracking
Force IRQL checking
I/O verification
Enhanced I/O verification
Deadlock detection
DMA checking
Low resources simulation

The verifier.exe is provided by Windows XP, and the pnpdtest.exe is provided
by WDK. A BSOD can be reproduced by

PNPDTest.exe->Rebalace Test-> NewResources.

The information provided by WinDbg is listed below:

---------------------------------------------------------------------
************************************************** *****************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for u*** ERROR: Module load completed but symbols
could not be loaded for usbser.sys
PNPFILTR: Events being initialized
PNPFILTR: Received IRP_MN_QUERY_LEGACY_BUS_INFORMATION which I am simply
passing down
PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
passing down
PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
0x8210FBF0
PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
8210FBF0 is 281 miliseconds
PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_CAPABILITIES which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
status 0x00000000 and information 0x00000000
PNPFILTR: Passing down unhandled PNP IRP - minor function = 0xff
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_TEXT which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_ID which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
Running Rebalance Test(ForceResourceChange) on node with hwid:
USB\Vid_0e8d&Pid_0003&Rev_0100
PNPFILTR: Received IOCTL_QUERY_DEVICE_COUNT
PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID_SIZE for PDO 0x8210FBF0
PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID for PDO 0x8210FBF0
PNPFILTR: Received IOCTL_REBALANCE_DEVICE for PDO 0x8210FBF0
PNPFILTR: Calling IoInvalidateDeviceState on PDO 8210FBF0
PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
status 0x00000000 and information 0x00000014
PNPFILTR: Recieved Query Result
PNPFILTR: Waiting for test to be completed - will wait for 50 seconds
PNPFILTR: Received IRP_MN_QUERY_STOP_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: FilterQueryStop returning 0x00000004 for stack with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
passing down
PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
0x8210FBF0
PNPFILTR: Fake(new) Requirements created for PDO 0x8210FBF0
PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_STOP_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_STOP_DEVICE to get processed for the PDO
8210FBF0 is 31 miliseconds
PNPFILTR: Completing FilterStop with status 0x4 for stack with PDO 0x8210fbf0
PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
8210FBF0 is 266 miliseconds
PNPFILTR: Start: Test Event cleared
PNPFILTR: Irp recorded, sequence count = 7
PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
PNPFILTR: Query Result Wait Satisfied... 7
PNPFILTR: Number of IRPs Stored... 7
PNPFILTR: Query Result - Releasing the remove
PNPFILTR: Query Result -Result Stored Event set
Relevant Sequence of Irps:
IRP_MN_QUERY_PNP_DEVICE_STATE
IRP_MN_QUERY_STOP_DEVICE
IRP_MN_QUERY_RESOURCE_REQUIREMENTS
IRP_MN_FILTER_RESOURCE_REQUIREMENTS
IRP_MN_QUERY_INTERFACE
IRP_MN_STOP_DEVICE
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_REMOVE_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: FilterQueryRemove returning 0x00000004 for stack with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_REMOVE_DEVICE for stack with PDO 0x8210FBF0
IRP_MN_START_DEVICE
PNPFILTR: Deleting the global control object
PNPFILTR: FilterRemove returning 0x00000004 for stack with PDO 0x8210FBF0

*** Fatal System Error: 0x000000c4
(0x00000060,0x00000040,0x000000A0,0x00000004)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.................................................. .................................................. .................
Loading User Symbols

Loading unloaded module list
...................
*** ERROR: Module load completed but symbols could not be loaded for
cmaudio.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for
fltMgr.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for
prepdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for
asyncmac.sys
*** ERROR: Module load completed but symbols could not be loaded for
edgevcom.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for
pnpfiltr.sys
*** ERROR: Module load completed but symbols could not be loaded for
pciwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for
usbser.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for
smsmdm.sys
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {60, 40, a0, 4}

Probably caused by : usbser.sys

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

nt!RtlpBreakWithStatusInstruction:
804e3592 cc int 3
kd> !analyze -v
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
will
be among the most commonly seen crashes.
Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a '!deadlock' KD command to get more information.
Arguments:
Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
unloading.
Arg2: 00000040, paged bytes
Arg3: 000000a0, nonpaged bytes,
Arg4: 00000004, total # of (paged+nonpaged) allocations that weren't freed.
To get the name of the driver at fault, type
dp ViBadDriver l1; dS @$p
Then type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.

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

*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660

BUGCHECK_STR: 0xc4_60

IMAGE_NAME: usbser.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3fec8a55

MODULE_NAME: usbser

FAULTING_MODULE: f9c1c000 usbser

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 805586e0 -- (!locks 805586e0)

Resource @ nt!IopDeviceTreeLock (0x805586e0) Shared 1 owning threads
Threads: 8255f8b8-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x805586e0
Thread Count : 1
Thread address: 0x8255f8b8
Thread wait : 0x8afc1

LAST_CONTROL_TRANSFER: from 80532487 to 804e3592

STACK_TEXT:
f9c5b6f8 80532487 00000003 f9c5ba54 00000000 nt!RtlpBreakWithStatusInstruction
f9c5b744 80532f5e 00000003 82595f08 82595f08 nt!KiBugCheckDebugBreak+0x19
f9c5bb24 8053354e 000000c4 00000060 00000040 nt!KeBugCheck2+0x574
f9c5bb44 8066b831 000000c4 00000060 00000040 nt!KeBugCheckEx+0x1b
f9c5bb6c 805f0457 820ead38 82310d98 82310dc0
nt!MiVerifyingDriverUnloading+0x12a
f9c5bb98 805c1a2d 820ead38 82310da8 f9c5bbc4 nt!MmUnloadSystemImage+0x17d
f9c5bba8 80563af7 82310dc0 82310da8 00000000 nt!IopDeleteDriver+0x32
f9c5bbc4 804e36d5 82310dc0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
f9c5bbe8 805a0043 00000000 f9c5bc10 80563af7 nt!ObfDereferenceObject+0x5f
f9c5bbf4 80563af7 823c62fc 823c62c0 00000000 nt!IopDeleteDevice+0x43
f9c5bc10 804e36d5 823c62d8 00000000 ff7d7a08 nt!ObpRemoveObjectRoutine+0xdf
f9c5bc34 8053154f 00000000 e2807798 00000001 nt!ObfDereferenceObject+0x5f
f9c5bc54 8061bac3 e19ca3f8 00000015 e2807798
nt!IopRemoveLockedDeviceNode+0x1de
f9c5bc6c 8061bb2f 820e4768 00000002 e2807798 nt!IopDeleteLockedDeviceNode+0x34
f9c5bca0 8061d8f6 8210fbf0 02807798 00000002
nt!IopDeleteLockedDeviceNodes+0x3f
f9c5bd34 805ec82d f9c5bd70 806ee778 e10ce838
nt!PiProcessQueryRemoveAndEject+0x76b
f9c5bd50 8059fbb1 f9c5bd70 8222cee0 8056167c
nt!PiProcessTargetDeviceEvent+0x2a
f9c5bd74 804e426b 8222cee0 00000000 8255f8b8 nt!PiWalkDeviceList+0x122
f9c5bdac 8057d0f1 8222cee0 00000000 00000000 nt!ExpWorkerThread+0x100
f9c5bddc 804f827a 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27

BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27

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

"Leo Havmøller" wrote:

> "Lono" <Lono@discussions.microsoft.com> wrote in message
> news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
> >
> > I tried to pass the Windows Logo Test for the driver of USB modem
> > product
> > of our company, however, the PnP Driver tests failed. A BSOD occued during
> > PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck
> > code
> > is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was
> > caused
> > by USBSer.sys which is a standard driver in Windows XP. Because we provide
> > nothing but an .inf file

>
> What about your USB device and the firmware in it?
>
> > and the only driver is standard USBSER.sys driver,
> > the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> > both Windows XP SP1 and SP2. Any ideas about how to fix this problem?

>
> Make a USB bus trace of what happens when the BSOC occurs, then fix your
> firmware.
>
> Leo Havmøller.
>

 
Old 12-01-2008, 12:36 PM   #5
Lono
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

The WinDbg indicated that BSOD occured when USBSer.sys was unloading. I don't
know if BSOD was caused by USBSer.sys or my USB COM port device.

The detailed information is here:


Device description: A mobile device with a usb port. The USB port supports
only virtual COM port functionality. The

device conforms to USB CDCACM standard. The driver used on Windows is
standard USBSer.sys which is provided by

Microsoft.

Operating system: Windows XP SP2 English(United States)
Processor: x86Qualification program: Unclassified Qualification Level:
Unclassified signature
Windows Logo Kit Version: WLK 1.1
USBSer.sys Version: version: 5.1.2600.2180

I then tested the driver with PnpTest.exe with Verifier enabled.

Verifier.exe version: 5.1.2600.0
Pnpdtest.exe version: 3.4

Verifier Enabled Settings:
Special Pool
Pool Tracking
Force IRQL checking
I/O verification
Enhanced I/O verification
Deadlock detection
DMA checking
Low resources simulation

The verifier.exe is provided by Windows XP, and the pnpdtest.exe is provided
by WDK. A BSOD can be reproduced by

PNPDTest.exe->Rebalace Test-> NewResources.

The information provided by WinDbg is listed below:

---------------------------------------------------------------------
************************************************** *****************************
*
* This is the string you add to your checkin description
* Driver Verifier: Enabled for u*** ERROR: Module load completed but symbols
could not be loaded for usbser.sys
PNPFILTR: Events being initialized
PNPFILTR: Received IRP_MN_QUERY_LEGACY_BUS_INFORMATION which I am simply
passing down
PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
passing down
PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
0x8210FBF0
PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
8210FBF0 is 281 miliseconds
PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_CAPABILITIES which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
status 0x00000000 and information 0x00000000
PNPFILTR: Passing down unhandled PNP IRP - minor function = 0xff
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_TEXT which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_ID which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
Running Rebalance Test(ForceResourceChange) on node with hwid:
USB\Vid_0e8d&Pid_0003&Rev_0100
PNPFILTR: Received IOCTL_QUERY_DEVICE_COUNT
PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID_SIZE for PDO 0x8210FBF0
PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID for PDO 0x8210FBF0
PNPFILTR: Received IOCTL_REBALANCE_DEVICE for PDO 0x8210FBF0
PNPFILTR: Calling IoInvalidateDeviceState on PDO 8210FBF0
PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
status 0x00000000 and information 0x00000014
PNPFILTR: Recieved Query Result
PNPFILTR: Waiting for test to be completed - will wait for 50 seconds
PNPFILTR: Received IRP_MN_QUERY_STOP_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: FilterQueryStop returning 0x00000004 for stack with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
passing down
PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
0x8210FBF0
PNPFILTR: Fake(new) Requirements created for PDO 0x8210FBF0
PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
PNPFILTR: Received IRP_MN_STOP_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_STOP_DEVICE to get processed for the PDO
8210FBF0 is 31 miliseconds
PNPFILTR: Completing FilterStop with status 0x4 for stack with PDO 0x8210fbf0
PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
8210FBF0 is 266 miliseconds
PNPFILTR: Start: Test Event cleared
PNPFILTR: Irp recorded, sequence count = 7
PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
PNPFILTR: Query Result Wait Satisfied... 7
PNPFILTR: Number of IRPs Stored... 7
PNPFILTR: Query Result - Releasing the remove
PNPFILTR: Query Result -Result Stored Event set
Relevant Sequence of Irps:
IRP_MN_QUERY_PNP_DEVICE_STATE
IRP_MN_QUERY_STOP_DEVICE
IRP_MN_QUERY_RESOURCE_REQUIREMENTS
IRP_MN_FILTER_RESOURCE_REQUIREMENTS
IRP_MN_QUERY_INTERFACE
IRP_MN_STOP_DEVICE
PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
down
PNPFILTR: Received IRP_MN_QUERY_REMOVE_DEVICE for stack with PDO 0x8210FBF0
PNPFILTR: FilterQueryRemove returning 0x00000004 for stack with PDO 0x8210FBF0
PNPFILTR: Received IRP_MN_REMOVE_DEVICE for stack with PDO 0x8210FBF0
IRP_MN_START_DEVICE
PNPFILTR: Deleting the global control object
PNPFILTR: FilterRemove returning 0x00000004 for stack with PDO 0x8210FBF0

*** Fatal System Error: 0x000000c4
(0x00000060,0x00000040,0x000000A0,0x00000004)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.................................................. .................................................. .................
Loading User Symbols

Loading unloaded module list
...................
*** ERROR: Module load completed but symbols could not be loaded for
cmaudio.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for
fltMgr.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for
prepdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for
asyncmac.sys
*** ERROR: Module load completed but symbols could not be loaded for
edgevcom.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
drmk.sys -
*** ERROR: Module load completed but symbols could not be loaded for
pnpfiltr.sys
*** ERROR: Module load completed but symbols could not be loaded for
pciwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for
usbser.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** ERROR: Module load completed but symbols could not be loaded for
smsmdm.sys
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {60, 40, a0, 4}

Probably caused by : usbser.sys

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

nt!RtlpBreakWithStatusInstruction:
804e3592 cc int 3
kd> !analyze -v
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
will
be among the most commonly seen crashes.
Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
Typically the code is 0x1001 (deadlock detected) and you can
issue a '!deadlock' KD command to get more information.
Arguments:
Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
unloading.
Arg2: 00000040, paged bytes
Arg3: 000000a0, nonpaged bytes,
Arg4: 00000004, total # of (paged+nonpaged) allocations that weren't freed.
To get the name of the driver at fault, type
dp ViBadDriver l1; dS @$p
Then type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.

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

*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660
*** No owner thread found for resource 80558660

BUGCHECK_STR: 0xc4_60

IMAGE_NAME: usbser.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3fec8a55

MODULE_NAME: usbser

FAULTING_MODULE: f9c1c000 usbser

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LOCK_ADDRESS: 805586e0 -- (!locks 805586e0)

Resource @ nt!IopDeviceTreeLock (0x805586e0) Shared 1 owning threads
Threads: 8255f8b8-01<*>
1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0x805586e0
Thread Count : 1
Thread address: 0x8255f8b8
Thread wait : 0x8afc1

LAST_CONTROL_TRANSFER: from 80532487 to 804e3592

STACK_TEXT:
f9c5b6f8 80532487 00000003 f9c5ba54 00000000 nt!RtlpBreakWithStatusInstruction
f9c5b744 80532f5e 00000003 82595f08 82595f08 nt!KiBugCheckDebugBreak+0x19
f9c5bb24 8053354e 000000c4 00000060 00000040 nt!KeBugCheck2+0x574
f9c5bb44 8066b831 000000c4 00000060 00000040 nt!KeBugCheckEx+0x1b
f9c5bb6c 805f0457 820ead38 82310d98 82310dc0
nt!MiVerifyingDriverUnloading+0x12a
f9c5bb98 805c1a2d 820ead38 82310da8 f9c5bbc4 nt!MmUnloadSystemImage+0x17d
f9c5bba8 80563af7 82310dc0 82310da8 00000000 nt!IopDeleteDriver+0x32
f9c5bbc4 804e36d5 82310dc0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
f9c5bbe8 805a0043 00000000 f9c5bc10 80563af7 nt!ObfDereferenceObject+0x5f
f9c5bbf4 80563af7 823c62fc 823c62c0 00000000 nt!IopDeleteDevice+0x43
f9c5bc10 804e36d5 823c62d8 00000000 ff7d7a08 nt!ObpRemoveObjectRoutine+0xdf
f9c5bc34 8053154f 00000000 e2807798 00000001 nt!ObfDereferenceObject+0x5f
f9c5bc54 8061bac3 e19ca3f8 00000015 e2807798
nt!IopRemoveLockedDeviceNode+0x1de
f9c5bc6c 8061bb2f 820e4768 00000002 e2807798 nt!IopDeleteLockedDeviceNode+0x34
f9c5bca0 8061d8f6 8210fbf0 02807798 00000002
nt!IopDeleteLockedDeviceNodes+0x3f
f9c5bd34 805ec82d f9c5bd70 806ee778 e10ce838
nt!PiProcessQueryRemoveAndEject+0x76b
f9c5bd50 8059fbb1 f9c5bd70 8222cee0 8056167c
nt!PiProcessTargetDeviceEvent+0x2a
f9c5bd74 804e426b 8222cee0 00000000 8255f8b8 nt!PiWalkDeviceList+0x122
f9c5bdac 8057d0f1 8222cee0 00000000 00000000 nt!ExpWorkerThread+0x100
f9c5bddc 804f827a 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27

BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27

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

"Leo Havmøller" wrote:

> "Lono" <Lono@discussions.microsoft.com> wrote in message
> news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
> >
> > I tried to pass the Windows Logo Test for the driver of USB modem
> > product
> > of our company, however, the PnP Driver tests failed. A BSOD occued during
> > PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck
> > code
> > is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was
> > caused
> > by USBSer.sys which is a standard driver in Windows XP. Because we provide
> > nothing but an .inf file

>
> What about your USB device and the firmware in it?
>
> > and the only driver is standard USBSER.sys driver,
> > the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> > both Windows XP SP1 and SP2. Any ideas about how to fix this problem?

>
> Make a USB bus trace of what happens when the BSOC occurs, then fix your
> firmware.
>
> Leo Havmøller.
>

 
Old 12-01-2008, 12:37 PM   #6
yoann@philog.com
Guest
 
Posts: n/a
RE: USBSer.sys causes BSOD

Same error for me with two different devices.
We had to use a proprietary equivalent of usbser.sys

"Lono" wrote:

>
> I tried to pass the Windows Logo Test for the driver of USB modem product
> of our company, however, the PnP Driver tests failed. A BSOD occued during
> PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck code
> is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was caused
> by USBSer.sys which is a standard driver in Windows XP. Because we provide
> nothing but an .inf file and the only driver is standard USBSER.sys driver,
> the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> both Windows XP SP1 and SP2. Any ideas about how to fix this problem?
>
> Thanks,
> Lono Kao

 
Old 12-01-2008, 12:37 PM   #7
yoann@philog.com
Guest
 
Posts: n/a
RE: USBSer.sys causes BSOD

Same error for me with two different devices.
We had to use a proprietary equivalent of usbser.sys

"Lono" wrote:

>
> I tried to pass the Windows Logo Test for the driver of USB modem product
> of our company, however, the PnP Driver tests failed. A BSOD occued during
> PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck code
> is 0xC4(0x60,0x40,0xA0,0x04). With WinDbg, I found that the crash was caused
> by USBSer.sys which is a standard driver in Windows XP. Because we provide
> nothing but an .inf file and the only driver is standard USBSER.sys driver,
> the failure is very possible due to bugs in USBSER.sys. The BSOD occurs in
> both Windows XP SP1 and SP2. Any ideas about how to fix this problem?
>
> Thanks,
> Lono Kao

 
Old 12-01-2008, 12:38 PM   #8
Alan
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

Hi there,

I had a similar issue on Windows XP. I raised an MS support request, the
problem was analysed and I received an errata code to enable me to complete
the submission with this failure included. I would suggest you follow the
same route if you require the driver to be signed.

Regards,
Alan

"Lono" wrote:

> The WinDbg indicated that BSOD occured when USBSer.sys was unloading. I don't
> know if BSOD was caused by USBSer.sys or my USB COM port device.
>
> The detailed information is here:
>
>
> Device description: A mobile device with a usb port. The USB port supports
> only virtual COM port functionality. The
>
> device conforms to USB CDCACM standard. The driver used on Windows is
> standard USBSer.sys which is provided by
>
> Microsoft.
>
> Operating system: Windows XP SP2 English(United States)
> Processor: x86Qualification program: Unclassified Qualification Level:
> Unclassified signature
> Windows Logo Kit Version: WLK 1.1
> USBSer.sys Version: version: 5.1.2600.2180
>
> I then tested the driver with PnpTest.exe with Verifier enabled.
>
> Verifier.exe version: 5.1.2600.0
> Pnpdtest.exe version: 3.4
>
> Verifier Enabled Settings:
> Special Pool
> Pool Tracking
> Force IRQL checking
> I/O verification
> Enhanced I/O verification
> Deadlock detection
> DMA checking
> Low resources simulation
>
> The verifier.exe is provided by Windows XP, and the pnpdtest.exe is provided
> by WDK. A BSOD can be reproduced by
>
> PNPDTest.exe->Rebalace Test-> NewResources.
>
> The information provided by WinDbg is listed below:
>
> ---------------------------------------------------------------------
> ************************************************** *****************************
> *
> * This is the string you add to your checkin description
> * Driver Verifier: Enabled for u*** ERROR: Module load completed but symbols
> could not be loaded for usbser.sys
> PNPFILTR: Events being initialized
> PNPFILTR: Received IRP_MN_QUERY_LEGACY_BUS_INFORMATION which I am simply
> passing down
> PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> passing down
> PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> 0x8210FBF0
> PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> 8210FBF0 is 281 miliseconds
> PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_CAPABILITIES which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> status 0x00000000 and information 0x00000000
> PNPFILTR: Passing down unhandled PNP IRP - minor function = 0xff
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_TEXT which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_ID which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> Running Rebalance Test(ForceResourceChange) on node with hwid:
> USB\Vid_0e8d&Pid_0003&Rev_0100
> PNPFILTR: Received IOCTL_QUERY_DEVICE_COUNT
> PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID_SIZE for PDO 0x8210FBF0
> PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID for PDO 0x8210FBF0
> PNPFILTR: Received IOCTL_REBALANCE_DEVICE for PDO 0x8210FBF0
> PNPFILTR: Calling IoInvalidateDeviceState on PDO 8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> status 0x00000000 and information 0x00000014
> PNPFILTR: Recieved Query Result
> PNPFILTR: Waiting for test to be completed - will wait for 50 seconds
> PNPFILTR: Received IRP_MN_QUERY_STOP_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: FilterQueryStop returning 0x00000004 for stack with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> passing down
> PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> 0x8210FBF0
> PNPFILTR: Fake(new) Requirements created for PDO 0x8210FBF0
> PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_STOP_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_STOP_DEVICE to get processed for the PDO
> 8210FBF0 is 31 miliseconds
> PNPFILTR: Completing FilterStop with status 0x4 for stack with PDO 0x8210fbf0
> PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> 8210FBF0 is 266 miliseconds
> PNPFILTR: Start: Test Event cleared
> PNPFILTR: Irp recorded, sequence count = 7
> PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> PNPFILTR: Query Result Wait Satisfied... 7
> PNPFILTR: Number of IRPs Stored... 7
> PNPFILTR: Query Result - Releasing the remove
> PNPFILTR: Query Result -Result Stored Event set
> Relevant Sequence of Irps:
> IRP_MN_QUERY_PNP_DEVICE_STATE
> IRP_MN_QUERY_STOP_DEVICE
> IRP_MN_QUERY_RESOURCE_REQUIREMENTS
> IRP_MN_FILTER_RESOURCE_REQUIREMENTS
> IRP_MN_QUERY_INTERFACE
> IRP_MN_STOP_DEVICE
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: FilterQueryRemove returning 0x00000004 for stack with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> IRP_MN_START_DEVICE
> PNPFILTR: Deleting the global control object
> PNPFILTR: FilterRemove returning 0x00000004 for stack with PDO 0x8210FBF0
>
> *** Fatal System Error: 0x000000c4
> (0x00000060,0x00000040,0x000000A0,0x00000004)
>
> Break instruction exception - code 80000003 (first chance)
>
> A fatal system error has occurred.
> Debugger entered on first try; Bugcheck callbacks have not been invoked.
>
> A fatal system error has occurred.
>
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Loading Kernel Symbols
> .................................................. .................................................. ................
> Loading User Symbols
>
> Loading unloaded module list
> ..................
> *** ERROR: Module load completed but symbols could not be loaded for
> cmaudio.sys
> *** WARNING: Unable to verify timestamp for fltMgr.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> fltMgr.sys
> *** WARNING: Unable to verify timestamp for nv4_disp.dll
> *** ERROR: Module load completed but symbols could not be loaded for
> prepdrv.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> asyncmac.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> edgevcom.sys
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> drmk.sys -
> *** ERROR: Module load completed but symbols could not be loaded for
> pnpfiltr.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> pciwdm.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> usbser.sys
> *** WARNING: Unable to verify timestamp for Null.SYS
> *** ERROR: Module load completed but symbols could not be loaded for Null.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> smsmdm.sys
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck C4, {60, 40, a0, 4}
>
> Probably caused by : usbser.sys
>
> Followup: MachineOwner
> ---------
>
> nt!RtlpBreakWithStatusInstruction:
> 804e3592 cc int 3
> kd> !analyze -v
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
> A device driver attempting to corrupt the system has been caught. This is
> because the driver was specified in the registry as being suspect (by the
> administrator) and the kernel has enabled substantial checking of this driver.
> If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
> will
> be among the most commonly seen crashes.
> Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
> Typically the code is 0x1001 (deadlock detected) and you can
> issue a '!deadlock' KD command to get more information.
> Arguments:
> Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
> unloading.
> Arg2: 00000040, paged bytes
> Arg3: 000000a0, nonpaged bytes,
> Arg4: 00000004, total # of (paged+nonpaged) allocations that weren't freed.
> To get the name of the driver at fault, type
> dp ViBadDriver l1; dS @$p
> Then type !verifier 3 drivername.sys for info on the allocations
> that were leaked that caused the bugcheck.
>
> Debugging Details:
> ------------------
>
> *** No owner thread found for resource 80558660
> *** No owner thread found for resource 80558660
> *** No owner thread found for resource 80558660
>
> BUGCHECK_STR: 0xc4_60
>
> IMAGE_NAME: usbser.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3fec8a55
>
> MODULE_NAME: usbser
>
> FAULTING_MODULE: f9c1c000 usbser
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> PROCESS_NAME: System
>
> LOCK_ADDRESS: 805586e0 -- (!locks 805586e0)
>
> Resource @ nt!IopDeviceTreeLock (0x805586e0) Shared 1 owning threads
> Threads: 8255f8b8-01<*>
> 1 total locks, 1 locks currently held
>
> PNP_TRIAGE:
> Lock address : 0x805586e0
> Thread Count : 1
> Thread address: 0x8255f8b8
> Thread wait : 0x8afc1
>
> LAST_CONTROL_TRANSFER: from 80532487 to 804e3592
>
> STACK_TEXT:
> f9c5b6f8 80532487 00000003 f9c5ba54 00000000 nt!RtlpBreakWithStatusInstruction
> f9c5b744 80532f5e 00000003 82595f08 82595f08 nt!KiBugCheckDebugBreak+0x19
> f9c5bb24 8053354e 000000c4 00000060 00000040 nt!KeBugCheck2+0x574
> f9c5bb44 8066b831 000000c4 00000060 00000040 nt!KeBugCheckEx+0x1b
> f9c5bb6c 805f0457 820ead38 82310d98 82310dc0
> nt!MiVerifyingDriverUnloading+0x12a
> f9c5bb98 805c1a2d 820ead38 82310da8 f9c5bbc4 nt!MmUnloadSystemImage+0x17d
> f9c5bba8 80563af7 82310dc0 82310da8 00000000 nt!IopDeleteDriver+0x32
> f9c5bbc4 804e36d5 82310dc0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
> f9c5bbe8 805a0043 00000000 f9c5bc10 80563af7 nt!ObfDereferenceObject+0x5f
> f9c5bbf4 80563af7 823c62fc 823c62c0 00000000 nt!IopDeleteDevice+0x43
> f9c5bc10 804e36d5 823c62d8 00000000 ff7d7a08 nt!ObpRemoveObjectRoutine+0xdf
> f9c5bc34 8053154f 00000000 e2807798 00000001 nt!ObfDereferenceObject+0x5f
> f9c5bc54 8061bac3 e19ca3f8 00000015 e2807798
> nt!IopRemoveLockedDeviceNode+0x1de
> f9c5bc6c 8061bb2f 820e4768 00000002 e2807798 nt!IopDeleteLockedDeviceNode+0x34
> f9c5bca0 8061d8f6 8210fbf0 02807798 00000002
> nt!IopDeleteLockedDeviceNodes+0x3f
> f9c5bd34 805ec82d f9c5bd70 806ee778 e10ce838
> nt!PiProcessQueryRemoveAndEject+0x76b
> f9c5bd50 8059fbb1 f9c5bd70 8222cee0 8056167c
> nt!PiProcessTargetDeviceEvent+0x2a
> f9c5bd74 804e426b 8222cee0 00000000 8255f8b8 nt!PiWalkDeviceList+0x122
> f9c5bdac 8057d0f1 8222cee0 00000000 00000000 nt!ExpWorkerThread+0x100
> f9c5bddc 804f827a 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_NAME: MachineOwner
>
> FAILURE_BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27
>
> BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27
>
> Followup: MachineOwner
> ---------
>
> "Leo Havmøller" wrote:
>
> > "Lono" <Lono@discussions.microsoft.com> wrote in message
> > news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
> > >
> > > I tried to pass the Windows Logo Test for the driver of USB modem
> > > product
> > > of our company, however, the PnP Driver tests failed. A BSOD occued during
> > > PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck

 
Old 12-01-2008, 12:38 PM   #9
Alan
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

Hi there,

I had a similar issue on Windows XP. I raised an MS support request, the
problem was analysed and I received an errata code to enable me to complete
the submission with this failure included. I would suggest you follow the
same route if you require the driver to be signed.

Regards,
Alan

"Lono" wrote:

> The WinDbg indicated that BSOD occured when USBSer.sys was unloading. I don't
> know if BSOD was caused by USBSer.sys or my USB COM port device.
>
> The detailed information is here:
>
>
> Device description: A mobile device with a usb port. The USB port supports
> only virtual COM port functionality. The
>
> device conforms to USB CDCACM standard. The driver used on Windows is
> standard USBSer.sys which is provided by
>
> Microsoft.
>
> Operating system: Windows XP SP2 English(United States)
> Processor: x86Qualification program: Unclassified Qualification Level:
> Unclassified signature
> Windows Logo Kit Version: WLK 1.1
> USBSer.sys Version: version: 5.1.2600.2180
>
> I then tested the driver with PnpTest.exe with Verifier enabled.
>
> Verifier.exe version: 5.1.2600.0
> Pnpdtest.exe version: 3.4
>
> Verifier Enabled Settings:
> Special Pool
> Pool Tracking
> Force IRQL checking
> I/O verification
> Enhanced I/O verification
> Deadlock detection
> DMA checking
> Low resources simulation
>
> The verifier.exe is provided by Windows XP, and the pnpdtest.exe is provided
> by WDK. A BSOD can be reproduced by
>
> PNPDTest.exe->Rebalace Test-> NewResources.
>
> The information provided by WinDbg is listed below:
>
> ---------------------------------------------------------------------
> ************************************************** *****************************
> *
> * This is the string you add to your checkin description
> * Driver Verifier: Enabled for u*** ERROR: Module load completed but symbols
> could not be loaded for usbser.sys
> PNPFILTR: Events being initialized
> PNPFILTR: Received IRP_MN_QUERY_LEGACY_BUS_INFORMATION which I am simply
> passing down
> PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> passing down
> PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> 0x8210FBF0
> PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> 8210FBF0 is 281 miliseconds
> PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_CAPABILITIES which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> status 0x00000000 and information 0x00000000
> PNPFILTR: Passing down unhandled PNP IRP - minor function = 0xff
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_TEXT which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_ID which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> Running Rebalance Test(ForceResourceChange) on node with hwid:
> USB\Vid_0e8d&Pid_0003&Rev_0100
> PNPFILTR: Received IOCTL_QUERY_DEVICE_COUNT
> PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID_SIZE for PDO 0x8210FBF0
> PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID for PDO 0x8210FBF0
> PNPFILTR: Received IOCTL_REBALANCE_DEVICE for PDO 0x8210FBF0
> PNPFILTR: Calling IoInvalidateDeviceState on PDO 8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> status 0x00000000 and information 0x00000014
> PNPFILTR: Recieved Query Result
> PNPFILTR: Waiting for test to be completed - will wait for 50 seconds
> PNPFILTR: Received IRP_MN_QUERY_STOP_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: FilterQueryStop returning 0x00000004 for stack with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> passing down
> PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> 0x8210FBF0
> PNPFILTR: Fake(new) Requirements created for PDO 0x8210FBF0
> PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> PNPFILTR: Received IRP_MN_STOP_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_STOP_DEVICE to get processed for the PDO
> 8210FBF0 is 31 miliseconds
> PNPFILTR: Completing FilterStop with status 0x4 for stack with PDO 0x8210fbf0
> PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> 8210FBF0 is 266 miliseconds
> PNPFILTR: Start: Test Event cleared
> PNPFILTR: Irp recorded, sequence count = 7
> PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> PNPFILTR: Query Result Wait Satisfied... 7
> PNPFILTR: Number of IRPs Stored... 7
> PNPFILTR: Query Result - Releasing the remove
> PNPFILTR: Query Result -Result Stored Event set
> Relevant Sequence of Irps:
> IRP_MN_QUERY_PNP_DEVICE_STATE
> IRP_MN_QUERY_STOP_DEVICE
> IRP_MN_QUERY_RESOURCE_REQUIREMENTS
> IRP_MN_FILTER_RESOURCE_REQUIREMENTS
> IRP_MN_QUERY_INTERFACE
> IRP_MN_STOP_DEVICE
> PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> down
> PNPFILTR: Received IRP_MN_QUERY_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> PNPFILTR: FilterQueryRemove returning 0x00000004 for stack with PDO 0x8210FBF0
> PNPFILTR: Received IRP_MN_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> IRP_MN_START_DEVICE
> PNPFILTR: Deleting the global control object
> PNPFILTR: FilterRemove returning 0x00000004 for stack with PDO 0x8210FBF0
>
> *** Fatal System Error: 0x000000c4
> (0x00000060,0x00000040,0x000000A0,0x00000004)
>
> Break instruction exception - code 80000003 (first chance)
>
> A fatal system error has occurred.
> Debugger entered on first try; Bugcheck callbacks have not been invoked.
>
> A fatal system error has occurred.
>
> Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> Loading Kernel Symbols
> .................................................. .................................................. ................
> Loading User Symbols
>
> Loading unloaded module list
> ..................
> *** ERROR: Module load completed but symbols could not be loaded for
> cmaudio.sys
> *** WARNING: Unable to verify timestamp for fltMgr.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> fltMgr.sys
> *** WARNING: Unable to verify timestamp for nv4_disp.dll
> *** ERROR: Module load completed but symbols could not be loaded for
> prepdrv.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> asyncmac.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> edgevcom.sys
> *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> drmk.sys -
> *** ERROR: Module load completed but symbols could not be loaded for
> pnpfiltr.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> pciwdm.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> usbser.sys
> *** WARNING: Unable to verify timestamp for Null.SYS
> *** ERROR: Module load completed but symbols could not be loaded for Null.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> smsmdm.sys
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck C4, {60, 40, a0, 4}
>
> Probably caused by : usbser.sys
>
> Followup: MachineOwner
> ---------
>
> nt!RtlpBreakWithStatusInstruction:
> 804e3592 cc int 3
> kd> !analyze -v
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
> A device driver attempting to corrupt the system has been caught. This is
> because the driver was specified in the registry as being suspect (by the
> administrator) and the kernel has enabled substantial checking of this driver.
> If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
> will
> be among the most commonly seen crashes.
> Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
> Typically the code is 0x1001 (deadlock detected) and you can
> issue a '!deadlock' KD command to get more information.
> Arguments:
> Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
> unloading.
> Arg2: 00000040, paged bytes
> Arg3: 000000a0, nonpaged bytes,
> Arg4: 00000004, total # of (paged+nonpaged) allocations that weren't freed.
> To get the name of the driver at fault, type
> dp ViBadDriver l1; dS @$p
> Then type !verifier 3 drivername.sys for info on the allocations
> that were leaked that caused the bugcheck.
>
> Debugging Details:
> ------------------
>
> *** No owner thread found for resource 80558660
> *** No owner thread found for resource 80558660
> *** No owner thread found for resource 80558660
>
> BUGCHECK_STR: 0xc4_60
>
> IMAGE_NAME: usbser.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3fec8a55
>
> MODULE_NAME: usbser
>
> FAULTING_MODULE: f9c1c000 usbser
>
> DEFAULT_BUCKET_ID: DRIVER_FAULT
>
> PROCESS_NAME: System
>
> LOCK_ADDRESS: 805586e0 -- (!locks 805586e0)
>
> Resource @ nt!IopDeviceTreeLock (0x805586e0) Shared 1 owning threads
> Threads: 8255f8b8-01<*>
> 1 total locks, 1 locks currently held
>
> PNP_TRIAGE:
> Lock address : 0x805586e0
> Thread Count : 1
> Thread address: 0x8255f8b8
> Thread wait : 0x8afc1
>
> LAST_CONTROL_TRANSFER: from 80532487 to 804e3592
>
> STACK_TEXT:
> f9c5b6f8 80532487 00000003 f9c5ba54 00000000 nt!RtlpBreakWithStatusInstruction
> f9c5b744 80532f5e 00000003 82595f08 82595f08 nt!KiBugCheckDebugBreak+0x19
> f9c5bb24 8053354e 000000c4 00000060 00000040 nt!KeBugCheck2+0x574
> f9c5bb44 8066b831 000000c4 00000060 00000040 nt!KeBugCheckEx+0x1b
> f9c5bb6c 805f0457 820ead38 82310d98 82310dc0
> nt!MiVerifyingDriverUnloading+0x12a
> f9c5bb98 805c1a2d 820ead38 82310da8 f9c5bbc4 nt!MmUnloadSystemImage+0x17d
> f9c5bba8 80563af7 82310dc0 82310da8 00000000 nt!IopDeleteDriver+0x32
> f9c5bbc4 804e36d5 82310dc0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
> f9c5bbe8 805a0043 00000000 f9c5bc10 80563af7 nt!ObfDereferenceObject+0x5f
> f9c5bbf4 80563af7 823c62fc 823c62c0 00000000 nt!IopDeleteDevice+0x43
> f9c5bc10 804e36d5 823c62d8 00000000 ff7d7a08 nt!ObpRemoveObjectRoutine+0xdf
> f9c5bc34 8053154f 00000000 e2807798 00000001 nt!ObfDereferenceObject+0x5f
> f9c5bc54 8061bac3 e19ca3f8 00000015 e2807798
> nt!IopRemoveLockedDeviceNode+0x1de
> f9c5bc6c 8061bb2f 820e4768 00000002 e2807798 nt!IopDeleteLockedDeviceNode+0x34
> f9c5bca0 8061d8f6 8210fbf0 02807798 00000002
> nt!IopDeleteLockedDeviceNodes+0x3f
> f9c5bd34 805ec82d f9c5bd70 806ee778 e10ce838
> nt!PiProcessQueryRemoveAndEject+0x76b
> f9c5bd50 8059fbb1 f9c5bd70 8222cee0 8056167c
> nt!PiProcessTargetDeviceEvent+0x2a
> f9c5bd74 804e426b 8222cee0 00000000 8255f8b8 nt!PiWalkDeviceList+0x122
> f9c5bdac 8057d0f1 8222cee0 00000000 00000000 nt!ExpWorkerThread+0x100
> f9c5bddc 804f827a 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
> 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_NAME: MachineOwner
>
> FAILURE_BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27
>
> BUCKET_ID: 0xc4_60_VRF_IMAGE_usbser.sys_DATE_2003_12_27
>
> Followup: MachineOwner
> ---------
>
> "Leo Havmøller" wrote:
>
> > "Lono" <Lono@discussions.microsoft.com> wrote in message
> > news:261AF5CD-21A5-439D-847C-509B49D75A8E@microsoft.com...
> > >
> > > I tried to pass the Windows Logo Test for the driver of USB modem
> > > product
> > > of our company, however, the PnP Driver tests failed. A BSOD occued during
> > > PnPtest.exe->Rebalance Test with verifier option enabled. The bugcheck

 
Old 15-01-2008, 05:15 PM   #10
Lono
Guest
 
Posts: n/a
Re: USBSer.sys causes BSOD

Dear Alan,
Thnak you for your reply. Would you tell me which version of WLK you used
and the errata applied?
Besides, how did you get support from Microsoft? I had sent a email to
WHQL@MS, but they just tell me to pay first!

Thanks.

"Alan" wrote:

> Hi there,
>
> I had a similar issue on Windows XP. I raised an MS support request, the
> problem was analysed and I received an errata code to enable me to complete
> the submission with this failure included. I would suggest you follow the
> same route if you require the driver to be signed.
>
> Regards,
> Alan
>
> "Lono" wrote:
>
> > The WinDbg indicated that BSOD occured when USBSer.sys was unloading. I don't
> > know if BSOD was caused by USBSer.sys or my USB COM port device.
> >
> > The detailed information is here:
> >
> >
> > Device description: A mobile device with a usb port. The USB port supports
> > only virtual COM port functionality. The
> >
> > device conforms to USB CDCACM standard. The driver used on Windows is
> > standard USBSer.sys which is provided by
> >
> > Microsoft.
> >
> > Operating system: Windows XP SP2 English(United States)
> > Processor: x86Qualification program: Unclassified Qualification Level:
> > Unclassified signature
> > Windows Logo Kit Version: WLK 1.1
> > USBSer.sys Version: version: 5.1.2600.2180
> >
> > I then tested the driver with PnpTest.exe with Verifier enabled.
> >
> > Verifier.exe version: 5.1.2600.0
> > Pnpdtest.exe version: 3.4
> >
> > Verifier Enabled Settings:
> > Special Pool
> > Pool Tracking
> > Force IRQL checking
> > I/O verification
> > Enhanced I/O verification
> > Deadlock detection
> > DMA checking
> > Low resources simulation
> >
> > The verifier.exe is provided by Windows XP, and the pnpdtest.exe is provided
> > by WDK. A BSOD can be reproduced by
> >
> > PNPDTest.exe->Rebalace Test-> NewResources.
> >
> > The information provided by WinDbg is listed below:
> >
> > ---------------------------------------------------------------------
> > ************************************************** *****************************
> > *
> > * This is the string you add to your checkin description
> > * Driver Verifier: Enabled for u*** ERROR: Module load completed but symbols
> > could not be loaded for usbser.sys
> > PNPFILTR: Events being initialized
> > PNPFILTR: Received IRP_MN_QUERY_LEGACY_BUS_INFORMATION which I am simply
> > passing down
> > PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> > passing down
> > PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> > 0x8210FBF0
> > PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> > with PDO 0x8210FBF0
> > PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> > PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> > 8210FBF0 is 281 miliseconds
> > PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> > PNPFILTR: Received IRP_MN_QUERY_CAPABILITIES which I am simply passing down
> > PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> > PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> > status 0x00000000 and information 0x00000000
> > PNPFILTR: Passing down unhandled PNP IRP - minor function = 0xff
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> > down
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> > down
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_TEXT which I am simply passing down
> > PNPFILTR: Received IRP_MN_QUERY_ID which I am simply passing down
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> > down
> > PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> > PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> > down
> > Running Rebalance Test(ForceResourceChange) on node with hwid:
> > USB\Vid_0e8d&Pid_0003&Rev_0100
> > PNPFILTR: Received IOCTL_QUERY_DEVICE_COUNT
> > PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID_SIZE for PDO 0x8210FBF0
> > PNPFILTR: Received IOCTL_QUERY_HARDWARE_ID for PDO 0x8210FBF0
> > PNPFILTR: Received IOCTL_REBALANCE_DEVICE for PDO 0x8210FBF0
> > PNPFILTR: Calling IoInvalidateDeviceState on PDO 8210FBF0
> > PNPFILTR: Received IRP_MN_QUERY_PNP_DEVICE_STATE for stack with PDO 0x8210FBF0
> > PNPFILTR: Completing IRP_MN_QUERY_PNP_DEVICE_STATE for PDO 0x8210FBF0 with
> > status 0x00000000 and information 0x00000014
> > PNPFILTR: Recieved Query Result
> > PNPFILTR: Waiting for test to be completed - will wait for 50 seconds
> > PNPFILTR: Received IRP_MN_QUERY_STOP_DEVICE for stack with PDO 0x8210FBF0
> > PNPFILTR: FilterQueryStop returning 0x00000004 for stack with PDO 0x8210FBF0
> > PNPFILTR: Received IRP_MN_QUERY_RESOURCE_REQUIREMENTS which I am simply
> > passing down
> > PNPFILTR: Received IRP_MN_FILTER_RESOURCE_REQUIREMENT for stack with PDO
> > 0x8210FBF0
> > PNPFILTR: Fake(new) Requirements created for PDO 0x8210FBF0
> > PNPFILTR: FilterFilterResourceRequirement returning 0x00000004 for stack
> > with PDO 0x8210FBF0
> > PNPFILTR: Received IRP_MN_QUERY_INTERFACE which I am simply passing down
> > PNPFILTR: Received IRP_MN_STOP_DEVICE for stack with PDO 0x8210FBF0
> > PNPFILTR: Time taken for IRP_MN_STOP_DEVICE to get processed for the PDO
> > 8210FBF0 is 31 miliseconds
> > PNPFILTR: Completing FilterStop with status 0x4 for stack with PDO 0x8210fbf0
> > PNPFILTR: Received IRP_MN_START_DEVICE for stack with PDO 0x8210FBF0
> > PNPFILTR: Time taken for IRP_MN_START_DEVICE to get processed for the PDO
> > 8210FBF0 is 266 miliseconds
> > PNPFILTR: Start: Test Event cleared
> > PNPFILTR: Irp recorded, sequence count = 7
> > PNPFILTR: Completing Start request with status == 0x00000002 PDO = 0x8210FBF0
> > PNPFILTR: Query Result Wait Satisfied... 7
> > PNPFILTR: Number of IRPs Stored... 7
> > PNPFILTR: Query Result - Releasing the remove
> > PNPFILTR: Query Result -Result Stored Event set
> > Relevant Sequence of Irps:
> > IRP_MN_QUERY_PNP_DEVICE_STATE
> > IRP_MN_QUERY_STOP_DEVICE
> > IRP_MN_QUERY_RESOURCE_REQUIREMENTS
> > IRP_MN_FILTER_RESOURCE_REQUIREMENTS
> > IRP_MN_QUERY_INTERFACE
> > IRP_MN_STOP_DEVICE
> > PNPFILTR: Received IRP_MN_QUERY_DEVICE_RELATIONS which I am simply passing
> > down
> > PNPFILTR: Received IRP_MN_QUERY_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> > PNPFILTR: FilterQueryRemove returning 0x00000004 for stack with PDO 0x8210FBF0
> > PNPFILTR: Received IRP_MN_REMOVE_DEVICE for stack with PDO 0x8210FBF0
> > IRP_MN_START_DEVICE
> > PNPFILTR: Deleting the global control object
> > PNPFILTR: FilterRemove returning 0x00000004 for stack with PDO 0x8210FBF0
> >
> > *** Fatal System Error: 0x000000c4
> > (0x00000060,0x00000040,0x000000A0,0x00000004)
> >
> > Break instruction exception - code 80000003 (first chance)
> >
> > A fatal system error has occurred.
> > Debugger entered on first try; Bugcheck callbacks have not been invoked.
> >
> > A fatal system error has occurred.
> >
> > Connected to Windows XP 2600 x86 compatible target, ptr64 FALSE
> > Loading Kernel Symbols
> > .................................................. .................................................. ................
> > Loading User Symbols
> >
> > Loading unloaded module list
> > ..................
> > *** ERROR: Module load completed but symbols could not be loaded for
> > cmaudio.sys
> > *** WARNING: Unable to verify timestamp for fltMgr.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > fltMgr.sys
> > *** WARNING: Unable to verify timestamp for nv4_disp.dll
> > *** ERROR: Module load completed but symbols could not be loaded for
> > prepdrv.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > asyncmac.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > edgevcom.sys
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols for
> > drmk.sys -
> > *** ERROR: Module load completed but symbols could not be loaded for
> > pnpfiltr.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > pciwdm.sys
> > *** ERROR: Module load completed but symbols could not be loaded for
> > usbser.sys
> > *** WARNING: Unable to verify timestamp for Null.SYS
> > *** ERROR: Module load completed but symbols could not be loaded for Null.SYS
> > *** ERROR: Module load completed but symbols could not be loaded for
> > smsmdm.sys
> > ************************************************** *****************************
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> > ************************************************** *****************************
> >
> > Use !analyze -v to get detailed debugging information.
> >
> > BugCheck C4, {60, 40, a0, 4}
> >
> > Probably caused by : usbser.sys
> >
> > Followup: MachineOwner
> > ---------
> >
> > nt!RtlpBreakWithStatusInstruction:
> > 804e3592 cc int 3
> > kd> !analyze -v
> > ************************************************** *****************************
> > *
> > *
> > * Bugcheck Analysis
> > *
> > *
> > *
> > ************************************************** *****************************
> >
> > DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
> > A device driver attempting to corrupt the system has been caught. This is
> > because the driver was specified in the registry as being suspect (by the
> > administrator) and the kernel has enabled substantial checking of this driver.
> > If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA
> > will
> > be among the most commonly seen crashes.
> > Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error codes.
> > Typically the code is 0x1001 (deadlock detected) and you can
> > issue a '!deadlock' KD command to get more information.
> > Arguments:
> > Arg1: 00000060, A driver has forgotten to free its pool allocations prior to
> > unloading.
> > Arg2: 00000040, paged bytes
> > Arg3: 000000a0, nonpaged bytes,
> > Arg4: 00000004, total # of (paged+nonpaged) allocations that weren't freed.
> > To get the name of the driver at fault, type
> > dp ViBadDriver l1; dS @$p
> > Then type !verifier 3 drivername.sys for info on the allocations
> > that were leaked that caused the bugcheck.
> >
> > Debugging Details:
> > ------------------
> >
> > *** No owner thread found for resource 80558660
> > *** No owner thread found for resource 80558660
> > *** No owner thread found for resource 80558660
> >
> > BUGCHECK_STR: 0xc4_60
> >
> > IMAGE_NAME: usbser.sys
> >
> > DEBUG_FLR_IMAGE_TIMESTAMP: 3fec8a55
> >
> > MODULE_NAME: usbser
> >
> > FAULTING_MODULE: f9c1c000 usbser
> >
> > DEFAULT_BUCKET_ID: DRIVER_FAULT
> >
> > PROCESS_NAME: System
> >
> > LOCK_ADDRESS: 805586e0 -- (!locks 805586e0)
> >
> > Resource @ nt!IopDeviceTreeLock (0x805586e0) Shared 1 owning threads
> > Threads: 8255f8b8-01<*>
> > 1 total locks, 1 locks currently held
> >
> > PNP_TRIAGE:
> > Lock address : 0x805586e0
> > Thread Count : 1
> > Thread address: 0x8255f8b8
> > Thread wait : 0x8afc1
> >
> > LAST_CONTROL_TRANSFER: from 80532487 to 804e3592
> >
> > STACK_TEXT:
> > f9c5b6f8 80532487 00000003 f9c5ba54 00000000 nt!RtlpBreakWithStatusInstruction
> > f9c5b744 80532f5e 00000003 82595f08 82595f08 nt!KiBugCheckDebugBreak+0x19
> > f9c5bb24 8053354e 000000c4 00000060 00000040 nt!KeBugCheck2+0x574
> > f9c5bb44 8066b831 000000c4 00000060 00000040 nt!KeBugCheckEx+0x1b
> > f9c5bb6c 805f0457 820ead38 82310d98 82310dc0
> > nt!MiVerifyingDriverUnloading+0x12a
> > f9c5bb98 805c1a2d 820ead38 82310da8 f9c5bbc4 nt!MmUnloadSystemImage+0x17d
> > f9c5bba8 80563af7 82310dc0 82310da8 00000000 nt!IopDeleteDriver+0x32
> > f9c5bbc4 804e36d5 82310dc0 00000000 00000000 nt!ObpRemoveObjectRoutine+0xdf
> > f9c5bbe8 805a0043 00000000 f9c5bc10 80563af7 nt!ObfDereferenceObject+0x5f
> > f9c5bbf4 80563af7 823c62fc 823c62c0 00000000 nt!IopDeleteDevice+0x43
> > f9c5bc10 804e36d5 823c62d8 00000000 ff7d7a08 nt!ObpRemoveObjectRoutine+0xdf
> > f9c5bc34 8053154f 00000000 e2807798 00000001 nt!ObfDereferenceObject+0x5f
> > f9c5bc54 8061bac3 e19ca3f8 00000015 e2807798
> > nt!IopRemoveLockedDeviceNode+0x1de
> > f9c5bc6c 8061bb2f 820e4768 00000002 e2807798 nt!IopDeleteLockedDeviceNode+0x34
> > f9c5bca0 8061d8f6 8210fbf0 02807798 00000002
> > nt!IopDeleteLockedDeviceNodes+0x3f
> > f9c5bd34 805ec82d f9c5bd70 806ee778 e10ce838
> > nt!PiProcessQueryRemoveAndEject+0x76b
> > f9c5bd50 8059fbb1 f9c5bd70 8222cee0 8056167c
> > nt!PiProcessTargetDeviceEvent+0x2a
> > f9c5bd74 804e426b 8222cee0 00000000 8255f8b8 nt!PiWalkDeviceList+0x122
> > f9c5bdac 8057d0f1 8222cee0 00000000 00000000 nt!ExpWorkerThread+0x100
> > f9c5bddc 804f827a 804e4196 00000001 00000000 nt!PspSystemThreadStartup+0x34
> > 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
> >
> >
> > STACK_COMMAND: kb
> >

 
 

Thread Tools
Display Modes



< Home - Windows Help - MS Office Help - Hardware Support >


New To Site? Need Help?

All times are GMT. The time now is 12:44 PM.


vBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO
Copyright © 2005-2013, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional