Blue screen IRQL NOT LESS OR EQUAL.

[azmaldor]

Bonjour à tous,

J’ai voulu me lancer sur le dernier desperados l’installation c’est bien passer etc et malheureusement j’ai eux deux blue screen.
-le premier est en code d’arret : IRQL NOT LESS OR EQUAL.
-le deuxième est en code d’arrêt : APC INDEX MISMATCH

Je me suis demander si c’etais pas un pilote qui etais le problème est ce qu’une personne pourrait m’aider a resoudre ce problème merci d’avance ;)

[Malekal_morte]

Salut,

Faire une mise à jour de pilotes driversCloud


et :

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : Les écrans bleus de plantages (BSOD)

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

[azmaldor]

Pas de soucis je vais vérifier tout cela quand je rentre du travail ce soir je te ferais mon retour mais ce qui est bizarre c’est quand je lance desperados 3 des la première mission sa blue screen et uniquement ce jeu ^^“

[azmaldor]

je reviens vers toi j'ai fait une analyse driverscloud et l'installation des drivers sa ma mis " l'installation à échoué sur les drivers : Starship/Matisse Reserved SPP et Realtek High Definition Audio"

et j'ai donc fait une analyse par la suite avec WhoCrashed je te met le résultat ci-dessous:


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: DESKTOP-DUSO5QT
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., TUF GAMING X570-PLUS
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17087430656 bytes (15,9GB)




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

Crash dumps are enabled on your computer.

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

On Tue 16/06/2020 22:56:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061620-7906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x1 (0x7FFA8B5CAE14, 0x0, 0xFFFF, 0xFFFF94811124CB80)
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 Tue 16/06/2020 22:56:03 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+0x81B9)
Bugcheck code: 0x1 (0x7FFA8B5CAE14, 0x0, 0xFFFF, 0xFFFF94811124CB80)
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 Tue 16/06/2020 22:44:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061620-8484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xA (0xC9, 0x2, 0x0, 0xFFFFF80622A27D8C)
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 Tue 16/06/2020 22:12:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\061620-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xA (0x5238272C40, 0xFF, 0x0, 0xFFFFF804566E74EF)
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 Mon 08/06/2020 23:10:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\060820-8750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80716AFA318)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

5 crash dumps have been found and analyzed. 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.

[Malekal_morte]

Mets à jour les pilotes pour voir.

[azmaldor]

J’ai bien effectué les mise a jour restante et pour le moment je n’ai plus de blue screen sur ce jeu a ce moment la je vais patienter 2 jour en jouant pour voir si cela me le refait et si c’est tout bon je te le dirais pour que le topic soit en résolu =) je te remerci par avance pour ton aide ;)

[Malekal_morte]

ok c'est quel jeu ?

[azmaldor]

C’est le jeu Desperados III

[Malekal_morte]

Installe et lance OCCT.
Lance une vidéo Youtube ou Netflix (si tu as).
Vois à combien les températures montent.

Puis lance ton jeu et même chose, vois à combien cela monte.