personne ??? PAGED_FAULT_IN_NON_PAGED_AREA

Question

Bonjour,      

Jai regarder plein de forum sans jamais trouver mon bonheur !   
J'ai un pc avec windows 7 64bit et windows 7 32bit ( sur 2 partition différente ) jusqua la tout va bien !     
Voilà ma config :     
amd athlon 64 X2 4600+ 2.41GHZ     
2 go ram (1 x 2Go) DDR2     
Ati radeon HD 4350 series ( je sais plus exactement ) 512mb DDR2     
Carte mere M2N-X     

Voila alors jai un ecran bleu qui apparait qui affiche " Paged_fault_in_nonpaged_area".     
je lai donc amené chez un réparateur qui ma fait payé 20 euros pour un nettoyage et une nouvelle pate thermique et il ma fait que sa lui avait pas fait l'ecran bleu !     
Jai dit bon ca va alors.     
Je le rebranche 2 a 3 heures aprés , ca me la refait et c'est souvent quand jutilise les performance au max !     
A laide !!!!      


Configuration: Windows 7 / Firefox 6.0.1

jlpjlp · Answer

slt
c'est quoi un windows 34bits ?

https://www.commentcamarche.net/informatique/windows/25143-ecran-bleu-windows-bsod-explications-solutions/

hylian45 · Answer

J'aimerais que tu lise la premiere phrase s'il te plait !

jlpjlp · Answer

ok tu as corrigé ! 


tu as regardé le lien donné 

sinon cela le fait à quel moment? sur quel windows ? et 
colle un rapport avec whocrashed 

et 
tu peux lire ceci:
https://support.microsoft.com/en-us

hylian45 · Answer

Bonjour
Sa le fait sur les 2 windows !
je poste le rapport quand il a fini !

hylian45 · Answer

Il m'affiche ca   

http://img66.xooimage.com/views/a/3/1/whocrashed-2c89b52.png/

jlpjlp · Answer

erreur minidump  https://forum.zebulon.fr/topic/55305-comment-reparer-lerreur-minidump



et pour voir


Télécharge ZHPDiag ( de Nicolas coolman ).
https://www.zebulon.fr/telechargements/securite/systeme/zhpdiag.html


(outil de diagnostic)

Double clique sur le fichier d'installation, puis installe le avec les paramètres par défaut ( N'oublie pas de cocher " Créer une icône sur le bureau " )

Lance ZHPDiag en double cliquant sur l'icône présente sur ton bureau (Clique droit -> Executer en tant qu'admin ( vista )

Clique sur la loupe en haut à gauche, puis laisse l'outil scanner.

Une fois le scan terminé, clique sur l'icône en forme de disquette et enregistre le fichier sur ton bureau.

Rend toi sur Cjoint : http://www.cijoint.fr/

Clique sur "Parcourir " dans la partie " Joindre un fichier[...] "

Sélectionne le rapport ZHPdiag.txt qui se trouve sur ton bureau

Clique ensuite sur "Cliquez ici pour déposer le fichier " et copie/colle le lien dans ton prochain message

ou sinon pour transmettre ton rapport:
* Quand le scan est fini, utilise le site http://pjjoint.malekal.com/ pour envoyer les rapports.
Donnes le liens pjjoint ici ensuite pour pouvoir être consultés.

Hylian45 · Answer

Merci a tous mais j'ai trouver et je vais en faire partager les autres !

Quand jai fait un scan avec WhoCrashed il ma affiché des fichiers qui contiennent mon erreur ecran bleu !
jai renommé le fichier Memory.dmp en rajoutant un "2" devant ( Memory2.dmp )
et jai supprimé le dossier Minidump  ( tout ca ce trouve dans 
(Lettre de votre lecteur):\windows
Je vous remercie de votre aide qui m'a été bien utile!

antipolis a · Answer

https://support.microsoft.com/fr-fr/help/222635

Hylian45 · Answer

Je suis degouter :-(  ca me la refait !!!!

Help--ps2-- · Answer

Salut , 
ça c'est un message pas cool :/
en général , c'est quand la RAM déconne et qu'elle n'arrive pas à se vider , elle plante le pc .. passe tes barrettes sous memtest ( en live CD sinon ça testera pas tout ) 
tiens nous au jus :)

Hylian45 · Answer

Ben mem test me dit que la RAM sont ok et jai essayer de les changer une par une et ca plante encore ! 
Je pense pas que c'est la RAM

jlpjlp · Answer

tente de faire le reste que je t'ai proposé

a plus

Hylian45 · Answer

C'est fait ca donne rien
jai vu des erreur sur c'est fichier avec who crashed
-atikmdag.sys
-ntoskernel.exe
-ntkrnlmp.exe


le 1er c'est un ecran bleu avec ATTEMPED_EXECUTE_OF_NONEXECUTE_MEMORY
les 2 autre sont page_fault_in_nonpaged_area

Je tien a dire que mes barette memoire sont OK !

Hylian45 · Answer

up!!!

jlpjlp · Answer

je suis occupé ce week en attendant regarde ces liens


-atikmdag.sys 

cela vient de ta carte ATI:

mets à jour les pilotes 

https://forums.commentcamarche.net/forum/affich-12088452-atikmdag-sys

https://www.overclock.net/forums/



-ntoskernel.exe 
https://forums.commentcamarche.net/forum/affich-2002686-probleme-de-boot-ntoskrnl-exe

http://forum.telecharger.01net.com/forum/high-tech/PRODUITS/Pannes-courantes/message-ntoskrnl-endommage-sujet_184752_1.htm

-ntkrnlmp.exe 

https://answers.microsoft.com/fr-fr/windows/forum/windows_7-system/bsod-windows-7-x64-related-ntkrnlmpexe/d34c205b-e5fa-4c59-8398-1c75f5284302

- ATTEMPED_EXECUTE_OF_NONEXECUTE_MEMORY 

https://www.google.fr/search?q=ATTEMPED_EXECUTE_OF_NONEXECUTE_MEMORY+&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:fr:official&client=firefox-a&gws_rd=ssl#sclient=psy&hl=fr&client=firefox-a&hs=GON&rls=org.mozilla:fr%3Aofficial&source=hp&q=NON+EXECUTE+MEMORY&pbx=1&oq=NON+EXECUTE+MEMORY&aq=f&aqi=&aql=&gs_sm=e&gs_upl=5016l23648l0l23843l2l2l0l0l0l0l175l335l0.2l2l0&bav=on.2,or.r_gc.r_pw.&fp=63bf063c9eb94920&biw=1366&bih=596


_page_fault_in_nonpaged_area

https://forums.commentcamarche.net/forum/affich-2173519-page-fault-in-nonpaged-area

Hylian45 · Answer

Jai essayer tout ca mais ca marche pas puis il faut pas oublier que je suis sous Windows 7

Hylian45 · Answer

Maintenant jai que 3 Page_Fault_In_Nonpaged_Area avec ntoskrnl.exe
et 1 ntkrnlmp.exe 


HELP

jlpjlp · Answer

répare windows 7 64 et windows 7 32 bits via le DVD de windows 7

cela écartera un fichier endommagé

aide toi de ceci

https://www.commentcamarche.net/informatique/windows/259-que-faire-quand-windows-ne-demarre-plus/#reparer-a-partir-d-un-cd-de-windows-ou-une-cle-usb-contenant-windows



si cela perssite refais le point: depuis quand? suite à quoi? as tu mis un nouveau materiel ou logiciel?
as tu vérifié que tu as bien pris les pilotes pour 64 bits ou 32 bits suivant le système utilisé?

...

Hylian45 · Answer

ok je vais essayer

hylian45 · Answer

Cela na pas marcher !


Voila un screen whocrashed monter avec paint !
Beaucoup de truc rajouter ! Ché pa pourqoi

http://img74.xooimage.com/views/e/5/7/whocrashedprobleme-2cc482d.png/

jlpjlp · Answer

donc une erreur de type minidump... Il faut voir le lien donné pour cela . Sinon donner beaucoups plus d infos pour pouvoir t aider.

Hylian45 · Answer

en attente de réponse

Hylian45 · Answer

Voila le crash dump


Crash dump file:        K:\Windows\Minidump\091111-24538-01.dmp
Date/time:              9/11/2011 10:17:14 AM GMT
Uptime:                 00:12:24
Machine:                
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xD1
Bug check parm 1:       0xFFFFF88002C9FF58
Bug check parm 2:       0xD
Bug check parm 3:       0x8
Bug check parm 4:       0xFFFFF88002C9FF58
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091111-18688-01.dmp
Date/time:              9/10/2011 11:19:23 PM GMT
Uptime:                 01:43:14
Machine:                
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xD1
Bug check parm 1:       0xFFFFF88002CA4CEC
Bug check parm 2:       0xD
Bug check parm 3:       0x8
Bug check parm 4:       0xFFFFF88002CA4CEC
Probably caused by:     atikmdag.sys
Driver description:     ATI Radeon Kernel Mode Driver
Driver product:         ATI Radeon Family
Driver company:         ATI Technologies Inc.
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.). 



Crash dump file:        K:\Windows\memory.dmp
Date/time:              9/14/2011 10:03:17 AM GMT
Uptime:                 00:22:58
Machine:                
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xD1
Bug check parm 1:       0xFFFFF88002CE2CEC
Bug check parm 2:       0xD
Bug check parm 3:       0x8
Bug check parm 4:       0xFFFFF88002CE2CEC
Probably caused by:     ntkrnlmp.exe
Driver description:     
Driver product:         
Driver company:         
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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 which cannot be identified at this time. 


Crash dump file:        K:\Windows\Minidump\091411-18376-01.dmp
Date/time:              9/14/2011 10:03:17 AM GMT
Uptime:                 00:22:58
Machine:                
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xD1
Bug check parm 1:       0xFFFFF88002CE2CEC
Bug check parm 2:       0xD
Bug check parm 3:       0x8
Bug check parm 4:       0xFFFFF88002CE2CEC
Probably caused by:     atikmdag.sys
Driver description:     ATI Radeon Kernel Mode Driver
Driver product:         ATI Radeon Family
Driver company:         ATI Technologies Inc.
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.). 

Crash dump file:        K:\Windows\Minidump\091111-18517-01.dmp
Date/time:              9/11/2011 1:06:10 PM GMT
Uptime:                 01:28:36
Machine:                
Bug check name:         DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xD1
Bug check parm 1:       0x0
Bug check parm 2:       0xD
Bug check parm 3:       0x1
Bug check parm 4:       0xFFFFF88002CA6D98
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091311-16270-01.dmp
Date/time:              9/13/2011 12:31:42 PM GMT
Uptime:                 00:53:12
Machine:                
Bug check name:         IRQL_NOT_LESS_OR_EQUAL
Bug check code:         0xA
Bug check parm 1:       0x8
Bug check parm 2:       0x2
Bug check parm 3:       0x1
Bug check parm 4:       0xFFFFF80002D00B37
Probably caused by:     atapi.sys
Driver description:     ATAPI IDE Miniport Driver
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

Comments:
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091211-18252-02.dmp
Date/time:              9/12/2011 3:49:07 PM GMT
Uptime:                 00:13:51
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88002C10768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88002C10768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091311-16816-01.dmp
Date/time:              9/12/2011 9:27:10 PM GMT
Uptime:                 04:17:19
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88003201768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88003201768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091011-17331-01.dmp
Date/time:              9/10/2011 3:47:22 PM GMT
Uptime:                 17:37:51
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88003214768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88003214768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Date/time:              9/10/2011 9:08:40 PM GMT
Uptime:                 00:18:55
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88002C18768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88002C18768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091211-18236-01.dmp
Date/time:              9/11/2011 5:24:18 PM GMT
Uptime:                 04:17:32
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88002C1A768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88002C1A768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091111-19624-01.dmp
Date/time:              9/11/2011 10:48:54 AM GMT
Uptime:                 00:31:02
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88002C14768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88002C14768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091011-22838-01.dmp
Date/time:              9/10/2011 9:35:28 PM GMT
Uptime:                 00:07:23
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88003210768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88003210768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091211-18080-01.dmp
Date/time:              9/12/2011 4:58:48 PM GMT
Uptime:                 01:08:42
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF88003202768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF88003202768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Crash dump file:        K:\Windows\Minidump\091211-17518-01.dmp
Date/time:              9/12/2011 5:08:41 PM GMT
Uptime:                 00:08:42
Machine:                
Bug check name:         PAGE_FAULT_IN_NONPAGED_AREA
Bug check code:         0x50
Bug check parm 1:       0xFFFFF8800320A768
Bug check parm 2:       0x8
Bug check parm 3:       0xFFFFF8800320A768
Bug check parm 4:       0x0
Probably caused by:     ntoskrnl.exe
Driver description:     NT Kernel & System
Driver product:         Microsoft® Windows® Operating System
Driver company:         Microsoft Corporation
OS build:               Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Architecture:           x64 (64 bit)
CPU count:              2
Page size:              4096

Bug check description:
This indicates that invalid system memory has been referenced.

Comments:
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 which cannot be identified at this time. 

Cest un peu long  
Jattend vos réponse
(Voila les details)

Hylian45 · Answer

UPpp !!!!

Personne ??? PAGED_FAULT_IN_NON_PAGED_AREA

24 réponses

Votre réponse

Newsletters