Bsod

HP 6005 Pro System running OEM Win 7 x32 bit Pro

4 Gigs of ram

Several USB to serial adapters (THink the issue lies with them)

Any help is appreciated

SirPorl said:

HP 6005 Pro System running OEM Win 7 x32 bit Pro

4 Gigs of ram

Several USB to serial adapters (Think the issue lies with them)

Any help is appreciated

Though serial.sys is the cause of all of these, it is used in conjunction with some of the below drivers (ser2pl.sys) and it is almost 10 years old. If there is an update you may be able to get it to work if not, there is now way something written for XP will work in win 7.

Good luck

Ancient drivers. These add least need updating

Code:

ser2pl.sys    1/15/2001 1:52:48    0x3a629e40    0x97ee2000    0x97eecc60        0x0000ac60                    
SENTINEL.SYS    6/19/2001 18:35:16    0x3b2fe1b4    0x92bec000    0x92bfe000        0x00012000                    
secdrv.SYS    9/13/2006 8:18:32    0x45080528    0x99306000    0x99310000        0x0000a000                    
USA19H2kp.SYS    5/29/2007 18:32:56    0x465cb828    0x97f9b000    0x97fa0e80        0x00005e80                    
USA19H2k.sys    10/30/2007 14:41:44    0x472788f8    0x97eef000    0x97f9ae00        0x000abe00                    
PxHelp20.sys    3/12/2008 20:57:44    0x47d88a18    0x8c3dd000    0x8c3e6200        0x00009200                    
atikmdag.sys    4/24/2009 5:50:20    0x49f1996c    0x9200c000    0x92460000        0x00454000                    
AtiPcie.sys    5/5/2009 10:00:16    0x4a005480    0x8c7e3000    0x8c7eb000        0x00008000                    
spldr.sys    5/11/2009 11:13:47    0x4a084ebb    0x8c9f6000    0x8c9fe000        0x00008000                    
amdxata.sys    5/19/2009 12:57:35    0x4a12f30f    0x8c38f000    0x8c398000        0x00009000                    
b57nd60x.sys    5/28/2009 20:58:23    0x4a1f413f    0x9256f000    0x925b0000        0x00041000                    
RTKVHDA.sys    7/2/2009 4:28:49    0x4a4c7dd1    0x97c08000    0x97e8ed80        0x00286d80

These were all (virtually identical) caused by your serial devices as you suspected. There is a known bug "IF" the enumeration in registry is set to "1". If you have not done that you should run a system file check to verify and repair serial.sys and the other OS files.

Code:

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


Loading Dump File [C:\Users\K\Desktop\022211-10639-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c02000 PsLoadedModuleList = 0x82d4a810
Debug session time: Tue Feb 22 11:17:36.014 2011 (GMT-5)
System Uptime: 0 days 0:21:34.247
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {807c, 2, 1, 830158b3}

Probably caused by : serial.sys ( serial!SerialIntervalReadTimeout+13 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000807c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 830158b3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d6a718
Unable to read MiSystemVaType memory at 82d4a160
 0000807c 

CURRENT_IRQL:  2

FAULTING_IP: 
hal!KeAcquireQueuedSpinLockRaiseToSynch+33
830158b3 8902            mov     dword ptr [edx],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  82d28aa0 -- (.trap 0xffffffff82d28aa0)
ErrCode = 00000002
eax=82d2c170 ebx=82d35280 ecx=82d6b302 edx=0000807c esi=00000000 edi=82d28ba0
eip=830158b3 esp=82d28b14 ebp=82d28b1c iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
hal!KeAcquireQueuedSpinLockRaiseToSynch+0x33:
830158b3 8902            mov     dword ptr [edx],eax  ds:0023:0000807c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 830158b3 to 82c4882b

STACK_TEXT:  
82d28aa0 830158b3 badb0d00 0000807c 00000000 nt!KiTrap0E+0x2cf
82d28b14 82cbd034 82d28b38 90f20e39 82d28b34 hal!KeAcquireQueuedSpinLockRaiseToSynch+0x33
82d28b1c 90f20e39 82d28b34 00000000 00000001 nt!IoAcquireCancelSpinLock+0xe
82d28b38 82c6c04d 8690cb8c 8690c948 04653e1f serial!SerialIntervalReadTimeout+0x13
82d28b7c 82c6bff1 82d2bd20 82d28ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82d28c68 82c6beae 82d2bd20 82d28ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82d28cdc 82c6a20e 00014414 858448a0 82d35280 nt!KiTimerExpiration+0x25c
82d28d20 82c6a038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82d28d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
serial!SerialIntervalReadTimeout+13
90f20e39 8b750c          mov     esi,dword ptr [ebp+0Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  serial!SerialIntervalReadTimeout+13

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: serial

IMAGE_NAME:  serial.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc71d

FAILURE_BUCKET_ID:  0xA_serial!SerialIntervalReadTimeout+13

BUCKET_ID:  0xA_serial!SerialIntervalReadTimeout+13

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

0: kd> lmvm serial
start    end        module name
90f1c000 90f36000   serial     (pdb symbols)          c:\symbols\serial.pdb\B81C98B2B3EB4E4E847D36C8A6474A1A2\serial.pdb
    Loaded symbol image file: serial.sys
    Mapped memory image file: C:\Symbols\serial.sys\4A5BC71D1a000\serial.sys
    Image path: \SystemRoot\system32\DRIVERS\serial.sys
    Image name: serial.sys
    Timestamp:        Mon Jul 13 19:45:33 2009 (4A5BC71D)
    CheckSum:         00023A45
    ImageSize:        0001A000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     serial.sys
    OriginalFilename: serial.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Serial Device Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Thank you very much for taking the time to point me in the right direction ZigZag.

What registry key should I change to correct

There is a known bug "IF" the enumeration in registry is set to "1". If you have not done that you should run a system file check to verify and repair serial.sys and the other OS files.

Thanks