HELP, problème d'arrêt intempestif de mon pc portable • page 2

[nono63]

pour le rapport je n’arrive pas à le sauvegarder en ".text" , il n'y a pas l'option

[bernard53]

fait juste un copier coller du rapport et mets le dans ta réponse.

[nono63]

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Fri 13/02/2015 20:35:45 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-17877-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC5EF)
Bugcheck code: 0x50 (0xFFFFFFFFB0467AAC, 0x1, 0xFFFFFFFF823664C1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.



On Fri 13/02/2015 20:35:45 GMT your computer crashed
crash dump file: C:\windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngUnlockSurface+0x257F)
Bugcheck code: 0x50 (0xFFFFFFFFB0467AAC, 0x1, 0xFFFFFFFF823664C1, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that invalid system memory has been referenced.
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 that cannot be identified at this time.



On Fri 13/02/2015 20:32:06 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-16879-01.dmp
This was probably caused by the following module: igdkmd32.sys (igdkmd32+0x47426)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8B93BBA8, 0xFFFFFFFFAFA308A0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\igdkmd32.sys
product: Intel Graphics Accelerator Drivers for Windows Vista(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M



On Fri 13/02/2015 20:14:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-17050-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0xA885)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF86B29885, 0xFFFFFFFF87C679D4, 0xFFFFFFFF87C675B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.



On Fri 13/02/2015 19:50:19 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-41667-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40A18)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801B4000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
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 a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 13/02/2015 17:24:26 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-18673-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xC05E3)
Bugcheck code: 0x1A (0x3452, 0x233000, 0xFFFFFFFFC0803580, 0x0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 13/02/2015 17:21:28 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-18376-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8DA1D)
Bugcheck code: 0x50 (0xFFFFFFFFD9CFC82C, 0x0, 0xFFFFFFFF8247A641, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 13/02/2015 17:18:06 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-17752-01.dmp
This was probably caused by the following module: athr.sys (athr+0xC3002)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFFFFF8ACC9002)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\windows\system32\drivers\athr.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: athr.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 13/02/2015 16:58:04 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-18439-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEE0C)
Bugcheck code: 0x51 (0x1, 0xFFFFFFFF87A1B708, 0x146B000, 0x374)
Error: REGISTRY_ERROR
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 a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
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 13/02/2015 16:56:28 GMT your computer crashed
crash dump file: C:\windows\Minidump\021315-15272-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xCC5EF)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF823264C1, 0xFFFFFFFFACAEF4F4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 that cannot be identified at this time.





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

18 crash dumps have been found and analyzed. Only 10 are included in this report. 3 third party drivers have 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:

iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation)
igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
athr.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

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

[SyLvErFoX]

Les 3 pilotes fautifs sont ceux-ci

1- iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation)

2- igdkmd32.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)

3- athr.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)

3 à la fois c'est plutôt rare, le fichier système est probablement corrompu.

[nono63]

Pas cool, sniff...
Comment dois je faire pour tout remettre en ordre ?

[SyLvErFoX]

Moi je téléchargerais ces 3 pilotes, ensuite dans le gestionnaire de périphérique je les désinstallerais, je redémarrerais en mode sans échec et j'installerais les nouveaux.

[nono63]

Dak, je vais voir ça, car c'est Bernard53 qui suivait le dossier et je me demandais si avec le logiciel qu'il m'avait demandé d'installer pour que je lui envoie le rapport il y avait pas quelque chose à faire par la suite....

[nono63]

J'ai une question qui peut paraître bête mais je suis pas un expert non plus. Quand on désinstalle des pilotes puis que l'on redémarre le pc pour terminer la désinstallation, les pilotes ne sont plus là et celà n'affecte pas le fonctionnement du pc si ils sont plus la ?

[SyLvErFoX]

Non Windows fait fonctionner le périphérique avec un pilote générique. L'idée de démarrer en mode sans échec empêche quelques fois Windows d'installer un pilote générique, ça permet d'installer nous-même le vrai pilote c'est encore mieux lorsqu'on a eu des difficulté avec ce même pilote.

[routman54]

Bonsoir ,
C'est le domaine des Helpers et normalement je n'y interviens pas , mais là comme tu as plusieurs rapports whocrashed qui donnent des résultats différents , c'est en général significatif d'un problème de ram .
Donc si tu en as plusieurs tu en ôtes une , tu travaille comme ça une journée puis ensuite avec l'autre , on trouvera la fautive comme ça , sinon on peut utiliser Memtest > ICI < mais c'est pareil barrette après barrette et cinq a six passes chacune .
Bonne continuation .

[nono63]

Bonsoir routman
Je ne sais pas du tout si j'ai plusieurs ram, je n'ai jamais rien rajouté, tout est d'origine..

[SyLvErFoX]

Ça peut être un problème de ram, en effet, mais moi je suis convaincu que le problème vient d'ici, iastor.sys ...

[bernard53]

Bonjour routman et SyLvErFoX.
Vous êtes très compétant dans ce genre de soucis, je vous laisse et je suis cela quand même.
Bon dimanche

[nono63]

Bonjour, petite question, une fois que j'ai désinstallé un driver, comment dois je mis prendre pour le réinstallé correctement ?

[nono63]

J'ai téléchargé celui là iastor.sys (Intel Matrix Storage Manager driver - ia32, Intel Corporation) mais il y a pas de .exe pour lancer l'installation