J'aurai besoin de votre avis. J'ai fait une installation sur un ordi que j'ai monté moi-même.
J'ai installé un seven et j'y ai mis tous les drivers, pilotes qui m'étaient proposés. Tout avait l'air parfait
mais le problème c'est que le système crach régulièrement depuis aujourd'hui.
J'ai pu prendre une photo du message qui apparaît à l'écran. Voici:
Qu'en pensez-vous?...
Merci pour votre aide.
Modifié en dernier par ale le dim. 29 janv. 2012 18:47, modifié 1 fois.
Bonsoir,
Il s'agit d'un problème de périphérique mal reconnu.
Dans le BIOS choisis de charger les paramètres par défaut pour commencer.
Une fois démarré, au besoin en mode sans échec, lance cet outil. WhoCrashed Home Edition 3.01 de Resplendence
Tu l'installes et tu le lances par Analyze. Tu postes un copier-coller de ce qui apparait .
Le rapport LOCALT~11.html sera dans le dossier du programme WhoCrashed.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
On Sat 28.01.2012 15:50:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-32682-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF8800167F586)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 28.01.2012 15:50:02 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x21219)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF8800167F586)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x 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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: e1q62x64.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 28.01.2012 15:44:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002FED76C)
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 which cannot be identified at this time.
On Sat 28.01.2012 14:41:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-32775-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800167E730)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 28.01.2012 14:01:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-38469-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002FF076C)
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 which cannot be identified at this time.
On Sat 28.01.2012 13:14:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-24258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800167E730)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 28.01.2012 13:03:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-27456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002FEE76C)
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 which cannot be identified at this time.
On Sat 28.01.2012 12:57:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012812-34179-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001680730)
Error: DRIVER_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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
8 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:
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.
Oups...je ne sais pas à quoi j'ai pensé, il m'avait semblé avoir installer
mes pilotes...mais apparemment pas...Je les réinstalle. En tous cas merci pour votre aide.
Bonjour,
donc j'ai réinstallé tous mes pilotes. Ensuite j'ai fait un scanne avec driverScanner
(super logiciel que je ne connaissais pas) Voici le résultat du scanne
J'ai voulu télécharger le dernier pilote pour nvidia mais quand je lance un téléchargement sur la toile c'est là qu'il crash...
Est-ce que ça viendrait d'un mauvais fonctionnement de mon pilote de la carte réseau?
Bonjour,
Je crois avoir déjà répondu à ta question.
Avec ta carte mère tu dois avoir un CD avec tous les pilotes.
Ce sera mieux que Driver Scanner de Uniblue.
Cet éditeur a une politique commerciale un peu douteuse.
@+
En cas de problème constaté sur un sujet, contactez un modérateur par MP. N'intervenez pas vous-même. Merci
WhoCrashed Home Edition 3.01 de Resplendence 
Tu postes un copier-coller de ce qui apparait .
