(résolu) crash système: bluescreen
Posté : lun. 20 août 2012 09:08
Bonjour,
je suis confronté à un problème récurant de bluescreen qui semble être lié avec ma carte réseau qui me crash le système régulièrement.
Dans le bluescreen j'ai repéré que cpdudrv64.sys est toujours indiqué. Quand je fais un test sur la page Identifier et rechercher automatiquement les pilotes
de l'utilitaire de intel, le système crash systématiquement. http://www.intel.com/p/fr_FR/support/detect
J'ai pu tout de même installer ma dernière version de ma carte réseau.
Après de nombreuses recherche et ne parvenant pas à trouver de solutions,
je fais appel à la communauté windows !
En vous remerciant.
(J'ai eu un problème similaire il y a quelques temps que j'avais posté
mais je ne pense pas qu'il s'agisse du même bug.)
-> topic12601.html
Liste matériel:
Voici le résultat avec WhoCrashed
je suis confronté à un problème récurant de bluescreen qui semble être lié avec ma carte réseau qui me crash le système régulièrement.
Dans le bluescreen j'ai repéré que cpdudrv64.sys est toujours indiqué. Quand je fais un test sur la page Identifier et rechercher automatiquement les pilotes
de l'utilitaire de intel, le système crash systématiquement. http://www.intel.com/p/fr_FR/support/detect
J'ai pu tout de même installer ma dernière version de ma carte réseau.
Après de nombreuses recherche et ne parvenant pas à trouver de solutions,
je fais appel à la communauté windows !
En vous remerciant.
(J'ai eu un problème similaire il y a quelques temps que j'avais posté
mais je ne pense pas qu'il s'agisse du même bug.)
-> topic12601.html
Liste matériel:
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
Voici le résultat avec WhoCrashed
System Information (local)
computer name: SEVEN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X6 1090T Processor AMD586, level: 16
6 logical processors, active mask: 63
RAM: 12882989056 total
VM: 2147352576, free: 1953312768
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 17.08.2012 11:00:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-26301-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88006F8E912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 11:00:16 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88006F8E912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 10:51:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-21496-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800688E912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 10:18:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-22651-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007A7D912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 10:11:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-22573-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007BDA912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 10:05:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-21621-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800AD6B912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 09:44:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-28735-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88007E9F912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 09:21:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-27690-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF8800A6F3912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 09:16:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-26988-01.dmp
This was probably caused by the following module: cpudrv64.sys (cpudrv64+0x1912)
Bugcheck code: 0x1E (0xFFFFFFFFC0000096, 0xFFFFF88008001912, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: cpudrv64.sys .
Google query: cpudrv64.sys KMODE_EXCEPTION_NOT_HANDLED
On Fri 17.08.2012 08:45:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-26395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800172CD24)
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 Fri 17.08.2012 06:16:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081712-21886-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF8800166CB1F)
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 Thu 16.08.2012 06:01:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081612-23244-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001691D24)
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 Tue 14.08.2012 14:49:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081412-22401-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001694B1F)
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 Tue 17.07.2012 08:41:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071712-33509-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x18ED3)
Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8801107AED3)
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 Sun 15.07.2012 11:14:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-22183-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8800166ED24)
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
19 crash dumps have been found and analyzed. Only 15 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)
cpudrv64.sys
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.
J'ai fait un test avec ma-config.com et voici ce qu'il me propose :
Cartes réseaux
Intel Corporation 82583V Gigabit Network Connection
Intel PRO/100/1000/10GbE
Date du fichier INF 10/07/2012
Version du pilote 17.2 WHQL
Télécharger
Détails du pilote proposé
Détails du pilote détecté
Nom du pilote
PRO/100/1000/10GbE
Intel(R) 82583V Gigabit Network Connection
Fabricant
Intel
Intel
Version
12.1.77.0
11.4.7.0
Nom du fichier INF
e1q6332.inf
oem9.inf
Date du fichier INF
10/07/2012
04/12/2009
Date de mise en ligne
13/08/2012 11:24:06
****
Classe
net
net
Identifiant matériel