KERNEL DATA INPAGE ERROR [Résolu/Fermé]

Signaler
Messages postés
3
Date d'inscription
dimanche 9 mars 2014
Statut
Membre
Dernière intervention
4 juin 2014
-
Messages postés
3
Date d'inscription
dimanche 9 mars 2014
Statut
Membre
Dernière intervention
4 juin 2014
-
Bonjour,

Depuis quelque temps , j'ai fréquemment des écrans bleus avec un smiley " :(" qui s'affiche avec le message d'erreur " SYSTEME SERVICE EXCEPTION" ou "KERNEL DATA INPAGE ERROR" ou "KERNEL DATA INPAGE ERROR (dxgkrnl.sys)" et quelque fois ce message sur mon bureau "l'instruction a 0x01055662 emploie l'adresse memoire 0x01b7eaa4. La mémoire ne peux pas etre en etat "written" ".
Depuis deux jours, mon ordinateur met quelques temps a s'afficher avec un affichage des "tuiles" très longue et quelques fois cet écran bleu qui s'affiche dès le démarrage.
Je ne sais plus quoi faire du tout surtout que mon ordi me sert tout le temps pour mes cours de fac...
Je vous joint l'analyse WHO CRASHED que je viens de réaliser et en espérant que vous viendrez a mon aide sachant que je n'y connais pas grand chose en informatique , merci beaucoup ! :

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

computer name: PORTABLECRIS
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\WINDOWS
Hardware: HP Pavilion g7 Notebook PC, Hewlett-Packard, 1845
CPU: GenuineIntel Intel(R) Pentium(R) CPU B950 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4179910656 total
VM: 2147352576, free: 1856479232




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 09/03/2014 19:13:23 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030914-22750-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF80001D908A2)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000010B8300, 0xFFFFF80001D908A2)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 that cannot be identified at this time.



On Sun 09/03/2014 19:13:23 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!DpiGetDriverVersion+0x17102)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000010B8300, 0xFFFFF80001D908A2)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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 that cannot be identified at this time.



On Sun 09/03/2014 17:35:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030914-26937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000012FE520, 0xFFFFC0000B46F3E8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 09/03/2014 17:18:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030914-25156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00005FDAB60, 0x7FF8E201A048)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 09/03/2014 13:33:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030914-25109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00006392D10, 0x302108)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 09/03/2014 10:44:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030914-22953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00000650010, 0xFFFFD00036FE9000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 08/03/2014 20:16:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030814-29015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xEF (0xFFFFE000049A0900, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 08/03/2014 18:49:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030814-24484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00000CAC470, 0xFFFFC00005C24128)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 08/03/2014 18:06:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030814-27296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000007B7BD0, 0xFFFFC0000B42E018)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 08/03/2014 16:34:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030814-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000056A0D60, 0xFFFFF90143390000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

19 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:

netr28x.sys (Ralink 802.11 Wireless Adapter Driver, Ralink Technology, Corp.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.





2 réponses

Messages postés
43176
Date d'inscription
lundi 25 avril 2011
Statut
Contributeur sécurité
Dernière intervention
19 juin 2021
3 692
Hello

As tu mis à jour ta carte graphique ?

Car Directx est en cause
Messages postés
3
Date d'inscription
dimanche 9 mars 2014
Statut
Membre
Dernière intervention
4 juin 2014

Bonsoir ce probleme était du a un gros probleme sur mon ordi donc jai fais une restauration et tout remarche ! Merci de m'avoir consacre du temps et bonne soiree :)