PROBLEMA BSOD continue

xwx

Utente Attivo
83
12
CPU
Intel Core i5
HDD
SSD 850 EVO 500 GB
RAM
8,00 GB DDR3
GPU
Nvidia GeForce GTX
Monitor
LG FLATRON L177WSB
OS
WIndows 10
Ciao a tutti,

da qualche tempo il mio PC mi da problemi, però ultimamente si stanno acuendo le BSOD (la maggiore va per il IRQL_NOT_LESS[...]), oggi addirittura quattro in 10 minuti.
Vi allego il report di WhoCrashed e BlueScreenView, non ci capisco molto... sembra il problema dipenda da NVIDIA o ESET, però se qualcuno può dare un'occhiatina gliene sarei grato.

Caratteristiche PC

System Information (local)
computer name: MAU-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: KA927AA-ABZ a6325.it, HP-Pavilion, ASUSTeK Computer INC., Benicia
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220480000 total
VM: 2147352576, free: 1938255872
Scheda video: Nvidia GeForce 7300 LE

WHOCRASHED

Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 26/07/2014 10:53:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072614-27034-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF82EB5E73)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Sat 26/07/2014 10:50:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072614-16504-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0xFFFFFFFFE56C6946, 0x2, 0x1, 0xFFFFFFFF82EB3E73)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Sat 26/07/2014 10:46:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072614-15943-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x2DA6)
Bugcheck code: 0xD1 (0x40008019, 0xFF, 0x0, 0xFFFFFFFF910D5DA6)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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.



On Fri 25/07/2014 10:46:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072514-21278-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xCDA88)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF82F3F87B)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 307.83
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 307.83
Bug check description: This indicates that the system attempted to access invalid 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. 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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 307.83 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_CORRUPTED_EXPOOL



On Fri 18/07/2014 13:27:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071814-14367-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0x4300BC, 0x2, 0x1, 0xFFFFFFFF82EC8F4F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Wed 16/07/2014 07:24:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071614-17612-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x4C6D)
Bugcheck code: 0xD1 (0xD0, 0x2, 0x0, 0xFFFFFFFF8BBA9C6D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 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.



On Sun 08/06/2014 13:05:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060814-15210-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x850F5)
Bugcheck code: 0x1A (0x5001, 0xFFFFFFFF8BE00000, 0x33FA, 0x33FBFEE)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that a severe memory management error occurred.
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 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.



On Tue 29/04/2014 14:37:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042914-13821-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1512)
Bugcheck code: 0xFE (0x6, 0xFFFFFFFF87433A88, 0x63706458, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver porta USB 1.1 & 2.0
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
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.



On Tue 29/04/2014 14:34:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042914-14648-01.dmp
This was probably caused by the following module: eamonm.sys (eamonm+0x22D5A)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF82D2B87B)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\eamonm.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
Bug check description: This indicates that the system attempted to access invalid 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. 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.
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: eamonm.sys (Amon monitor, ESET).
Google query: ESET DRIVER_CORRUPTED_EXPOOL



On Fri 25/04/2014 12:30:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042514-13197-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0x1AFD14, 0x2, 0x0, 0xFFFFFFFF82CC4E3D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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

10 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

eamonm.sys (Amon monitor, ESET)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 307.83 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


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

BLUESCREENVIEW

==================================================
File Dump : 072614-27034-01.dmp
Orario Crash : 26/07/2014 12:53:33
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x00000000
Parametro 2 : 0x00000002
Parametro 3 : 0x00000001
Parametro 4 : 0x82eb5e73
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+78e73
Indirizzo Stack 2 : ntkrnlpa.exe+7cce6
Indirizzo Stack 3 : ntkrnlpa.exe+76a71
Nome Computer :
Path Completo : C:\Windows\Minidump\072614-27034-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 131.072
Dump File Time : 26/07/2014 12:55:09
==================================================


==================================================
File Dump : 072614-16504-01.dmp
Orario Crash : 26/07/2014 12:50:03
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0xe56c6946
Parametro 2 : 0x00000002
Parametro 3 : 0x00000001
Parametro 4 : 0x82eb3e73
Causato dal Driver: Unknown_Module_00000000
Causato dall'Indirizzo: Unknown_Module_00000000+a
Descrizione del File:
Nome Prodotto :
Società :
Versione del File :
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+78e73
Indirizzo Stack 2 : ntkrnlpa.exe+7cce6
Indirizzo Stack 3 : ntkrnlpa.exe+76a71
Nome Computer :
Path Completo : C:\Windows\Minidump\072614-16504-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 131.072
Dump File Time : 26/07/2014 12:51:37
==================================================


