Bonjour à tous,  
 
1er message et premier topic sur votre forum d'entraide, et j’espère que tout ce passera bien
 
Je vous écrit, car depuis quelques temps, je dirais après avoir réinstaller complètement Windows 7 64 bits avec le choix au niveau du bios de mettre le disque dur en AHCI et non pas en IDE comme il l'était auparavant, je remarque que mon pc fixe, tour montée par un informaticien de ma région (descriptif plus bas), à tendance à planté et à me sortir des BSOD et autres redémarrages intempestifs quand bon lui semble.
 
Au niveau alimentation je suis sur un alim Thermaltake 80+ TR2 800W et sur un onduleur Riello AROS UPS idialog 1200 VA. Le profil au niveau de windows est réglé sur performances élevées au lieu de Normales, car je pensais que ça allait régler mes problèmes ....
Que nini !
 
Les vacances de noël étant là, nouvelle installation comme je l'ai dis vers le 15 décembre, et je recommence à installer Skyrim et autres jeux avec Steam.
Skyrim impeccable, configuration automatique en Ultra élevé, pas de blocage en jouant ni redémarrage.
J'installe le seigneur des anneaux la Guerre du Nord, et là ... BOUM BSOD au lancement !
Problème : la version de mon bios doit être mise a jour pour inclure cette compatibilité (après conseil sur forum Steam)
Mise à jour du bios : les jeux qui ,ne marchaient pas fonctionnent mais les ennuis commencent, où plus précisément s'intensifient.
 
-Tout d'abord impossibilité d'utiliser le service Ma config, pour mettre à jour mes pilotes, BSOD : BAD POOL HEADER au différents stades de détection.
- Parfois, il arrive que la souris laggue, l'image se fige, plus rien n'est opérant, et le pc redémarre tout seul si pas d'écran bleu ou redémarrage forcé avec écran bleu et dump sur le disque
- A la suite de ce redémarrage, le bios et windows ont vu qu'ils n'avaient pas été arrêtés correctement, sans solutions
- Par contre pas de Wifi (Clé wifi) au redémarrage, obligé de redémarrer manuellement et tout rentre dans l'ordre.
 
Je m'en remet à vous, en espérant trouver solutions.
Au niveau antivirus rien à signaler, et je peux vous fournir en cas de besoin un rapport whocrashed.  
 
Config : windows version: Windows 7 Service Pack 1, 6.1, build: 7601
 
Hardware: GA-880GM-USB3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 8570572800 total
 
Système    
--------------------------------------------------------------------------------
 
  Fabricant Gigabyte Technology Co., Ltd.  
  Modèle GA-880GM-USB3  
  Quantité totale de mémoire système Mémoire vive 8,00 Go  
  Type du système Système d’exploitation 64 bits  
  Nombre de cœurs de processeur 6  
 
Stockage    
--------------------------------------------------------------------------------
 
  Taille totale des disques durs 931 Go  
  Partition de disque (C 816 Go libre (931 Go au total)  
  Lecteur multimédia (D CD/DVD  
 
Carte graphique    
--------------------------------------------------------------------------------
 
  Afficher le type de carte NVIDIA GeForce GTX 560  
  Mémoire graphique totale disponible 4095 Mo  
        Mémoire graphique dédiée 1024 Mo  
        Mémoire système dédiée 0 Mo  
        Mémoire système partagée 3071 Mo  
  Afficher la version du pilote de la carte 9.18.13.3182  
  Résolution du moniteur principal 1920x1080  
  Version DirectX DirectX 10  
 
Réseau    
--------------------------------------------------------------------------------
 
  Carte réseau Realtek PCIe GBE Family Controller  
  Carte réseau Belkin Wireless Adapter  
 
 
 

je vous rajoute l'analyse Whocrashed :
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Sun 05/01/2014 11:58:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-30919-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007A64420, 0xFFFFFA8007A644A0, 0xC080005)
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 that cannot be identified at this time.  
 
 
 
On Sun 05/01/2014 11:58:06 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0x3438)  
Bugcheck code: 0x19 (0x20, 0xFFFFFA8007A64420, 0xFFFFFA8007A644A0, 0xC080005)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
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.  
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc).  
Google query: Etron Technology Inc BAD_POOL_HEADER
 
 
 
On Sun 05/01/2014 10:58:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-28267-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007969678, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 05/01/2014 09:04:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-30342-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA80079608F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 05/01/2014 08:56:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-30544-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA800796F038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Fri 03/01/2014 22:16:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010414-28953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008D16E50, 0xFFFFFA8008D16ED0, 0xC08000C)
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 that cannot be identified at this time.  
 
 
 
On Fri 03/01/2014 16:30:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010314-39780-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008447AC0, 0xFFFFFA8008447B40, 0xC080004)
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 that cannot be identified at this time.  
 
 
 
On Mon 30/12/2013 20:32:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123013-31200-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x90608C)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880139C808C, 0xFFFFF880061A7DA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 331.82  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 331.82  
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.  
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation).  
Google query: NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
 
 
 
On Mon 30/12/2013 20:17:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123013-32869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)  
Bugcheck code: 0x19 (0x20, 0xFFFFFA8008274A00, 0xFFFFFA8008274A80, 0xC080005)
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 that cannot be identified at this time.  
 
 
 
On Mon 30/12/2013 19:49:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123013-29406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADB3C)  
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007977038, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).  
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
17 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:  
 
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 331.82 , NVIDIA Corporation)
etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc)
 
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.

Hello,
 
- Windows sain et officiel?
- Drivers à jour depuis le site des fabriquant? (un de tes BSOD est un soucis avec le driver de ta cg Nvidia)
 
Le 90% des BSOD sont des soucis de drivers...
 
Bon courage...

Driver carte graphique à jour, Windows officiel (DVD officiel) , sain c'est à dire ?
Pour les pilotes pourquoi le service ma config ne fonctionne pas ?
 
Cordialement
 

N'y a t-il pas de solutions à mon problème ?