PROBLEMA Accesso negato

[Federico83]

Grazie mille per l'informazione su whocrashed, ora ho i file del bluescreen esportati da quest'ultimo. Malwarebytes non rileva nulla... Ma in questo momento non mi interessa più di tanto, le sdk non le devo installare, itunes sono riuscito quindi direi che quel problema è "superato", poichè ormai non mi crea più fastidio. Ora che ho i file di Whocrashed posso postare qua il file .htm? O devo creare una nuova discussione incentrata su quello?
Grazie mille ancora per il supporto!

fai copia e incolla senza postare il file html

 

[__Passe_]

[FONT=Segoe UI, Arial]System Information (local)

---

[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-4JNN5FQ
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8484569088 bytes total


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

---

Crash Dump Analysis

---

[/FONT]
[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 Sat 23/07/2016 15:14:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072316-9578-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys[/FONT] (SamsungRapidDiskFltr+0x10FD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800A2510FD1, 0x0, 0x200000008)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\samsungrapiddiskfltr.sys
product: [FONT=Segoe UI, Arial]Samsung RAPID Mode[/FONT]
company: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd.[/FONT]
description: Samsung RAPID Mode Disk Filter Driver
Bug check description: This indicates that a kernel-mode program 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.
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: samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.).
Google query: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd. KMODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 23/07/2016 15:14:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys[/FONT] (SamsungRapidDiskFltr+0x10FD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800A2510FD1, 0x0, 0x200000008)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\samsungrapiddiskfltr.sys
product: [FONT=Segoe UI, Arial]Samsung RAPID Mode[/FONT]
company: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd.[/FONT]
description: Samsung RAPID Mode Disk Filter Driver
Bug check description: This indicates that a kernel-mode program 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.
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: samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.).
Google query: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd. KMODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]2 crash dumps have been found and analyzed. A third party driver has 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:

[FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.



[/FONT]

 

[Alex2002ita]

[FONT=Segoe UI, Arial]System Information (local)

---

[/FONT]
[FONT=Segoe UI, Arial]Computer name: DESKTOP-4JNN5FQ
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., M5A97 R2.0
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8484569088 bytes total


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

---

Crash Dump Analysis

---

[/FONT]
[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 Sat 23/07/2016 15:14:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072316-9578-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys[/FONT] (SamsungRapidDiskFltr+0x10FD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800A2510FD1, 0x0, 0x200000008)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\samsungrapiddiskfltr.sys
product: [FONT=Segoe UI, Arial]Samsung RAPID Mode[/FONT]
company: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd.[/FONT]
description: Samsung RAPID Mode Disk Filter Driver
Bug check description: This indicates that a kernel-mode program 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.
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: samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.).
Google query: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd. KMODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 23/07/2016 15:14:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys[/FONT] (SamsungRapidDiskFltr+0x10FD1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800A2510FD1, 0x0, 0x200000008)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\samsungrapiddiskfltr.sys
product: [FONT=Segoe UI, Arial]Samsung RAPID Mode[/FONT]
company: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd.[/FONT]
description: Samsung RAPID Mode Disk Filter Driver
Bug check description: This indicates that a kernel-mode program 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.
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: samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.).
Google query: [FONT=Segoe UI, Arial]Samsung Electronics Co., Ltd. KMODE_EXCEPTION_NOT_HANDLED[/FONT]


[/FONT]

[FONT=Segoe UI, Arial]

---

Conclusion

---

[/FONT]
[FONT=Segoe UI, Arial]2 crash dumps have been found and analyzed. A third party driver has 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:

[FONT=Segoe UI, Arial]samsungrapiddiskfltr.sys (Samsung RAPID Mode Disk Filter Driver, Samsung Electronics Co., Ltd.)[/FONT]

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.



[/FONT]

Per caso nel PC hai un'SSD Samsung EVO come memoria? Pare che questi crash siano dovuti a Samsung RAPID Mode che sarebbe una roba per accellerare la lettura dei dati sull'SSD (correggetemi se sbaglio).

 

[__Passe_]

Si, il mio SSD è quello. Avevo letto anche io nel report questo errore,però volevo capire piú che altro se co fosse un modo per risolverlo senza disattivare la rapid mode di Samsung, con la quale ho notato evidenti miglioramenti.

 

[Alex2002ita]

Si, il mio SSD è quello. Avevo letto anche io nel report questo errore,però volevo capire piú che altro se co fosse un modo per risolverlo senza disattivare la rapid mode di Samsung, con la quale ho notato evidenti miglioramenti.