==================================================
File Dump : 072614-15943-01.dmp
Orario Crash : 26/07/2014 12:46:24
Stringa Controllo Bug: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x000000d1
Parametro 1 : 0x40008019
Parametro 2 : 0x000000ff
Parametro 3 : 0x00000000
Parametro 4 : 0x910d5da6
Causato dal Driver: nvlddmkm.sys
Causato dall'Indirizzo: nvlddmkm.sys+ef031
Descrizione del File: NVIDIA Windows Kernel Mode Driver, Version 307.83
Nome Prodotto : NVIDIA Windows Kernel Mode Driver, Version 307.83
Società : NVIDIA Corporation
Versione del File : 9.18.13.0783
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : intelppm.sys+2da6
Indirizzo Stack 2 : ntkrnlpa.exe+772cd
Indirizzo Stack 3 :
Nome Computer :
Path Completo : C:\Windows\Minidump\072614-15943-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 162.584
Dump File Time : 26/07/2014 12:47:18
==================================================


==================================================
File Dump : 072514-21278-01.dmp
Orario Crash : 25/07/2014 12:46:28
Stringa Controllo Bug: DRIVER_CORRUPTED_EXPOOL
Codice Controllo Bug: 0x000000c5
Parametro 1 : 0x00000004
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x82f3f87b
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+12187b
Indirizzo Stack 2 : ntkrnlpa.exe+12135f
Indirizzo Stack 3 : nvlddmkm.sys+cda88
Nome Computer :
Path Completo : C:\Windows\Minidump\072514-21278-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 157.440
Dump File Time : 25/07/2014 12:49:00
==================================================


==================================================
File Dump : 071814-14367-01.dmp
Orario Crash : 18/07/2014 15:27:24
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x004300bc
Parametro 2 : 0x00000002
Parametro 3 : 0x00000001
Parametro 4 : 0x82ec8f4f
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+78f4f
Indirizzo Stack 2 : ntkrnlpa.exe+3760f
Indirizzo Stack 3 : ntkrnlpa.exe+79719
Nome Computer :
Path Completo : C:\Windows\Minidump\071814-14367-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 159.296
Dump File Time : 18/07/2014 15:28:33
==================================================


==================================================
File Dump : 071614-17612-01.dmp
Orario Crash : 16/07/2014 09:24:52
Stringa Controllo Bug: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x000000d1
Parametro 1 : 0x000000d0
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x8bba9c6d
Causato dal Driver: CLASSPNP.SYS
Causato dall'Indirizzo: CLASSPNP.SYS+4c6d
Descrizione del File: SCSI Class System Dll
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7600.16385 (win7_rtm.090713-1255)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : CLASSPNP.SYS+4c6d
Indirizzo Stack 2 : CLASSPNP.SYS+3fd5
Indirizzo Stack 3 : CLASSPNP.SYS+5a59
Nome Computer :
Path Completo : C:\Windows\Minidump\071614-17612-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 162.296
Dump File Time : 16/07/2014 09:26:04
==================================================


==================================================
File Dump : 060814-15210-01.dmp
Orario Crash : 08/06/2014 15:05:21
Stringa Controllo Bug: MEMORY_MANAGEMENT
Codice Controllo Bug: 0x0000001a
Parametro 1 : 0x00005001
Parametro 2 : 0x8be00000
Parametro 3 : 0x000033fa
Parametro 4 : 0x033fbfee
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+debfc
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+debfc
Indirizzo Stack 1 : ntkrnlpa.exe+63a97
Indirizzo Stack 2 : ntkrnlpa.exe+349c5
Indirizzo Stack 3 : ntkrnlpa.exe+5c85f
Nome Computer :
Path Completo : C:\Windows\Minidump\060814-15210-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 152.792
Dump File Time : 08/06/2014 15:06:52
==================================================


