Kernel data inpage error
Fermé
sabrinade
Messages postés
27
Date d'inscription
jeudi 5 juillet 2007
Statut
Membre
Dernière intervention
17 août 2018
-
16 août 2018 à 11:34
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 17 août 2018 à 10:52
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 17 août 2018 à 10:52
A voir également:
- Kernel_data_inpage_error ntoskrnl.exe
- App data - Guide
- Data error iptv - Forum TV & Vidéo
- Fan error lenovo ✓ - Forum Refroidissement
- Data (d:) - Forum Disque dur / SSD
- Kernel power ✓ - Forum Windows 10
4 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 656
16 août 2018 à 11:59
16 août 2018 à 11:59
Salut,
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 : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
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 : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
16 août 2018 à 12:05
ces plantages ont lieu quand personne ne se sert du pc et que le bureau est affiché
si je me sers du pc avec internet ou autre il ne plante pas et peut rester des heures sans plantage
rien de particulier de branché en usb juste des enceintes et une imprimante que j'ai déjà débranché
16 août 2018 à 12:07
16 août 2018 à 12:14
--------------------------------------------------------------------------------
Computer name: COLETTE
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\WINDOWS
Hardware: EasyNote TE11HC, Packard Bell, EG50_HC_HR
CPU: GenuineIntel Intel(R) Celeron(R) CPU B830 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4099174400 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 16/08/2018 11:16:29 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!MmUnlockPages+0x549B)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE0018C9FA450, 0x16289000)
Error: KERNEL_DATA_INPAGE_ERROR
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 28/07/2018 18:17:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072818-28546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x5, 0x0, 0x12000, 0xFFFFE0009EFAC390)
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 28/07/2018 17:34:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072818-36828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00136C0DDA0, 0xD789D71AAF)
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 28/07/2018 17:00:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072818-34109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000DB5BDB70, 0xFFFFF80137E8B000)
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 28/07/2018 11:48:34 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072818-31703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE001F23F71E0, 0x7AEBF60FCA)
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 Wed 25/07/2018 10:54:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072518-35421-01.dmp
This was probably caused by the following module: aswbidsdrivera.sys (0xFFFFF8010D80BDFD)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010D80BDFD, 0xFFFFD0004D744B40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\aswbidsdrivera.sys
product: Avast
company: AVAST Software
description: IDS Application Activity Monitor Driver.
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software).
Google query: aswbidsdrivera.sys AVAST Software SYSTEM_SERVICE_EXCEPTION
On Tue 24/07/2018 19:12:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072418-30656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00171A121E0, 0x24D96752)
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 22/07/2018 11:35:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072218-33656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF6802BF29010, 0x2C31392520323369, 0xFFFFE000EFFD2860)
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.
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. 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.
On Fri 20/07/2018 18:20:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072018-22750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE00171F521E0, 0x53782419A0)
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 Fri 20/07/2018 17:55:10 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072018-38796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1554A0)
Bugcheck code: 0x7A (0x5, 0x0, 0x2000, 0xFFFFE00126E94D80)
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
--------------------------------------------------------------------------------
On your computer a total of 51 crash dumps have been found. Only 10 have been analyzed. 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:
aswbidsdrivera.sys (IDS Application Activity Monitor Driver., AVAST Software)
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.