PROBLEMA Crash con schermata blu su windows 7

Pubblicità
mat7e0

mat7e0

Utente Attivo
Messaggi
490
Reazioni
24
Punteggio
51
Salve a tutti ieri mi è apparsa la prima volta sta famosa schermata blu e oggi altre 4 volte.....è successo mentre usavo pinnacle studio e una volta mentre avviavo tomb raider ......come posso verificare cosa è successo? ...Grazie anticipate :)
 
al riavvio dice questo :
Firma problema:
Nome evento problema: BlueScreen
Versione SO: 6.1.7601.2.1.0.256.48
ID impostazioni locali: 1040

Ulteriori informazioni sul problema:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800030B5732
BCP3: FFFFF880009A9758
BCP4: FFFFF880009A8FB0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\040413-9609-01.dmp
C:\Users\Matteo\AppData\Local\Temp\WER-20529-0.sysdata.xml

Leggere l'informativa sulla privacy online:
Informativa sulla privacy di Windows 7 - Microsoft Windows

Se l'informativa sulla privacy online non è disponibile, leggere quella offline:
C:\Windows\system32\it-IT\erofflps.txt
 
Pez_93 ha detto:
Scarica WhoCrashed e posta la lettura del file dmp.
Clicca per espandere...

ecco qui ;)

[FONT=Segoe UI, Arial]System Information (local)
[/FONT]
[FONT=Segoe UI, Arial]computer name: MATTEO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 6339239936 total
VM: 2147352576, free: 1894236160


[/FONT]
[FONT=Segoe UI, Arial]
Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Thu 04/04/2013 12:59:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-9609-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0xA6732)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030B5732, 0xFFFFF880009A9758, 0xFFFFF880009A8FB0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 04/04/2013 12:31:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-9625-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0xA6732)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030A8732, 0xFFFFF880033E06D8, 0xFFFFF880033DFF30)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 04/04/2013 11:42:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040413-9672-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F9180, 0x6)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 03/04/2013 14:18:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040313-13977-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]dxgmms1.sys[/FONT] (0xFFFFF88006F995C8)
Bugcheck code: 0x3D (0xFFFFF88002BA0B80, 0x0, 0x0, 0xFFFFF88006F995C8)
Error: [FONT=Segoe UI, Arial]INTERRUPT_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: DirectX Graphics MMS
Bug check description: This bug check appears very infrequently.
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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 may help you investigate this further.

[/FONT]

- - - Updated - - -

up
 
L'errore ntoskrnl.exe può anche essere causato dai driver video,disinstallali insieme(se lo hai) al software di gestione della scheda video,dai una ripulita a file e registro con Ccleaner riavvia il pc e installa i nuovi driver scaricandoli dal sito del produttore della tua gpu.
 
enrygoogle ha detto:
no memtest si esegue all'avvio puoi trovare facilmente il download dell iso cercando su google
Clicca per espandere...
sisi lo so solo che al momento non ho una penna usb per montare la iso, appena posso provo comunque


provato anche con memtest e niente errori...
Wolfestein ha detto:
L'errore ntoskrnl.exe può anche essere causato dai driver video,disinstallali insieme(se lo hai) al software di gestione della scheda video,dai una ripulita a file e registro con Ccleaner riavvia il pc e installa i nuovi driver scaricandoli dal sito del produttore della tua gpu.
Clicca per espandere...

ok grazie ora provo :)
in effetti non so se centra qualcosa ma il giorno prima (mi pare) è apparsa la notifica in basso a destra che i driver video avevano smesso di funzionare...però mi pare anhce che ho già provato a disintallare i driver o ad aggiornarli mm
disinstallato come consigliato ma niente .....comunque ma non mi compaiono neanche piu i file del crash....
 
Ultima modifica:
Pubblicità
Pubblicità
Indietro
Top