Problème écran bleu

Merci pour ton intervention.

Voici le rapport :



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: E5410-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: Latitude E5410, Dell Inc., 03VXMC
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3680346112 total



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 24/06/2015 18:37:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062415-17316-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x459FF)
Bugcheck code: 0xD1 (0x10, 0x2, 0x8, 0x10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


On Wed 24/06/2015 18:37:55 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xD1 (0x10, 0x2, 0x8, 0x10)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: ntkrpamp.exe .
Google query: ntkrpamp.exe DRIVER_IRQL_NOT_LESS_OR_EQUAL


On Wed 24/06/2015 18:36:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062415-21091-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x8BD38)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E9459B, 0xFFFFFFFF9B583BD4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Mon 25/05/2015 21:32:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052515-20670-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x37DE)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF825237DE, 0xFFFFFFFFACB91BE8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
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.
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 07/04/2015 18:58:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040715-19266-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0xB768)
Bugcheck code: 0x50 (0xFFFFFFFFFFB805DC, 0x0, 0xFFFFFFFF822BB768, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
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 05/04/2015 08:52:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040515-27081-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFFFFF82EBC602)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


On Tue 10/03/2015 19:30:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031015-18330-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x78CEE)
Bugcheck code: 0xD1 (0xE14, 0x2, 0x0, 0xFFFFFFFF8C4FCCEE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote NDIS 6.20
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 Mon 16/02/2015 23:14:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021715-20311-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBE011)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF820CE011, 0xFFFFFFFFAD507B98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 01/02/2015 08:20:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020115-19843-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFFFFF82EB3602)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


On Thu 01/01/2015 21:54:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010115-20810-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1BE77)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF82EAC155)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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
--------------------------------------------------------------------------------

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:

ntkrpamp.exe

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 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.

Concernant les points d'exclamation, j'en ai concernant deux périphériques bluetooth et un périphérique inconnu.

Les mises à jour de Windows 7 service pack 1 ne réussissent pas à s'installer.

Mon PC est un Dell Latitude E5410 avec Windows 7 pro, processeur intel core i5 cpu M560 2.67 GHz, mémoire 4 Go, système d'exploitation 32 bits.

Pour le périphérique inconnu, le n° d'identification est SMO8800.
Pour le périphérique bluetooth 1, c'est BTHENUM\{0000110b-0000-1000-8000-00805f9b34fb}_LOCALMFG&000f
Pour le périphérique bluetooth 2, c'est BTHENUM\{0000110e-0000-1000-8000-00805f9b34fb}_LOCALMFG&000f.

Quand j'essaie d'installer les mises à jour de Windows 7, j'obtiens ce message : "Certaines mises à jour n'ont pas été installées. Code 80073712 : Windows Update a rencontré une erreur inconnue."

Apparemment, il semblerait que l'installation ait marché.

L'ordinateur a encore planté.

On Sat 27/06/2015 07:55:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062715-17893-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBE011)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8210E011, 0xFFFFFFFF9C54FB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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.
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 Sat 27/06/2015 07:55:36 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8210E011, 0xFFFFFFFF9C54FB98, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED


J'ai également fait une recherche de mise à jour pour le périphérique bluetooth 1 mais ça n'a rien donné.

Alors non, ça n'a pas fonctionné. Dans le panneau de configuration, c'est indiqué
"/!\ installez des mises à jour pour votre ordinateur" et dans Propriétés, l'édition de Windows n'indique pas Service Pack 1.

Via Windows Update, ça ne fonctionne pas.

Je ne sais pas. Quand je referai une mise à jour, je te dirai ce que ça affiche.

Depuis hier soir, mon câble d'alimentation ne fonctionne plus. D'habitude, quand il est branché sur le secteur, une lumière bleue s'allume. Ici, rien. Et ce matin, pour couronner le tout, mon pc a refait un écran bleu. C'est la fête...

J'ai racheté un nouveau câble et la batterie se charge.
J'ai trouvé où on peut avoir le code d'erreur. Les tentatives de mise à jour du 28 et du 29 juin ont pour code d'erreur 80073712.

Voici le rapport de WhoCrashed pour l'écran bleu de ce matin :

On Tue 30/06/2015 06:59:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-20139-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x459FF)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFFFFF82E6CA62)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Tue 30/06/2015 06:59:41 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x5B3AE)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFFFFF82E6CA62)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus
company: AVAST Software
description: avast! self protection module
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.
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: aswsp.sys (avast! self protection module, AVAST Software).
Google query: AVAST Software IRQL_NOT_LESS_OR_EQUAL