Crash con schermata blu su windows 7

[matty200]

Salve a tutti l'altro ieri mi è apparsa la prima volta sta famosa schermata blu e ieri altre 4 volte.....è successo mentre usavo pinnacle studio e una volta mentre avviavo tomb raider ......all'ultimo riavvio ho copiato l'errore , eccolo :

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

e usando WhoCrashed mi da questo come risultato:

System Information (local)
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



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

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: ntoskrnl.exe (nt+0xA6732)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030B5732, 0xFFFFF880009A9758, 0xFFFFF880009A8FB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.



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: ntoskrnl.exe (nt+0xA6732)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030A8732, 0xFFFFF880033E06D8, 0xFFFFF880033DFF30)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.



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: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030F9180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
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 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.



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: dxgmms1.sys (0xFFFFF88006F995C8)
Bugcheck code: 0x3D (0xFFFFF88002BA0B80, 0x0, 0x0, 0xFFFFF88006F995C8)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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.



Conclusion
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.

quindi? cosa può essere? la cpu che non ce la fa? ...o.O o cosa?

[Eress]

Potrebbe anche essere che il processore stia per lasciarti.

http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

[matty200]

Originariamente inviato da Eress

Potrebbe anche essere che il processore stia per lasciarti.

http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

dici? di già? però lo fa solo col programma di eidting...forse è il video da caricare troppo grosso e sforza troppo? mmh