Blue Screen: [ntkrnlpa.exe]

[NLDoMy]

schermata blu si è verificata 5 minuti fa all'avvio del computer che è stato spento da ieri

code errore:Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.0.6001.2.1.0.256.1
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: a
BCP1: 00000001
BCP2: 00000002
BCP3: 00000001
BCP4: 81CB75C9
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\Mini072608-01.dmp
C:\Users\DoMy\AppData\Local\Temp\WER-158015-0.sysdata.xml
C:\Users\DoMy\AppData\Local\Temp\WER9512.tmp.version.txt

Leggere l'informativa sulla privacy:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0410



mhm causato da un'applicazione?



se vado qui: %SystemRoot%\system32\wercon.exe a "cronologia" o "visualizza problemi da risolvere" ad oggi 26 luglio non c'è niente in crash


ho salvato il file .dump relativo all'errore, con cosa posso controllarlo?


in un altro 3d ho trovato questo:Il metodo più semplice è quello di usare WinDbg, facente parte del pacchetto Debugging Tools for Windows. Oltre a questo devi installare anche i Symbols, che servono ad avere un'analisi più accurata del problema. Dopodiché lanci WinDbg, gli dai il path dei Symbols e poi apri il crash dump. A questo punto, dovrebbero comparire un sacco di scritte e, in fondo a tutto, il nome del programma/driver che ha causato il crash.

sto procedendo con il download

[davidemail]

Ciao,è capitato anche a me 3 volte .
a me il memorydump dà questo risultato:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c16000 PsLoadedModuleList = 0x81d2dc70
Debug session time: Sat Jul 26 16:04:57.107 2008 (GMT+2)
System Uptime: 3 days 2:10:56.271
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols

Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 803d1120, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1c

STACK_TEXT:
81d0b880 81cce321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
81d0b8b4 81cce02d 81d1031b 000000d1 81d0b974 nt!KeUpdateRunTime+0xd5
81d0b8b4 81ccdcbe 81d1031b 000000d1 81d0b974 nt!KeUpdateSystemTime+0xed
81d0b940 81c1c671 0000000e 81c1c712 806985d4 nt!KiIpiSendPacket+0xaa
81d0ba5c 805b3084 8408ae68 863cd210 805b1521 nt!KeIpiGenericCall+0x6e
81d0ba68 805b1521 00000103 81d0baa0 805acef0 acpi!ACPIIrpDispatchDeviceControl+0xa4
863cd210 863b37b0 00000000 00000000 863cd220 acpi!ACPIInternalDecrementIrpReferenceCount+0x15
WARNING: Frame IP not in any known module. Following frames may be wrong.
863cd218 00000000 863cd220 863cd220 c00000bb 0x863b37b0


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

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

qualcuno mi sà dire cosa significa?

[NLDoMy]

Ciao,è capitato anche a me 3 volte .
a me il memorydump dà questo risultato:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x81c16000 PsLoadedModuleList = 0x81d2dc70
Debug session time: Sat Jul 26 16:04:57.107 2008 (GMT+2)
System Uptime: 3 days 2:10:56.271
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols

Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 803d1120, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 1c

STACK_TEXT:
81d0b880 81cce321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
81d0b8b4 81cce02d 81d1031b 000000d1 81d0b974 nt!KeUpdateRunTime+0xd5
81d0b8b4 81ccdcbe 81d1031b 000000d1 81d0b974 nt!KeUpdateSystemTime+0xed
81d0b940 81c1c671 0000000e 81c1c712 806985d4 nt!KiIpiSendPacket+0xaa
81d0ba5c 805b3084 8408ae68 863cd210 805b1521 nt!KeIpiGenericCall+0x6e
81d0ba68 805b1521 00000103 81d0baa0 805acef0 acpi!ACPIIrpDispatchDeviceControl+0xa4
863cd210 863b37b0 00000000 00000000 863cd220 acpi!ACPIInternalDecrementIrpReferenceCount+0x15
WARNING: Frame IP not in any known module. Following frames may be wrong.
863cd218 00000000 863cd220 863cd220 c00000bb 0x863b37b0


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_ANALYSIS_INCONCLUSIVE

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