==================================================
File Dump : 042914-13821-01.dmp
Orario Crash : 29/04/2014 16:37:08
Stringa Controllo Bug: BUGCODE_USB_DRIVER
Codice Controllo Bug: 0x000000fe
Parametro 1 : 0x00000006
Parametro 2 : 0x87433a88
Parametro 3 : 0x63706458
Parametro 4 : 0x00000000
Causato dal Driver: USBPORT.SYS
Causato dall'Indirizzo: USBPORT.SYS+1512
Descrizione del File: Driver porta USB 1.1 & 2.0
Nome Prodotto : Sistema operativo Microsoft® Windows®
Società : Microsoft Corporation
Versione del File : 6.1.7600.16385 (win7_rtm.090713-1255)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+debfc
Indirizzo Stack 1 : USBPORT.SYS+1512
Indirizzo Stack 2 : USBPORT.SYS+7ac0
Indirizzo Stack 3 : USBPORT.SYS+8817
Nome Computer :
Path Completo : C:\Windows\Minidump\042914-13821-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 152.736
Dump File Time : 29/04/2014 16:38:36
==================================================


==================================================
File Dump : 042914-14648-01.dmp
Orario Crash : 29/04/2014 16:34:08
Stringa Controllo Bug: DRIVER_CORRUPTED_EXPOOL
Codice Controllo Bug: 0x000000c5
Parametro 1 : 0x00000004
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x82d2b87b
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+12187b
Indirizzo Stack 2 : ntkrnlpa.exe+9aa88
Indirizzo Stack 3 : ntkrnlpa.exe+120132
Nome Computer :
Path Completo : C:\Windows\Minidump\042914-14648-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 153.200
Dump File Time : 29/04/2014 16:35:10
==================================================


==================================================
File Dump : 042514-13197-01.dmp
Orario Crash : 25/04/2014 14:30:01
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x001afd14
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x82cc4e3d
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+78e3d
Indirizzo Stack 2 : ntkrnlpa.exe+7cce6
Indirizzo Stack 3 : ntkrnlpa.exe+79465
Nome Computer :
Path Completo : C:\Windows\Minidump\042514-13197-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 162.624
Dump File Time : 25/04/2014 14:31:30
==================================================
 
Ultima modifica:

xwx

Utente Attivo
83
12
CPU
Intel Core i5
HDD
SSD 850 EVO 500 GB
RAM
8,00 GB DDR3
GPU
Nvidia GeForce GTX
Monitor
LG FLATRON L177WSB
OS
WIndows 10
Nessuno mi può dare una mano?
Stamani altre tre BSOD, però bluescreenview mi ha salvato il dump di una sola, mentre whocrashed di due:

BLUESCREENVIEW
==================================================
File Dump : 072914-17924-01.dmp
Orario Crash : 29/07/2014 08:09:55
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x0000000c
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x82eb3fbd
Causato dal Driver: rdyboost.sys
Causato dall'Indirizzo: rdyboost.sys+cda8
Descrizione del File: ReadyBoost Driver
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+98fbd
Indirizzo Stack 2 : ntkrnlpa.exe+77dd3
Indirizzo Stack 3 : CLASSPNP.SYS+4498
Nome Computer :
Path Completo : C:\Windows\Minidump\072914-17924-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 135.520
Dump File Time : 29/07/2014 08:14:18
==================================================

WHOCRASHED

[FONT=Segoe UI, Arial]On Tue 29/07/2014 06:15:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0xFFFFFFFF82F7B890)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82F7B890, 0xFFFFFFFF82F7B890, 0xFFFFFFFF82F7B880)
Error: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]
Bug check description: This indicates that a pool header is corrupt.
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.
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]BAD_POOL_HEADER[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Tue 29/07/2014 06:09:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072914-17924-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]iastorv.sys[/FONT] (iaStorV+0x45215)
Bugcheck code: 0xA (0xC, 0x2, 0x0, 0xFFFFFFFF82EB3FBD)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\iastorv.sys
product: [FONT=Segoe UI, Arial]Intel Matrix Storage Manager driver[/FONT]
company: [FONT=Segoe UI, Arial]Intel Corporation[/FONT]
description: Intel Matrix Storage Manager driver - ia32
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.
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: iastorv.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation).
Google query: [FONT=Segoe UI, Arial]Intel Corporation IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
 

xwx

Utente Attivo
83
12
CPU
Intel Core i5
HDD
SSD 850 EVO 500 GB
RAM
8,00 GB DDR3
GPU
Nvidia GeForce GTX
Monitor
LG FLATRON L177WSB
OS
WIndows 10
[FONT=Segoe UI, Arial]Oggi altri due crash... pensate si possa risolvere formattando il C e mettendo Windows 8?


