Xp/2000 - Schermate blu (bsod):individuazione cause dell'errore e possibili soluzioni

[xcdegasp]

Originariamente inviato da DevilOfSky

l'errore è questo


irql_not_less_or_equal

(0x0000000a,...,...)

cosa può essere?

memtest niente errori
parte solo in mod.provvisoria

driver nvidia e della stampante da aggiornare

[AlbertoF]

Buon giorno a tutti.
Un paio di volte mi e' capitato che il PC parte e non avendo ancora finito di caricare tutto (si vedo lo sfondo del desk top, il puntatore del mouse ecc.) si riavvia senza alcuna schermata blu e sintomi del genere.
Al riavvio funziona tutto, compare la segnalazione che qualche device ha causato un problema ma non si sa quale.
E' possibile capirlo analizzando il minidump e c'e' qualche sistema più semplice ?

Grazie di ogni suggerimento

Alberto

[ezio]

Originariamente inviato da DevilOfSky

l'errore è questo
irql_not_less_or_equal
(0x0000000a,...,...)
cosa può essere?
memtest niente errori
parte solo in mod.provvisoria

IRQ_NOT_LESS_OR_EQUAL può derivare da tanti fattori, il debug dei file dump serve proprio ad individuare eventuali file problematici (sempre che non sia un problema hardware delle ram).
Segui le indicazioni del primo post.

Originariamente inviato da AlbertoF

Buon giorno a tutti.
Un paio di volte mi e' capitato che il PC parte e non avendo ancora finito di caricare tutto (si vedo lo sfondo del desk top, il puntatore del mouse ecc.) si riavvia senza alcuna schermata blu e sintomi del genere.
Al riavvio funziona tutto, compare la segnalazione che qualche device ha causato un problema ma non si sa quale.
E' possibile capirlo analizzando il minidump e c'e' qualche sistema più semplice ?
Grazie di ogni suggerimento
Alberto

Hai disattivato il riavvio automatico in caso di errore come indicato nel primo post? La schermata blu potrebbe esserci comunque senza che tu te ne renda conto. Controlla la presenza di file dump nel relativo percorso, altrimenti dai un'occhiata al Visualizzatore Eventi di Windows, potrebbe contenere avvisi utili a capire il problema.

[furia.cieca]

ciao a tutti, ho seguito la guida in prima pagina, sperando di aver fatto tutto bene vi posto il mio dmp file

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


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

Symbol search path is: C:\WINDOWS\Symbols\acm;C:\WINDOWS\Symbols\ax;C:\WINDOWS\Symbols\cnv;C:\WINDOWS\Symbols\com;C:\WINDOWS\Symbols\cpl;C:\WINDOWS\Symbols\dic;C:\WINDOWS\Symbols\dll;C:\WINDOWS\Symbols\drv;C:\WINDOWS\Symbols\ds;C:\WINDOWS\Symbols\exe;C:\WINDOWS\Symbols\iec;C:\WINDOWS\Symbols\ime;C:\WINDOWS\Symbols\ocx;C:\WINDOWS\Symbols\scr;C:\WINDOWS\Symbols\sys;C:\WINDOWS\Symbols\tpl;C:\WINDOWS\Symbols\tsp;C:\WINDOWS\Symbols\wpc
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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sat May 30 08:26:49.187 2009 (GMT+2)
System Uptime: 0 days 0:19:32.769
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 100000D1, {f77f9fff, 2, 8, f77f9fff}

Probably caused by : memory_corruption ( nt!MiAllocatePoolPages+a64 )

Followup: MachineOwner

sulla schermata blu avevo scritto qualcosa del tipo "IRQ_NOT_LESS_OR_EQUAL"
è la ram che mi sta mollando?

[furia.cieca]

up dopo qualche giorno con un nuovo crash e nuova causa

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


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

Symbol search path is: C:\WINDOWS\Symbols\acm;C:\WINDOWS\Symbols\ax;C:\WINDOWS\Symbols\cnv;C:\WINDOWS\Symbols\com;C:\WINDOWS\Symbols\cpl;C:\WINDOWS\Symbols\dic;C:\WINDOWS\Symbols\dll;C:\WINDOWS\Symbols\drv;C:\WINDOWS\Symbols\ds;C:\WINDOWS\Symbols\exe;C:\WINDOWS\Symbols\iec;C:\WINDOWS\Symbols\ime;C:\WINDOWS\Symbols\ocx;C:\WINDOWS\Symbols\scr;C:\WINDOWS\Symbols\sys;C:\WINDOWS\Symbols\tpl;C:\WINDOWS\Symbols\tsp;C:\WINDOWS\Symbols\wpc
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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Jun 3 18:03:27.234 2009 (GMT+2)
System Uptime: 0 days 9:11:50.839
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 FC, {f77f9fff, 16e94163, 80549b58, 0}

