Bonjour !
 
Je vous expose mon problème, suite au changement de ma carte 3d (j'avais une HD4870), pour passer à une GTX 560 Ti DC II (Asus), j'ai eu 4 écrans bleu en étant sur windows ! Je ne sais pas si c'est dû à cette nouvelle carte, mais avant je n'avais jamais eu ça... Ces écrans arrivent uniquement lorsque je suis sous windows et lorsque je fais presque rien... Quand je joue à SC2 ou autre, jamais de problème (même en 2h de jeux...).
 
Dans le problème il note ceci, je sais pas si ça aide^^ :  
 
"Signature du problème :
  Nom d’événement de problème: BlueScreen
  Version du système: 6.0.6002.2.2.0.768.3
  Identificateur de paramètres régionaux: 4108
Informations supplémentaires sur le problème :
  BCCode: c5
  BCP1: 00000005
  BCP2: 00000002
  BCP3: 00000001
  BCP4: 83D37010
  OS Version: 6_0_6002
  Service Pack: 2_0
  Product: 768_1
 
Fichiers aidant à décrire le problème :
  C:\Windows\Minidump\Mini043012-01.dmp
  C:\Users\Raphael\AppData\Local\Temp\WER-36831-0.sysdata.xml
  C:\Users\Raphael\AppData\Local\Temp\WER4C4B.tmp.version.txt"

 
Là j'ai mis pilote à jour etc... rien ne change !?
 
Est-ce un problème de sous-voltage? Faut-il une alimentation plus puissante ? (sachant qu'avec ma HD4870 no problème)
 
Merci d'avance pour toutes aides !
 
Ma config :  
 
voici ma config :  
 
Cases : ATX with power supply
Antec Sonata-III-EC / 500W, black
 
CPU Intel socket LGA 775 - Core 2 Duo
Core 2 Duo E8500 - 3.16
 
MB : Intel Socket LGA 775  
Asus P5Q
 
mem : DDR2-800/PC-6400
DDR2 2x2 GB DIMM Corsair Twin2X
 
GC : PCI express - AMD
HIS Radeon HD 4870 - 512 MB
 
HDD : 3.5'' - S-ATA II - Samsung
750GB SpinPoint F1
 
DVD- Writers Internal, S-ATA
 
Windows Vista Home Premium SP1, 32-Bit, fr.
 
PS: j'ai utiliser WHOCRASHED et j'ai eu ça comme indication :  
 
On Mon 30.04.2012 16:46:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043012-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x232C1)  
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF871C98E0, 0xFFFFFFFF871C98E8, 0x8010007)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).  
Google query: aswsp.sys AVAST Software BAD_POOL_HEADER
 

un mini up !

T'avais une ATI avant, t'as bien nettoyé tous les drivers avant d'installer ta nvidia?

yes j'ai tout viré sauf : AMD catalyst Install Manager, car je savais pas vu que j'ai un proco/CM à base AMD (donc plusieurs drivers avec ça...) !

une autre idée?

Pour moi on voit clairement que c'est avast qui fout la merde

ta mis a jour a quelle version du pilote?

 
C'est pas faux
 
T'as essayé en désinstallant avast ?

Mais je l'avais avant de changé de CG, et il n'y a eu que des mises à jour (base de données), et donc avant jamais eu ce problème !J'ai cru aussi que c'étais avast en lisant le rapport, mais je vois pourquoi/comment...

Bonsoir.  
Retirer les pilotes, c'est une chose mais ne jamais oublier de nettoyer le registre après." Les traces restent après le passage de l'escargot"...

Alors comment faire ? j'ai fait avec tuneup ?Dois-je utiliser autre chose ?

et AMD catalyst install Manager je peux le virer ?

?

prend les derniers drivers beta de nvidia les 300 j'ai eu des ecran bleu avec les 296

Okay je vais essayer merci

Dans l'ordre :
- Dégager AMD Catalyst Install Manager
- Dégager Avast
- Nettoyer le registre
- Mettre à jour les drivers
- Si rien n'a fonctionné : fresh install, ca fait toujours du bien

Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Thu 03.05.2012 13:41:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-03.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8D38)  
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF8310D82A)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).  
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
 
 
 
 
On Thu 03.05.2012 13:41:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x8D38)  
Bugcheck code: 0xC5 (0x0, 0x2, 0x1, 0xFFFFFFFF8310D82A)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
Bug check description: This indicates that the system attempted to access invalid 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. 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: aswsp.sys (avast! self protection module, AVAST Software).  
Google query: aswsp.sys AVAST Software DRIVER_CORRUPTED_EXPOOL
 
 
 
 
On Thu 03.05.2012 12:41:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4DFD9)  
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFFFFF83109EB9)
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 which cannot be identified at this time.  
 
 
On Wed 02.05.2012 23:40:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050312-01.dmp
This was probably caused by the following module: lnsfw1.sys (lnsfw1+0x9F91)  
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8080007, 0xFFFFFFFF87142910)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lnsfw1.sys
product: LNSFW1 Look 'n' Stop Driver
description: LNSFW1 LnS Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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: lnsfw1.sys (LNSFW1 LnS Driver, ).  
Google query: lnsfw1.sys BAD_POOL_CALLER
 
 
 
 
On Mon 30.04.2012 16:46:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043012-02.dmp
This was probably caused by the following module: aswsp.sys (aswSP+0x232C1)  
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF871C98E0, 0xFFFFFFFF871C98E8, 0x8010007)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\aswsp.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! self protection module
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: aswsp.sys (avast! self protection module, AVAST Software).  
Google query: aswsp.sys AVAST Software BAD_POOL_HEADER
 
 
 
 
On Mon 30.04.2012 08:41:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini043012-01.dmp
This was probably caused by the following module: lnsfw.sys (lnsfw+0x36C3)  
Bugcheck code: 0xC5 (0x5, 0x2, 0x1, 0xFFFFFFFF83D37010)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\lnsfw.sys
product: Look 'n' Stop Driver
description: Look 'n' Stop Driver
Bug check description: This indicates that the system attempted to access invalid 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. 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: lnsfw.sys (Look 'n' Stop Driver, ).  
Google query: lnsfw.sys DRIVER_CORRUPTED_EXPOOL
 
 
 
 
On Sat 28.04.2012 14:41:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042812-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xA2BEF)  
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF83E14D07, 0xFFFFFFFF80FE3C34, 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 which cannot be identified at this time.  
 
 
On Wed 25.04.2012 22:22:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042612-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x712F4)  
Bugcheck code: 0xC5 (0x1402FE, 0x2, 0x0, 0xFFFFFFFF83D37770)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that the system attempted to access invalid 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. 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 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 Sat 21.04.2012 20:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini042112-01.dmp
This was probably caused by the following module: aswfsblk.sys (aswFsBlk+0x1A66)  
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8C0FD7B2, 0xFFFFFFFFBF79086C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\aswfsblk.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! File System Access Blocking 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.  
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: aswfsblk.sys (avast! File System Access Blocking Driver, AVAST Software).  
Google query: aswfsblk.sys AVAST Software KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

