USB-Serial Gives Blue Screen every time

[syncron]

Hi,

I am running Win7 X64 pro on my Dell M4500.

Everything is fine, until I use any USB-Serial Adapter.

I have no problem using the USB with Disks, scanners etc.

I have verified I have the latest drivers for the device from the Manf. website.

The Hardware is fine, when I reboot my machine into Linux, using the same USB-Serial then it runs happily all day.. Linux has the drivers for the USB-Serial built in

I have attached the Minidump ..

Any help Much appreciated..

 

[zigzag3143]

Hi,

I am running Win7 X64 pro on my Dell M4500.

Everything is fine, until I use any USB-Serial Adapter.

I have no problem using the USB with Disks, scanners etc.

I have verified I have the latest drivers for the device from the Manf. website.

The Hardware is fine, when I reboot my machine into Linux, using the same USB-Serial then it runs happily all day.. Linux has the drivers for the USB-Serial built in

I have attached the Minidump ..

Any help Much appreciated..

This was caused by serpl64.sys which is the serial driver. Are the devices and all else win 7 compatible?

RE-install with the newest version you can find

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


Loading Dump File [C:\Users\K\Desktop\022511-19110-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`03659e50
Debug session time: Fri Feb 25 06:03:27.341 2011 (GMT-5)
System Uptime: 0 days 0:53:28.278
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa8007c4f010, eae, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ser2pl64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ser2pl64.sys
*** ERROR: Module load completed but symbols could not be loaded for ser2pl64.sys
Probably caused by : ser2pl64.sys ( ser2pl64+7b3d )

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

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

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8007c4f010, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000

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


IRP_ADDRESS:  fffffa8007c4f010

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003476365 to fffff8000348c740

STACK_TEXT:  
fffff880`035a09b8 fffff800`03476365 : 00000000`00000044 fffffa80`07c4f010 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`035a09c0 fffff880`00effa52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x3ec7e
fffff880`035a0aa0 fffff880`00ef013e : fffffa80`07c4f010 00000000`00000000 00000000`00000002 fffffa80`07c4f010 : Wdf01000!FxRequest::CompleteInternal+0x646
fffff880`035a0b50 fffff880`091e0b3d : fffffa80`0bfcf900 fffffa80`0727d020 fffffa80`0bfcf900 0000057f`f8d82fd8 : Wdf01000!imp_WdfRequestCompleteWithInformation+0x1aa
fffff880`035a0bc0 fffffa80`0bfcf900 : fffffa80`0727d020 fffffa80`0bfcf900 0000057f`f8d82fd8 fffffa80`0bfcf890 : ser2pl64+0x7b3d
fffff880`035a0bc8 fffffa80`0727d020 : fffffa80`0bfcf900 0000057f`f8d82fd8 fffffa80`0bfcf890 fffff880`091e0c2d : 0xfffffa80`0bfcf900
fffff880`035a0bd0 fffffa80`0bfcf900 : 0000057f`f8d82fd8 fffffa80`0bfcf890 fffff880`091e0c2d fffffa80`0727d1b0 : 0xfffffa80`0727d020
fffff880`035a0bd8 0000057f`f8d82fd8 : fffffa80`0bfcf890 fffff880`091e0c2d fffffa80`0727d1b0 00000000`00000000 : 0xfffffa80`0bfcf900
fffff880`035a0be0 fffffa80`0bfcf890 : fffff880`091e0c2d fffffa80`0727d1b0 00000000`00000000 fffffa80`0bfcf900 : 0x57f`f8d82fd8
fffff880`035a0be8 fffff880`091e0c2d : fffffa80`0727d1b0 00000000`00000000 fffffa80`0bfcf900 fffff880`044d0f79 : 0xfffffa80`0bfcf890
fffff880`035a0bf0 fffffa80`0727d1b0 : 00000000`00000000 fffffa80`0bfcf900 fffff880`044d0f79 fffffa80`0bfcf890 : ser2pl64+0x7c2d
fffff880`035a0bf8 00000000`00000000 : fffffa80`0bfcf900 fffff880`044d0f79 fffffa80`0bfcf890 00000000`00000000 : 0xfffffa80`0727d1b0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ser2pl64+7b3d
fffff880`091e0b3d ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ser2pl64+7b3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ser2pl64

IMAGE_NAME:  ser2pl64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47a1234d

FAILURE_BUCKET_ID:  X64_0x44_ser2pl64+7b3d

BUCKET_ID:  X64_0x44_ser2pl64+7b3d

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

2: kd> lmvm ser2pl64
start             end                 module name
fffff880`091d9000 fffff880`091f8000   ser2pl64 T (no symbols)           
    Loaded symbol image file: ser2pl64.sys
    Image path: \SystemRoot\system32\DRIVERS\ser2pl64.sys
    Image name: ser2pl64.sys
    Timestamp:        Wed Jan 30 20:24:29 2008 (47A1234D)
    CheckSum:         0001F28F
    ImageSize:        0001F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4