Blue screen (beaucoup)

Le problème c'est que je suis a ma deuxième installation windows (deux versions différentes , famille et après professionnel) donc ca peut plus que être un problème de composant ?

Pour les BSOD, j'utilise l'analyse de Whocrashed.

Sous l'invite de commande, entre la commande

net user

et transmets la capture de la fenêtre cmd

Pour tester sur un autre compte, on peut activer le compte Administrateur intégré par la commande

net user administrateur /active:yes

redémarre le PC

connecte-toi sur le compte "Administrateur" et teste pour vérifier si les BSOD perdurent.

Bonjour

> Mais les fichiers dmp ne vous sont pas utiles ? Comment je fais pour que ce soit sous un autre utilisateur? Se pourrait-il que ce soit un probleme de composant ?

Tes derniers fichiers dmp n'incriminent plus Avast mais les causes concernant les BSODs sont multiples (4 erreurs différents) :

Crash Dump Analysis

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 24/08/2021 11:25:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082421-6328-01.dmp
uptime: 1 day, 16:33:20
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x1 (0x7FFA20F8CF24, 0x0, 0xFFFF0000, 0xFFFFFE09469B1B80)
Error: **APC\_INDEX\_MISMATCH**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 there has been a mismatch in the APC state index.
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 19/08/2021 04:58:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081921-5843-01.dmp
uptime: 00:05:15
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x50 (0xFFFF898C0938FF70, 0x2, 0xFFFFF80207620E6B, 0x2)
Error: **PAGE\_FAULT\_IN\_NONPAGED\_AREA**
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 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.

On Thu 19/08/2021 04:52:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081921-5875-01.dmp
uptime: 16:14:43
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x139 (0xE, 0xFFFF8002305E9650, 0xFFFF8002305E95A8, 0x0)
Error: **KERNEL\_SECURITY\_CHECK\_FAILURE**
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 15/08/2021 21:35:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081521-6671-01.dmp
uptime: 04:49:10
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80044001CE4, 0xFFFFEF0D180B51F8, 0xFFFFEF0D180B4A30)
Error: **SYSTEM\_THREAD\_EXCEPTION\_NOT\_HANDLED\_M**
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

4 crash dumps have been found and analyzed. No offending third party drivers have been found.

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.

La conclusion de WhoCrashed exclue la cause s'un pilote tiers mais pas de façon catégorique.

Si tes pilotes et ton BIOS sont à jour, oui, il se peut qu'il s'agisse d'un problème matériel et dans ce cas commence par vérifier tes barrettes mémoires et ton disque dur.

Sinon, la seule bonne méthodes qui reste est celle qui consiste à sauvegarder tes données et réinstaller Windows.

Pour cela, crée d'abord une partition de données comme l'avait recommandé Aski dans son deuxième message sur ce fil.

Mais les fichiers dmp ne vous sont pas utiles ? Comment je fais pour que ce soit sous un autre utilisateur? Se pourrait-il que ce soit un probleme de composant ?

Bonjour,

La nouvelle analyse ZHP ne révèle rien.

Teste ton système sous un autre compte utilisateur administrateur.