Errore sistema

Ciao a tutti, questa mattina mi sono trovato la famosa schermata blu in avvio del pc...ed ho dovuto chiudere e riavviare (xp, sp3).Nella visualizzazione eventi ho questo tipo di errore:

Codice errore 00000019, parametro1 00000020, parametro2 e247c070, parametro3 e247c3a0, parametro4 b866ede2.

Ho anche il mini-dump. Come posso fare per scovare l'errore? Grazie.

E' un errore troppo generico ,potrebbe essere qualche driver in conflitto.

Ha incominciato ad uscirti dopo aver installato qualche cosa in particolare?

Puoi vedere di aggiornare i driver della scheda video e audio che spesso sono quelli + soggetti a dare questi errori

Prova a vedere qui l'errore sembra simile al tuo anche se il S.O. è windows server 2003

http://support.microsoft.com/kb/892260/it

puoi utilizzare il debugging tool di Microsoft per analizzare il minidump e risalire alla causa del problema. Segui questo mio post che spiegava come fare.

Grazie per le risposte...io personalmente non ho installato nulla...il pc un paio di giorni fa mi ha fatto windows update, solo quello.

Ciao, volevo utilizzare windbg, ma mi da errore e cioè che i simboli non possono essere caricati, probabile causa ntoskrnl.exe, come si inizializzano questi simboli? Grazie

l'intera discussione in cui si utilizzava il windebugger era questa.
A parte l'errore sui simboli, il modulo su cui si verifica l'errore dovrebbe comunque essere visualizzato in fondo a tutti i messaggi:

Probably caused by : (nome modulo)

Ciao, quando apro il dump vedo queste righe: (il problema quindi dovrebbe essere ntoskrnl.exe) Cosè?

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


Loading Dump File [C:\Documents and Settings\utente\Desktop\Mini121408-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Dec 14 22:40:49.421 2008 (GMT+1)
System Uptime: 0 days 1:10:22.113
*********************************************************************
* 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
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8166d, 0, 0}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+6067a )

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

troppi errori, meglio caricare i simboli.
La procedura è descritta qua

Nel dettaglio:

To set up the debugger to do this, verify that you have a live Internet connection and set the symbol file path in WinDbg by selecting File | Symbol File Path. Then enter the following string: SRV*c:\local cache*http://msdl.microsoft.com/download/symbols
Substituting your own directory path for c:\local cache. For example, if you want the symbols to be placed in c:\symbols, then set your symbol path to
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
The location of the symbol table is up to you.


In pratica -con il PC collegato ad internet- devi selezionare dal menù del debugger:
File-> symbol file path
ed immettere la stringa:
SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols

per sicurezza dovresti impostare la variabile di ambiente _NT_SYMBOL_PATH
al valore della directory dove sono i simboli che hai scaricato :

C:\windows\symbols


per ulteriori chiarimenti leggi anche questa pagina

Ciao, questo è il risultato:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\utente\Desktop\Mini121408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\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 Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Dec 14 22:40:49.421 2008 (GMT+1)
System Uptime: 0 days 1:10:22.113
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8166d, 0, 0}



Probably caused by : memory_corruption ( nt!MiDecrementShareCount+4f )

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

0: kd> .restart /f

Loading Dump File [C:\Documents and Settings\utente\Desktop\Mini121408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\windows\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 Personal
Built by: 2600.xpsp_sp3_gdr.080814-1236
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sun Dec 14 22:40:49.421 2008 (GMT+1)
System Uptime: 0 days 1:10:22.113
Loading Kernel Symbols
..................................................................................................................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8166d, 0, 0}



Probably caused by : memory_corruption ( nt!MiDecrementShareCount+4f )

Followup: MachineOwner


QUESTO è LO SPECIFICO:
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000099, A PTE or PFN is corrupt
Arg2: 0008166d, page frame number
Arg3: 00000000, current page state
Arg4: 00000000, 0

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




BUGCHECK_STR: 0x4E_99

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: atiptaxx.exe

LAST_CONTROL_TRANSFER: from 80529c49 to 8053767a