qualcuno mi sà dire cosa significa?


nell'altro post di un altro utente c'era:

*** WARNING: Unable to verify timestamp for raspppoe.sys
Probably caused by : FILTNT.SYS ( FILTNT+fe73 )

ma tu hai:Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) ... riprova a fare l'analisi, non è buon segno, spero di avere un responso migliore

aspetto di finire di scaricare i symbols, che porca miseria avendo problemi con alice 7, andando solo a 2 me ce vuole l'anima de li mortacci di alice e c'ho pure da uscire cribio!!!

[NLDoMy]

quante volte hai verificato quell'errore?

prima volta che te lo ha dato?




moahahoaho... ho fatto cerca soluzione automaticamente dal messaggio di errore che ancora non avevo chiuso, e mi ha detto "Trovata Soluzione"... e io: ALLELUJAAAA!!!... e invece guarda cosa mi ha detto:
Problem caused by computer hardware

You received this message because hardware or software in your computer caused Windows to shut down unexpectedly and restart. This is a serious problem, commonly referred to as a stop error or blue screen.

Troubleshooting

--------------------------------------------------------------------------------


If you have received this error more than once, we recommend that you do the following:

Back up your files to avoid data loss in case of a complete hardware failure.

Contact the original manufacturer of your computer to determine the specific component which is failing. ma chi si sarà sprecato alla microsoft per questa bella presa per il culo?!?!?! ma ci vuole un genio per capire che c'è un errore hardware o software di ignoto motivo?!?!? questa sarebbe la loro soluzione?!?!? ma andate a vendere i pesci

[NLDoMy]

ntkrnlpa.exe

trovatoDescrizione

ntkrnlpa.exe è un process connesso con Microsoft® Windows® Operating System da Microsoft Corporation.

Click to run a free scan for ntkrnlpa.exe related errors.

Raccomandazione

Non un componente critico, ma vede le informazioni qui sopra prima di inabilitarle. Altamente è suggerito a ottimizzare automaticamente memoria, regolazioni del Internet e del CPU..


ntkrnlpa.exe generalità
Autore:

Microsoft Corporation

Parte di:

Microsoft® Windows® Operating System

Path(s) Comune:

%windir%\$NtUninstallKB890859$

%windir%\ServicePackFiles\i386

%system%

%windir%\Driver Cache\i386

%windir%\$hf_mig$\KB890859\SP2QFE


se ricapita il crash mi devo preoccupare?

si può rimuovere e rinstallare?

[davidemail]

Se non uso i symbols mi da questo:



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


Loading Dump File [C:\Users\davide\AppData\Local\Temp\WER380C.tmp\Mini072608-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c16000 PsLoadedModuleList = 0x81d2dc70
Debug session time: Sat Jul 26 16:04:57.107 2008 (GMT+2)
System Uptime: 3 days 2:10:56.271
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 803d1120, 1}

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************

AUTOBUG_OS_SKU: 6

MODULE_NAME: nt

