PROBLEMA Aiuto BSOD! sono disperato!

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
ciao a tutti, è un pò di tempo che poco dopo aver accesso il pc mi crasha; ho provato ad usare memtest ma non mi da nessun errore, i driver sono tutti aggiornati; vi posto il risultato dell'analisi fatta con who crashed

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 06/01/2015 12:10:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010615-10358-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8987858A2, 0xB3B7465EEAF527F8, 0xFFFFF80003130713, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.



On Tue 06/01/2015 12:06:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010615-10202-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1048C0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002F078C0, 0xFFFFF8800338C758, 0xFFFFF8800338BFB0)
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 Tue 06/01/2015 12:06:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002F078C0, 0xFFFFF8800338C758, 0xFFFFF8800338BFB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 05/01/2015 22:58:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010615-12121-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4E (0x99, 0x6D69, 0x3, 0xC2F1)
Error: PFN_LIST_CORRUPT
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 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.



On Sat 03/01/2015 12:41:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010315-10015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D89889E50E, 0xB3B7465EEB06B464, 0xFFFFF80002F295B0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.



On Sat 03/01/2015 12:33:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010315-11778-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D89848E681, 0xB3B7465EEAC5B5D7, 0xFFFFF80002F29615, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.



On Wed 31/12/2014 01:25:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123114-9843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D898C8F4EC, 0xB3B7465EEB45C452, 0xFFFFF8000323D2D0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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.



On Wed 31/12/2014 01:19:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123114-10264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF68000016C80, 0x0, 0x0, 0xFFFFF80002FA83B6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 30/12/2014 18:28:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123014-13150-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFF6800037D6B0, 0x0, 0x0, 0xFFFFF80002E615D7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.




Conclusion


9 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


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



 

Unreal6777

Utente Èlite
4,420
603
Hardware Utente
CPU
I7 8700k
RAM
16gb
Scheda Video
1080ti
Monitor
2k
Sistema Operativo
Windows/macos/Linux
Non riesco a capire perché ci sono tutti errori diversi.

Prova ad avviare in modalità provvisoria e fare un ripristino da un punto precedente. Poi una scansione con qualche antivirus e anti malware.

Prova anche a cambiare driver della gpu. Perché avevo letto che era legato alla scheda video per qualche motivo anche se non dovrebbe centrare.
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
Non riesco a capire perché ci sono tutti errori diversi.

Prova ad avviare in modalità provvisoria e fare un ripristino da un punto precedente. Poi una scansione con qualche antivirus e anti malware.

Prova anche a cambiare driver della gpu. Perché avevo letto che era legato alla scheda video per qualche motivo anche se non dovrebbe centrare.
il problema è che non so quando il pc era perfettamente funzionante, è un pò che mi crasha.
la scansione l'ho fatta qualche giorno fa e non mi ha rilevato niente.
per aggiornare i driver della scheda meglio andare sul sito del produttore?
 

mattia29

Utente Attivo
884
104
Hardware Utente
CPU
FX-8320 + HYPER 212 EVO
Scheda Madre
ASUS M5A99FX R2.0
Hard Disk
SSD CORSAIR FORCE 3 120 GB +HD CAVIAR BLUE 1 TB
RAM
8GB CRUCIAL BALLISTIX ELITE
Scheda Video
SAPPHIRE R9 280X VAPOR-X
Scheda Audio
RAZER KRAKEN 7.1
Monitor
SAMSUNG 20'' 1680X1050
Alimentatore
MK III 500W 80+ BRONZE
Case
COOLER MASTER 690 II ADVANCED USB 3.0 EDITION
Sistema Operativo
WINDOWS 7 ULTIMATE
hai toccato voltaggi ? se si riporta a default
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
ho cambiato la frequenza delle ram, da auto a 1600mhz
 

neurone3

Utente Attivo
1,005
126
Hardware Utente
CPU
Intel Core i5 4670k @4.5Ghz | i7 4700HQ
Scheda Madre
Msi GD-65 z87 Gaming
Hard Disk
SSD Kingston V300 120gb | 750GB 7200rpm
RAM
G.skil ripjaws 8GB 1600Mhz | 16GB 1600Mhz
Scheda Video
evga GTX770 Classified 4gb ACX cooler | Gtx 880M
Scheda Audio
Main Default
Monitor
LG Buffissimo da spendere poco 21.5" LED FHD | 17.3" FHD
Alimentatore
Seasonic P660W 80+ Platinum
Case
Corsair obsidian 650D | Asus rog G750JZ
Sistema Operativo
Windows 7 Ultimate x64 | Windows 8.1 Pro x64
riporta le ram a auto e fai un format
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1

neurone3

