PROBLEMA BSOD, IRQL NOT LESS OR EQUAL

[Sir Jack]

SAlve,
poco fa sono incappato in bsod sul mio sistema win 10 x64

Spoiler: SPECIFICHE

Spoiler: Ecco l'analisi di Whocrashed

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

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

On Mon 15/06/2020 16:37:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061520-18187-01.dmp
This was probably caused by the following module: ndu.sys (0xFFFFF801977B4FF0)
Bugcheck code: 0xD1 (0xFFFFCF0E708E7040, 0x2, 0x1, 0xFFFFF801977B4FF0)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring 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 bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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.

Posso avere aiuto?

 

[Sir Jack]

altro crash.
stavolta è ndu.sys

Spoiler: Ecco l'analisi di Whocrashed

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

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

On Thu 18/06/2020 01:46:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061820-14875-01.dmp
This was probably caused by the following module: ndu.sys (0xFFFFF8018DB94540)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8018DB94540, 0xFFFF8A899F991A78, 0xFFFFF80188C7E930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
Bug check description: This indicates that a system thread 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.
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.

Dopo il crash il pc ha stentato a riavviarsi per un paio di volte. UNa volta si è riavviato senza accedere al mio profilo utente, nonostante avessi correttamente eseguito l'identificazione. La seconda si è caricato tutto normalmente ma senza la possibilità di utilizzare la scheda di rete. Neanche Speccy funzionava.

Ora sembra tutto a posto.
Il Pc è nuovissimo e non ha MAI dato problemi negli ultimi mesi. Forse un aggiornamento di Windows 10?

 

[DareDevil_]

Provato l sfc/ scannow? i driver sono tutti aggiornati dal sito ufficiale dei produttori?

Per caso hai BitDefender installato?

 

[Sir Jack]

Per caso hai BitDefender installato?

No, non ce l'ho.

Ho eseguito sfc e il report dice "errori rilevati e corretti". Il log è lunghissimo, non so se serve.

Credo comunque ci sia un qualche problema con i driver della scheda di rete, dato che oggi all'avvio non riuscivo assolutamente ad utilizzare internet nonostante il pc (cavo ethernet diretto) risultasse collegato alla rete.

 

[DareDevil_]

No, non ce l'ho.

Ho eseguito sfc e il report dice "errori rilevati e corretti". Il log è lunghissimo, non so se serve.

Credo comunque ci sia un qualche problema con i driver della scheda di rete, dato che oggi all'avvio non riuscivo assolutamente ad utilizzare internet nonostante il pc (cavo ethernet diretto) risultasse collegato alla rete.

Disinstalla i driver di rete e reinstalla gli ultimi dal sito ufficiale.

 

[Sir Jack]

Disinstalla i driver di rete e reinstalla gli ultimi dal sito ufficiale.

Fatto, vediamo come va.

Grazie del tempo che mi dedichi :)

 

[DareDevil_]

Fatto, vediamo come va.

Grazie del tempo che mi dedichi :)

Di nulla, speriamo bene :).
Tienimi aggiornato :).

 

[Sir Jack]

Niente, accaduto di nuovo.
Questa volta ntoskrnl.exe

Spoiler: whocrashed

crash dump file: C:\WINDOWS\Minidump\061820-13796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8035461A4A4, 0x1, 0xFFFFCD09D842A020)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Post unito automaticamente: 18 Giugno 2020

E ancora!

Spoiler: whocrahed

crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ndu.sys (0xFFFFF80463804FF0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80463804FF0, 0xFFFFD3818136F930, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ndu.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Network Data Usage Monitoring Driver
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 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.