On Mon 01/09/2014 12:43:59 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] (0xFFFFFFFFC0000005)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8B77BB37, 0xFFFFFFFF8F4FC94C, 0x0)
Error: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]KERNEL_MODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Mon 01/09/2014 12:43:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090114-14274-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]Unknown[/FONT] ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
A third party driver was identified as the probable root cause of this system error.
Google query: [FONT=Segoe UI, Arial]CUSTOM_ERROR[/FONT]
[/FONT]
 

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
no non risolveresti controlla la ram con memtest
 

xwx

Utente Attivo
83
12
CPU
Intel Core i5
HDD
SSD 850 EVO 500 GB
RAM
8,00 GB DDR3
GPU
Nvidia GeForce GTX
Monitor
LG FLATRON L177WSB
OS
WIndows 10
no non risolveresti controlla la ram con memtest

Ieri ho provato con memtest... gli ho fatto fare 7 cicli e non ha rilevato nulla (ho messo la modalità sommario errori e non c'era nulla).
Ho più di un banco di RAM, mi pare 3 ed il test l'ho fatto con tutti i banchi inseriti. Dovrei riprovare uno a uno o se con tutti non da errore posso evitare?
Soprattutto, anche io temevo fosse la RAM ma non ha trovato nulla memtest :(
 

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
prova a fare uno scandisk approfondito sul disco tanto volte fosse quello il problema
 

xwx

Utente Attivo
83
12
CPU
Intel Core i5
HDD
SSD 850 EVO 500 GB
RAM
8,00 GB DDR3
GPU
Nvidia GeForce GTX
Monitor
LG FLATRON L177WSB
OS
WIndows 10
Fatto con l'utility di Windows 7, non sembra abbia fatto un granché... dovrei provare con l'utility del produttore dell'hard disk?

Controllo in corso del file system su C:
Il file system è di tipo NTFS.


Il disco sarà ora controllato come pianificato.
Il disco sarà ora controllato.


Verifica dei file in corso (fase 1 di 5)...
265728 record di file elaborati.
Verifica file completata.
733 record di file di grandi dimensioni elaborati.
0 record file non validi elaborati.
2 record EA elaborati.
136 record reparse elaborati.

Verifica degli indici in corso (fase 2 di 5)...
348178 voci di indice elaborate.
Verifica indici completata.
0 file non indicizzati analizzati.
0 file non indicizzati ripristinati.

Verifica dei descrittori di sicurezza in corso (fase 3 di 5)...
265728 descrittori di protezione/SID di file elaborati.
CHKDSK: è in corso la compattazione del flusso dei descrittori di sicurezza
Pulizia dei descrittori di sicurezza inutilizzati 5172.
41226 file di dati elaborati.
CHKDSK sta verificando il journal USN...
37140600 byte USN elaborati.
Verifica del journal USN completata.

Verifica dei dati dei file in corso (fase 4 di 5))...
265712 file elaborati.
Verifica dei dati del file completata.


CHKDSK sta verificando la spazio disponibile (fase 5 di 5)...
Cluster liberi elaborati: 3039858.
Verifica dello spazio disponibile completata.

CHKDSK ha individuato spazio libero su disco contrassegnato come
allocato nella bitmap della Tabella file master (MFT).
Correzione errori nella mappa di bit del volume.
Correzioni apportate al file system.


102399999 KB di spazio totale su disco.
89757008 KB in 205895 file.
111044 KB in 41229 indici.
0 KB in settori danneggiati.
372511 KB in uso dal sistema.
65536 KB occupati dal file registro.
12159436 KB disponibili su disco.


4096 byte in ogni unità di allocazione.
25599999 unità totali di allocazione su disco.
3039859 unità di allocazione disponibili su disco.


Informazioni interne:
00 0e 04 00 5d c5 03 00 84 b0 06 00 00 00 00 00 ....]...........
fa 13 00 00 88 00 00 00 00 00 00 00 00 00 00 00 ................
00 90 30 00 50 01 2f 00 40 1c 2f 00 00 00 2f 00 ..0.P./.@./.../.


Controllo del disco completato.
Attendere il riavvio del computer.


