Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Tous les problèmes de Windows : message d'erreur, BSOD et écran bleu, erreur Windows Update ou d'installation, etc

Modérateur : Mods Windows

Oxmo60
Messages : 3
Inscription : 20 nov. 2020 12:16

Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Message par Oxmo60 »

Bonjour,

J'ai des soucis d'écran bleu qui apparaissent aléatoirement.

Voici le test de who crashed qui j'ai effectué:

Code : Tout sélectionner

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-813FQHA
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: A0000001, CSL-Computer GmbH & Co. KG, ASUSTeK COMPUTER INC., PRIME B450M-A
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17107881984 bytes (15,9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Fri 20/11/2020 12:23:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112020-11750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210) 
Bugcheck code: 0x1 (0x7FFC189ABE24, 0x1, 0x0, 0xFFFFC68E10A05B80)
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. 
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 Fri 20/11/2020 12:23:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x8209) 
Bugcheck code: 0x1 (0x7FFC189ABE24, 0x1, 0x0, 0xFFFFC68E10A05B80)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index. 
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/11/2020 18:25:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111920-11046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210) 
Bugcheck code: 0xA (0xFFFFE08962E55158, 0xFF, 0xF2, 0xFFFFF8014C160AC5)
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. 



On Thu 19/11/2020 12:56:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111920-16578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210) 
Bugcheck code: 0xA (0xC9, 0x2, 0x0, 0xFFFFF80070EDFE6C)
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. 



On Wed 18/11/2020 13:32:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111820-22718-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8074789BCC2) 
Bugcheck code: 0xD1 (0xFFFFF807478940C0, 0xFF, 0x0, 0xFFFFF8074789BCC2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device 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. 



On Thu 12/11/2020 18:54:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111220-23578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8045D5FC2DD, 0x0, 0xFFFFFFFFFFFFFFFF)
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. 



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\LiveKernelReports\PoW32kWatchdog-20201114-1238.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. Only 6 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors. 
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. 
A noter que j'ai tester mon disque dur avec crsital info disk qui est en bonne santé et que j'utilise windows defender comme antivirus.



Merci Bien PDT_008

Malekal_morte
Site Admin
Site Admin
Messages : 104616
Inscription : 10 sept. 2005 13:57
Contact :

Re: Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Message par Malekal_morte »

Salut,

Vu que les codes d'arrêt et STOP Code sont différents à chaque fois, j'aurai tendance à dire que c'est un problème matériel.
D'ailleurs WhoCrashed conclut là dessus.

Je te mets une réponse générique, mais commencer plutôt par les tests du matériel.
Suivre ce lien : Résoudre BSOD sur Windows et :

Installe et lance OCCT.
Lance une vidéo Youtube ou Netflix (si tu as).
Laisse tourner la vidéo 5min.
Donne une capture d'écran :
- de l'onglet Système
- des températures
- des ventilateurs
- de l'onglet puissance.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Les tutoriels Windows 10 du moment : Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.

Oxmo60
Messages : 3
Inscription : 20 nov. 2020 12:16

Re: Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Message par Oxmo60 »

Merci pour la réponse super rapide !

J'ai lancer une analyse sfc scannow qui m'a trouvé ça:
La Protection des ressources Windows a détecté des fichiers corrompus et les a réparés.
Pour les réparations en ligne, les détails sont inclus dans le fichier journal de CBS situé à l'emplacement suivant :
windir\Logs\CBS\CBS.log. Exemple : C:\Windows\Logs\CBS\CBS.log. Pour les réparations
hors connexion, les détails sont inclus dans le fichier journal fourni par l'indicateur /OFFLOGFILE.
J'ai également voulu tester les barrettes de mémoire à l'aide de mem 86 à partir d'une clef usb mais quand je sélectionne la clef usb depuis le menu boot il ne se passe rien.

J'ai bien suivi le tuto pour crée une clef bootable.

J'ai du coup par la suite utilisé le programme de Windows pour la mémoire qui ne m'a pas trouvé de problème.

Je pars sur le test OCCT la

Oxmo60
Messages : 3
Inscription : 20 nov. 2020 12:16

Re: Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Message par Oxmo60 »

Bon j'ai lancer le test de OCCT qui dure une heure et je n'ai pas eu de soucis en particulier.

Je n'ai pas eu de problème d'écran bleue depuis le test sfc scannow.

Je ne voudrais pas crier victoire trop vite mais il se pourrait bien que le soucis soit réglé.


Je reviendrais mettre le topic en résolu si je n'ai plus de problème d’ici la.


Merci encore pour tout PDT_003

Malekal_morte
Site Admin
Site Admin
Messages : 104616
Inscription : 10 sept. 2005 13:57
Contact :

Re: Ecran Bleu IRQL_NOT_LESS_OR_EQUAL / APC_INDEX_MISMATCH dans ntoskrnl.exe

Message par Malekal_morte »

humm ok ça me paraît un peu simple comme résolution, mais soit.
Faut voir sur la durée =)
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Les tutoriels Windows 10 du moment : Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.

Répondre

Revenir à « Windows : Résoudre les problèmes »