Josmast Skrevet 5. mars 2018 Del Skrevet 5. mars 2018 jeg sliter med Mini stuttering (når jeg spiller spill så får jeg mini lagg, av og til litt mer enn mini lagg. (Spillene føles hakkete.) . Jeg lurer på om det kan være feil på hovedkortet mitt. Jeg har formatert og reinstallert Windows 10 3 ganger. Samme problem oppstår. Ingen ting har vært overklokket. GPU når ikke mer enn 63 Grader, CPU har vært oppi 70 grader på max. Så er lave og stabile Temperaturer. Jeg har prøvd og oppdatere biosen, testet flere Nvidia drivere, det gjør ingen forskjell. Noen som kan hjelpe så setter jeg stor pris på det Acer 27" Predator LED G-Sync XB271HUA Kingston Value DDR4 2400Mhz 16GB ASUS Prime Z270-P, Socket-1151 Corsair Force MP500 240GB M.2 PCIe SSD ASUS GeForce GTX 1070 ROG Strix Gaming Intel Core i7-7700K Kaby Lake Prosessor Noctua NH-U12S CPU KjølerCorsair HX850i Har en SSD på 128 GB og en HDD på 2 Tb Jeg har kjørt LatencyMon og får denne feilmeldingen: CONCLUSION _________________________________________________________________________________________________________ Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. 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:03:05 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: DESKTOP-KR306CK OS version: Windows 10 , 10.0, build: 16299 (x64) Hardware: ASUSTeK COMPUTER INC., PRIME Z270-P CPU: GenuineIntel Intel® Core i7-7700K CPU @ 4.20GHz Logical processors: 8 Processor groups: 1 RAM: 16329 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 420 MHz Measured CPU speed: 1 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): 3534,750045 Average measured interrupt to process latency (µs): 3,245698 Highest measured interrupt to DPC latency (µs): 3531,580522 Average measured interrupt to DPC latency (µs): 0,932026 _________________________________________________________________________________________________________ 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): 206,089524 Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total ISR routine time (%): 0,123987 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0,146977 ISR count (execution time <250 µs): 241060 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): 314,276190 Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 391.01 , NVIDIA Corporation Highest reported total DPC routine time (%): 0,078694 Driver with highest DPC total execution time: Wdf01000.sys - Driverrammeverk under kjøring i kjernemodus, Microsoft Corporation Total time spent in DPCs (%) 0,235165 DPC count (execution time <250 µs): 934229 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 11 DPC count (execution time 1000-1999 µs): 0 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. Process with highest pagefault count: none Total number of hard pagefaults 0 Hard pagefault count of hardest hit process: 0 Highest hard pagefault resolution time (µs): 0,0 Total time spent in hard pagefaults (%): 0,0 Number of processes hit: 0 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 9,515359 CPU 0 ISR highest execution time (µs): 193,986190 CPU 0 ISR total execution time (s): 2,123961 CPU 0 ISR count: 228473 CPU 0 DPC highest execution time (µs): 314,276190 CPU 0 DPC total execution time (s): 2,724850 CPU 0 DPC count: 814142 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 7,113579 CPU 1 ISR highest execution time (µs): 206,089524 CPU 1 ISR total execution time (s): 0,051845 CPU 1 ISR count: 12587 CPU 1 DPC highest execution time (µs): 285,447381 CPU 1 DPC total execution time (s): 0,331061 CPU 1 DPC count: 29716 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 5,163827 CPU 2 ISR highest execution time (µs): 0,0 CPU 2 ISR total execution time (s): 0,0 CPU 2 ISR count: 0 CPU 2 DPC highest execution time (µs): 195,777619 CPU 2 DPC total execution time (s): 0,113611 CPU 2 DPC count: 23756 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 7,216228 CPU 3 ISR highest execution time (µs): 0,0 CPU 3 ISR total execution time (s): 0,0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 164,697857 CPU 3 DPC total execution time (s): 0,036023 CPU 3 DPC count: 7472 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 4,812956 CPU 4 ISR highest execution time (µs): 0,0 CPU 4 ISR total execution time (s): 0,0 CPU 4 ISR count: 0 CPU 4 DPC highest execution time (µs): 224,859762 CPU 4 DPC total execution time (s): 0,106749 CPU 4 DPC count: 21945 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 6,887250 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): 152,360238 CPU 5 DPC total execution time (s): 0,039451 CPU 5 DPC count: 8875 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 4,039425 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): 179,077143 CPU 6 DPC total execution time (s): 0,098119 CPU 6 DPC count: 21701 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 6,035829 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): 149,486190 CPU 7 DPC total execution time (s): 0,031464 CPU 7 DPC count: 6633 _________________________________________________________________________________________________________ Lenke til kommentar
Syar-2003 Skrevet 7. mars 2018 Del Skrevet 7. mars 2018 Legg inn unpark. Fjern autparking på core 3/4 Enable bitsum high performace profil (power profile) Og test igjen. https://bitsum.com/parkcontrol/ Alt er jo tilrettelagt og defaulter for ECO idag. Sikker på at lagging ikke skyldes spilldata som loades fra minne/disker da ? Lenke til kommentar
Josmast Skrevet 7. mars 2018 Forfatter Del Skrevet 7. mars 2018 Legg inn unpark. Fjern autparking på core 3/4 Enable bitsum high performace profil (power profile) Og test igjen. https://bitsum.com/parkcontrol/ Alt er jo tilrettelagt og defaulter for ECO idag. Sikker på at lagging ikke skyldes spilldata som loades fra minne/disker da ? Takk for svar, skal teste det ut nå. Har lagt inn spillene på 3 forskjellige disker. SSD, SSD M.2 og HDD. Samme problem oppstår. Tror heller ikke det er minne siden jeg ikke bruker stort mer enn 7-8 GB av 16 GB når jeg spiller. Det rare er jo at alle spille har fungert helt topp i type 3-4 måneder. Plutselig kom den mini stutteringen Lenke til kommentar
Josmast Skrevet 7. mars 2018 Forfatter Del Skrevet 7. mars 2018 Dessverre hjalp ikke dette. Fortsatt mini spikes og LatencyMon fikk samme melding som sist. Lenke til kommentar
Fartlitter Skrevet 15. mars 2018 Del Skrevet 15. mars 2018 Var borti en maskin med samme problem(dog z370 kort) som hadde ram brikkene på a1 og a2, bytta til a2 og b2 så ordna det seg. Se i manualen om ram brikkene har best optimalisert plassering ivertfall Lenke til kommentar
Grubleruble124 Skrevet 20. mars 2018 Del Skrevet 20. mars 2018 Har du blitt klokere? Føler jeg har samme problem som deg. Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå