PROBLEMA crash frequente di win7

superfabio

Nuovo Utente
36
0
CPU
AMD FX 8320
Scheda Madre
Asrock 990FX Extreme3
HDD
SSD Samsung Pro 256GB - HDD WD Caviar Blue 1TB
RAM
G.Skill Ares 8GB (2x4GB) 1866Mhz CL 9-10-9
GPU
ATI Radeon HD 7950 Sapphire 3GB
Monitor
Hanns G 22"
PSU
Enermax Triathlor 650W
Case
Cooler Master Haf 912 Plus
OS
Windows 7
Salve a tutti, vi presento un problema che mi capita da alcuni giorni, meno di una settimana.
Ogni tanto, con tempistiche random, il pc dà bsod, con errori spesso diversi. Capita che per qualche ora non accada nulla, poi magari in mezz'ora crasha 3 volte.


Eseguendo Memtest86+ da boot, in 3 ore (2 cicli completi) ho collezionato la bellezza di 988.000 errori circa: è possibile? Con Hcl Memtest neanche un errore oppure errore all'avvio ("memory error detected! Pair 106374279 does not store values accurately."), che si risolve facendo partire più copie di memtest contemporaneamente, come suggerito.


Ciò che mi lascia perplesso è la serie di "stranezze" che si stanno verificando contemporaneamente, per esempio alcuni processi non vengono aperti (es services.exe), windows firewall non si riesce ad attivare in nessun modo, windows update idem, steam non riesce più a installare nessun gioco (mi crashava in particolare quando giocavo a cs, l'ho disinstallato e ora non me lo fa più installare).
Questo è ciò che ho notato PER ORA.

Non credo di avere virus, ho fatto girare ComboFix ma non ha dato errori.
Adesso sto controllando la CPU con prime95 ma non ci dovrebbe essere nulla di strano.

Alcuni driver non erano aggiornati all'inizio, poi ho usato sia la utility di AMD, sia DriverBooster e ora sono tutti aggiornati.

Ormai credo di aver provato tutto, in spoiler vi lascio le specifiche del mio pc e i bsod.
Preciso inoltre che il mio pc ha meno di un anno di vita, in quanto l'ho ordinato da nuovo e montato a luglio.


Appena finirà lo stress test eseguirò MemTest86+ con un solo banco di RAM alla volta, ma davvero così tanti errori mi sembrano eccessivi, potrebbe essere non compatibile? Infatti nella schermata di MemTest la frequenza delle RAM non era corretta....

Ringrazio estremamente chiunque mi aiuti.

PC:
CPU AMD FX- 8320
MOBO Asrock FX990 Extreme3
RAM G.Skill Ares 8GB (2x4GB CL 9-10-9 1866MHz)
VGA ATI Radeon HD Sapphire 7950 3GB
SSD Samsung Pro 840 256GB
HDD WD Caviar Blue 1TB
PSU Enermax Triathlor 650W

Crash:
Crash Reports from WhoCrashed

Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.

On Wed 19/02/2014 13:22:29 your computer crashed

This was likely caused by the following module: mpfilter.sys
Bugcheck code: 0x50 (0xFFFFFA33073A2198, 0x0, 0xFFFFF88001125100, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021914-11528-01.dmp
file path: C:\Windows\system32\drivers\mpfilter.sys
product: Microsoft Malware Protection
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 18/02/2014 22:24:22 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x38, 0x2, 0x0, 0xFFFFF80003105C27)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\021814-11434-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 18/02/2014 14:30:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B79A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021814-15366-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 18/02/2014 13:36:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B7970, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021814-10951-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 18/02/2014 13:07:43 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000307BE94, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\021814-12807-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 17/02/2014 10:55:06 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B7970, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021714-19890-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 17/02/2014 10:50:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B7940, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021714-10826-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 17/02/2014 10:49:31 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800CFAFF78, 0xFFFFF8800CFAF7D0, 0xFFFFF80003072929)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\021714-12885-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 17/02/2014 08:08:53 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xFFFFF97FC0D94F04, 0x0, 0xFFFFF9600006BF0E, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021714-10779-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 16/02/2014 20:01:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B79A0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021614-10951-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 16/02/2014 11:50:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFA817FA53C38, 0x0, 0xFFFFF800030660A9, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021614-11138-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 15/02/2014 23:03:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B79D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021514-12433-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 14/02/2014 11:54:07 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80053B79D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\021414-11934-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 14/02/2014 11:53:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFA4C0974C4DC, 0x1, 0xFFFFF8000307121E, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021414-11824-02.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 14/02/2014 11:50:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF8CD0122009F, 0x8, 0xFFFFF8CD0122009F, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\021414-11824-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\021814-11746-01.dmp




Conclusion

16 crash dumps have been found on your computer. Only 15 could be analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
 

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili