Asus Maximus VII Hero + Probleme Grafikkarte! Dringend!

Servus,

ich hab mir ein Maximus VII gegönnt. Nun habe ich mal eine frage da ich bei BF1 immer wieder ruckle habe und die mir nicht erklären kann.. Der Pc ist voller Power und vor dem BOARD wechsel war alles ok.

Ich änge mal ein Bildchen aus dem Handbuch an. Da ich mir nicht sicher bin ob der obere PCI E nich schneller ist als der untere und wenn der untere langsamer sein sollte gibt es da ne möglichkeit im UEFI das so zu schalten das ich die Graka unten lassen kann? Ich brauche den Platz für meinen Kühler.

Grafikkarte ist eine GTX 1080

GRAKA STECKT also auf Nummer 4


MFG BRANDY

Steht doch eh da, der untere hat maximal 8 lanes.
Sieht man hier auch am Bild, dass die Kontakte fehlen:
http://intl.rakuten-static.com/t/74a/eeb/5c5f/37be/40fe/7959/6e07/1116e4a2a5005056b7016d.jpg

nö, der obere ist der, den du verwenden solltest

die Grafikkarte gehört in den oberen PCIe X16 Slot, denn der läuft auch mit x16, der mittlere läuft halt mit X8

Die Differenz zwischen 8x und 16x beträgt etwa 1%. Gibt immer wieder Benchmarks. Glaube auf Techpowerup.com.

Naja vorher war die graka auf nem 16er um er es gab keine ruckler. Kann aber auch nicht umstellen oder bios?

Wenn du schon Probleme mit dem Kühler ansprichst, warum nennst du nicht das Model ?

Dark Rock pro be quit wenn die graka oben steckt passt er nicht mehr rein.

falsch rum hast du den Kühler aber nicht verbaut oder? der wird doch sicherlich keine zwei PCIe Slots zusätzlich überdecken.
du hast ja als Abstand sogar noch einen PCIe x1 slot über dem benötigten PCIe x16 Slot

der Kühler muss so verbaut werden

auf dem bild wäre sogar noch der obere PCIe x1 Slot frei

Wenn ich die graka auf Platz 2 stecke passt der kühler net rein. Deswegen hab ich sie auf Platz 4.

edit*
hier stand müll

kannst du mal bitte ein bild vom mainboard inkl. eingebauten kühler posten. danke.

laut google:

Mach ich morgen. Könnte das die Ursache sein mit den 16 langes für die ruckler? Mein ne 1080 sollte bei m bf4 nicht mal ultra nicht rucklen

Ruckler entstehen eher durch eine limitierende Komponente, z.B. deine CPU....
oder durch Temperaturprobleme selbiger.

Gerade BF1 braucht massig CPU-Power. V.a. in Verbindung mit einer GTX 1080.

hab nen i7 4790 hashwell da wren noch nie ruckler ich bau das neue board ein und zack ruckler :-D

Hast Du nach dem Boardwechsel Windows neu installiert? Das kann auch eine Ursache sein. Auch wenn Windows nach dem Boardwechsel gestartet ist. Optimal ist das nicht.

jipp habe ich gerade getestet ruckler hab ich imme rnoch das sestsame ist die sind nicht konsant sonder kommen immer wieder unerwartet

http://www.resplendence.com/latencymon

Lass mal das mitlaufen, evtl. findet mal Treiber/Programme die die Latenzen verursachen.

dann mal hier die screenshots



CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:02:43 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: BRANDY
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., MAXIMUS VII HERO
CPU: GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
Logical processors: 8
Processor groups: 1
RAM: 16326 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3598 MHz
Measured CPU speed: 19 MHz (approx.)

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1692,533548
Average measured interrupt to process latency (µs): 7,058488

Highest measured interrupt to DPC latency (µs): 1688,482754
Average measured interrupt to DPC latency (µs): 3,815914


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 218,079489
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,247212
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,309077

ISR count (execution time <250 µs): 288051
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 1371,823791
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 378.66 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,141205
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0,763555

DPC count (execution time <250 µs): 2306446
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 86
DPC count (execution time 1000-1999 µs): 5
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0


_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: searchprotocolhost.exe

Total number of hard pagefaults 981
Hard pagefault count of hardest hit process: 310
Highest hard pagefault resolution time (µs): 252357,700389
Total time spent in hard pagefaults (%): 0,300173
Number of processes hit: 26


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 13,322909
CPU 0 ISR highest execution time (µs): 218,079489
CPU 0 ISR total execution time (s): 3,375595
CPU 0 ISR count: 220346
CPU 0 DPC highest execution time (µs): 1371,823791
CPU 0 DPC total execution time (s): 7,279904
CPU 0 DPC count: 1289084
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3,906473
CPU 1 ISR highest execution time (µs): 121,097276
CPU 1 ISR total execution time (s): 0,601663
CPU 1 ISR count: 61549
CPU 1 DPC highest execution time (µs): 535,514175
CPU 1 DPC total execution time (s): 1,534461
CPU 1 DPC count: 127281
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,196379
CPU 2 ISR highest execution time (µs): 79,800167
CPU 2 ISR total execution time (s): 0,051962
CPU 2 ISR count: 5533
CPU 2 DPC highest execution time (µs): 598,563369
CPU 2 DPC total execution time (s): 0,505579
CPU 2 DPC count: 350575
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1,491201
CPU 3 ISR highest execution time (µs): 25,327404
CPU 3 ISR total execution time (s): 0,003362
CPU 3 ISR count: 601
CPU 3 DPC highest execution time (µs): 799,033074
CPU 3 DPC total execution time (s): 0,090424
CPU 3 DPC count: 63830
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,600087
CPU 4 ISR highest execution time (µs): 12,830461
CPU 4 ISR total execution time (s): 0,000104
CPU 4 ISR count: 22
CPU 4 DPC highest execution time (µs): 643,851028
CPU 4 DPC total execution time (s): 0,135748
CPU 4 DPC count: 132924
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1,614936
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 758,603947
CPU 5 DPC total execution time (s): 0,119770
CPU 5 DPC count: 101500
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,511369
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 869,589772
CPU 6 DPC total execution time (s): 0,134521
CPU 6 DPC count: 130495
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,629672
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 1099,359922
CPU 7 DPC total execution time (s): 0,162096
CPU 7 DPC count: 110848
_________________________________________________________________________________________________________

Wahrscheinlich ist einfach der Dienst "Windows Search" bzw. der Indexdienst dran schuld.