RISOLTO BSOD errore 0xc000021a

Pubblicità
Ultima modifica:
ok, per togliere almeno qualche dubbio, per caso tutto ciò è causato da qualche driver aggiornato?
si certo che e' possibile https://neosmart.net/wiki/0xc000021a/

Cause 1: Misconfigured software or driver​

The most common cause of this error is a certain key piece of software or system driver that is malfuncioning.

Ma sicuramente non facile da scoprire
 
Non e' lui a causare l'elevata temperatura, ma certo non la dissipa (essendo la plastica isolante) come il metallo e quindi rimane all'interno del piccolo case
chiaro. Per curiosità ho controllato sempre con CrystalDiskInfo l'altro portatile, e portava una temperatura tra i 30°, e con questo chiarimento volevo provare se cambia qualcosa installando un' altra ssd (è un Samsung 850 Pro). Tempo da perdere ce l'avrei,
 
chiaro. Per curiosità ho controllato sempre con CrystalDiskInfo l'altro portatile, e portava una temperatura tra i 30°, e con questo chiarimento volevo provare se cambia qualcosa installando un' altra ssd (è un Samsung 850 Pro). Tempo da perdere ce l'avrei,
Faresti prima a togliere le plastiche (poi in caso le rimetti) e vedere se la remperatura scende.... pero' fai tu ?
 
Ho tolto la plastica e oggi adoperando il laptop normalmente ho monitorato la temperatura. Alla fine si manteneva bassa, non andava oltre i 30°. Capitava se dovevo installare qualche programma, la temperatura si alzava verso i 60
 
Ultima modifica:
Ho tolto la plastica e oggi adoperando il laptop normalmente ho monitorato la temperatura. Alla fine si manteneva bassa, non andava oltre i 30°. Capitava se dovevo installare qualche programma, la temperatura si alzava verso i 60
Mi sembra che hai fatto un passo in avanti, ora tienlo monitorato, in caso passiamo al dissipatore
 
Aggiornamento:
ieri tutto nella norma, dopo dei "crash" continui, la temperatura è salita e fino ad ora oscilla tra i 56° e 62°.

Questo è il resoconto dei crash:

crash dump file: C:\Windows\Minidump\012022-30750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF80511A0572F, 0xFFFF890021A86920, 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.


crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8239)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF80511A0572F, 0xFFFF890021A86920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.


crash dump file: C:\Windows\Minidump\012022-34765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8026A618BD1, 0xFFFFA4816DDCEF40, 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.


crash dump file: C:\Windows\Minidump\011922-31015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0xA (0xFFFFF8013F3E3800, 0x2, 0x8, 0xFFFFF8013F3E3800)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


crash dump file: C:\Windows\Minidump\011922-32390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72E0)
Bugcheck code: 0x3B (0xC0000096, 0xFFFFF80447C0C72F, 0xFFFFDF80543FE920, 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.
 
Pubblicità
Pubblicità
Indietro
Top