Bonjour amis passionnés d'informatique.
 
J'ai récupéré le PC portable d'un ami pour une réinstallation en règle.
 
Tout se passe très bien jusqu'à l'installation du pilote graphique (Intel).
 
Au redémarrage du PC, j'ai un magnifique écran bleu avec un compte à rebours puis l'ordinateur redémarre.
 
Seul un démarrage en mode sans échec fonctionne, je suis donc obligé de désinstaller ce pilote puis le PC démarre correctement.
 
Le pilote graphique est le bon puisque c'est le dernier en date et qu'il était installé (dans ça même version) sur ce même PC.
 
Je ne sais plus quoi faire et m'en remet à vous
 
je vous remercie d'avance
 
 
 

Regarde avec le logiciel Whocrashed quel est l'erreur que tu as eu.

Bonjour Nex84, je te remercie de ton retour, je vais regarder tout ça et reviens vers toi dès que je suis chez moi

Voici les éléments en anglais :s
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: ELIANE-PC
Windows version: Windows 7 , 6.1, build: 7600
Windows dir: C:\Windows
Hardware: X55A, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Pentium(R) CPU B980 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4173152256 bytes total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Tue 04/10/2016 16:15:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100416-28454-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F840)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF8000336F3BC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 04/10/2016 16:15:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64!hybDriverEntry+0x5969B)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF8000336F3BC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel Graphics Accelerator Drivers for Windows 8(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).  
Google query: Intel Corporation IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Mon 03/10/2016 20:25:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100316-25240-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800033CA42C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 03/10/2016 20:17:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100316-25350-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800033CA42C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 03/10/2016 19:49:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100316-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800031B842C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 03/10/2016 19:10:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100316-20560-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)  
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF800031CC42C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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
--------------------------------------------------------------------------------
 
6 crash dumps have been found and 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:  
 
igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)
 
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.  

Je pense avoir un début de réponse en postant le rapport du logiciel.
 
Il est marqué Driver graphique Intel pour Windows 8, c'est peut être de là que viens le problème.
 
Je vais essayer de trouver un autre pilote (sur le site d'ASUS) et essayer
 
Merci ma connexion 2 Mbit ^^

Après installation d'un autre pilote, ça ne fonctionne toujours pas ...

On dirait effectivement que ça vient de la partie graphique.
 
Soit du driver (trop ancien, même si celui de Windows 8 peut fonctionner)
Soit du gpu (problème hardware)
 
Quel est le modèle du PC ?

 
C'est un portable ASUS X55A, j'ai essayé plusieurs version du pilote, c'est toujours le même problème.
 
J'ai, en attendant, installé Windows 8 avec le même pilote graphique et la tout fonctionne correctement.
 

Bonjour, un bon moyen pour avoir le driver adéquat est de télécharger Intel driver utility sur le site d'intel là
 https://downloadcenter.intel.com/do [...] te-Utility