FAULTING_MODULE: 81c16000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd71

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
81d0b880 81cce321 00000101 00000031 00000000 nt+0xcd163
81d0b8b4 81cce02d 81d1031b 000000d1 81d0b974 nt+0xb8321
81d0b8c4 81ccdcbe badb0d00 81d0e920 8079d663 nt+0xb802d
81d0b974 80698786 806985d4 81d0b988 806d82ec nt+0xb7cbe
81d0b9c0 80698d31 0000001f 80698c06 81d0b9e0 sptd+0x3786
81d0b9ec 806a1bc7 01000001 863b3c48 869f6900 sptd+0x3d31
81d0ba04 806a6369 00000103 86876308 8510d198 sptd+0xcbc7
81d0ba30 806a6776 863b3c48 81d0ba88 806a5d00 sptd+0x11369
81d0ba90 862ee518 862ee310 81d0baa0 00000000 sptd+0x11776
81d0bab8 822ef52c 87fab1f4 8696d018 87fad000 0x862ee518
81d0bad8 822f20ed 8696d018 4a000000 81cd2053 PxHelp20+0x252c
81d0bafc 87f9e264 8688fb70 868762e8 8688fab8 PxHelp20+0x50ed
81d0bb10 87f9e45d 8688fb70 86876300 00000000 CLASSPNP+0x4264
81d0bb28 87f9e2af 8688fb70 868702bc 81d4acc0 CLASSPNP+0x445d
81d0bb48 81c50598 8688fab8 00000000 81d0bbb8 CLASSPNP+0x42af
81d0bb68 81cccd00 81d4aca0 02d4ac44 9229f260 nt+0x3a598
81d0bc88 81ccc8c0 81d0bcd0 8630bf02 81d0bcd8 nt+0xb6d00
81d0bce8 81ccc483 00000000 00000000 0105351a nt+0xb68c0
81d0bd50 81ccaf9d 00000000 0000000e 00000000 nt+0xb6483
81d0bd54 00000000 0000000e 00000000 00000000 nt+0xb4f9d


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

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

[NLDoMy]

Se non uso i symbols mi da questo:



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


Loading Dump File [C:\Users\davide\AppData\Local\Temp\WER380C.tmp\Mini072608-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81c16000 PsLoadedModuleList = 0x81d2dc70
Debug session time: Sat Jul 26 16:04:57.107 2008 (GMT+2)
System Uptime: 3 days 2:10:56.271
*********************************************************************
* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
................................................................................................................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, 803d1120, 1}

*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.SYS
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntkrnlpa.exe

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

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.

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

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************

AUTOBUG_OS_SKU: 6

MODULE_NAME: nt

FAULTING_MODULE: 81c16000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4812bd71

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
81d0b880 81cce321 00000101 00000031 00000000 nt+0xcd163
81d0b8b4 81cce02d 81d1031b 000000d1 81d0b974 nt+0xb8321
81d0b8c4 81ccdcbe badb0d00 81d0e920 8079d663 nt+0xb802d
81d0b974 80698786 806985d4 81d0b988 806d82ec nt+0xb7cbe
81d0b9c0 80698d31 0000001f 80698c06 81d0b9e0 sptd+0x3786
81d0b9ec 806a1bc7 01000001 863b3c48 869f6900 sptd+0x3d31
81d0ba04 806a6369 00000103 86876308 8510d198 sptd+0xcbc7
81d0ba30 806a6776 863b3c48 81d0ba88 806a5d00 sptd+0x11369
81d0ba90 862ee518 862ee310 81d0baa0 00000000 sptd+0x11776
81d0bab8 822ef52c 87fab1f4 8696d018 87fad000 0x862ee518
81d0bad8 822f20ed 8696d018 4a000000 81cd2053 PxHelp20+0x252c
81d0bafc 87f9e264 8688fb70 868762e8 8688fab8 PxHelp20+0x50ed
81d0bb10 87f9e45d 8688fb70 86876300 00000000 CLASSPNP+0x4264
81d0bb28 87f9e2af 8688fb70 868702bc 81d4acc0 CLASSPNP+0x445d
81d0bb48 81c50598 8688fab8 00000000 81d0bbb8 CLASSPNP+0x42af
81d0bb68 81cccd00 81d4aca0 02d4ac44 9229f260 nt+0x3a598
81d0bc88 81ccc8c0 81d0bcd0 8630bf02 81d0bcd8 nt+0xb6d00
81d0bce8 81ccc483 00000000 00000000 0105351a nt+0xb68c0
81d0bd50 81ccaf9d 00000000 0000000e 00000000 nt+0xb6483
81d0bd54 00000000 0000000e 00000000 00000000 nt+0xb4f9d


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlpa.exe

