Bonjour
Je viens de terminer le montage d'un nouveau PC:
config Gaming de Hardware.fr d'avant la dernière mouture ç.à.d.:
Boitier NZXT source 210 Elite noir
Alim Corsair CX500 v2
Carte mère MSI P67A-C43 (B3)
Processeur Intel I3 2100
CG HD6870 1G D5
Mémoire 2* GSKILL RIP JA F3 12800CL9D 4GBXL
Disque dur Seagate Barracuda 3.5 1000 go 64 MO 72 st 31000524AS
Graveur dvd SH 222 AB/BEBE Samsung.
Aprés installation de Windows 7 plusieurs écrans bleus aux démarrages suivis de restaurations.
Deux autres réinstallations de Windows 7 avec les mêmes problèmes ...mises à jour de Windows trés difficiles car suivis de plantages au démarrage et restaurations laborieuses.
Comme la config est à priori connue,y a-t-il des témoignages similaires et des soupçons quand aux origines de la panne?
J'ai installé le logiciel Whocrashed qui m'a donné ceci pour les derniers crash:
Welcome to WhoCrashed (HOME EDITION) v 3.04
System Information (local)
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4264935424 total
VM: 2147352576, free: 1950220288
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 29/03/2012 05:49:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032912-18236-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88000F3547C)
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 29/03/2012 05:49:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x247C)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88000F3547C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\acpi.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote ACPI pour NT
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 which cannot be identified at this time.
On Fri 23/03/2012 20:46:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032412-13696-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x19 (0x20, 0xFFFFFA8005189150, 0xFFFFFA8005189190, 0x4040015)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Conclusion
3 crash dumps have been found and analyzed.
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.