PROBLEMA Blue Screen Windows 7

[RobyPaice89]

Salve ragazzi, sto impazzendo con i vari blue screen che si verificano quando navigo in internet mentre guardo video (raramente), mentre gioco (di frequente), e ogni qualvolta accendo Torrent durante la notte, ritrovando spesso la mattina seguente il pc riavviato. Come posso risolvere? vi ringrazio in anticipo.

 

[Tekuru]

Detto così penso siano le temperature. Prima avevi questo problema? Da quanto hai questo problema? Tieni sotto controllo le temperature della CPU e della GPU mentre fai le tue cose in modo da capire se è quello il problema poi facci sapere.

 

[RobyPaice89]

Non ricordo di preciso quando è iniziato, ma saranno già 2 settimane più o meno, per quanto riguarda le temperature per la CPU si va dai 28° a max. 39°, mentre per la scheda grafica dai 42° ai 46°.

 

[Kilotroon]

Per le temperature sono normali , per avere un minimo di strada da seguire puoi leggere negli eventi di windows di che errore si tratta anche se dubito che sia un kernel error

 

[RobyPaice89]

Ho fatto un test con memtest86+, l'ho lasciato andare per tutta la notte, ha completato 8 passaggi senza errori.

Questo è quanto riportato da WhoCrashed

[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 Tue 08/04/2014 22:41:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040914-31265-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x8, 0x8, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 08/04/2014 22:41:28 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: 0xD1 (0xFFFFFFFFFFFFFFFF, 0x8, 0x8, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 08/04/2014 22:23:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040914-18375-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x101 (0x60, 0x0, 0xFFFFF880009E9180, 0x1)
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 Tue 08/04/2014 22:16:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040914-30406-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x101 (0x60, 0x0, 0xFFFFF880009E9180, 0x1)
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 Tue 08/04/2014 21:46:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-30812-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BC0)
Bugcheck code: 0x101 (0x60, 0x0, 0xFFFFF880009E9180, 0x1)
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 Tue 08/04/2014 20:20:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040814-28218-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80036CB038, 0xB6000000, 0x181)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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]

- - - Updated - - -

Up