ntoskrnl.exe BSoD

Question

Salve, è da più di un anno che ho problemi con bsod con il mio pc.. ho provato di tutto e di più quindi eccomi qui. In seguito posto una serie di analisi dei "crash dump", prodotta dal programma "whocrashed":

Crash Dump Analysis

---

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Tue 22/06/2021 19:01:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062221-8234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0xC2 (0xD, 0xFFFFB88BD3312140, 0x6661754C, 0x189BF06C9B2686C4)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 22/06/2021 19:01:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: luafv.sys (luafv+0x103E0)
Bugcheck code: 0xC2 (0xD, 0xFFFFB88BD3312140, 0x6661754C, 0x189BF06C9B2686C4)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\luafv.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver filtro virtualizzazione file LUA
Bug check description: This indicates that the current thread is making a bad pool request.
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 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 22/06/2021 18:42:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062221-8625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8060E3120CB, 0xFFFFA883B641DB70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.

On Thu 17/06/2021 22:59:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061721-10671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8044B1184C9, 0xFFFFED011DFBEF80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.

On Wed 16/06/2021 08:50:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061621-11390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x1A (0x411, 0xFFFF860135EDC038, 0x645E1880, 0xFFFFC10EAF0B5F20)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. A page table entry (PTE) has been corrupted. Parameter 2 is the address of the PTE.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (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.

On Mon 14/06/2021 20:48:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061421-10531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F6C20)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802037144EB, 0xFFFFA2033B3CB9A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.

---

---

Conclusion

---

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

Answer 1

Per il momento l'analisi dei dump porta a cause svariate, da Discord a Geshin Impact, ma probabilmente ci sono motivi diversi da quegli applicativi.

Inizia ad aggiornare il BIOS (5.90) e il Chipset:

https://www.asrock.com/mb/AMD/A320M-DGS/index.it.asp#Download

Bisognerebbe anche verificare la memoria RAM.

Se hai più di un banco, lasciane uno solo a rotazione, testa il sistema ogni volta e se avrai errori con uno solo di questi, probabilmente è da sostituire.

Answer 2

Per quanto riguarda la marca e il modello, non saprei dirle, vuole il nome dei vari componenti?

Certo. Se è assemblato fai una lista completa.

Answer 3

https://1drv.ms/u/s!AmOnaBiZkwGrm1EqAZLW32vKO6Ew?e=r5YgU0 
Per quanto riguarda la marca e il modello, non saprei dirle, vuole il nome dei vari componenti?

Answer 4

ciao Assu12

Copia i file più recenti da C:\Windows\Minidump al tuo Onedrive, poi condividili. Comunica anche marca e modello del tuo computer.

Answer 5

Benvenuto.

Usi macchine virtuali che causano conflitti.

Inoltre descrivi, in dettaglio, il tuo pc.

E, proprio per iniziare, leggi attentamente la premessa (a titolo informativo) e esegui, senza omettere nulla, i primi 5 passaggi del mio articolo AVVIO PULITO per eliminare conflitti, interferenze e ripristinare file e moduli di sistema.