|
|||||||
|
|
|
 |
|
|
Strumenti |
05-07-2009, 14:18
|
#1 |
|
Member
Iscritto dal: Nov 2006
Messaggi: 124
|
USBSTOR.SYS - Blu Screen
Ciao a tutti, ho un problema che mi affligge da quando ho acquistato il pc, descrivo il problema dall'inizio.
Quando comprai il pc c'era preinstallata una versione pirata di windows xp home edition, avendo io l'originale formattai subito il pc ed installai tutto per bene. dopo qualche mese il pc iniziava ad andarmi in crash a random. Dopo aver settato windows in modo che non si riavviasse in automatico alla presenza di un errore vidi che il motivo del riavvio era il seguente: Codice:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini062209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Jun 22 14:08:14.046 2009 (GMT+2)
System Uptime: 0 days 0:52:18.034
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..............
Unable to load image USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {21d253e0, 2, 1, b9f437b3}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*** WARNING: Unable to verify timestamp for USBSTOR.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBSTOR.SYS
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for Fastfat.SYS
*** ERROR: Module load completed but symbols could not be loaded for Fastfat.SYS
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : USBSTOR.SYS ( USBSTOR+165f )
Followup: MachineOwner
---------
il file "USBSTOR.SYS" noto ch el'errore si presenta di tanto in tanto quando utilizzo la rotellina del mouse in determinati programmi, ma non sempre ho provato anche a camiare mouse, ma senza risultati. come posso risolvere?? il pc lo usa mio padre, è stracolmo di dati e a formattare non se ne parla! Volevo provare a sostituire il suddetto file, ma non riesco a trovarlo da nessuna parte. dovrei tentare un ripristino di windows?? (il ripristino non l'ho mai fatto, causa la perdita dei collegamenti sul desktop ? o si limita a sostituire i file di sistema? ) grazie 
|
|
|
|
05-07-2009, 19:54
|
#2 |
|
Senior Member
Iscritto dal: Sep 2007
Città: poggio mirteto
Messaggi: 658
|
il file usbstor.sys si trova in C:\WINDOWS\inf.Però prima devi abilitare i file nascosti.
|
|
|
|
|
05-07-2009, 20:45
|
#3 | |
|
Member
Iscritto dal: Nov 2006
Messaggi: 124
|
Quote:
no intendevo dire che non trovo il file "nuovo" (da internet/cd).vorrei provare a sostituirlo, magari si è danneggiato, boh |
|
|
|
|
|
06-07-2009, 09:49
|
#4 |
|
Senior Member
Iscritto dal: Sep 2007
Città: poggio mirteto
Messaggi: 658
|
|
|
|
|
|
06-07-2009, 10:21
|
#5 |
|
Member
Iscritto dal: Nov 2006
Messaggi: 124
|
su quel sito l'avevo trovato, ma un file del genere cell'ha solo uno strano sito che non si occupa manco direttamente di informatica??
cioè un file del genere viene dato in giro da un sito che si pubblicizza come "portale tuttofare" è come se un idraulico nel tempo libero andasse a svolgere importanti calcoli ingegneristici alla nasa  almeno mi ha fatto questa impressione! mi puzza boh se mi dite che quel sito è sicuro ok Ultima modifica di magen1 : 06-07-2009 alle 10:34. |
|
|
|
|
06-07-2009, 14:32
|
#6 |
|
Member
Iscritto dal: Nov 2006
Messaggi: 124
|
solo ora ho notato che il vero problema non è il file sopra indicato ma è NTFS.SYS
infatti il crash mi si è ripresentato, ho letto direttamente la scehrmata blu e c'era ntfs.sys al riavvio vado a controllare in windows/minidump e noto che non ha salvato alcun file DMP, quindi il file che avevo letto era un vecchio crash! detto questo, il problema riguarda NTFS.SYS |
|
|
|
|
|
| Strumenti | |
|
|
Tutti gli orari sono GMT +1. Ora sono le: 23:59.
