Ecran Bleu intempestif..

Bonjour,

Depuis 1 an j'ai des BSOD qui n'arrêtent pas de survenir, plus souvent lorsque je joue à un jeu (ou après avoir joué, ou encore plus rarement lorsque je ne fais rien à part surfer sur le net..). Avant Juillet 2013, j'avais Windows Vista. Pensant que le problème venait de l'OS, j'ai changé vers Windows 8, hélas le problème persistait. Le problème ne venait donc pas de l'OS.

J'ai essayé alors de nettoyer et dépoussiérer mon ordi (ordinateur fixe, je précise) ainsi que d'interchanger les barrettes RAM. Rien n'a changé..
J'ai mis à jour quelques pilotes, j'ai eu quelque problème (notamment avec DriverMax que je n'ai plus utilisé) auquel j'ai du faire une restauration du système (ecran noir qui clignote après l'écran de boot) ... Je ne sais pas si ça vient de la MàJ foiré à cause de DriverMax (Ati Radeon) ou la Màj du Intel Chipset Device Software (que je n'ai pas mis à jour après la restauration du système..)

Voici ma configuration :

Système d'exploitation :Windows 8 Professionnel ?(X64)?
Date d'installation: 18/07/2013

-

Processeur :Intel Core 2 Quad Q8400 Cadencé à 2.67 GHz
Nombre de coeurs: 4 physique(s), 4 logique(s)
Socket: Socket 775 LGA

-

Carte mère :ASUSTeK Computer INC. P5Q SE2 Rev X.0x
Numéro de série (carte mère): MT709BK03104466
SKU Number: To Be Filled By O.E.M.
Version du bios: 0801
Date: 31/03/2010

-

Chipset :Pont nord : Intel P45/P43/G45/G43
Identifiant de révision: A3
Pont sud : Intel 82801JR (ICH10R)
Identifiant de révision: 00

-

Mémoire :4 Go de mémoire totale de type DDR2
Timings mémoire: 6.0 clocks-6 clocks-6 clocks-18 clocks-2 TT
Barrette OCZ de 2 Go
Fréquence maximale: 400 MHz
Bande passante: PC2-6400
Barrette OCZ de 2 Go
Fréquence maximale: 400 MHz
Bande passante: PC2-6400

-

Carte Graphique :Radeon HD 5850 : Version DirectX installée: 11.0

-

Disque dur :Disque dur ST3500418AS de 465.76 Go SATA II
Firmware: CC38
Version du SATA: SATA Rev 2.6
Numéro de série: 9VMA4ZF2
Température HDD: 32 °C
Temps de fonctionnement: 8703 heures

-

Lecteurs optiques

LITE-ON COMBO LTC-48161H
Type: DVD-ROM Recorder
Version du firmware: KQHC

-

Réseau

Carte virtuelle directe Wi-Fi Microsoft
Type d'adaptateur: IEEE 802.11 wireless
D-Link System DWA-125 Wireless N 150 Adapter(rev.A2) [Ralink RT3070] (11n Adapter)
Type d'adaptateur: IEEE 802.11 wireless
Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Type d'adaptateur: ethernet
Software Loopback Interface 1
Type d'adaptateur: Loopback

-

Cartes multimedia

Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
Advanced Micro Devices, Inc. [AMD/ATI] Cypress HDMI Audio [Radeon HD 5800 Series]

-

Clavier

DRAC 5 Virtual Keyboard and Mouse SK-8125 Keyboard (Dell USB Keyboard Hub)

-

Souris

Logitech, Inc. M-UAS144 [LS1 Laser Mouse] (USB Laser Mouse)

-

Ecran(s)

HP 2159
Fabricant: Hewlett Packard
Resolution maximum: 1920 x 1080
Taille de l'écran: 21.7" (48 cm x 27 cm)
Date de fabrication: 15/04/2009
Ratio d'aspect: 16:9
Type d'entrée vidéo: Digital Signal

-

Périphérique USB

Microsoft Corp. LifeCam VX-6000 (SN9C20x + OV9650) (USB20 Camera )
Version USB supportée: 2.0
D-Link System DWA-125 Wireless N 150 Adapter(rev.A2) [Ralink RT3070] (11n Adapter)
Version USB supportée: 2.0
Logitech, Inc. M-UAS144 [LS1 Laser Mouse] (USB Laser Mouse)
Version USB supportée: 2.0
DRAC 5 Virtual Keyboard and Mouse SK-8125 Keyboard (Dell USB Keyboard Hub)
Version USB supportée: 1.10
_________________________________________________
J'ai utilisé WhoCrashed et voici les dernier rapports :

On Sat 07-09-13 09:21:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090713-18142-01.dmp
This was probably caused by the following module: nsiproxy.sys (0xFFFFF8800372583A)
Bugcheck code: 0x50 (0xFFFFF880265897F0, 0x1, 0xFFFFF8800372583A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\nsiproxy.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NSI Proxy
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 Sat 07-09-13 09:21:18 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nsiproxy.sys (nsiproxy+0x283A)
Bugcheck code: 0x50 (0xFFFFF880265897F0, 0x1, 0xFFFFF8800372583A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\nsiproxy.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NSI Proxy
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 Wed 04-09-13 19:20:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090413-14383-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xB4D1)
Bugcheck code: 0xD1 (0x12, 0xA, 0x1, 0xFFFFF88005E354D1)
Error: DRIVER_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 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 Tue 03-09-13 18:58:53 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090313-15022-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF88000B35DBE)
Bugcheck code: 0x50 (0xFFFFFA80616BDEFD, 0x0, 0xFFFFF88000B35DBE, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 Tue 03-09-13 15:49:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090313-16333-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF880061A03BE)
Bugcheck code: 0xD1 (0xFFFFFA7FC5810211, 0x2, 0x0, 0xFFFFF880061A03BE)
Error: DRIVER_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 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.
______________________________________________

Désolé du pavé mais ces BSOD m'empêchent vraiment de profiter de mon ordi. En pleine partie d'un Multijoueur avec des amis, je me fais régulièrement interrompre par cette saloperie de Crash.. Le pire c'est que je ne sais pas d'où ça vient et quoi faire..

-

Edit : Pour ceux qui se demanderait si j'ai utilisé MEMTEST (pour tester la RAM), non je ne l'ai pas encore utilisé car j'hésite au vu du temps que ça mets, et je doute que ça va repérer un problème..

-

Je vous remercie d'avoir lu, et d'avance pour vos réponses.