BSOD with terminal

[5t0rm]

Hi Guys,
The problem which I'm having his a persistent BSOD every time I use putty and my "trusty" old USB-to-COM adapter.
To me the strange thing is that it doesn't happen every time I connect the peripheral, sometimes is after some minutes, sometimes after a few seconds... I cant understand the pattern...

The baseline is that it only happens when I'm doing something with these two things, the USB-to-Serial adapter and putty.

I already updated the driver of the USB-to-Serial (Profilic) adapter with the latest one I could find.

I'm running Windows 7 Professional 32 bit edition OEM from HP and the system (and OS) is less than 1 year old. All the specs I could find/remember on the system are updated on my profile.


Can you please point me to the right direction?

Thank you all in advance.

 

[zigzag3143]

Hi Guys,
The problem which I'm having his a persistent BSOD every time I use putty and my "trusty" old USB-to-COM adapter.
To me the strange thing is that it doesn't happen every time I connect the peripheral, sometimes is after some minutes, sometimes after a few seconds... I cant understand the pattern...

The baseline is that it only happens when I'm doing something with these two things, the USB-to-Serial adapter and putty.

I already updated the driver of the USB-to-Serial (Profilic) adapter with the latest one I could find.

I'm running Windows 7 Professional 32 bit edition OEM from HP and the system (and OS) is less than 1 year old. All the specs I could find/remember on the system are updated on my profile.


Can you please point me to the right direction?

Thank you all in advance.

Well you nailed it. Your serial adapter is causing wdf01000.sys (Wdf01000.sys WDF Dynamic driver from Microsoft)to fail every single crash.

your choices are to find a newer driver (if exists), remove it, or live with the crashes.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\051811-22900-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.x86fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0x83050000 PsLoadedModuleList = 0x83198810
Debug session time: Wed May 18 11:45:30.286 2011 (GMT-4)
System Uptime: 0 days 5:11:51.472
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {60, 2, 0, 837a7a0c}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000060, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 837a7a0c, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 831b8718
Unable to read MiSystemVaType memory at 83198160
 00000060 

CURRENT_IRQL:  2

FAULTING_IP: 
Wdf01000!FxRequest::CompleteInternal+1a
837a7a0c 8b7960          mov     edi,dword ptr [ecx+60h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8d752b08 -- (.trap 0xffffffff8d752b08)
ErrCode = 00000000
eax=89ba1588 ebx=00000000 ecx=00000000 edx=00000001 esi=897d0500 edi=7682faf8
eip=837a7a0c esp=8d752b7c ebp=8d752b9c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
Wdf01000!FxRequest::CompleteInternal+0x1a:
837a7a0c 8b7960          mov     edi,dword ptr [ecx+60h] ds:0023:00000060=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 837a7a0c to 830967fb

STACK_TEXT:  
8d752b08 837a7a0c badb0d00 00000001 8d752bd8 nt!KiTrap0E+0x2cf
8d752b9c 8379a983 00000000 00000002 00000400 Wdf01000!FxRequest::CompleteInternal+0x1a
8d752bb4 9c1cc513 00000000 897d0500 00000000 Wdf01000!imp_WdfRequestCompleteWithInformation+0x114
WARNING: Stack unwind information not available. Following frames may be wrong.
8d752bd4 9c1cc5f1 7682faf8 00000000 00000001 ser2pl+0x6513
8d752bf0 9c1cc94a 897e36d0 7a059648 8d752c24 ser2pl+0x65f1
8d752c18 9c1cb66d 897e3690 00000000 00000000 ser2pl+0x694a
8d752c50 837b12f1 02364228 8d73b884 85c9bdd0 ser2pl+0x566d
8d752c64 837b1311 85c9be08 00000000 00000000 Wdf01000!FxDpc::DpcHandler+0x54
8d752c78 830b84f5 85c9be08 85c9bdd0 00000000 Wdf01000!FxDpc::FxDpcThunk+0x16
8d752cd4 830b8358 8d736120 8d73b800 00000000 nt!KiExecuteAllDpcs+0xf9
8d752d20 830b8178 00000000 0000000e ff7fffff nt!KiRetireDpcList+0xd5
8d752d24 00000000 0000000e ff7fffff ffffffff nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ser2pl+6513
9c1cc513 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ser2pl+6513

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ser2pl

IMAGE_NAME:  ser2pl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9a15d9

FAILURE_BUCKET_ID:  0xD1_ser2pl+6513

BUCKET_ID:  0xD1_ser2pl+6513

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