Selaimet hidastelevat ja muutakin tahmaamista

Viestiketju alueella 'Ongelmat' , aloittaja morpheus76, 31.12.2019.

NOSTOJA MUROPAKETIN SISÄLLÖSTÄ
  1. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Ongelma alkoi yhtäkkiä. Kaikki selaimet (firefox ensimmäisenä ja pahiten, chrome, opera) alkoivat hidastella. Hidastelu esiintyy aina, kun alkaa tekemään jotain (klikkaa linkkiä, avaa uuden ikkunan jne.). Kun jonkin asian saa alkuun, toimii se normaalilla nopeudella, esim. speedtest antaa normaalit lukemat. Ongelma myös pahenee koko ajan. Eräs paljon verkkoa käyttävä peli ei meinaa käynnistyä ollenkaan, kun taas toinen vain vähän verkkoa käyttävä peli toimii normaalisti. Välillä yhteys palvelimeen katkeaa kesken pelin. Konetta sammuttaessa jokin ohjelma ei meinaa sammua (ei kerro mikä). Koneen käynnistysruutu (salasana/kirjautuminen) on alkanut hidastelemaan ja windowsin käynnistyttyä tulee firefoxin "palautus ei onnistunut" -ilmoitus ja tuohon peliin liittyvä (....read only...) ilmoitus. Resurssienhallinta näyttää useita (8-17) firefoxin/operan prosesseja olevan käynnissä ja tehoja kuluvan prossulta useita prosentteja vaikkei mitään tekisikään ja virrankäytön olevan melko suuri firefoxin kohdalla.

    Tähän asti kokeiltu:
    - Etsitty syytä windowsin päivityksistä. Viimeisen päivitys oli 2 viikkoa sitten ja ongelma alkoi muutama päivä sitten. Ei selitä ongelmaa?
    -Refresh suoritettu firefoxille. Auttoi n. minuutiksi... Rajoitin prosesseja neljään ja laitoin laitteistokiihdytyksen pois, mutta silti niitä tulee enemmän.
    -ipconfig /flushdns, nbtstat -RR, netsh int ip reset, netsh winsock reset tehty, ei apua selaimiin, ainakin yhden käynnistyksen antoi ilman virheilmoituksia.

    Käytössä win10 v1909 18363.535

    Mikä avuksi? Voisiko joku auttaa?
     
  2. E.T

    Rekisteröitynyt:
    09.10.2000
    Viestejä:
    11 187
  3. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    _________________________________________________________________________________________________________
    CONCLUSION
    _________________________________________________________________________________________________________
    Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
    LatencyMon has been analyzing your system for 0:00:16 (h:mm:ss) on all processors.


    _________________________________________________________________________________________________________
    SYSTEM INFORMATION
    _________________________________________________________________________________________________________
    Computer name: DESKTOP-M3TULHA
    OS version: Windows 10 , 10.0, build: 18363 (x64)
    Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING EDGE AC (MS-7B17)
    CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Logical processors: 6
    Processor groups: 1
    RAM: 16319 MB total


    _________________________________________________________________________________________________________
    CPU SPEED
    _________________________________________________________________________________________________________
    Reported CPU speed: 3696 MHz

    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): 429,80
    Average measured interrupt to process latency (µs): 8,585440

    Highest measured interrupt to DPC latency (µs): 170,40
    Average measured interrupt to DPC latency (µs): 2,353457


    _________________________________________________________________________________________________________
    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): 139,187229
    Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

    Total time spent in ISRs (%) 0,001285

    ISR count (execution time <250 µs): 101
    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): 75,948593
    Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

    Highest reported total DPC routine time (%): 0,000926
    Driver with highest DPC total execution time: Wdf01000.sys - Suorituksenaikainen ydintilaohjainkehys, Microsoft Corporation

    Total time spent in DPCs (%) 0,001775

    DPC count (execution time <250 µs): 324
    DPC count (execution time 250-500 µs): 0
    DPC count (execution time 500-999 µs): 0
    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.

    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: avira.systemspeedup.realtimeoptimizer.exe

    Total number of hard pagefaults 113
    Hard pagefault count of hardest hit process: 104
    Number of processes hit: 5


    _________________________________________________________________________________________________________
    PER CPU DATA
    _________________________________________________________________________________________________________
    CPU 0 Interrupt cycle time (s): 0,63580
    CPU 0 ISR highest execution time (µs): 139,187229
    CPU 0 ISR total execution time (s): 0,001234
    CPU 0 ISR count: 101
    CPU 0 DPC highest execution time (µs): 75,948593
    CPU 0 DPC total execution time (s): 0,001605
    CPU 0 DPC count: 291
    _________________________________________________________________________________________________________
    CPU 1 Interrupt cycle time (s): 0,481272
    CPU 1 ISR highest execution time (µs): 0,0
    CPU 1 ISR total execution time (s): 0,0
    CPU 1 ISR count: 0
    CPU 1 DPC highest execution time (µs): 5,606602
    CPU 1 DPC total execution time (s): 0,000022
    CPU 1 DPC count: 12
    _________________________________________________________________________________________________________
    CPU 2 Interrupt cycle time (s): 0,279665
    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): 6,025433
    CPU 2 DPC total execution time (s): 0,000022
    CPU 2 DPC count: 6
    _________________________________________________________________________________________________________
    CPU 3 Interrupt cycle time (s): 0,237518
    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): 6,611472
    CPU 3 DPC total execution time (s): 0,000012
    CPU 3 DPC count: 3
    _________________________________________________________________________________________________________
    CPU 4 Interrupt cycle time (s): 0,194217
    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): 5,172619
    CPU 4 DPC total execution time (s): 0,000010
    CPU 4 DPC count: 3
    _________________________________________________________________________________________________________
    CPU 5 Interrupt cycle time (s): 0,216514
    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): 7,43290
    CPU 5 DPC total execution time (s): 0,000034
    CPU 5 DPC count: 9
    _________________________________________________________________________________________________________
     
  4. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Testi kesti vain 16 sekuntia. Laitoin pari nettisivua latautumaan ja tein testin uudelleen eri tuloksin:
    _________________________________________________________________________________________________________
    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 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:00:16 (h:mm:ss) on all processors.


    _________________________________________________________________________________________________________
    SYSTEM INFORMATION
    _________________________________________________________________________________________________________
    Computer name: DESKTOP-M3TULHA
    OS version: Windows 10 , 10.0, build: 18363 (x64)
    Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING EDGE AC (MS-7B17)
    CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Logical processors: 6
    Processor groups: 1
    RAM: 16319 MB total


    _________________________________________________________________________________________________________
    CPU SPEED
    _________________________________________________________________________________________________________
    Reported CPU speed: 3696 MHz

    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): 1307,0
    Average measured interrupt to process latency (µs): 6,551361

    Highest measured interrupt to DPC latency (µs): 170,60
    Average measured interrupt to DPC latency (µs): 1,791291


    _________________________________________________________________________________________________________
    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): 141,098485
    Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

    Total time spent in ISRs (%) 0,000972

    ISR count (execution time <250 µs): 57
    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): 77,266234
    Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

    Total time spent in DPCs (%) 0,000811

    DPC count (execution time <250 µs): 234
    DPC count (execution time 250-500 µs): 0
    DPC count (execution time 500-999 µs): 0
    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
    Number of processes hit: 0


    _________________________________________________________________________________________________________
    PER CPU DATA
    _________________________________________________________________________________________________________
    CPU 0 Interrupt cycle time (s): 0,775559
    CPU 0 ISR highest execution time (µs): 141,098485
    CPU 0 ISR total execution time (s): 0,000933
    CPU 0 ISR count: 57
    CPU 0 DPC highest execution time (µs): 77,266234
    CPU 0 DPC total execution time (s): 0,000698
    CPU 0 DPC count: 207
    _________________________________________________________________________________________________________
    CPU 1 Interrupt cycle time (s): 0,442382
    CPU 1 ISR highest execution time (µs): 0,0
    CPU 1 ISR total execution time (s): 0,0
    CPU 1 ISR count: 0
    CPU 1 DPC highest execution time (µs): 3,525974
    CPU 1 DPC total execution time (s): 0,000010
    CPU 1 DPC count: 5
    _________________________________________________________________________________________________________
    CPU 2 Interrupt cycle time (s): 0,297245
    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): 6,914502
    CPU 2 DPC total execution time (s): 0,000028
    CPU 2 DPC count: 6
    _________________________________________________________________________________________________________
    CPU 3 Interrupt cycle time (s): 0,264030
    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): 3,898810
    CPU 3 DPC total execution time (s): 0,000015
    CPU 3 DPC count: 9
    _________________________________________________________________________________________________________
    CPU 4 Interrupt cycle time (s): 0,186365
    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): 5,462662
    CPU 4 DPC total execution time (s): 0,000014
    CPU 4 DPC count: 4
    _________________________________________________________________________________________________________
    CPU 5 Interrupt cycle time (s): 0,198204
    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): 8,386905
    CPU 5 DPC total execution time (s): 0,000014
    CPU 5 DPC count: 3
    _________________________________________________________________________________________________________
     
  5. E.T

    Rekisteröitynyt:
    09.10.2000
    Viestejä:
    11 187
    Monitoroinnin on oltava päällä sen aikaa että ongelmaa esiintyy.
    DPC-latenssissa ei ainakaan tuossa ajassa ollut ongelmia.
    Ja jos DPC-latenssiongelmaa esiintyy, aiheuttajasta vihjaavat tiedot ovat tuon tekstiseinän sijaan Drivers-tabilla.
     
  6. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Löysin täpän mistä sai testin jatkumaan pidempään. 6 minuutin testin jälkeen sain mittarit menemään punaiselle, kun avasin 2 selainta ja yritin avata peliä (yritykseksi jäi).
    _________________________________________________________________________________________________________
    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:06:05 (h:mm:ss) on all processors.


    _________________________________________________________________________________________________________
    SYSTEM INFORMATION
    _________________________________________________________________________________________________________
    Computer name: DESKTOP-M3TULHA
    OS version: Windows 10 , 10.0, build: 18363 (x64)
    Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING EDGE AC (MS-7B17)
    CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz
    Logical processors: 6
    Processor groups: 1
    RAM: 16319 MB total


    _________________________________________________________________________________________________________
    CPU SPEED
    _________________________________________________________________________________________________________
    Reported CPU speed: 3696 MHz

    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): 10290,60
    Average measured interrupt to process latency (µs): 5,317428

    Highest measured interrupt to DPC latency (µs): 622,50
    Average measured interrupt to DPC latency (µs): 1,369457


    _________________________________________________________________________________________________________
    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): 135,553571
    Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

    Total time spent in ISRs (%) 0,000037

    ISR count (execution time <250 µs): 53
    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): 74,386364
    Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

    Total time spent in DPCs (%) 0,000028

    DPC count (execution time <250 µs): 207
    DPC count (execution time 250-500 µs): 0
    DPC count (execution time 500-999 µs): 0
    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.

    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: adawareservice.exe

    Total number of hard pagefaults 2
    Hard pagefault count of hardest hit process: 2
    Number of processes hit: 1


    _________________________________________________________________________________________________________
    PER CPU DATA
    _________________________________________________________________________________________________________
    CPU 0 Interrupt cycle time (s): 17,706608
    CPU 0 ISR highest execution time (µs): 135,553571
    CPU 0 ISR total execution time (s): 0,000803
    CPU 0 ISR count: 53
    CPU 0 DPC highest execution time (µs): 74,386364
    CPU 0 DPC total execution time (s): 0,000546
    CPU 0 DPC count: 188
    _________________________________________________________________________________________________________
    CPU 1 Interrupt cycle time (s): 10,888953
    CPU 1 ISR highest execution time (µs): 0,0
    CPU 1 ISR total execution time (s): 0,0
    CPU 1 ISR count: 0
    CPU 1 DPC highest execution time (µs): 3,454004
    CPU 1 DPC total execution time (s): 0,000016
    CPU 1 DPC count: 8
    _________________________________________________________________________________________________________
    CPU 2 Interrupt cycle time (s): 8,441993
    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): 4,750541
    CPU 2 DPC total execution time (s): 0,000009
    CPU 2 DPC count: 2
    _________________________________________________________________________________________________________
    CPU 3 Interrupt cycle time (s): 8,391325
    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): 4,766775
    CPU 3 DPC total execution time (s): 0,000024
    CPU 3 DPC count: 7
    _________________________________________________________________________________________________________
    CPU 4 Interrupt cycle time (s): 7,937287
    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): 8,291667
    CPU 4 DPC total execution time (s): 0,000009
    CPU 4 DPC count: 2
    _________________________________________________________________________________________________________
    CPU 5 Interrupt cycle time (s): 7,883056
    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): 0,0
    CPU 5 DPC total execution time (s): 0,0
    CPU 5 DPC count: 0
    _________________________________________________________________________________________________________

    [​IMG]
     
  7. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Jos olen ehtinyt käyttää selaimia, ei se peli käynnisty ollenkaan, vaan kone pitää käynnistää uudelleen. Ja nyt hidastelua on jo sisäänkirjautumisessakin.
     
  8. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Intel wireless and bluetooth päivitetty. Poistin firefoxin. Verkkoresetöity.

    netsh int ip reset tehdessä ”resetting resolve neighbour ok, ok...resetting failed. Käyttö estetty.”
     
  9. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Latencymonin listan kärjessä oli directx graphics kernel, nvidia windows kernel, hd audio bus, nt kernel&system, ms storage port... grafiikkaan liittyviä juttuja? Kokeilin päivittää nvidian ajurit. Geforce experiencen kautta asennus sekoilee. Joku oli saanut saman tyyppiseen ongelmaan apua poistamalla nvidia physx:n ja audio driverin, joten poistin ne. Ei apua. Jotkut suosittelevat cpu throttlingin ja muiden virtajuttujen ottamista pois päältä, en ole vielä kokeillut.
    BIOSia en ole koskaan päivittänyt, etten vain sotke koko konetta...
    Saako joku selvää tuosta raportista?
     
  10. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Uusimpien geforce-ajureiden asennus onnistui. Jätin pois physx:n ja audion. Latenssit pysyivät sen jälkeen kurissa. Pelasin peliä, joka nopeasti meni kunnolla jumiin. Jouduin uudelleen käynnistämään koneen ja taas oli latenssit korkealla. Vanhempien ajureiden asentamisessa en näe ideaa, koska koneessa on ollut vain yhdet ajurit ennen tätä päivitystä. Windowsin clean boot kuulosti myös riskaabelilta. Nvidian ohjauspaneelista laitoin virransäästötilaan ”suosii parasta suorituskykyä”, koska ,tätä suositeltiin uudessa lähteessä. Monet, joilla on latenssiongelmaa puhuvat äänen pätkimisestä (mihin tuo LM on kai alunperin suunniteltu), mutta sitä ongelmaa ei vielä ole.

    Olisiko jollain ideoita? Tai vinkkiä, mistä muualta voisi kysyä apua?
     
  11. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Poistin näytönohjaimen tilapäisesti käytöstä laitehallinnan kautta ja latency laski heti. Jonkin verran hitautta esiintyi vielä. Tällä kertaa listan kärjessä on wdf0100.sys (ajureihin liittyvä juttu) ja hdaudbus.sys. Mielestäni poistin nvidia audion, mutta intel driver and support assistantin mielestä minulla on se.

    Nyt kai alkaa jumppa ajureiden poistamisen ja uudelleen asentamisen kanssa.
     
  12. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    DDU:lla poistin vikasietotilassa näyttiksen ajurit ja myös intelin sekä ääniajurit. Ensin asensin pelkästään näyttiksen ajurin ilman mitään physx tai gfexperienceä. Ei auttanut. Tahmaaminen vaan pahenee vaikka nyt kyllä latency laski. Kone lähes käyttökelvoton. Ja en saa ääniä toimimaan :(
     
  13. Sport_FIN

    Rekisteröitynyt:
    11.12.2015
    Viestejä:
    2 469
    Testaa muistit ja onko kiintolevy kunnossa? Mikä versio on prossusta (R0 vai P0?)
     
  14. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Päädyin vetämään koko koneen sileäksi. Jonkin aikaa meni hyvin, mutta nyt ongelma palasi. Ei heti minkään asentamisen jälkeen, vaan pikkuhiljaa ja vähän eri tavalla. DirectX taas latencymonin kärjessä. En asentanut mitään näyttiksen ajureita, ainoastaan sen, minkä windows itse haki.
    Yksi peli, minkä olin ostanut windows storen kautta ei suostu asentumaan, koska windows versio on liian vanha nyt (17763). Yritin asentaa sen päivityksen, mutta tulee bsod (memory management) ja toosa palaa takaisin vanhaan.
     
  15. morpheus76

    Rekisteröitynyt:
    19.09.2004
    Viestejä:
    158
    Ajoin windowsin muistin diagnostiikan ja sen mukaan ei ole muistiongelmia. Tapahtumienvalvonnassa oli kuitenkin useita kertoja sama virhe; ”distributedCOM”.

    Miten tarkistan prossun version? En tiedä mitä nuo lyhenteet tarkoittavat.
     

Jaa tämä sivu

Alibi
Anna
Deko
Dome
Erä
Hymy
Kaksplus
Kippari
Kotilääkäri
Kotiliesi
Koululainen
Ruoka.fi
Parnasso
Seura
Suomen Kuvalehti
TM Rakennusmaailma
Tekniikan Maailma
Vauhdin Maailma
Golfpiste
Vene
Nettiauto
Ampparit
Plaza
Muropaketti