BUCKET_ID: WRONG_SYMBOLS

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

strano senza i symbols che ora ti dica -> Probably Caused: ntkrnlpa.exe


di questo file ho letto che può essere causato da un conflitto con un driver, ora io ho usato questa procedura per installare vista:

1) installato vista
2) aggiornamenti pre-sp1 importanti
3) 3 patches consigliate da installare prima della sp1
4) installato l'aggiornamento a bitlocker
5) dopo bitlocker mi è comparso vista sp1 ed installato
6) ho installato tutti i drivers scaricati dai siti dei produttori

cmq è stata la prima volta che mi è capitata sta schermata blu addirittura dopo il format, ieri ho riacceso il computer ed è andato tutto ok anche nell'uso

a te ciclicamente ti da' quella schermata blu o come me ti è capitato una volta?
usi un notebook o desktop? componenti?

[davidemail]

mi è capitato 3 volte...per fortuna non è il pc che uso per lavoro,quello ha ancora xp...ho un fisso q6600 8800gt 2gb....

certo che è delicato vista...adesso ho aggiornato un pò di driver vediamo se continua a farlo...

[NLDoMy]

mi è capitato 3 volte...per fortuna non è il pc che uso per lavoro,quello ha ancora xp...ho un fisso q6600 8800gt 2gb....

certo che è delicato vista...adesso ho aggiornato un pò di driver vediamo se continua a farlo...

mah sai mi è sempre capitato di peggio con xp, per me vista è una roccia e cmq non è vista sono i drivers di terze parti che sono stati "magari" scritti con il :ciapet:

cmq i componenti essenziali che creano più conflitto sono le schede di rete o i chipset, quindi sapere che hai un q6600 o 8800gt o 2gb di ram non serve a molto, servirebbe e serve adesso per sapere se fai overclock con 8800 e 6600, alcuni bios fanno strane cose o anche i componenti stessi se il clock non è stabile, magari creano anche instabilità con i drivers

cmq bho, l'unica cosa è provare ad aggiornare tutti drivers ed anche pregare a volte aiuta :ciapet:

[NLDoMy]

we davide, novità?

[davidemail]

we davide, novità?

Si :) ,essendo un Dell ho fatto il test dell'hardware dal boot ed è andato tutto liscio..quindi è una cosa di driver...ho aggiornato con quelli del sito dell e ho tolto programmi preinstallati tipo roxio,mouse suite........
adesso non resta che vedere se capita ancora,comunque quel pc lo uso poco...

[NLDoMy]

Si :) ,essendo un Dell ho fatto il test dell'hardware dal boot ed è andato tutto liscio..quindi è una cosa di driver...ho aggiornato con quelli del sito dell e ho tolto programmi preinstallati tipo roxio,mouse suite........
adesso non resta che vedere se capita ancora,comunque quel pc lo uso poco...

ah, ok, meglio :D

io devo ancora piallare quindi :sperem: che non ricapiti più

[davidemail]

Dopo aver segnalato il problema alla Dell mi hanno detto di aggiornare il bios del pc con uno che mi hanno inviato via mail...:sperem:

[robertogl]

