Bonjour,
 
lorsque j'active le SLI (2x gtx 580) + surround, je peux jouer pendant quelques heures puis le pc plante, et ça n'a pas l'air d'être lié au jeu lui même ça le fait avec plusieurs.
Donc j'ai essayé de mettre à jour les drivers mais sans succès, du coup là j'ai une version moddée mais c'est pas mieux.  
 
Mais je suis quasiment sûr que ça vient du surround vu que sans, ça ne plante pas.  
De plus j'ai un peu de mal à croire que mes cartes sont défectueuses vu que depuis que je les aie je n'aie jamais eut de problème (~3 ans) sauf depuis que je m'amuse avec le surround (~3 mois).
 
Voila ce que me donne WhoCrashed suivi du dump file:
computer name: LUC4S-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., Maximus IV Extreme-Z
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12777029632 total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Thu 10.09.2015 21:56:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091115-42401-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880085CA3EC)  
Bugcheck code: 0x50 (0xFFFFFB240B1B0300, 0x0, 0xFFFFF880085CA3EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
 
 
On Thu 10.09.2015 21:56:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xEF3EC)  
Bugcheck code: 0x50 (0xFFFFFB240B1B0300, 0x0, 0xFFFFF880085CA3EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
 
 
On Thu 10.09.2015 11:45:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091015-44990-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880085E13EC)  
Bugcheck code: 0x50 (0xFFFFFB240B584300, 0x0, 0xFFFFF880085E13EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
 
 
On Fri 14.08.2015 17:10:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081415-46815-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8800851A3EC)  
Bugcheck code: 0x50 (0xFFFFFB240B510300, 0x0, 0xFFFFF8800851A3EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
 
 
On Tue 21.07.2015 18:05:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072115-32916-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF880085D23EC)  
Bugcheck code: 0x50 (0xFFFFFB240B59C300, 0x0, 0xFFFFF880085D23EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
 
 
On Tue 21.07.2015 13:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072115-38875-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF88005AF23EC)  
Bugcheck code: 0x50 (0xFFFFFB240A7EC300, 0x0, 0xFFFFF88005AF23EC, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 353.38  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 353.38  
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.  
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 353.38 , NVIDIA Corporation).  
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
 
=========================================================================
 
 
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654
Machine Name:
Kernel base = 0xfffff800`0385a000 PsLoadedModuleList = 0xfffff800`03a9f890
Debug session time: Thu Sep 10 23:56:35.617 2015 (UTC + 2:00)
System Uptime: 0 days 10:10:31.507
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
 
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {fffffb240b1b0300, 0, fffff880085ca3ec, 7}
 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvlddmkm.sys -  
Probably caused by : nvlddmkm.sys ( nvlddmkm+ef3ec )
 
Followup: MachineOwner
---------
 
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffb240b1b0300, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880085ca3ec, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  fffffb240b1b0300 Nonpaged pool
 
FAULTING_IP:  
nvlddmkm+ef3ec
fffff880`085ca3ec 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h]
 
MM_INTERNAL_CODE:  7
 
IMAGE_NAME:  nvlddmkm.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  558aa204
 
MODULE_NAME: nvlddmkm
 
FAULTING_MODULE: fffff880084db000 nvlddmkm
 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
TRAP_FRAME:  fffff880081ab2f0 -- (.trap 0xfffff880081ab2f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=000000a3ffffff5c
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff880085ca3ec rsp=fffff880081ab480 rbp=fffff880081ab4f0
 r8=fffffa800b1ae000  r9=0000000000000008 r10=0000000000000000
r11=fffff880081ab038 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nvlddmkm+0xef3ec:
fffff880`085ca3ec 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h] ds:fffffb24`0b1b0300=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80003947552 to fffff800038cca40
 
STACK_TEXT:  
fffff880`081ab188 fffff800`03947552 : 00000000`00000050 fffffb24`0b1b0300 00000000`00000000 fffff880`081ab2f0 : nt!KeBugCheckEx
fffff880`081ab190 fffff800`038cab6e : 00000000`00000000 fffffb24`0b1b0300 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40221
fffff880`081ab2f0 fffff880`085ca3ec : 00000000`000126c8 fffffa80`0b56e000 fffffa80`0c13b000 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`081ab480 fffff880`085ca868 : 00000000`00000000 fffff8a0`17f0b5ed 00000000`00000000 00000000`00093e31 : nvlddmkm+0xef3ec
fffff880`081ab4c0 fffff880`085cb309 : 00000000`00000000 fffff8a0`17f0b5bd 00000000`00000007 fffff880`081ac3f9 : nvlddmkm+0xef868
fffff880`081ac360 fffff880`085cbbdc : fffff8a0`00000001 00000000`00000117 00000000`00000018 00000000`000a64f9 : nvlddmkm+0xf0309
fffff880`081ac460 fffff880`085c9fd4 : fffffa80`00000117 fffffa80`0b56e000 00000000`000ace89 fffff8a0`17ef2595 : nvlddmkm+0xf0bdc
fffff880`081ac4c0 fffff880`085489d8 : fffffa80`0b56e000 00000000`00000000 fffff880`081ac610 fffff880`081ac610 : nvlddmkm+0xeefd4
fffff880`081ac500 fffff880`07aa30e0 : fffff880`08548953 fffff8a0`166ffff0 fffff880`081ac610 fffffa80`0c6b2000 : nvlddmkm+0x6d9d8
fffff880`081ac590 fffff880`07ac9bd5 : fffff8a0`17c02480 fffff8a0`166ffff0 fffff8a0`17e9f422 fffffa80`11d0a4e0 : dxgkrnl!DXGADAPTER::DdiCollectDbgInfo+0x50
fffff880`081ac5c0 fffff880`07acae16 : fffffa80`11d0a4e0 fffffa80`11d0a4e0 fffffa80`10eed7e0 fffffa80`0c691410 : dxgkrnl!TdrCollectDbgInfoStage1+0x359
fffff880`081ac660 fffff880`07b72f13 : fffffa80`11d0a4e0 00000000`00000000 fffffa80`10eed7e0 fffffa80`0c691410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`081ac690 fffff880`07ba0ed6 : 00000000`ffffffff 00000000`0023d3fb fffff880`081ac7f0 fffffa80`0c691410 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`081ac770 fffff880`07b9ce21 : fffffa80`0c6ca000 ffffffff`feced300 fffffa80`0eb87760 fffff880`07b819d3 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`081ac7b0 fffff880`07b9cfd9 : fffffa80`0c6ca000 fffffa80`0c691410 fffffa80`0c6cb400 00000000`00000000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
fffff880`081ac8a0 fffff880`07b9beb8 : 00000000`0000001b 00000000`009e75ac fffffa80`0eb87760 fffffa80`0c691410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
fffff880`081ac9a0 fffff880`07b9b514 : fffff800`00b94000 fffff880`07b9af00 fffffa80`00000000 fffffa80`00000004 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`081acb90 fffff880`07b9b012 : 00000000`00000000 fffffa80`113d6010 00000000`00000080 fffffa80`0c691410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`081acbc0 fffff800`03b66aba : 00000000`047891f5 fffffa80`0c66f060 fffffa80`09cbe890 fffffa80`0c66f060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`081acc00 fffff800`038be426 : fffff800`03a4ce80 fffffa80`0c66f060 fffff800`03a5acc0 fffffa80`0abb17e0 : nt!PspSystemThreadStartup+0x5a
fffff880`081acc40 00000000`00000000 : fffff880`081ad000 fffff880`081a7000 fffff880`081abbe0 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP:  
nvlddmkm+ef3ec
fffff880`085ca3ec 428b8401a4230000 mov     eax,dword ptr [rcx+r8+23A4h]
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  nvlddmkm+ef3ec
 
FOLLOWUP_NAME:  MachineOwner
 
FAILURE_BUCKET_ID:  X64_0x50_nvlddmkm+ef3ec
 
BUCKET_ID:  X64_0x50_nvlddmkm+ef3ec
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:x64_0x50_nvlddmkm+ef3ec
 
FAILURE_ID_HASH:  {b61e4b98-95e2-b422-a5aa-f34ee39bebea}
 
Followup: MachineOwner
---------

As tu formaté depuis ? Quelle est la résolution de l'écran créé par NVidia ? Le surround crée un écran virtuel qu'il splitte en trois, est ce que la résolution correspond à la résolution totale de tes écrans ? As tu un antialisaing d'activé (certains AA calculent une image plus grande pour ensuite la réduire) ?
 
Et sous un windows plus "moderne" ? Je pense au 10, as tu essayé ? Tu peux toujours revenir par la suite vers le 7 pendant 30 jours je crois.

Ouais j'ai formaté mais ça n'a rien changé.
 
Pour ce qui est de la résolution, avec la correction des bordures je suis à 6060x1080, et 5760x1080 sans la correction (crash dans les deux cas) ce qui correspond bien à la résolution totale.
 
Par contre j'ai pas fait gaffe à l'antialiasing, je vais essayer sans.
 
Et je n'ai pas essayé windows 10 mais j'ai entendu dire que ça causait des problèmes avec directx, ou je ne sais quoi qui empêche pas mal de jeux de fonctionner mais pourquoi pas essayer.

Qu'as-tu comme alim? elle donne peut-être des signes de faiblesse en grosse charge.

 
C'est vrai qu'on n'a pas les specs de ton PC.

Peut être mais comment je vérifie? j'ai une cooler master silent pro gold 1000W
 
EDIT
 
ma config:
ASUS maximus iv extreme-z
12go ram DDR3-1600
2x ASUS gtx 580 (direct-cu II)
SDD OCZ revodrive 3 x2 240go
1to hdd (oublié le modèle)
intel i7 2600k
 
 

Tu arrives quand même à jouer quelques heures dessus avant le plantage. Quelle est la température de tes CG à peu près au moment du plantage ? Si tu pousses les ventilo ça donne quoi ?

j'ai un watercooling donc niveau temp ça va ^^

Tes cartes sont OC ? Parce que là il essaie de lire un truc en mémoire et n'y arrive pas.

Pas que je sache, et elles ne sont pas oc d'usine il me semble.

Et si tu élèves la tension un tout petit peu sans augmenter la fréquence genre avec asus gpu tweak ? 10 mV c'est pas méchant surtout avec du WC.

Ok je vais essayer, aussi peut être changer le bridge sli j'en ai en rab des fois que...