Multiple screen bleu SB NB CHAUFF :x

nsk86

Elite
bonjour à tous ,

je reouvre un post au sujet de mes screen bleu :x

j ai tout esseyé rien n y fais.. tjs des screen bleu dé que j utilise quelque chose qui utilise les perfs de la config :x

je remarque surtout que ca crash une fois la temp du sb et nb atteignant 42 degrer

en idle ils sont à 38 degrer et en burn à 42 ca crash :x

sur le net je remarque que bcp de personne ont se soucis avec win7 x64

j ai mis à jour le bios, win 7, ethernet + update win7 du ethernet

pilote x64 pour la carte son inexistant pour le moment..

config :

i7 950
rampage extrem II
4go ddr3 1600 ocz platinium
3hdd en raid 0 raptor
GTX 260
antec true power quatro 850 w


HHHEEELLPPPPPPPP !!!!!!!! :beuh:

voici les rapports :

On Sat 20/11/2010 15:39:36 your computer crashed
This was likely caused by the following module: cmudax3.sys
Bugcheck code: 0:cool:1 (0xFFFFFA80275B5378, 0x2, 0x0, 0xFFFFF8800489A240)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\112010-23478-01.dmp
file path: C:\Windows\system32\drivers\cmudax3.sys
product: C-Media Audio Driver (WDM)
company: C-Media Inc
description: C-Media Audio WDM Driver



On Sat 20/11/2010 15:31:11 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008A37878, 0xFFFFF88008A370E0, 0xFFFFF880016B9085)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\112010-22854-01.dmp
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
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 20/11/2010 15:26:31 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800B6646B8, 0xFFFFF8800B663F20, 0xFFFFF8000286548D)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\112010-23930-01.dmp
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
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 20/11/2010 02:01:57 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFF880083FCB00, 0x1, 0xFFFFF800028BD749, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\112010-19219-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 19/11/2010 21:37:58 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8001481250, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\111910-19656-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 19/11/2010 20:39:55 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800494F3A8, 0xFFFFF8800A072950, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\111910-22557-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 19/11/2010 19:40:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x31, 0xFFFFFA8007668CE0, 0xFFFFF8800C9A2000, 0xFFFFF8A00B2B556B)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\111910-28111-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 18/11/2010 20:05:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000286FA38, 0xFFFFF880080BDA70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\111810-19718-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 15/11/2010 03:39:50 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88005A01D10, 0xFFFFF8800A5A3EE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\111510-21652-01.dmp



On Thu 11/11/2010 20:05:01 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002870C17)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\111110-18798-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 11/11/2010 14:43:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0:cool:E (0x2, 0xFFFFF8A0025E29A8, 0xFFFFF8A0025DC199, 0x8C9D08C0)
Error: POOL_CORRUPTION_IN_FILE_AREA
Dump file: C:\Windows\Minidump\111110-29234-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 10/11/2010 22:58:51 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0:cool:1 (0x1170, 0x2, 0x0, 0xFFFFF88004676B74)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\111010-29530-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
 

Akabane

The Chemical Stig
T'as essayé de réinstaller avec un autre disque de windows ?
 
1er
OP
nsk86

nsk86

Elite
non .. tu pensse que ca peux venir de là ?
 

kingsteph

Touriste
J'ai plus ou moins la même config que vous, 2 velociraptor et gtx 285 6g ram alim 650w bequiet, I920.

Moi j'essayerai avec une autre alim.

Bonne chance.
@+
 

Akabane

The Chemical Stig
Je pense que ça vaut la peine d'essayer. Et tenter de mettre une autre alim également.
 

Fist

‼️‼️‼️‼️‼️
Format tout .. Reinstalle W7 avec une ram... une fois l installation terminé tu remets la 2 eme ram ..

Enfin c ce que je ferais ..Les conseilleurs sont pas les payeurs :)
 
1er
OP
nsk86

nsk86

Elite
qui ne tente rien n q rien je test le formatage avec un new win 7 sur 1 seul barette puis si ca va tjs pas je test new alim
 

leval

Gnagnagna
le probleme c'est que tu as une MB Asus :cool:


test un memtest tout con
 

Demoniak_Angel

Le + beau ;-)
Ouaip, les cm Asus c'est plus ce que c'était :-(
 

kingsteph

Touriste
Moi perso jamais eux de soucis avec de l'asus, ni gigabyte...
 
1er
OP
nsk86

nsk86

Elite
Je pensse avoir trouvé le problème

ALLELLOOUUYYAAAAAAA !!!!! :proud:


mis à jour du bios ( une nouvelle version est sortie il y a quelque jours ) pour les new cpu.

partage de l alimentation sur le RAID ( les 3 hdd etaient connecté sur une seul NAPPE de 3 SATA ) maintenant ils sont connecté sur 2 NAPPE

Rapport OCCT et HDWARE ( 1er fois que le pc résiste à un occt dans le boitier )






Hardware monitor Intel Core i7 950
Power 0 40.72 W (Processor)
Temperature 0 39°C (102°F) [0x3D] (Core #0)
Temperature 1 33°C (91°F) [0x43] (Core #1)
Temperature 2 39°C (102°F) [0x3D] (Core #2)
Temperature 3 34°C (93°F) [0x42] (Core #3)

Hardware monitor NVIDIA GeForce GTX 260
Temperature 0 47°C (116°F) (GPU Core)

Hardware monitor Asus IROG 01
Voltage 0 0.94 Volts [0x3AB] (CPU)
Voltage 1 1.65 Volts [0x676] (DRAM)
Voltage 2 1.11 Volts [0x457] (ICH Core)
Voltage 3 1.51 Volts [0x5E4] (ICH PCIE +1.5V)
Voltage 4 1.81 Volts [0x714] (CPU PLL)
Voltage 5 1.51 Volts [0x5E4] (IOH Core)
Voltage 6 1.13 Volts [0x46B] (IOH PCIE +1.5V)
Voltage 7 1.18 Volts [0x4A0] (QPI)

Hardware monitor Winbond W83627DHG
Voltage 0 0.95 Volts [0x77] (VIN0)
Voltage 1 12.55 Volts [0xE1] (+12V)
Voltage 2 3.33 Volts [0:cool:0] (AVCC)
Voltage 3 3.30 Volts [0xCE] (+3.3V)
Voltage 4 5.38 Volts [0xE0] (+5V)
Temperature 0 32°C (89°F) [0x20] (SYSTIN)
Temperature 1 36°C (96°F) [0x48] (CPUTIN)
Temperature 2 8°C (45°F) [0x1F1] (AUXTIN)
Fan 1 1223 RPM [0x45] (CPUFANIN0)
 
le rais 0 des raptor c la 1er chose éliminé comme facteur de panner .

Ton cpu il monte a combien sur le graphe 96 ° ?

Ps: vérifie que le fan présant sur le chipset fonctionne .
 
1er
OP
nsk86

nsk86

Elite
lol non max 60 degrer ce que tu vois c est 96 Farenheit

tout les Fan sont niquel.

Test de plusieur heures sous FSX en max = 0 Bug
je peux enfin jouer au jeux pour lequel j ai monter cet config à plein régime, la qualitée texture et réalisme me laisse sur le Ass :p


merci pour vos réponsse

Système stable et opérationnel on peux cloturer :)
 
Haut