riapro questo thread perchè ho lo stesso problema.
Schermate blu che capitano in qualsiasi situazione,mentre navigo o mentre il pc scarica la notte.Ho aggiornato il bios e il problema sembrava essere scomparso,ma dopo 2 settimane è riapparso.Ho aggiornato i driver video ma non è cambiato nulla;ho fatto un test veloce della ram(un quarto d'ora perchè mi serviva il pc)e non mi ha dato problemi;nessun overclock;mi preoccupa la frase:
An expected clock interrupt was not received on a secondary processor...
cioè c'entra il processore?Grazie a chi mi aiuterà.:)
windbg mi dice 'Probably caused by : ntkrnlpa.exe'

[NLDoMy]

riapro questo thread perchè ho lo stesso problema.
Schermate blu che capitano in qualsiasi situazione,mentre navigo o mentre il pc scarica la notte.Ho aggiornato il bios e il problema sembrava essere scomparso,ma dopo 2 settimane è riapparso.Ho aggiornato i driver video ma non è cambiato nulla;ho fatto un test veloce della ram(un quarto d'ora perchè mi serviva il pc)e non mi ha dato problemi;nessun overclock;mi preoccupa la frase:
An expected clock interrupt was not received on a secondary processor...
cioè c'entra il processore?Grazie a chi mi aiuterà.:)
windbg mi dice 'Probably caused by : ntkrnlpa.exe'

http://forums.techarena.in/windows-x64-edition/837192.htm

trovo sempre discussioni che parlano di overclock e un utente che registra un ovrclock del 2% pur dichiarando di non aver overclocckato

può essere una qualche impostazioni della mobo o di qualche software (vedi epu o six engine di asus)

fai così: imposta MANUALMENTE i valori della cpu, togli tutto quello che è su auto relativo al core, fsb, ram, timings etc.. imposta su user o manual e togli tutte le opzioni nel bios relative allo speedstep e varie

non saprei che altro dirti, appena ho tempo provo a cercare meglio in rete

[robertogl]

http://forums.techarena.in/windows-x64-edition/837192.htm

trovo sempre discussioni che parlano di overclock e un utente che registra un ovrclock del 2% pur dichiarando di non aver overclocckato

può essere una qualche impostazioni della mobo o di qualche software (vedi epu o six engine di asus)

fai così: imposta MANUALMENTE i valori della cpu, togli tutto quello che è su auto relativo al core, fsb, ram, timings etc.. imposta su user o manual e togli tutte le opzioni nel bios relative allo speedstep e varie

non saprei che altro dirti, appena ho tempo provo a cercare meglio in rete
mi sembra di aver risolto...allora,cercando in rete,ho provato a :disabilitare file di paging(ho 4gb di ram),disinstallare daemon tools e rimuovere periferiche virtuali.Non ho schermate blu da 3 giorni,prima ne avevo 2 al giorno.:)

[NLDoMy]

mi sembra di aver risolto...allora,cercando in rete,ho provato a :disabilitare file di paging(ho 4gb di ram),disinstallare daemon tools e rimuovere periferiche virtuali.Non ho schermate blu da 3 giorni,prima ne avevo 2 al giorno.:)

se posso evito daemon tools :D

cmq se la ram e il disco sono ok, prova allora a ripristinare il file di paging, se ti da' schermate blu è una brutta storia.. potrebbe essere la mobo

se non hai più schermate blue invece, spero fosse daemon

[ciccio83a]

post errore

[Kis]

ho avuto 7 crash di fila in mezz'ora , mai successo, win7 x64 sp1 tutto aggiornato!

==================================================
File Dump : 051112-32062-01.dmp
Orario Crash : 11/05/2012 03:35:23
Stringa Controllo Bug: KERNEL_DATA_INPAGE_ERROR
Codice Controllo Bug: 0x0000007a
Parametro 1 : 00000000`00000020
Parametro 2 : ffffffff`c000009d
Parametro 3 : fffffa80`05566078
Parametro 4 : 00000000`00000000
Causato dal Driver: ntoskrnl.exe
Causato dall'Indirizzo: ntoskrnl.exe+7f1c0
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.17803 (win7sp1_gdr.120330-1504)
Processore : x64
Indirizzo Crash : ntoskrnl.exe+7f1c0
Indirizzo Stack 1 :
Indirizzo Stack 2 :
Indirizzo Stack 3 :
Nome Computer :
Path Completo : C:\Windows\Minidump\051112-32062-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 306.936
==================================================