-
.
Salve a tutti,ebbene si torno qui a scrivere dei miei problemi,ora sembrerebbe una cosa piu grave
Ogni giorno(soprattutto ieri)che gioco a Black Ops,che sia su Photoshop o Msn il pc mi mostra una schermata blu con in seguito un riavvio. Si riavvia e al caricamento del So si riavvia di nuovo. Dopo un po di tentativi però parte. Quando si accende e accede al desktop mi esce una schermata con errore di windows ecc...clicco su visualizza dettagli,e vedo sempre i soliti 2 file che contribuiscono al problema:120910-25552-01.dmp e WER-32307-0.sysdata.xml. Se guardo la loro di creazione...è data dall'ultimo riavvio,quindi non so che sia,e quindi chiedo agli esperti aiuto
Grazie
. -
Hack3rMinD.
User deleted
installa whocrashed www.resplendence.com/download/whocrashedSetup.exe e posta un risultato dell'analisi
sistema operativo?. -
.
Windows 7 Ultimate...ora scarico e vedo.. SPOILER (click to view)Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 09/12/2010 15:52:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-32307-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007EBE188, 0xFFFFF88007EBD9F0, 0xFFFFF80002FB20BF)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 09/12/2010 15:52:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: amon.sys (amon+0x49E5)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007EBE188, 0xFFFFF88007EBD9F0, 0xFFFFF80002FB20BF)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\amon.sys
product: NOD32 Antivirus System
company: Eset
description: Amon monitor
Bug check description: This indicates a problem occurred in the NTFS file system.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amon.sys (Amon monitor, Eset ).
Google query: amon.sys Eset NTFS_FILE_SYSTEM
On Thu 09/12/2010 14:33:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-25552-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002E61698, 0xFFFFF88002E60F00, 0xFFFFF880012CCB35)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Thu 09/12/2010 13:40:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-24710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00282F560, 0xFFFFF8A00282F580, 0x5020111)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 09/12/2010 13:18:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120910-23244-01.dmp
This was probably caused by the following module: sptd.sys (sptd+0x1160)
Bugcheck code: 0xBE (0xFFFFF88001060160, 0x39E6121, 0xFFFFF88002FFC5A0, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\drivers\sptd.sys
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sptd.sys .
Google query: sptd.sys ATTEMPTED_WRITE_TO_READONLY_MEMORY
On Wed 08/12/2010 17:14:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120810-20888-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x4CA97)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880016CDA97, 0xFFFFF88002FE0EC8, 0xFFFFF88002FE0730)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 08/12/2010 12:17:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120810-19827-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x882B7)
Bugcheck code: 0xD1 (0xFFFFCC80324CFE98, 0x2, 0x1, 0xFFFFF880016C62B7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 08/12/2010 11:45:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120810-18283-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0xD1 (0x147782C10, 0x2, 0x0, 0xFFFFF8800183EB97)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 08/12/2010 09:08:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120810-26208-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003196720, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 05/12/2010 12:08:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120510-25069-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x50 (0xFFFFF87FBB179784, 0x0, 0xFFFFF8800104C884, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 02/12/2010 15:02:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120210-23306-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x50 (0xFFFFF80002CE63B0, 0x8, 0xFFFFF80002CE63B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 02/12/2010 15:00:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120210-24741-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031A20CC, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 24/11/2010 13:08:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112410-21543-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0xD1 (0x1, 0x2, 0x8, 0x1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 23/11/2010 14:36:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112310-20592-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x4CA97)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001702A97, 0xFFFFF88002FD9EC8, 0xFFFFF88002FD9730)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 10/11/2010 19:09:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111010-22417-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x202AF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003AA22AF, 0xFFFFF880051F68B8, 0xFFFFF880051F6120)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
21 crash dumps have been found and analyzed. Only 15 are included in this report. 3 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
amon.sys (Amon monitor, Eset )
sptd.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer m. -
Hack3rMinD.
User deleted
> aggiorna win7
> aggiorna i driver della scheda video
> disinstalla nod32 e metti antivir free
> esegui uno scandisk #entry293242482. -
.
Ok,lo scandisk l'ho fatto e anche l'aggiornamento driver..domani che ho tempo faccio le ultime 2 cosette e poi ti dico . -
.
Ma al riavvio dopo aver dato la procedura dal prompt dei comandi,dovrei vedere una finestra col processo?Perchè al riavvio non ho notato nulla..poi Windows update mi da un errore,non so cosa sia ma nob mi lascia..Nod32 invece mio fratello mi obbliga a lasciarlo perchè secondo lui va benissimo e non abbiamo mai avuto problemi(infatti)...ultima cosa,ma i driver delle schede video ati io l'ho aggiornato dal setup dentro la cartella della directory..ma per essere sicuro come potrei fare?
Scusa se disturbo ma vorrei essere sicuro
. -
milanista95.
User deleted
sicuro di aver programmato lo scandisk al prossimo riavvio 
?
. -
Hack3rMinD.
User deleted
Ma al riavvio dopo aver dato la procedura dal prompt dei comandi,dovrei vedere una finestra col processo?Perchè al riavvio non ho notato nulla..poi Windows update mi da un errore,non so cosa sia ma nob mi lascia..Nod32 invece mio fratello mi obbliga a lasciarlo perchè secondo lui va benissimo e non abbiamo mai avuto problemi(infatti)...ultima cosa,ma i driver delle schede video ati io l'ho aggiornato dal setup dentro la cartella della directory..ma per essere sicuro come potrei fare?
Scusa se disturbo ma vorrei essere sicuro
> si quella procedura viene eseguita all'avvio successivo
> hai eseguito il windows update da Pannello di controllo\Sistema e sicurezza\Windows Update?
qui http://kbupdate.info/ puoi trovare tutti i fix suddivisi per sistema operativo (ordine cronologico e alfabetico)
> se proprio vuoi lasciare nod32, assicurati di avere l'ultima versione
> i driver della scheda video devi prenderli dal sito del produttore
http://support.amd.com/it/gpudownload/Pages/index.aspx o www.nvidia.it/Download/index.aspx?lang=it
> temperature della scheda video?
> temperature dell'hard disk?
scarica hdtune www.hdtune.com/files/hdtune_255.exe esegui un error scan e posta uno screen del risultato ed uno screen della schermata Health. -
.
Ok,il procedimento con scandisk l'ho fatto,nod32 ho l'ultimo aggiornamento perchè è sempre aggiornamento..ora metto hdtune e poi vedo con l'update e i driver..grazie poi ti dico
Driver installatie aggiornato sistema operativo..tra poco l'esito di HD tune. -
.
http://img535.imageshack.us/f/rim.png/ . -
Hack3rMinD.
User deleted
tutto ok
e la pagina health?
nod32: devi avere l'ultima versione del software (non intendevo gli aggiornamenti), dovrebbe essere la 4.20
temperature della scheda video? puoi monitorarle con gpu-z http://www.techpowerup.com/downloads/1907/...U-Z_v0.4.9.html
. -
.
Pagine Health SPOILER (click to view)
La temperatura è a 47°-48° stabili della scheda video...
Quindi?Oggi il problema non si è verificato quindi spero di aver risolto..ora aspetto le opinioni del tecnico
. -
Hack3rMinD.
User deleted
mah niente di preoccupante
vedi un pò come va la situazione dopo tutte queste operazioni che hai fatto...
ps. cosa sono tutte quelle barre in firefox?
. -
. boh sinceramente non so dirti,sono tutte cose che mette mio fratello e io anche senza volerlo..però dai sono abbastanza utili
Vi terrò aggiornati. -
.
Mi ha fatto schermata blu con spbm.sys..dannazione .
![Pro Evolution Soccer Online League [PESOL]](https://i.imgur.com/AsL9j.png)
Blue screen... |
