Hello tout le monde !

J'aurais bien besoin de vous sur ce coup !

Je viens d'installer des jeux via mon disque dur externe et j'ai eu suite à ça 2 x le mème écran bleu = IRQL NOT LESS OR EQUAL .

Des idees sur comment le resoudre svp ?

J'ai résolu un bsod sur un portable dell a cause de driver graphique foireux, à voir

ps : Des jeux via le disque dur ou importer des jeux depuis ton disque dur ensuite installer sur ton pc ?

Des jeux installer sur un dd externe depuis l ordi a ma copine pour le mettre sur mon pc apres

Ok , ta essayer le drivers graphique ?

Des jeux installer sur un dd externe depuis l ordi a ma copine pour le mettre sur mon pc apres

Driver a jour tout est remis a jour ca qui est etrange :/

Installe whocrashed et posté le résultat ici, peut être que tu verra par toi même il est pas mal pour trouver les raison d'un blue screen

Crash dumps are enabled on your computer.

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

On Thu 25/07/2019 20:33:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072519-9218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF8056D0CEBDF)
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 25/07/2019 20:33:28 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+0x7EF9)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF8056D0CEBDF)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

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

2 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.

Voilà le rapport j'y comprends pas grand chose pour tout avouer

sa semble plus être logiciel que matériel, tu a dit que tu avais installé le dernier drivers graphique mais moi aussi sa planté justement avec le dernier pilote sortie, essaye de désinstalle complétement le driver actuel, et installe le driver précédent,

sinon, même si le dump affiche un problème logiciel, c'est chiant, mais si le changement de driver ne change rien, essaye de tester avec une barrette sur deux, en changeant bien sur à chaque fois de barrette,

Okay je vais essayer ça ! merci

Hello bon je reviens vers vous car y a toujours le meme problème ... Ca avais pas été le cas aujourd'hui pourtant .

Voici le rapport :

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

On Sat 27/07/2019 00:01:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072719-7828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0xA (0xE8, 0x2, 0x1, 0xFFFFF8013633CE42)
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 Fri 26/07/2019 23:59:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072719-7875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x1A (0x403, 0xFFFFEF812A4AB308, 0xC00000027C599867, 0xFFFFEF8000196250)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (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.

J'ai tenter de réinstaller la précedente version de ma CG voir si ça change quelque chose je vous tiens au courant

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

On Sat 27/07/2019 00:16:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072719-8000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8040EEDDE3B, 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.

Je suis entrain de faire le memtest la pour voir si la ram est le soucis

déjà eu problème de driver réinstalle Windows ça a marché pour moi

rien qu'a marché d'autre pour moi et j'ai chercher pendant des jours et c'était pas un problème matériel donc si t'as tout testé et que rien marche réinstalle windows complètement à zero

Tu reinstalle comment windows a 0 deja ? Je ne sais plus du tout :/

Le 27 juillet 2019 à 00:04:07 proudhy a écrit :
Hello bon je reviens vers vous car y a toujours le meme problème ... Ca avais pas été le cas aujourd'hui pourtant .

Voici le rapport :

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

On Sat 27/07/2019 00:01:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072719-7828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0xA (0xE8, 0x2, 0x1, 0xFFFFF8013633CE42)
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 Fri 26/07/2019 23:59:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\072719-7875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3F50)
Bugcheck code: 0x1A (0x403, 0xFFFFEF812A4AB308, 0xC00000027C599867, 0xFFFFEF8000196250)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (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.

Lut ! Hummm ram donc instable voir défectueuse (si vraiment pas de bol. Cela peut être une fréquence de ram trop haute pour l'IMC de ton cpu à gérer. Ou de slatences trop agressives et serrées.

Conseil perso: télécharges et utilises Memtest86 (de chez Passmark) et testes ta ram.

De préférence donc en Parallal (Sequencial n'est pas assez pour chercher en profondeur).

Sur une clé usb formate en FAT32:ok:

Fait très atention ! Un soucis de ram peut te faire penser que ta cg est défectueuse ou son driver voir ton alim...voir que TOUT ce que tu pourras télécharger sera sujet à être corrompue..applications comme autre (donc jeux).

Hello ! J'ai pas bien compris ce que tu dissait par : "De préférence donc en Parallal (Sequencial n'est pas assez pour chercher en profondeur).

Sur une clé usb formate en FAT32:ok:"

Moyen de degrossir ?

Je me tappe blue screen sur blue screen la

Le 27 juillet 2019 à 01:00:53 proudhy a écrit :
Hello ! J'ai pas bien compris ce que tu dissait par : "De préférence donc en Parallal (Sequencial n'est pas assez pour chercher en profondeur).

Sur une clé usb formate en FAT32:ok:"

Moyen de degrossir ?

Je me tappe blue screen sur blue screen la

En gros télécharges Memtest86 puis installes le sur ta clé usb formaté en FAT32.

Le soucis là c'est qu'il vaudrait mieux que tu le télécharges à partir de ton pc..vu que ta ram à un soucis justement:hap: (prend la à partir du tel et fait un transfert vers l pc au pire).

Ensuite une fois fait.

Met la clé usb avec Memtest86 en 1er position dans ton BIOS pour boter dessus. (tu auras dans le BIOS partition 1 et partition 2).

Une fois lançé vas dans l'onglet cpu test juste au dessus de start test..Puis choisis sequancial.

Et lançes le test:ok:

Selon ton cpu et sa fréquence il te faudra plusieurs heures. (c'est en 4 passes au totalsur la version gratuite).