EDIT: con l'utility della WD da DOS non è stato rilevato nessun errore del disco (scansione approfondita).


EDIT 9-9-14: non male, adesso si blocca addirittura all'avvio :D (quando c'è la schermata del caricamento di Windows).

WhoCrashed
On Tue 09/09/2014 08:05:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFF8597A268)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8597A268, 0xFFFFFFFF859A9ED0, 0xFFFFFFFF8597A268)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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.
A third party driver was identified as the probable root cause of this system error.
Google query: BAD_POOL_HEADER



On Fri 05/09/2014 08:39:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-15194-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFFFFF82EC0744)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Thu 04/09/2014 19:07:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-12807-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x973FF)
Bugcheck code: 0xD1 (0x6, 0x4, 0x0, 0xFFFFFFFF9357AB71)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 307.83
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 307.83
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 307.83 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 04/09/2014 19:04:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-14976-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x7F7EE)
Bugcheck code: 0xA (0x20206F49, 0x2, 0x1, 0xFFFFFFFF82EC2E73)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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.

Bluescreenview
==================================================
File Dump : 090514-15194-01.dmp
Orario Crash : 05/09/2014 10:39:30
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x00000010
Parametro 2 : 0x00000002
Parametro 3 : 0x00000000
Parametro 4 : 0x82ec0744
Causato dal Driver: ntkrnlpa.exe
Causato dall'Indirizzo: ntkrnlpa.exe+40b7f
Descrizione del File: NT Kernel & System
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : ntkrnlpa.exe+b0744
Indirizzo Stack 2 : ntkrnlpa.exe+b5bfc
Indirizzo Stack 3 : ntkrnlpa.exe+7809f
Nome Computer :
Path Completo : C:\Windows\Minidump\090514-15194-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 131.072
Dump File Time : 05/09/2014 10:42:10
==================================================


==================================================
File Dump : 090514-12807-01.dmp
Orario Crash : 04/09/2014 21:07:48
Stringa Controllo Bug: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x000000d1
Parametro 1 : 0x00000006
Parametro 2 : 0x00000004
Parametro 3 : 0x00000000
Parametro 4 : 0x9357ab71
Causato dal Driver: dxgmms1.sys
Causato dall'Indirizzo: dxgmms1.sys+8b71
Descrizione del File: DirectX Graphics MMS
Nome Prodotto : Microsoft® Windows® Operating System
Società : Microsoft Corporation
Versione del File : 6.1.7601.18510 (win7sp1_gdr.140615-1511)
Processore : 32-bit
Indirizzo Crash : ntkrnlpa.exe+40b7f
Indirizzo Stack 1 : dxgmms1.sys+8b71
Indirizzo Stack 2 : dxgmms1.sys+a69d
Indirizzo Stack 3 : dxgmms1.sys+c952
Nome Computer :
Path Completo : C:\Windows\Minidump\090514-12807-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 162.272
Dump File Time : 05/09/2014 10:34:47
==================================================


==================================================
File Dump : 090414-14976-01.dmp
Orario Crash : 04/09/2014 21:04:36
Stringa Controllo Bug: IRQL_NOT_LESS_OR_EQUAL
Codice Controllo Bug: 0x0000000a
Parametro 1 : 0x20206f49
Parametro 2 : 0x00000002
Parametro 3 : 0x00000001
Parametro 4 : 0x82ec2e73
Causato dal Driver:
Causato dall'Indirizzo:
Descrizione del File:
Nome Prodotto :
Società :
Versione del File :
Processore : 32-bit
Indirizzo Crash :
Indirizzo Stack 1 : ntkrnlpa.exe+772cd
Indirizzo Stack 2 :
Indirizzo Stack 3 :
Nome Computer :
Path Completo : C:\Windows\Minidump\090414-14976-01.dmp
Numero Processori : 2
Versione più Recente: 15
Versione più Vecchia: 7601
Dimensione File di Dump: 131.072
Dump File Time : 04/09/2014 21:05:53
==================================================


Ho visto che alcune volte è causato dal driver Nvidia, ma per la mia scheda video (schifosa) ho già l'ultima versione :/
Se RAM e HD sono apposto, che mi stia finendo nelle barbe il PC?
 
Ultima modifica:

Entra

oppure Accedi utilizzando
Discord Ufficiale Entra ora!

Discussioni Simili