*** WARNING: Unable to verify timestamp for SCSIPORT.SYS
Probably caused by : SCSIPORT.SYS ( SCSIPORT!SpFreeSrbData+cb )

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

[arcofreccia]

Ragazzi mi sta facendo uscire pazzo la tastiera non so cosa gli sia successo, riavvio il pc e mi appare la scritta:

keyboard error or no keyboard present

[mike74]

Salve, in 7 giorni é la seconda volta che mi si presenta questo errore:

DRIVER_IRQ_NOT_LESS_OR_EQUAL

iastor.sys-adress F70FD7D4 base at F70F8000, DateStamp 48cod1b8

Qualcuno sa aiutarmi a risolvere questo fastidioso problema? grazie.

[lvking]

il mio PC freeza ogni tanto, ma di files dump o minidump nella cartella C:\Windows\minidump non c'è neppure l'ombra
Come faccio a capire come evitare i freeze?

[emiliano1984]

Buongiorno a tutti, dopo mesi e mesi durante i quali mi sono fatto un'attenta lettura di tutti i post sparsi per la Rete che trattavano di problemi legati alle famosissime schermate blu e dopo vari invani tentativi di porvi rimedio ho deciso di provare a scrivere un post relativo al mio fastidiosissimo problema.
Praticamente da quando ho il mio notebook, saltuariamente il PC mi si riavvia dopo aver visualizzato la schermata blu di errore. Ciò capita in media una volta ogni due settimane, non ho potuto trovare nessuna corrispondenza tra ciò che sto facendo e quando si verifica il problema.
La configurazione del mio PC è la seguente:

Processor
Model : Intel(R) Core(TM)2 Duo CPU     T5470  @ 1.60GHz
Speed : 1.60GHz
Cores per Processor : 2 Unit(s)
Threads per Core : 1 Unit(s)
Type : Mobile, Dual-Core
Internal Data Cache : 2x 32kB, Synchronous, Write-Thru, 8-way, Inclusive, 64 byte line size
L2 On-board Cache : 2MB, ECC, Synchronous, ATC, 8-way, Inclusive, 64 byte line size, 2 threads sharing

System
System : Hewlett-Packard HP Compaq 6820s
Platform Compliance : Intel Centrino Mobile Technology
Mainboard : Hewlett-Packard 30D7
Bus(es) : X-Bus PCI PCIe IMB PCMCIA USB
Multi-Processor (MP) Support : No
Multi-Processor Advanced PIC (APIC) : Yes
System BIOS : Hewlett-Packard 15.11
Total Memory : 3.00GB DDR2

Chipset 1
Model : HP Mobile PM965/GM965/GL960 Express Processor to DRAM Controller
Front Side Bus Speed : 4x 200MHz (800MHz)
Total Memory : 4GB DDR2
Memory Bus Speed : 2x 333MHz (666MHz)

Video System
Monitor/Panel : Monitor Plug and Play
Adapter : ATI MOBILITY RADEON X1350  

Logical Storage Devices
Hard Disk (C:) : 135.22GB (106.06GB, 78% Free Space) (NTFS) @ TOSHIBA MK2546GSX 250GB (SATA300, NCQ, 8MB Cache)
Hard Disk (D:) : 97.65GB (91.27GB, 93% Free Space) (NTFS) @ TOSHIBA MK2546GSX 250GB (SATA300, NCQ, 8MB Cache)

Operating System(s)
Windows System : Microsoft Windows XP (2002) Professional 5.01.2600 (Service Pack 2)
Platform Compliance : Win32 x86

L'errore più recente (stamattina) è stato causato dal seguente file:

1- Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!xxxCreateDesktop+a14 )

altri errori che mi sono apparsi sono i seguenti:

2- BugCheck 1000000A, {ffffff8b, ff, 1, 806e3e58}
    Probably caused by : memory_corruption     (nt!MiMakeOutswappedPageResident+454 )

3- BugCheck 1000008E, {c0000005, d80ed09, aa8de6d4, 0}
     Probably caused by : win32k.sys 
( win32k!xxxSystemParametersInfo+1421 )

4- Could not read faulting driver name
    Probably caused by : win32k.sys ( win32k!xxxSBWndProc+764 )

5- BugCheck 24, {1902fe, f661b758, f661b454, f7163897}
    Probably caused by : Ntfs.sys ( Ntfs!NtfsWorldAclFile+17 )

