PROBLEMA schermata blu e analisi con whocrashed

[simone_asr]

Ho avuto per 4 volte una schermata blu di errore, che dopo poco sparisce e fa riavviare il computer. Dopo la prima, l'ho formattato, e poi è comparsa altre tre volte.
Ho sostituito ieri la mobo, la cpu e le ram, poco tempo fa ho sostituito anche l'hdd (ora ho un ssd, sull'hhd ho windows 8 e ubuntu).
La schermata blu mi si presenta casualmente, ora sto scrivendo con il pc che ha questo problema.

so: windows 7
mobo: asus m5a97 r2.0
cpu: amd fx 8120
ram: corsair 8gb a 1600 di frequenza

analisi whocrashed
[FONT=Segoe UI, Arial]On Sat 27/07/2013 10:04:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-22510-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E23B96, 0x0, 0x20)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 27/07/2013 10:04:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E23B96, 0x0, 0x20)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 27/07/2013 10:03:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-24351-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x6F880)
Bugcheck code: 0x50 (0xFFFFF89FE6633A54, 0x1, 0xFFFFF800031A5D98, 0x5)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 26/07/2013 22:51:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-8236-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x71F00)
Bugcheck code: 0x4E (0x99, 0x198B4D, 0x2, 0x199B4C)
Error: [FONT=Segoe UI, Arial]PFN_LIST_CORRUPT[/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 the page frame number (PFN) list is corrupted.
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 that cannot be identified at this time.
[/FONT]

 

[Isildur8]

In poche parole hai formattato, cambiato praticamente PC, e il problema continua a sussistere?

 

[simone_asr]

In poche parole hai formattato, cambiato praticamente PC, e il problema continua a sussistere?

No no, mi sono spiegato male, questo problema prima di cambiare mobo, cpu e ram non me lo dava!
Tutti e 4 i casi analizzati da whocrashed dicono che non dovrebbe essere un problema hardware, ma software..
Ho fatto il test delle RAM, niente errori.
Ho fatto scandisk sull'hdd, niente errori.
Ora provo con lo scandisk sull'ssd, poi faccio altri test e prove.
Tutti i pezzi comprati sono nuovi, non usati.

- - - Updated - - -

Ehm.. Forse potrebbe essere che avevo messo per sbaglio il processore in overclock? Invece di andare a 3100, andava a quasi 3900? Si surriscaldava e.. boom?