Windows 10 IoT Enterprise LTSC bsod continui

[giuvahhh]

ciao a tutti!

mobo asus rog strix h470-i gaming bios 2601
cpu intel i9-10900F
gpu nvidia t600 4gb
ali corsair tx850w
dissi noctua 2 ventole
ram kingston fury 2x16gb ddr4 3600 cl18-22-22 1.35v xmp
case Kolink Citadel Mesh RGB
keyboard meccanica cinese
mouse logitec mx master 2s
2 x huawei gt 34
1 x cinese 1920x480 aida64
2 x m.2 kingston a2000 1tb
1 x ssd samsung evo 1tb
2 h hdd 2,5 wd e seagate 1tb
Windows 10 IoT Enterprise LTSC 21h2
windows update bloccato con sledgehummer
bloatware puliti con o&o

Allora per 4 mesi acceso 24/7 ha lavorato bene senza mai nessun problema.
da 1 settimana, mentre stavo lavorando con la vmware console, ha iniziato a riavviarsi di continuo a random, a volte anche pochi istanti dopo che windows si e'caricato. a volte a caso ma comunque entro i 20 minuti.
prima cosa che ho fatto e' stato disinstallare la vmware console (ultimo software installato) ma i bsod continuavano coinvolgendo sempre driver diversi. lo vedevo da cronologia affidabilita'.
per prima cosa ho cambiato alimentatore e ho messo un corsair 850w.
poi ho fatto il test della ram ma zero errori sia con memtest che occp.
nel dubbio cambio ram, prima avevo le teamgroup ed ora ho le kingstom.
i bsod sono diventanti meno frequenti diciamo ogni ora oppure subito dopo l-accensione. allora ho aggiornato con windows update e con driverbooster
la situazione e'migliorata diciamo bsod ogni qualche ora.
allora ho tolto aida64. e sono arrivato a fare diverse ore senza bsod.
poi da bios ho disabilitato la lan intel, wifi, bluetooth. attiva sololan realtek.
poi ho fatto test con occp della scheda video e dopo mezzora mi ha dato 1 whea pero ha concluso il test.
ora la situazione e'che si blocca solo quando guardo lo streaming di tvheadend. se guardo youtube o un mkv nessun problema.
stamattina si e'gia riavviato un paio di volte.
ho fatto lo sfc /scannow e non ha riparato alcune cose perche'non ha le autorizzazioni di accesso.
ho fatto il dism e non ha trovato errori
ho fatto scansione con nod32 tutto ok

alla fine riesco a stare attivo per diverse ore ma non devo guardare
la tv tramite tvheadend e neanche usare aida64.
non e'una situazione sostenibile.

vi posto gli ultimi minidump di una ora fa

Bugcheck code: 0x50(0xFFFF9FD800000000, 0x10, 0xFFFF9FD85A81E4C0, 0x2)
Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component.
Analysis: This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

Bugcheck code: 0xD1(0xFFFFF80300000000, 0x2, 0x8, 0xFFFFF80345A6C8FF)
Bugcheck name: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Driver or module in which error occurred: NETIO.SYS (NETIO+0x2C8FF)
File path: C:\Windows\system32\drivers\NETIO.SYS
Description: Network I/O Subsystem
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash took place in a Microsoft module. Possibly this problem was caused by another driver on your system that cannot be identified at this time.

Crash dump file: C:\Windows\Minidump\042424-9140-01.dmp (Minidump)
Bugcheck code: 0x50(0xFFFFF805F9E90000, 0x10, 0xFFFFF80519070A3F, 0x0)
Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component.
Analysis: This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

Crash dump file: C:\Windows\Minidump\042324-9390-01.dmp (Minidump)
Bugcheck code: 0xA(0xFFFFF8037875C000, 0x2, 0x8, 0xFFFFF8035EA1EA7F)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.


allora ho preso una altra nvidia e mi arriva dopo il ponte.
alla fine ho cambiato tutto eccetto la scheda madre.
potrebbe essere la tastiera meccanica usb? ultimamente vedo che si perde delle lettere ogni tanto.
ho messo un dito sopra il chip che sta dietro la nvidia, dalla parte dove non c'e'la ventola ed e'ustionante.
provo a metterci un pad termico e un dissipatore da chipset

secondo voi devo reinstallare tutto, una bella formattata e via?
se si come si procede? prima il windows con lan staccata, poi antivirus, poi windows update o prima i driver asus che sono fermi al 2020? oppure windows update bloccato e via di driver booster?
disperazione totale! grazie per il tempo perso a leggere il post.
grazie a tutti. ciao.

nel mentre scrivevo altro bsod

Crash dump file: C:\Windows\Minidump\042524-9828-01.dmp (Minidump)
Bugcheck code: 0xA(0xFFFFF80202DDC000, 0x2, 0x8, 0xFFFFF8027C21EA7F)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0xA(0xFFFFF80202DDC000, 0x2, 0x8, 0xFFFFF8027C21EA7F)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.

Crash dump file: C:\Windows\Minidump\042524-10125-01.dmp (Minidump)
Bugcheck code: 0xD1(0xFFFFF80100000000, 0x2, 0x8, 0xFFFFF801142B1281)
Bugcheck name: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Driver or module in which error occurred: WppRecorder.sys (WppRecorder+0x1281)
File path: C:\Windows\system32\drivers\WppRecorder.sys
Description: WPP Trace Recorder
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver. The crash took place in a Microsoft module. Possibly this problem was caused by another driver on your system that cannot be identified at this time.