6- BugCheck 4E, {8f, 9b345, 99f45, 0}
    Probably caused by : ntoskrnl.exe ( nt!IoFreeWorkItem+4f )

7- BugCheck 1000007F, {8, f7717d70, 0, 0}
    Probably caused by : memory_corruption 
    (nt!MmCleanProcessAddressSpace+d1 )

...e potrei andare avanti così ancora per molto.
Leggendo tutti i vari post già presenti in Rete ho già provato a:
- aggiornare tutti i driver possibili.
- testare la RAM per verificare se fosse danneggiata.
- aggiornare il CCC della scheda video.
- formattare il PC!
inutile sottolineare il fatto che a nulla è servito...
Considerato che uso il PC per lavoro chiedo disperatamente aiuto!

Grazie mille in anticipo a chiunque volesse darmi una mano.

[lvking]

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


Loading Dump File [C:\WINDOWS\Minidump\Mini061109-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 \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jun 11 19:30:34.593 2009 (GMT+2)
System Uptime: 0 days 0:06:44.203
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8054b168, b4505564, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
Probably caused by : ntkrnlpa.exe ( nt!g_rgAttributeTags+170 )

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

il secondo invece è:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini061109-02.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 \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (3 procs) Free x86 compatible
Product: WinNt
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jun 11 19:42:01.453 2009 (GMT+2)
System Uptime: 0 days 0:03:33.324
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {e37e0000, 0, 8054b0ba, 1}

*** WARNING: Unable to verify timestamp for mssmbios.sys

Could not read faulting driver name
Probably caused by : ntkrnlpa.exe ( nt!g_rgAttributeTags+c2 )

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

Grazie in anticipo

[ezio]

Originariamente inviato da furia.cieca

ciao a tutti, ho seguito la guida in prima pagina, sperando di aver fatto tutto bene vi posto il mio dmp file

sulla schermata blu avevo scritto qualcosa del tipo "IRQ_NOT_LESS_OR_EQUAL"
è la ram che mi sta mollando?

Molto probabile vedendo il debug.
Esegui un test approfondito delle memorie con Memtest (cd, floppy o pendrive autoavviabile) seguendo queste indicazioni:
Controllo della RAM con Memtest86+

Originariamente inviato da arcofreccia

Ragazzi mi sta facendo uscire pazzo la tastiera non so cosa gli sia successo, riavvio il pc e mi appare la scritta:
keyboard error or no keyboard present

Non è il thread adatto, sono problemi che non riguardano Windows.
Chiedi nelle sezioni hardware e verifica che la tastiera sia connessa correttamente (soprattutto se ps2, controlla che i pin siano a posto).

Originariamente inviato da mike74

Salve, in 7 giorni é la seconda volta che mi si presenta questo errore:

DRIVER_IRQ_NOT_LESS_OR_EQUAL

iastor.sys-adress F70FD7D4 base at F70F8000, DateStamp 48cod1b8

Qualcuno sa aiutarmi a risolvere questo fastidioso problema? grazie.

Aggiorna Intel Matrix Storage all'ultima versione disponibile, alcune precedenti soffrono di questi problemi con iastor.sys

Originariamente inviato da emiliano1984

Buongiorno a tutti, dopo mesi e mesi durante i quali mi sono fatto un'attenta lettura di tutti i post sparsi per la Rete che trattavano di problemi legati alle famosissime schermate blu e dopo vari invani tentativi di porvi rimedio ho deciso di provare a scrivere un post relativo al mio fastidiosissimo problema.
Praticamente da quando ho il mio notebook, saltuariamente il PC mi si riavvia dopo aver visualizzato la schermata blu di errore. Ciò capita in media una volta ogni due settimane, non ho potuto trovare nessuna corrispondenza tra ciò che sto facendo e quando si verifica il problema.
cut

...e potrei andare avanti così ancora per molto.
Leggendo tutti i vari post già presenti in Rete ho già provato a:
- aggiornare tutti i driver possibili.
- testare la RAM per verificare se fosse danneggiata.
- aggiornare il CCC della scheda video.
- formattare il PC!
inutile sottolineare il fatto che a nulla è servito...
Considerato che uso il PC per lavoro chiedo disperatamente aiuto!

Grazie mille in anticipo a chiunque volesse darmi una mano.

Aggiornato il bios? Prova anche a scambiare di posto i moduli ram e provane uno alla volta se ne hai più di uno, può darsi che la tua scheda madre sia poco compatibile con questi soprattutto se posti un dual channel.

Vedendo che hai errori anche su Ntfs.sys e Win2k.sys, mi viene da suggerirti anche un controllo del disco fisso e una sostituzione dei cavi sAta.

Originariamente inviato da lvking

Probably caused by : ntkrnlpa.exe ( nt!g_rgAttributeTags+c2 )

E' d'obbligo un controllo delle ram (vedi link sopra) in caso di errori generici con ntkrnlpa.exe

[gnpb]

ciao a tutti, ho un problema con un pc di un amico con XP. E' mancata la corrente in fase di avvio e ora il pc continua a riavviarsi da solo dopo il logo di windows.

Stessa cosa se parto in modalità provvisoria (ho provato anche il ripristino dall'ultima configurazione funzionate ma nulla).

Allora sono partito escludendo il riavvio automatico e mi ha dato una schermata blu con scritto:
PAGE_FAULT_IN_NONPAGED_AREA
stop: 0x00000050 (0x80087000, 0x00000000, 0x89c9f9dc, 0x00000000).

Già tentato fixboot, chkdsk /r e superato senza errori il 35% di memtest (poi ho fermato). Speravo nel file .dmp ma non l'ha creato.

A questo punto 2 domande:
- è possibile forzare la creazione di questo file in modo da trovare il file corrotto?
- le informazioni dei vechi dmp che ho trovato sul suo pc le ho lette col mio. Quello che vedo (sp3 installato) è relativo al mio pc o al suo (mi ricordavo avesse solo sp2 installato)?

ps. se qualcuno ha qualche idea di come dovrei procedere per evitare il format sono tutt'orecchi

[maprilia]

Ciao a tutti... ho questo problema con il pc in firma...
come unico sistema operativo ho Xp 32bit Sp3...
da un pò di tempo mi succede che mentre sto lavorando compaiono prima degli artefatti grafici sulla barra di xp e poi il pc sembra bloccarsi (mouse a scatti, artefatti grafici e rallentamenti ) per un po fino alla comparsa della schermata blu contenente quest'errore:

bugcode_usb_driver

STOP: 0x000000FE (0x00000005; 0x89C1A0E0; 0x80862936; 0x897A8F70)

Ho seguito la guida e ho ottenuto il log:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini070509-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 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul  5 18:07:50.718 2009 (GMT+2)
System Uptime: 0 days 0:16:49.439
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
............
Unable to load image USBPORT.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 89c1a0e0, 80862936, 897a8f70}

Unable to load image usbuhci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbuhci.sys
Unable to load image sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : usbuhci.sys ( usbuhci!UhciPollAsyncEndpoint+32 )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: 89c1a0e0, Device extension pointer of the host controller
Arg3: 80862936, PCI Vendor,Product id for the controller
Arg4: 897a8f70, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  Idle

LAST_CONTROL_TRANSFER:  from b741ce7b to 804f9f33

STACK_TEXT:  
b84d3b90 b741ce7b 000000fe 00000005 89c1a0e0 nt!_woutput+0x404
b84d3bb0 b74297b9 89c1a028 00000fd0 8970d000 USBPORT!USBPORT_BugCheck+0x2d
b84d3be4 b8463102 5650706d 89c1a9dc 897a8f70 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x11d
b84d3c08 b8460ded 89c1a9dc 8970d000 b84d3c38 usbuhci!UhciPollAsyncEndpoint+0x32
b84d3c18 b74164aa 89c1a9dc 897a8f70 80546abc usbuhci!UhciPollEndpoint+0x1f
b84d3c38 b7417768 026c6f50 89c1a0e0 897a8df8 USBPORT!USBPORT_PollEndpoint+0xe8
b84d3c60 b741b0a0 89c1a028 50457270 80546abc USBPORT!USBPORT_CoreEndpointWorker+0x2be
b84d3c90 b742924b 89c1a028 80546abc 89c1a028 USBPORT!USBPORT_DpcWorker+0x18a
b84d3ccc b74293c2 89c1a028 00000001 89cac52c USBPORT!USBPORT_IsrDpcWorker+0x38f
b84d3ce8 b7eb8d54 89c1a64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
WARNING: Stack unwind information not available. Following frames may be wrong.
b84d3d18 89cacaaa 89cac008 b742925c b84d3d2c sptd+0x11d54
b84d3d1c 89cac008 b742925c b84d3d2c 80545e6f 0x89cacaaa
b84d3d20 b742925b b84d3d2c 80545e6f 89c1a64c 0x89cac008
b84d3d24 b84d3d2c 80545e6f 89c1a64c 89c1a028 USBPORT!USBPORT_IsrDpcWorker+0x39f
b84d3d28 80545e6f 89c1a64c 89c1a028 00000000 0xb84d3d2c
b84d3d2c 89c1a64c 89c1a028 00000000 00000000 nt!ExDisableResourceBoostLite+0x17
b84d3d30 89c1a028 00000000 00000000 8055c0c0 0x89c1a64c
b84d3d34 00000000 00000000 8055c0c0 b833ae20 0x89c1a028


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbuhci!UhciPollAsyncEndpoint+32
b8463102 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  usbuhci!UhciPollAsyncEndpoint+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbuhci

IMAGE_NAME:  usbuhci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  480254ce

FAILURE_BUCKET_ID:  0xFE_usbuhci!UhciPollAsyncEndpoint+32

BUCKET_ID:  0xFE_usbuhci!UhciPollAsyncEndpoint+32

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

Le schermate blu arrivano pochi minuti dopo ogni riavvio, e inoltre non ho ne Hd Ubs e ne altre periferiche ataccate...
La cosa che mi ha spaventa di piu sono gli artefatti grafici, non vorrei si sia crepata la vga, anche se c'è da dire compaiono solo in win xp....
sapete aiutarmi a capire da che cosa deriva l' errore?

[gifrgifr]

Problema anomalo il mio: dopo le continue schermate blu sono giunto alla conclusione di salvare il salvabile e formattare.
Il PC è un vecchiotto pentium4 del 2002, l'unico problema più o meno palpabile era l'orologio sempre sballato causa la batteria scarica.
Ho formattato e fino a lì tutto normale, quando poi ho iniziato l'installazione di windows mi si è bloccato per ore quando il timer diceva mancano 22 minuti alla fine dell'installazione.Ho deciso di spegnere e rifare la procedura daccapo, ma nulla, continue schermate blu dopo pochi secondi o minuti di procedura di installazione, ho cambiato la batteria della schedamadre con una nn totalmente scarica, ma niente, ho provato poi col cd di XP tiny ma niente lo stesso.
Esistono altre vie??qualcuno è in grado di indicarmele??
Muchas gracias!!

[ezio]

Originariamente inviato da gnpb

ciao a tutti, ho un problema con un pc di un amico con XP. E' mancata la corrente in fase di avvio e ora il pc continua a riavviarsi da solo dopo il logo di windows.
Stessa cosa se parto in modalità provvisoria (ho provato anche il ripristino dall'ultima configurazione funzionate ma nulla).
Allora sono partito escludendo il riavvio automatico e mi ha dato una schermata blu con scritto:
PAGE_FAULT_IN_NONPAGED_AREA
stop: 0x00000050 (0x80087000, 0x00000000, 0x89c9f9dc, 0x00000000).

Già tentato fixboot, chkdsk /r e superato senza errori il 35% di memtest (poi ho fermato). Speravo nel file .dmp ma non l'ha creato.

A questo punto 2 domande:
- è possibile forzare la creazione di questo file in modo da trovare il file corrotto?
- le informazioni dei vechi dmp che ho trovato sul suo pc le ho lette col mio. Quello che vedo (sp3 installato) è relativo al mio pc o al suo (mi ricordavo avesse solo sp2 installato)?

ps. se qualcuno ha qualche idea di come dovrei procedere per evitare il format sono tutt'orecchi

Se sono due moduli ram in dual channel, provame uno alla volta e vedi che succede.
Effettuerei anche un controllo approfondito del disco fisso con i tool del produttore per assicurarmi che la mancanza di corrente o un eventuale sbalzo di tensione possano averlo danneggiato: Click

Facci sapere.

Originariamente inviato da maprilia

Ciao a tutti... ho questo problema con il pc in firma...
come unico sistema operativo ho Xp 32bit Sp3... ?
cut

Se il sistema è overcloccato, e soprattutto se hai agito sul bus, riportalo a default. Anche un'eccessiva frequenza delle ram o un voltaggio elevato delle stesse possono provocare l'errore.

Se usi un modem usb, potrebbe essere questo a causare il problema (può capitare che queste periferiche sovraccarichino le porte in dotazione alla scheda madre o i driver possono essere instabili). Se ne possiedi uno, prova a usare il pc senza connetterlo.

Visto che il debugger non trova il timestamp corretto per alcuni file di sistema relativi al controller usb, se non risolvi prova ad eseguire sfc /scannow dal prompt dei comandi in modo da verificare e correggere eventuali incongruenze con questi file (soprattutto se hai installato qualche driver dal cd della scheda madre, potrebbe aver sovrascritto i driver integrati di Windows relativi al controller).

Ancora, prova a disinstallare manualmente tutte le voci relative al controller usb da Gestione Periferiche e riavvia, così facendo dovrebbero essere ricaricati i driver standard.

Originariamente inviato da gifrgifr

Problema anomalo il mio: dopo le continue schermate blu sono giunto alla conclusione di salvare il salvabile e formattare.
Il PC è un vecchiotto pentium4 del 2002, l'unico problema più o meno palpabile era l'orologio sempre sballato causa la batteria scarica.
Ho formattato e fino a lì tutto normale, quando poi ho iniziato l'installazione di windows mi si è bloccato per ore quando il timer diceva mancano 22 minuti alla fine dell'installazione.Ho deciso di spegnere e rifare la procedura daccapo, ma nulla, continue schermate blu dopo pochi secondi o minuti di procedura di installazione, ho cambiato la batteria della schedamadre con una nn totalmente scarica, ma niente, ho provato poi col cd di XP tiny ma niente lo stesso.
Esistono altre vie??qualcuno è in grado di indicarmele??
Muchas gracias!!

Un controllo delle ram con Memtest è d'obbligo, clicca qui per i dettagli: Click

[gnpb]

Originariamente inviato da ezio

Se sono due moduli ram in dual channel, provame uno alla volta e vedi che succede.
Effettuerei anche un controllo approfondito del disco fisso con i tool del produttore per assicurarmi che la mancanza di corrente o un eventuale sbalzo di tensione possano averlo danneggiato: Click

Facci sapere.

Ora ho formattato. Purtroppo la situazione era complicata dal fatto che era un pc packard bell, quindi con s.o. personalizzato e partizione d'avvio anch'essa modificata (punta alla partizione principale che contiene una parte di so packard bell per il ripristino e quella di win è secondaria quindi i vari tool modificano la tabella di partizione ma così facendo il sistema non è più avviabile) e non aveva fatto il cd di ripristino che serve per far funzionare il programma di ripristino integrato packard bell.
Una volta piallato tutto e facendo un'installazione con s.o. e partizioni standard tutto funziona correttamente.

[ezio]

Buono a sapersi, la formattazione è sempre una soluzione drastica ma a volte evita perdite di tempo ancora maggiori

[gnpb]

Eh sì, questo era proprio quel caso tipico. Poiché , tra l'altro, nel tempo il mio amico aveva aggiunto 1GB di ram, cambiato la scheda video ed aveva aggiornato a sp2. Se il sistema di ripristino avesse funzionato, comunque avrebbe fatto casino perché andava installata una patch P.B. nel sistema di ripristino x i 2GB di ram (e lui non l'aveva fatto) e poi sarebbe stato cancellato sp2, ie7 e probabilmente i driver della nuova scheda video. Comunque un macello insomma.

[fabrilas]

ragazzi a me ne trova addirittura 6....

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Apr  8 17:09:48.649 2009 (GMT+2)
System Uptime: 0 days 0:09:23.224
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 1000008E, {c0000005, 805674c7, f02bec7c, 0}

Unable to load image pci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pci.sys
Probably pool corruption caused by Tag:  MmSt

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

---

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sat Apr 18 18:58:37.305 2009 (GMT+2)
System Uptime: 0 days 0:29:57.878
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 C2, {50, e1e7d000, e7d, a000000}

Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
Unable to load image pci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pci.sys
Probably caused by : win32k.sys ( win32k!HeavyFreePool+bb )

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

---

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Thu Jun 25 08:26:58.115 2009 (GMT+2)
System Uptime: 0 days 0:01:27.686
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 1000008E, {c0000005, 805677c4, f74f8ba0, 0}

Unable to load image pci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pci.sys
Probably caused by : ntoskrnl.exe ( nt!ExpAllocateHandleTableEntry+1be )

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

---

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Tue Jun 30 07:39:39.211 2009 (GMT+2)
System Uptime: 0 days 0:43:14.781
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 C2, {7, cd4, 0, e20bcd50}

Unable to load image kmixer.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kmixer.sys
*** WARNING: Unable to verify timestamp for ks.sys
Unable to load image sysaudio.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sysaudio.sys
GetUlongFromAddress: unable to read from 80563070
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** WARNING: Unable to verify timestamp for s3sav4.dll
*** WARNING: Unable to verify timestamp for HTTP.sys
*** WARNING: Unable to verify timestamp for srv.sys
*** WARNING: Unable to verify timestamp for avgntflt.sys
*** ERROR: Module load completed but symbols could not be loaded for avgntflt.sys
*** WARNING: Unable to verify timestamp for wdmaud.sys
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** WARNING: Unable to verify timestamp for ndisuio.sys
*** WARNING: Unable to verify timestamp for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** WARNING: Unable to verify timestamp for ipnat.sys
*** WARNING: Unable to verify timestamp for SASKUTIL.sys
*** ERROR: Module load completed but symbols could not be loaded for SASKUTIL.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** WARNING: Unable to verify timestamp for netbt.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** WARNING: Unable to verify timestamp for ipsec.sys
*** WARNING: Unable to verify timestamp for update.sys
*** WARNING: Unable to verify timestamp for rdpdr.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** WARNING: Unable to verify timestamp for ndiswan.sys
*** WARNING: Unable to verify timestamp for parport.sys
*** WARNING: Unable to verify timestamp for serial.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** WARNING: Unable to verify timestamp for ds1wdm.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for s3sav4m.sys
*** WARNING: Unable to verify timestamp for Dxapi.sys
*** WARNING: Unable to verify timestamp for Mup.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** WARNING: Unable to verify timestamp for KSecDD.sys
*** WARNING: Unable to verify timestamp for Fastfat.sys
*** WARNING: Unable to verify timestamp for sr.sys
*** WARNING: Unable to verify timestamp for fltMgr.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** WARNING: Unable to verify timestamp for dmio.sys
*** WARNING: Unable to verify timestamp for ftdisk.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** WARNING: Unable to verify timestamp for ACPI.sys
*** WARNING: Unable to verify timestamp for isapnp.sys
*** WARNING: Unable to verify timestamp for MountMgr.sys
*** WARNING: Unable to verify timestamp for VolSnap.sys
*** WARNING: Unable to verify timestamp for disk.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for viaagp.sys
*** WARNING: Unable to verify timestamp for p3.sys
*** WARNING: Unable to verify timestamp for imapi.sys
*** WARNING: Unable to verify timestamp for cdrom.sys
*** WARNING: Unable to verify timestamp for redbook.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for i8042prt.sys
*** WARNING: Unable to verify timestamp for rasl2tp.sys
*** WARNING: Unable to verify timestamp for raspppoe.sys
*** WARNING: Unable to verify timestamp for raspptp.sys
*** WARNING: Unable to verify timestamp for msgpc.sys
*** WARNING: Unable to verify timestamp for termdd.sys
*** WARNING: Unable to verify timestamp for NDProxy.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** WARNING: Unable to verify timestamp for netbios.sys
*** WARNING: Unable to verify timestamp for wanarp.sys
*** WARNING: Unable to verify timestamp for Fips.SYS
*** WARNING: Unable to verify timestamp for Cdfs.SYS
*** WARNING: Unable to verify timestamp for PCIIDEX.SYS
*** WARNING: Unable to verify timestamp for PartMgr.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 usbuhci.sys
*** WARNING: Unable to verify timestamp for RTL8139.SYS
*** WARNING: Unable to verify timestamp for fdc.sys
*** WARNING: Unable to verify timestamp for kbdclass.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** WARNING: Unable to verify timestamp for ptilink.sys
*** WARNING: Unable to verify timestamp for raspti.sys
*** WARNING: Unable to verify timestamp for mouclass.sys
*** WARNING: Unable to verify timestamp for flpydisk.sys
*** WARNING: Unable to verify timestamp for vga.sys
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** WARNING: Unable to verify timestamp for ssmdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for ssmdrv.sys
*** WARNING: Unable to verify timestamp for SASDIFSV.SYS
*** ERROR: Module load completed but symbols could not be loaded for SASDIFSV.SYS
*** WARNING: Unable to verify timestamp for sermouse.sys
*** WARNING: Unable to verify timestamp for watchdog.sys
*** WARNING: Unable to verify timestamp for BOOTVID.dll
*** WARNING: Unable to verify timestamp for serenum.sys
*** WARNING: Unable to verify timestamp for ndistapi.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** WARNING: Unable to verify timestamp for gameenum.sys
*** WARNING: Unable to verify timestamp for rasacd.sys
*** WARNING: Unable to verify timestamp for kdcom.dll
*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** WARNING: Unable to verify timestamp for viaide.sys
*** WARNING: Unable to verify timestamp for dmload.sys
*** WARNING: Unable to verify timestamp for swenum.sys
*** WARNING: Unable to verify timestamp for USBD.SYS
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for Beep.SYS
*** WARNING: Unable to verify timestamp for mnmdd.SYS
*** WARNING: Unable to verify timestamp for RDPCDD.sys
*** WARNING: Unable to verify timestamp for avgio.sys
*** ERROR: Module load completed but symbols could not be loaded for avgio.sys
*** WARNING: Unable to verify timestamp for dump_WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for dump_WMILIB.SYS
*** WARNING: Unable to verify timestamp for ParVdm.SYS
*** WARNING: Unable to verify timestamp for dxgthk.sys
*** WARNING: Unable to verify timestamp for audstub.sys
*** WARNING: Unable to verify timestamp for Null.SYS
Probably caused by : kmixer.sys ( kmixer!PinDispatchClose+322 )

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

---

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sun Jul 19 22:51:41.985 2009 (GMT+2)
System Uptime: 0 days 0:01:06.555
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 C2, {7, cd4, 0, e13bd090}

Unable to load image Fastfat.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Fastfat.sys
*** WARNING: Unable to verify timestamp for sr.sys
Unable to load image pci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pci.sys
Probably caused by : ntoskrnl.exe ( nt!ExFreePoolWithTag+2be )

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

---

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


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

Symbol search path is: C:\Documents and Settings\Marty\Desktop\Nuova cartella (2)
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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sun Jul 19 23:09:24.937 2009 (GMT+2)
System Uptime: 0 days 0:01:49.517
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
..
Unable to load image Npfs.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Npfs.SYS
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {974dd4ea, 0, 80578224, 0}


Could not read faulting driver name
Unable to load image pci.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pci.sys
Probably caused by : Npfs.SYS ( Npfs!NpCreateNewNamedPipe+107 )

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

[VdW]

ciao, ne ho diversi, il pc ha un comportamento un po' particolare che ho descritto qui: http://www.hwupgrade.it/forum/showthread.php?t=2024613

per il resto vi porto i vari report se qualcuno volesse provare ad aiutarmi

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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Fri Jul 31 17:25:36.031 2009 (GMT+2)
System Uptime: 0 days 0:00:56.587
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 1000000A, {0, 2, 1, 8051e106}

Probably caused by : ntoskrnl.exe ( nt!KiInsertTimerTable+57 )

Followup: MachineOwner

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-07.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 20:18:10.625 2009 (GMT+2)
System Uptime: 0 days 0:01:05.195
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 1000000A, {2c, 2, 1, 8051e17d}

Probably caused by : ntoskrnl.exe ( nt!KiRaiseException+76 )

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

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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 20:21:43.640 2009 (GMT+2)
System Uptime: 0 days 0:03:00.199
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 1000008E, {c0000005, 80543803, ee250804, 0}

Unable to load image aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : hardware ( aswMon2+66ce )

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

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-07.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 20:18:10.625 2009 (GMT+2)
System Uptime: 0 days 0:01:05.195
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 1000000A, {2c, 2, 1, 8051e17d}

Probably caused by : ntoskrnl.exe ( nt!KiRaiseException+76 )

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

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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 20:02:24.859 2009 (GMT+2)
System Uptime: 0 days 0:01:26.406
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 1000000A, {0, 2, 1, 8051e106}

*** WARNING: Unable to verify timestamp for Ntfs.sys
*** WARNING: Unable to verify timestamp for fltmgr.sys
Unable to load image aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+83c )

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

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-05.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 19:56:30.562 2009 (GMT+2)
System Uptime: 0 days 0:01:36.115
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 1000000A, {0, 2, 1, 8051e106}

