Il y a un bug récurant sur ma machine que je ne parviens pas à résoudre.
Il s'agit d'un ordinateur que j'ai monté moi-même. J'ai un disque
avec Linux et un autre avec windows. Ils sont tous les deux ssd.
Et trois autres disques avec mes fichiers. Quand je tourne sous Linux
je n'ai aucun soucis mais lorsque je suis sur windows seven il me crash
régulièrement (Blue screen). J'ai pourtant bien mis tous mes pilotes à jours.
Si quelqu'un à une idée ça me serait d'un grand secours.
Voici les informations du crash avec (WhoCrashed):
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 15.05.2014 08:45:05 GMT your computer crashed
crash dump file: C:\Windows
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645450)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001645450)
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 Thu 15.05.2014 08:45:05 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 (0x28, 0x2, 0x0, 0xFFFFF88001645450)
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: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Thu 15.05.2014 08:17:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051514-11871-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001845373)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001845373)
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 Wed 14.05.2014 18:36:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051414-10545-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001846373)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001846373)
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 Wed 14.05.2014 06:50:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051414-10233-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645373)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001645373)
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 Tue 13.05.2014 14:47:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051314-9921-02.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800184616C)
Bugcheck code: 0xD1 (0x6, 0x2, 0x0, 0xFFFFF8800184616C)
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 Tue 13.05.2014 14:22:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051314-9906-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x9BBE2C)
Bugcheck code: 0x116 (0xFFFFFA800C0284E0, 0xFFFFF88011A2DE2C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 335.23
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 335.23
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA Corporation).
Google query: NVIDIA Corporation VIDEO_TDR_ERROR
On Sun 11.05.2014 08:20:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051114-10077-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646373)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001646373)
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 11.05.2014 07:27:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051114-10171-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646373)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001646373)
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 Fri 09.05.2014 06:38:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050914-10202-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001662B82)
Bugcheck code: 0xD1 (0x2A, 0x2, 0x0, 0xFFFFF88001662B82)
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.
Conclusion
22 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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:
e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 335.23 , NVIDIA 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.