Se ti succede di nuovo un crash causato da quel file .sys, penso due cose:
1) O fai un formattone e reinstalli in modo pulito Windows 10;
2) Oppure se è un problema dell'SSD, chiedi assistenza alla Samsung ed eventualmente te lo fai cambiare.

Per informazione, quale modello di Samsung EVO hai? Samsung 850 EVO, 750 EVO o cosa?

 

[__Passe_]

Ok, quel problema della schermata blu per colpa dell'ssd era la prima volta che mi succedeva e non mi è più risuccesso, qui di seguito c'è il problema che volevo risolvere (capita 2 volte al giorno non di più solitamente).

[FONT=Segoe UI, Arial]On Sun 24/07/2016 17:20:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072416-11484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0x50 (0xFFFFC00387D77A28, 0x0, 0xFFFFF80315AA6B7C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/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 invalid system memory has been referenced.
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 Sun 24/07/2016 17:20:52 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: 0x50 (0xFFFFC00387D77A28, 0x0, 0xFFFFF80315AA6B7C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
Bug check description: This indicates that invalid system memory has been referenced.
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]

 

[Alex2002ita]

Ok, quel problema della schermata blu per colpa dell'ssd era la prima volta che mi succedeva e non mi è più risuccesso, qui di seguito c'è il problema che volevo risolvere (capita 2 volte al giorno non di più solitamente).

[FONT=Segoe UI, Arial]On Sun 24/07/2016 17:20:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072416-11484-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x142940)
Bugcheck code: 0x50 (0xFFFFC00387D77A28, 0x0, 0xFFFFF80315AA6B7C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/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 invalid system memory has been referenced.
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 Sun 24/07/2016 17:20:52 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: 0x50 (0xFFFFC00387D77A28, 0x0, 0xFFFFF80315AA6B7C, 0x2)
Error: [FONT=Segoe UI, Arial]PAGE_FAULT_IN_NONPAGED_AREA[/FONT]
Bug check description: This indicates that invalid system memory has been referenced.
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]

Da quel che ho letto i fattori sono molteplici per questo errore. Dal file system NTFS corrotto, alla RAM difettata. Per iniziare, che tipo di RAM monti sul tuo PC?

 

[__Passe_]

Quello che volevo sapere era proprio se fosse colpa delle ram. Da un po' di tempo a questa parte il pc di mio padre iniziava a dare questo errore, perciò cercai un po' su internet e vidi che poteva essere un problema dei banchi delle ram, così le ho spostate sul mio pc, mettendo temporaneamente le mie in quello di mio padre, in modo da vedere se fossero quelle il problema. Non me ne intendo molto, però da quello che ho capito è probabilmente un problema delle ram. Le ram in questione sono 4 banchi da 2 gb l'uno modello Corsair CMX8GX3M4A1333C9, questa è la sigla che mi dà hwinfo. L'unica soluzione è cambiare i banchi?

 

[Alex2002ita]

Quello che volevo sapere era proprio se fosse colpa delle ram. Da un po' di tempo a questa parte il pc di mio padre iniziava a dare questo errore, perciò cercai un po' su internet e vidi che poteva essere un problema dei banchi delle ram, così le ho spostate sul mio pc, mettendo temporaneamente le mie in quello di mio padre, in modo da vedere se fossero quelle il problema. Non me ne intendo molto, però da quello che ho capito è probabilmente un problema delle ram. Le ram in questione sono 4 banchi da 2 gb l'uno modello Corsair CMX8GX3M4A1333C9, questa è la sigla che mi dà hwinfo. L'unica soluzione è cambiare i banchi?

Prova ad usare Memtest86 per testare i banchi di RAM e vedere quali sono sani e quali no. Sai come si usa oppure devo spiegartelo?

 

[__Passe_]

Ora non sono a casa, appena arrivo provo, nel caso mi serva aiuto per usarlo scrivo qui. Grazie mille.

 

[__Passe_]

Grazie mille! Dei due banchi di ram su uno erano rilevati tantissimi errori, ho comprato due nuovi banchi ram e ora sembra tutto a posto (da due o tre volte al giorno ora non si ripresenta più nemmeno una volta da 2 giorni). Grazie ancora per il supporto immediato.

 

[Alex2002ita]

Grazie mille! Dei due banchi di ram su uno erano rilevati tantissimi errori, ho comprato due nuovi banchi ram e ora sembra tutto a posto (da due o tre volte al giorno ora non si ripresenta più nemmeno una volta da 2 giorni). Grazie ancora per il supporto immediato.

Di niente!;) Se poi incontri altri problemi, non esitare ad avvertirci!