Ecran bleu de la mort IRQL_NOT_LESS_OR_EQUAL (ntkrnlpa.exe)

Résolu/Fermé
Thomasus Messages postés 70 Date d'inscription lundi 14 septembre 2015 Statut Membre Dernière intervention 30 janvier 2019 - 20 mars 2017 à 16:18
Thomasus Messages postés 70 Date d'inscription lundi 14 septembre 2015 Statut Membre Dernière intervention 30 janvier 2019 - 21 mars 2017 à 14:34
Bonjour a tous,

10 minutes après le demarrage, mon ordi (windows 7)plante sur un écran bleu IRQL_NOT_LESS_OR_EQUAL.

ça viens d’où cette merde SVP ??? Windows de M****

L'ordi fonctionne correctement en mode sans echec.

Mes drivers graphiques sont a jour. j'en 2 CG (je crois), une intel HD 4000 et une VGA standard. En désactivant L'intel HD 4000 dans le gestionnaire de périph, ça plante quand même avec l'autre.

Démarrer dernière bonne config ne marche pas.

Memtest ne donne rien. (+200 % sans erreurs)

Rapports whocrashed :

System Information (local)
Computer name: C3PO-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: HP Pavilion g6 Notebook PC, Hewlett-Packard, 183E
CPU: GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 2592452608 bytes total



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 20/03/2017 14:14:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-19702-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83649AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 14:14:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83649AE8)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL



On Mon 20/03/2017 13:51:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-14461-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83642AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 13:16:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-15865-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83072AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 13:03:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-14196-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83076AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 12:26:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-14882-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83076AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 10:11:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-14757-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83071AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 09:57:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-13478-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83038AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 09:45:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-13338-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83046AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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 Mon 20/03/2017 09:14:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032017-11824-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4106F)
Bugcheck code: 0xA (0x16, 0x2, 0x0, 0xFFFFFFFF83089AE8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 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
13 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.



Si vous avez d'autres question je suis a votre disposition.




A voir également:

5 réponses

Malekal_morte- Messages postés 180242 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 24 588
Modifié par Malekal_morte- le 20/03/2017 à 22:55
Salut,

Tu as quel antivirus ?
Si c'est Avast!, il est probablement la source.

Veuillez appuyer sur une touche pour continuer la désinfection...
0
Thomasus Messages postés 70 Date d'inscription lundi 14 septembre 2015 Statut Membre Dernière intervention 30 janvier 2019
20 mars 2017 à 16:26
Avast.
0
Thomasus Messages postés 70 Date d'inscription lundi 14 septembre 2015 Statut Membre Dernière intervention 30 janvier 2019
20 mars 2017 à 16:36
J'ai avast. il ne marche pas en mode sans echec. je vais essayer une version d'essai de norton, je verrais bien.
0
Malekal_morte- Messages postés 180242 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 24 588
20 mars 2017 à 20:59
Pas une bonne idée.
Désinstalle Avast! et teste sans déjà.
0
Apparement j'ai trouvé tout seul, c'est a cause d'une MAJ winbobe. GG microsoft.

j'ai fait f8 au démarrage, réparer l'ordinateur, Restaurer le système a une date antérieure. ça a mis un moment, après j'ai eu un message d'erreur comme quoi ça a fail. J'ai relancé, la j'ai eu un message comme quoi la restauration s'est faite correctement O_o et j'usqu'a présent plus de soucis.

Je touche du singe.
0
0
Peut être une incompatibilité entre Avast Et une maj windows ? (celle que j'ai eu datait du 15 mars.)
Au moins si ça reviens, ça me donne une piste. merci beaucoup a vous !.
0

Vous n’avez pas trouvé la réponse que vous recherchez ?

Posez votre question
Thomasus Messages postés 70 Date d'inscription lundi 14 septembre 2015 Statut Membre Dernière intervention 30 janvier 2019
Modifié par Thomasus le 21/03/2017 à 14:38
Je me permet un petit retour en disant que ma manip a bien fonctionné, c'est donc bien une incompatibilité entre les MAJ windows et Avast.

Donc vous avez le choix, restaurer comme j'ai fait pour virer les MAJ windows et désactiver windows update ou désinstaller Avast.

J'ai fais mon choix perso j'ai virer les MAJ, même si j’imagine que c'est plus simple de virer Avast Si vous avez ce problème.
On va dire que c'est plus "safe" de conseiller de laisser windows update (LOL).

enfin bref, problème résolu, merci quand même ;)
0