Utente Attivo
1,005
126
Hardware Utente
CPU
Intel Core i5 4670k @4.5Ghz | i7 4700HQ
Scheda Madre
Msi GD-65 z87 Gaming
Hard Disk
SSD Kingston V300 120gb | 750GB 7200rpm
RAM
G.skil ripjaws 8GB 1600Mhz | 16GB 1600Mhz
Scheda Video
evga GTX770 Classified 4gb ACX cooler | Gtx 880M
Scheda Audio
Main Default
Monitor
LG Buffissimo da spendere poco 21.5" LED FHD | 17.3" FHD
Alimentatore
Seasonic P660W 80+ Platinum
Case
Corsair obsidian 650D | Asus rog G750JZ
Sistema Operativo
Windows 7 Ultimate x64 | Windows 8.1 Pro x64
in teoria è la soluzione più comoda.
In modalità provvisoria ti da lo stesso problema? se non te lo da disintalla tutti i driver da li e poi reinstallali
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
in teoria è la soluzione più comoda.
In modalità provvisoria ti da lo stesso problema? se non te lo da disintalla tutti i driver da li e poi reinstallali
scusa l'ignoranza ma praticamente dopo che ho rimesso su auto le ram entro in modalità provvisoria e poi per reinstallare i driver come faccio? da gestione dispositivi?
 

neurone3

Utente Attivo
1,005
126
Hardware Utente
CPU
Intel Core i5 4670k @4.5Ghz | i7 4700HQ
Scheda Madre
Msi GD-65 z87 Gaming
Hard Disk
SSD Kingston V300 120gb | 750GB 7200rpm
RAM
G.skil ripjaws 8GB 1600Mhz | 16GB 1600Mhz
Scheda Video
evga GTX770 Classified 4gb ACX cooler | Gtx 880M
Scheda Audio
Main Default
Monitor
LG Buffissimo da spendere poco 21.5" LED FHD | 17.3" FHD
Alimentatore
Seasonic P660W 80+ Platinum
Case
Corsair obsidian 650D | Asus rog G750JZ
Sistema Operativo
Windows 7 Ultimate x64 | Windows 8.1 Pro x64
dovresti poterli disinstallare dal pannello di controllo, oppure metti il cd e li reinstalli
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
dovresti poterli disinstallare dal pannello di controllo, oppure metti il cd e li reinstalli
una volta disinstallati li devo per forza installare con il cd?o è meglio scaricarli?
 

Chunky2

Utente Attivo
476
85
Hardware Utente
CPU
Intel® Core™ i3-550 @3.20 GHz
Scheda Madre
ASRock > H55M-LE
Hard Disk
HDD Western Digital 500 GB 7200 RPM
RAM
Corsair (se non erro) 4GB DDR3 1333 Mhz
Scheda Video
AMD Radeon™ HD 7770 1 GB
Scheda Audio
Integrata
Monitor
Samsung SyncMaster 2043SN LCD HD
Alimentatore
Corsair 550 Watt
Case
nero, cinese
Sistema Operativo
Windows 7 Ultimate x64 bit
aaaah i poteri degli UPS, questi sconosciuti sottovalutati...
mai avute BSOD in vita mia...
 

Marchio87

Utente Attivo
429
47
Hardware Utente
CPU
I7 4790K
Dissipatore
Cooler Master Hyper 212 Evo
Scheda Madre
Msi Z97 Gaming 5
Hard Disk
Western Digital 2 Tb + Samsung 250 GB 840 Evo
RAM
Corsair Dimm Vengeance 8GB (2x4GB) DDR3 1600 MHz
Scheda Video
ASUS GeForce GTX 970 4 GB
Scheda Audio
Integrata
Monitor
BenQ XL2420T
Alimentatore
Silverstone 700W 80 Plus Bronze
Case
CM Storm Trooper
Sistema Operativo
Windows 7 Ultimate SP1
dopo alcuni giorni che andava tutto bene oggi ha crashato di nuovo. non so più cosa fare!

[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 10/02/2015 12:26:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021015-10264-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x76E80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034B54C6, 0xFFFFF88006E12080, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/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 exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 10/02/2015 12:24:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021015-10249-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x35A4C2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF800033A94C2, 0xFFFFF880033708C8, 0xFFFFF88003370120)
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 Tue 10/02/2015 12:24:26 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: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF800033A94C2, 0xFFFFF880033708C8, 0xFFFFF88003370120)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 10/02/2015 12:23:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021015-10374-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x76E80)
Bugcheck code: 0x109 (0xA3A039D8984AC897, 0xB3B7465EEAC797ED, 0xFFFFF80003035620, 0x1)
Error: [FONT=Segoe UI, Arial]CRITICAL_STRUCTURE_CORRUPTION[/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 kernel has detected critical kernel code or data corruption.
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]
 

Entra

oppure Accedi utilizzando