Merci DARK. Je vais faire cela, mais si je vire Avast après plus d'antivirus ?!Je peux le réinstaller ensuite ou ?

 
Perso je préfère claquer 22€ dans un Kaspersky que de prendre un antivirus gratuit qui fout la merde
 
Depuis que j'ai fait ce choix, je n'ai plus jamais eu de problèmes !

Mais on est pas sûr que c'est ça qui bug : /, donc je veux bien 22 euro, même que si c'est assuré que c'est ça...

Ben désinstalle d'abord avast pour voir si c'est ça
 
Et évite tout comportement dangereux sur internet pendant ce temps là

L'antivirus de Micro$oft fera très bien l'affaire.
 
Sinon, je dirais que ces MSI overclockées ne tiennent souvent pas bien leur OC => repasse aux fréquences normales (823/2000)

ok, maintenant j'ai de nouveau des écran bleu mais dûe à :  
 
On Sun 06.05.2012 21:40:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050612-02.dmp
This was probably caused by the following module: lnsfw1.sys (lnsfw1+0x9F91)  
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8080005, 0xFFFFFFFF861B2D20)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lnsfw1.sys
product: LNSFW1 Look 'n' Stop Driver
description: LNSFW1 LnS Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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: lnsfw1.sys (LNSFW1 LnS Driver, ).  
Google query: lnsfw1.sys BAD_POOL_CALLER
 
 
 
 
On Sun 06.05.2012 21:40:59 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: lnsfw1.sys (lnsfw1+0x9F91)  
Bugcheck code: 0xC2 (0x7, 0x110B, 0x8080005, 0xFFFFFFFF861B2D20)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\lnsfw1.sys
product: LNSFW1 Look 'n' Stop Driver
description: LNSFW1 LnS Driver
Bug check description: This indicates that the current thread is making a bad pool request.
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: lnsfw1.sys (LNSFW1 LnS Driver, ).  
Google query: lnsfw1.sys BAD_POOL_CALLER
 
 
 
 
On Sun 06.05.2012 13:42:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini050612-01.dmp
This was probably caused by the following module: wlanuhn.sys (WLANUHN+0x145DD)  
Bugcheck code: 0xC5 (0x31447341, 0x2, 0x1, 0xFFFFFFFF831320F5)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\wlanuhn.sys
product: Driver for Atheros OTUS Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that the system attempted to access invalid 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. 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: wlanuhn.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).  
Google query: wlanuhn.sys Atheros Communications, Inc. DRIVER_CORRUPTED_EXPOOL
 
 
C'est vraiment étrange, je pense que ce programme m'indique n'importe quoi en fait, avez-vous un autre programme ?

 
Sinon Look'n'stop était une merveille d'instabilité quand je l'ai essayé il y a quelques années. Bien sûr, ils ont dû améliorer leur produit depuis, mais au vu des messages de crashdumps, je désinstallerais ce firewall et ses drivers associés.

Si c'est pour désinstaller 1 à 1 les logiciels que tu as autant repartir sur un Windows propre...

Bonjour
en effet, ça sent le windows qui part en vrille tout ça...

arf, donc plutôt un formatage en vue !ça doit faire 5 ans que j'ai pas fait ça ^^ !c'est toujours un problème, après il me manque des drivers, j'ai oublié de sauvegarder qqc.... Je crois que je vais essayer 1 par 1 .. !

Heu... non il vaux mieux réinstaller... aprés c'est comme tu le sens...
en même temps un windows qui à 5 ans...
 
bref bon courage si tu fais 1 par 1...

En plus j'ai accès à windows 7, (le 64 bit même), donc c'est presque mieux de le mettre ?ou je vais m'attirer encore plus de problème que now ?!

Au moins tes 4Go de RAM seront exploité...
 
aprés a toi de voir si tu as des logiciels qui ne seront plus compatible avec un Win 64...