Od czasu do czasu wysypuje się komp. uruchomiłem Debuggera i poniżej podaję wynik:
Kod: Zaznacz cały
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini020712-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
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.111025-1629
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Feb 6 14:23:09.484 2012 (GMT+1)
System Uptime: 0 days 7:16:39.156
Loading Kernel Symbols
...............................................................
....................................................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {ba33, 2, 1, 806e7a8e}
Probably caused by : serial.sys ( serial!SerialCompleteRead+11 )
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: 0000ba33, 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: 806e7a8e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000ba33
CURRENT_IRQL: 2
FAULTING_IP:
hal!KeAcquireQueuedSpinLock+42
806e7a8e 8902 mov dword ptr [edx],eax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: Idle
LAST_CONTROL_TRANSFER: from 804eee9e to 806e7a8e
STACK_TEXT:
8055140c 804eee9e 80551428 ba1cac0c 80551424 hal!KeAcquireQueuedSpinLock+0x42
80551414 ba1cac0c 80551424 ffdff9c0 ba1cabfb nt!IoAcquireCancelSpinLock+0xe
80551428 80545eef 89cd2b84 89cd2978 00000000 serial!SerialCompleteRead+0x11
80551440 8055be60 ffdffc50 00000000 8055be60 nt!KiRetireDpcList+0x61
80551450 80545dd4 00000000 0000000e 00000000 nt!KiIdleThread0
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
STACK_COMMAND: kb
FOLLOWUP_IP:
serial!SerialCompleteRead+11
ba1cac0c 8b750c mov esi,dword ptr [ebp+0Ch]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: serial!SerialCompleteRead+11
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: serial
IMAGE_NAME: serial.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 48025be0
FAILURE_BUCKET_ID: 0xA_serial!SerialCompleteRead+11
BUCKET_ID: 0xA_serial!SerialCompleteRead+11
Followup: MachineOwner
---------
System ma wbudowany port RS232 i przejściówkę USB na RS232. Oba porty są używane.
Myślałem, że wysypuje się ta przejściówka, ale po wersji sterownika wynika, że pada sterownik wbudowanego portu.
Czy z powyższego można jeszcze coś wywnioskować, ewentualnie jakieś nowsze stery jakiś diagnostyczny soft dla portu?
HM - dzięki za pomoc