STACK_TEXT:
ef93b520 80529c49 0000004e 00000099 0008166d nt!KeBugCheckEx+0x1b
ef93b54c 804f1110 77014000 c0300770 c01dc050 nt!MiDecrementShareCount+0x4f
ef93b578 804f1333 c01dc050 77014000 00000000 nt!MiDeletePte+0x197
ef93b63c 804f62d9 e1bb0c90 770e1fff 00000000 nt!MiDeleteVirtualAddresses+0x162
ef93b6e8 80500691 84b19da0 843cb838 84b19ed8 nt!MiRemoveMappedView+0x211
ef93b720 8058e3de 01b19da0 843d85c0 40010004 nt!MmCleanProcessAddressSpace+0x26e
ef93b7c0 8058eb3d 40010004 ef93b81c 804e75ba nt!PspExitThread+0x680
ef93b7cc 804e75ba 843d85c0 ef93b818 ef93b80c nt!PsExitSpecialApc+0x22
ef93b81c 804dda0a 00000001 00000000 ef93b834 nt!KiDeliverApc+0x1af
ef93b81c 7c91e440 00000001 00000000 ef93b834 nt!KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following frames may be wrong.
00e7ff44 00000000 00000000 00000000 00000000 0x7c91e440


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiDecrementShareCount+4f
80529c49 f6400401 test byte ptr [eax+4],1

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDecrementShareCount+4f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a4044a

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x4E_99_nt!MiDecrementShareCount+4f

BUCKET_ID: 0x4E_99_nt!MiDecrementShareCount+4f

Followup: MachineOwner

---------

eccolo qua, mi sembra abbastanza chiaro


DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: atiptaxx.exe

Questo eseguibile dovrebbe essere l'ATI agent che sta nel tray di windows.
Leggi qua. Viene spiegato come disattivarlo, in modo che non venga più caricato all'atto del boot.
Per la precisione, si deve metter mano al registro di windows, entrando nella chiave:
HKEY_LOCAL_MACHINE\SOFTWARE\ATI Technologies\Desktop
ed editare la sotto-chiave
NoAtipta mettendola ad 1 invece del suo valore di default (che dovrebbe esser 0).
Ti consiglio di fare un backup del registro, prima di metter mano alla key.

Ok, grazie per l'aiuto, una ultima cosa, l'eseguibile dovrebbe essere quindi l'icona della mia scheda ati sulla tool bar...ora disabilitandola non mi apparirà più, allora ti chiedo se aggiornando il driver della mia scheda, si sovrascrive l'eseguibile,quindi dovrei aver risolto, giusto?

ciao, leggi qua

e dalla microsoft support qua

Grazie, volevo solo sapere se aggiornando il driver, risolvo, grazie.

Ciao, allora ho seguito la procedura, modificato anche il registro mettendo valore "1" sulla key noatipta, ora non mi appare più l'icona sulla barra strumenti.Spero di aver risolto, volevo sapere ora come facevo, provando, a ritornare sul control panel, visto che non ho più l'icona...ho provato a cercare il programma sul disco, ma non si avvia il pannello.Grazie

potresti vedere sul sito dell'ATI se esiste una versione del tool più recente; non credo che quel programma faccia parte integrante dei driver, probabile che sia un componente a sè stante.
Puoi comunque sempre rimettere il precedente valore a zero nella chiave di registro, se proprio ne hai la necessità. Se però ti manda il PC in bluescreen, non vedo molte alternative. Come avevano detto gli altri che sono intervenuti nella discussione, magari è un problema che si verifica a causa di una interazione con altri software che hai installato recentemente, o sotto determinate condizioni (magari una risoluzione o un refresh della scheda video che hai impostato negli ultimi giorni, prova a ricordare).

Si, in effetti è un software differente rispetto al driver della scheda, comunque l'ho trovato su di un altro sito ed il pacchetto si chiama (ati_cp614105173), io avevo la 5090.L'ho installata con l'opzione modify sovrascrivendo la versioni precedente, mi sono fatto anche un punto di ripristino, ora mi sembra tutto ok. Grazie cmq.