Unable to load image aswMon2.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswMon2.SYS ( aswMon2+600e )

Followup: MachineOwner

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-04.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 19:52:54.406 2009 (GMT+2)
System Uptime: 0 days 0:01:20.955
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 1000000A, {0, ff, 1, 8052401a}

Probably caused by : memory_corruption ( nt!MiAttachToSecureProcessInSession+33 )

Followup: MachineOwner

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-03.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 19:50:59.218 2009 (GMT+2)
System Uptime: 0 days 0:00:23.785
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 1000000A, {2c, 2, 1, 8051e17d}

Probably caused by : ntoskrnl.exe ( nt!KiRaiseException+76 )

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

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-02.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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 14:04:09.234 2009 (GMT+2)
System Uptime: 0 days 0:00:52.787
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 1000000A, {c8966008, 2, 1, 8051e129}

Probably caused by : ntoskrnl.exe ( nt!KiInsertTreeTimer+23 )

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

Loading Dump File [C:\WINDOWS\Minidump\Mini073009-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) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Thu Jul 30 14:00:14.828 2009 (GMT+2)
System Uptime: 0 days 0:00:28.390
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 1000000A, {eb000043, 2, 1, 8051e17d}

Probably caused by : ntoskrnl.exe ( nt!KiRaiseException+76 )

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

questi sono solo quelli di oggi e ieri... se può servire ne ho 3 o 4 per ogni giorno...

saluti speranzosi