Forum-seven : Communauté francaise de Windows 7

Carte mère
SMBios version 2.6
ASUSTeK Computer INC. Crosshair IV Extreme Rev 1.xx
Bios: American Megatrends Inc. 0502 11/04/2010 taille: 2048Kb

Chipset
Northbridge: AMD 890FX
Southbridge: AMD SB850

Processeur
AMD Phenom II X6 1090T Thuban Socket AM3 (938) (@45 nm) 3200 Mhz ( L1I: 6 x 64 Ko, L1D: 6
x 64 Ko, L2: 6 x 512 Ko, L3: 6144 Ko )

Mémoire
Mémoire physique totale: 12288 Mo, Type: DDR3, @534.5MHz, 8.0-8-8-20-1T
DDR3 Patriot Memory 1600EL Series 4096 Mo PC3-8500F (533 Mhz)
DDR3 Patriot Memory 1600EL Series 4096 Mo PC3-8500F (533 Mhz)
DDR3 Patriot Memory 1600EL Series 4096 Mo PC3-8500F (533 Mhz)

Carte Graphique
NVIDIA GeForce GTS 250 (G92,,512 Mo)

Disque dur
Seagate Barracuda 7200.12
1000GB 3.5", SATA3

Crash dumps are enabled on your computer.


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.



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

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:

e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)

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.