schermo blu inserendo hdd esterno

[shinshi]

Quando collego all'usb l'hdd esterno da 160GB lacie xp si blocca con schermo blu.
le informazioni tecniche dell'errore sono:
stop: 0X0000007E (0XC0000005, 0XBA6C5D1C, 0XBA6C5C38, 0XBA6C5934)

Ho recentemente fatto upgrade del computer e la MB è la ECS PT880PRO-A che possiede 8 usb 2.0 alla quale ho fatto upgrade del bios. Il sistema operativo è xp pro sp2 con aggiornamenti automatici eseguiti. Mouse, stampante, lettore flash rom, adattatore BT funzionano perfettamente senza problemi. L'hdd funziona perfettamente su altri computer ed è formattato FAT32.
Qualcuno mi può aiutare?

Ho anche registrato l'evento di sistema mini******.dmp ma come posso fare per leggerlo?

[shinshi]

Ecco l'analisi fatta con WinDbg del file dump. Sembrerebbe un problema con USBPORT.SYS. Potete darmi qualche consiglio?




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


Loading Dump File [C:\WINDOWS\Minidump\Mini041208-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sat Apr 12 00:15:42.265 2008 (GMT+2)
System Uptime: 0 days 0:02:58.968
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, ba6bdca5, ba6bdc38, ba6bd934}

*** WARNING: Unable to verify timestamp for USBPORT.SYS


Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_CreateDevice+109 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: ba6bdca5, The address that the exception occurred at
Arg3: ba6bdc38, Exception Record Address
Arg4: ba6bd934, Context Record Address

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




EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

FAULTING_IP:
+ffffffffba6bdca5
ba6bdca5 0200 add al,byte ptr [eax]

EXCEPTION_RECORD: ba6bdc38 -- (.exr 0xffffffffba6bdc38)
ExceptionAddress: ba6bdca5
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT: ba6bd934 -- (.cxr 0xffffffffba6bd934)
eax=00000000 ebx=88e3e8d0 ecx=00000000 edx=00000000 esi=898670e0 edi=662c1db8
eip=ba6bdca5 esp=ba6bdd00 ebp=89867404 iopl=0 ov up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a07
ba6bdca5 0200 add al,byte ptr [eax] ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'istruzione a "0x%08lx" ha fatto riferimento alla memoria a "0x%08lx". La memoria non poteva essere "%s".

READ_ADDRESS: 00000000

FAILED_INSTRUCTION_ADDRESS:
+ffffffffba6bdca5
ba6bdca5 0200 add al,byte ptr [eax]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_DEREFERENCE

LAST_CONTROL_TRANSFER: from 88e3e8d0 to ba6bdca5

SYMBOL_ON_RAW_STACK: 1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffba6bdd1c

STACK_COMMAND: dds BA6BDD1C-0x20 ; kb

STACK_TEXT:
ba6bdcfc 00010a07
ba6bdd00 88e3e8d0
ba6bdd04 88e3e8d0
ba6bdd08 898677e8
ba6bdd0c 89867028
ba6bdd10 00000000
ba6bdd14 ba6bdd3c
ba6bdd18 b9745ab7 USBPORT!USBPORT_CreateDevice+0x109
ba6bdd1c 89867028
ba6bdd20 50457266
ba6bdd24 804e56fc nt!CcLazyWriteScan+0x16d
ba6bdd28 89867028
ba6bdd2c 00000000
ba6bdd30 89867458
ba6bdd34 6f6c6366
ba6bdd38 0001dd7c
ba6bdd3c ba6bdd7c
ba6bdd40 b973b700 USBPORT!USBPORT_GetResources+0x12
ba6bdd44 89867028
ba6bdd48 89867028
ba6bdd4c 898670e0
ba6bdd50 00000000
ba6bdd54 ba6bdd54
ba6bdd58 ba6bdd54
ba6bdd5c 89867028
ba6bdd60 898670ec
ba6bdd64 898670ec
ba6bdd68 2d747461
ba6bdd6c b9733fd9 USBPORT!USBPORT_WorkerThread+0x143
ba6bdd70 89867404
ba6bdd74 89867808
ba6bdd78 00000000


FOLLOWUP_IP:
USBPORT!USBPORT_CreateDevice+109
b9745ab7 ?? ???

SYMBOL_NAME: USBPORT!USBPORT_CreateDevice+109

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 453ca421

FAILURE_BUCKET_ID: 0x7E_BAD_IP_USBPORT!USBPORT_CreateDevice+109

BUCKET_ID: 0x7E_BAD_IP_USBPORT!USBPORT_CreateDevice+109

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