Bon je relance le sujet, car les écrans bleus ont recommencé. Voilà le rapport de Whocrashed:
System Information (local)
Computer name: PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., Crosshair V Formula
CPU: AuthenticAMD AMD FX™-8150 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8531505152 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 19/10/2015 09:53:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-16489-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88004B90A03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 19/10/2015 09:53:25 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88004B90A03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 19/10/2015 09:40:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-17019-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1B990)
Bugcheck code: 0xD1 (0x68, 0x2, 0x1, 0xFFFFF8800563F990)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 19/10/2015 09:29:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101915-18610-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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 Sun 18/10/2015 10:48:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-40809-02.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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 Sun 18/10/2015 10:43:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-40809-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 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 Sun 18/10/2015 09:33:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-17877-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88004A1BA03)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 18/10/2015 09:25:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-16052-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1B990)
Bugcheck code: 0xD1 (0x68, 0x2, 0x1, 0xFFFFF88004DA7990)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 18/10/2015 09:10:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101815-15771-01.dmp
This was probably caused by the following module: e1q62x64.sys (0xFFFFF88004C85867)
Bugcheck code: 0xD1 (0xA0, 0x2, 0x0, 0xFFFFF88004C85867)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 17/10/2015 18:26:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101715-16785-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1B990)
Bugcheck code: 0xD1 (0x68, 0x2, 0x1, 0xFFFFF88004C85990)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\e1q62x64.sys
product: Intel® Gigabit Adapter
company: Intel Corporation
description: Intel® 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® Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
15 crash dumps have been found and analyzed. Only 10 are included in this report. 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® 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 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.
J’ai beau cherché mais il y a très peu de sujets là dessus …
