PROBLEMA Windows 7 Blue Screen

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
Salve a tutti,
è da un po' di tempo che il mio PC si blocca improvvisamente (solitamente durante sessioni di gioco, ma talvolta anche mentre navigo su internet) e sono costretto a spegnerlo manualmente dal tasto di accensione. Al riavvio Windows mi apre questa finestra di errore:


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: 101
BCP1: 0000000000000061
BCP2: 0000000000000000
BCP3: FFFFF880009BF180
BCP4: 0000000000000001
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


File che contribuiscono alla descrizione del problema:
C:\Windows\Minidump\051716-23119-01.dmp
C:\Users\PC\AppData\Local\Temp\WER-93803-0.sysdata.xml

Inoltre la schermata di avvio non appare più, infatti il monitor non rileva nessun input fino a quando non appare la schermata del desktop.
Come posso risolvere?
Grazie in anticipo.
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
Ecco qui i log di Whocrashed (ho messo quelli di tutti i crash che ha rilevato):

[FONT=Segoe UI, Arial]Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 17/05/2016 14:13:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051716-23119-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]unknown_module_00000000`00000000.sys[/FONT] (Unloaded_Unknown_Module_00000000`00000000+0x101)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
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: unknown_module_00000000`00000000.sys .
Google query: [FONT=Segoe UI, Arial]unknown_module_00000000`00000000.sys CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Tue 17/05/2016 14:13:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]unknown_module_00000000`00000100.sys[/FONT] (Unloaded_Unknown_Module_00000000`00000100+0x1)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
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: unknown_module_00000000`00000100.sys .
Google query: [FONT=Segoe UI, Arial]unknown_module_00000000`00000100.sys CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 16/05/2016 17:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051716-21278-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74EC0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 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 Thu 05/05/2016 12:17:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050516-17628-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0xFFFFF8000228DEC0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial][/FONT]

- - - Updated - - -

Ho scaricato Driver Booster 3, aggiornato tutti i drivers, riavviato il pc e fatto un test per verificare se il problema persisteva e purtroppo è crashato ancora...
 
I

Il cecchino Jackson

Ospite
Aspetta qualcuno più esperto di me con i log di whocrashed . Vedrai che arriva . Anche perchè ora non posso mettermi a cercare info online per quegli errori ( magari prova a farlo tu nel frattempo )
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
Proverò a cercare...sperando che nel frattempo qualcuno risponda.
Intanto ti ringrazio!
 
Ultima modifica:
I

Il cecchino Jackson

Ospite
Poi a parte un avvio pulito ( cerca la guida ufficiale microsoft gongolando avvio pulito Windows 7) non so che consigliarti, ma vedrai che arriverà qualcuno più esperto che oggi non c'era
 

Federico83

UTENTE LEGGENDARIO
Utente Èlite
35,407
6,323
CPU
Ryzen 7 3700X
Dissipatore
NDH15
Scheda Madre
Gigabyte auros X570 elite
HDD
4.5TB + 15 di NAS lol
RAM
16 GB G.Skill 3200
GPU
RTX2070
Monitor
IIyama 28" 4K
PSU
Cooler Master GX 650
Case
REV200
OS
Windows11x64pro
Ecco qui i log di Whocrashed (ho messo quelli di tutti i crash che ha rilevato):

[FONT=Segoe UI, Arial]Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 17/05/2016 14:13:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051716-23119-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]unknown_module_00000000`00000000.sys[/FONT] (Unloaded_Unknown_Module_00000000`00000000+0x101)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
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: unknown_module_00000000`00000000.sys .
Google query: [FONT=Segoe UI, Arial]unknown_module_00000000`00000000.sys CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Tue 17/05/2016 14:13:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]unknown_module_00000000`00000100.sys[/FONT] (Unloaded_Unknown_Module_00000000`00000100+0x1)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
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: unknown_module_00000000`00000100.sys .
Google query: [FONT=Segoe UI, Arial]unknown_module_00000000`00000100.sys CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 16/05/2016 17:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051716-21278-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x74EC0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 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 Thu 05/05/2016 12:17:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050516-17628-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0xFFFFF8000228DEC0)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009BF180, 0x1)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
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.
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]


[/FONT]
[FONT=Segoe UI, Arial][/FONT]

- - - Updated - - -

Ho scaricato Driver Booster 3, aggiornato tutti i drivers, riavviato il pc e fatto un test per verificare se il problema persisteva e purtroppo è crashato ancora...

specifiche del sistema in uso? antivirus installato?
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
specifiche del sistema in uso? antivirus installato?

Come antivirus attualmente ho Avast Free. Per specifiche del sistema intendi CPU, scheda video etc.? (Non sono molto ferrato, scusami)

- - - Updated - - -

specifiche del sistema in uso? antivirus installato?

Come antivirus attualmente ho Avast Free. Per specifiche del sistema intendi CPU, scheda video etc.? (Non sono molto ferrato, scusami)
 
I

Il cecchino Jackson

Ospite
Come antivirus attualmente ho Avast Free. Per specifiche del sistema intendi CPU, scheda video etc.? (Non sono molto ferrato, scusami)

- - - Updated - - -



Come antivirus attualmente ho Avast Free. Per specifiche del sistema intendi CPU, scheda video etc.? (Non sono molto ferrato, scusami)

Si puoi usare speccy
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
Ecco qui il Riepilogo si Speccy:
Riepilogo Sistema Operativo
Windows 7 Professional 64-bit SP1
CPU
AMD A4-3400 61 °C
Tecnologia Llano 32nm
RAM
8,00GB DDR3 @ 532 MHz (7-7-7-20)
Scheda Madre
ASRock A75M-HVS (CPUSocket) 43 °C
Grafica
S22B150 (1920x1080@60Hz)
512 MBATI AMD Radeon HD 6410D (ASRock) 64 °C
2047 MBNVIDIA GeForce GT 630 (CardExpert Technology) 39 °C
CrossFire Disattivato
Versione ForceWare: 365.19
SLI Disattivato
Memorizzazione
465GB Western Digital WDC WD50 00AAKX-00ERMA0 SATA Disk Device (SATA) 45 °C
Drive Ottici
DTSOFT Virtual CdRom Device
HL-DT-ST DVDRAM GH24NS95 ATA Device
Audio
NVIDIA High Definition Audio
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
I

Il cecchino Jackson

Ospite
Appena fatto, il problema sembrerebbe essersi risolto...però allo startup continuo a non vedere nulla finché arriva alla schermata del desktop

Avast lo hai con lo strumento del produttore ?
Se capisco bene A me quella cosa la faceva su XP dove non tolsi Norton . Si risolse comunque dopo qualche accensione / riavvio
 

Manu01

Nuovo Utente
74
6
CPU
Intel Core i5-6600 3.30GHz
Scheda Madre
msi B150M Bazooka
HDD
500GB HDD, 250GB SSD
RAM
2x8GB HyperX Fury 2133MHz
GPU
Asus GeForce GTX960 Strix
PSU
Corsair CX550M
Case
NZXT S340
OS
Windows 7 Ultimate
Avast lo hai con lo strumento del produttore ?
Se capisco bene A me quella cosa la faceva su XP dove non tolsi Norton . Si risolse comunque dopo qualche accensione / riavvio
Ho disinstallato Avast per l'avvio pulito, ma riscontro lo stesso il problema
 

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!