query96 0 Napisano 26 Lipca 2018 Udostępnij Napisano 26 Lipca 2018 Witam. Kupiłem komputer niecałe 2 miesiące temu. Jakoś 2 tygodnie zaczęły się pojawiać dziwne zwiechy. Z początku nieszkodliwe, bo nie trwały nawet sekundy. Zawsze słychać przy tym charakterystyczny dźwięk. Teraz pojawiają się coraz częściej i czasem nawet na kilka sekund. Nie mam pojęcia, czym może być to spowodowane. Komputer zakupiony z nowych części. Używam systemu win10. Oto specyfikacja: Asrock z370 pro4 Intel i5-8400 Gigabyte gtx 1060 windforce 6gb 16 Gb ram crucial ballistix sport 2666mhz silentiumpc 500w vero l2 bronze hdd toshida p300 1tb ssd goodram irdm pro 240gb chłodzenie spartan 3 Proszę o pomoc w rozwiązaniu mojego problemu. Cytuj Link to post Share on other sites
vicodin 479 Napisano 26 Lipca 2018 Udostępnij Napisano 26 Lipca 2018 Sterowniki zaktualizowane, problem nasila się pod większym obciążeniem pc? Pobierz program http://www.resplendence.com/latencymon Kliknij zieloną strzałkę w tym programie, używaj komputer przez chwilę niech wystąpią te zawieszenia następnie zatrzymujesz monitorowanie czerwonym kwadratem i wrzucasz na forum foty poszczególnych kart z programu. 1 Cytuj Link to post Share on other sites
query96 0 Napisano 27 Lipca 2018 Autor Udostępnij Napisano 27 Lipca 2018 (edytowane) Ok. Jak wrócę do domu wieczorem, to tak zrobię. Zrobiłem 2 testy tym programikiem. Tutaj link do zdjęć z panelu głównego https://imgur.com/a/Zyn4ju5 A tutaj detale: 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 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:00:15 (h:mm:ss) on all processors._________________________________________________________________________________________________________SYSTEM INFORMATION_________________________________________________________________________________________________________Computer name: DESKTOP-N8IS4SLOS version: Windows 10 , 10.0, build: 17134 (x64)Hardware: ASRock, Z370 Pro4CPU: GenuineIntel Intel® Core i5-8400 CPU @ 2.80GHzLogical processors: 6Processor groups: 1RAM: 16319 MB total_________________________________________________________________________________________________________CPU SPEED_________________________________________________________________________________________________________Reported CPU speed: 2808 MHzNote: 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._________________________________________________________________________________________________________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): 139944,088443Average measured interrupt to process latency (µs): 7,204598Highest measured interrupt to DPC latency (µs): 139902,151129Average measured interrupt to DPC latency (µs): 5,020847_________________________________________________________________________________________________________ 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): 74,479701Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft CorporationHighest reported total ISR routine time (%): 0,305881Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft CorporationTotal time spent in ISRs (%) 0,319399ISR count (execution time <250 µs): 23788ISR count (execution time 250-500 µs): 0ISR count (execution time 500-999 µs): 0ISR count (execution time 1000-1999 µs): 0ISR count (execution time 2000-3999 µs): 0ISR 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): 139900,325499Driver with highest DPC routine execution time: ndis.sys - Specyfikacja NDIS (Network Driver Interface Specification), Microsoft CorporationHighest reported total DPC routine time (%): 0,168372Driver with highest DPC total execution time: ndis.sys - Specyfikacja NDIS (Network Driver Interface Specification), Microsoft CorporationTotal time spent in DPCs (%) 0,486719DPC count (execution time <250 µs): 74938DPC count (execution time 250-500 µs): 0DPC count (execution time 500-999 µs): 22DPC count (execution time 1000-1999 µs): 0DPC count (execution time 2000-3999 µs): 0DPC 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: firefox.exeTotal number of hard pagefaults 73Hard pagefault count of hardest hit process: 63Number of processes hit: 3_________________________________________________________________________________________________________ PER CPU DATA_________________________________________________________________________________________________________CPU 0 Interrupt cycle time (s): 0,926357CPU 0 ISR highest execution time (µs): 74,479701CPU 0 ISR total execution time (s): 0,286266CPU 0 ISR count: 23098CPU 0 DPC highest execution time (µs): 139900,325499CPU 0 DPC total execution time (s): 0,399140CPU 0 DPC count: 69480_________________________________________________________________________________________________________CPU 1 Interrupt cycle time (s): 0,279257CPU 1 ISR highest execution time (µs): 4,704060CPU 1 ISR total execution time (s): 0,001193CPU 1 ISR count: 690CPU 1 DPC highest execution time (µs): 46,534544CPU 1 DPC total execution time (s): 0,028257CPU 1 DPC count: 3352_________________________________________________________________________________________________________CPU 2 Interrupt cycle time (s): 0,284986CPU 2 ISR highest execution time (µs): 0,0CPU 2 ISR total execution time (s): 0,0CPU 2 ISR count: 0CPU 2 DPC highest execution time (µs): 60,424501CPU 2 DPC total execution time (s): 0,001654CPU 2 DPC count: 397_________________________________________________________________________________________________________CPU 3 Interrupt cycle time (s): 0,280149CPU 3 ISR highest execution time (µs): 0,0CPU 3 ISR total execution time (s): 0,0CPU 3 ISR count: 0CPU 3 DPC highest execution time (µs): 45,793803CPU 3 DPC total execution time (s): 0,003378CPU 3 DPC count: 693_________________________________________________________________________________________________________CPU 4 Interrupt cycle time (s): 0,197985CPU 4 ISR highest execution time (µs): 0,0CPU 4 ISR total execution time (s): 0,0CPU 4 ISR count: 0CPU 4 DPC highest execution time (µs): 48,434473CPU 4 DPC total execution time (s): 0,002843CPU 4 DPC count: 545_________________________________________________________________________________________________________CPU 5 Interrupt cycle time (s): 0,190367CPU 5 ISR highest execution time (µs): 0,0CPU 5 ISR total execution time (s): 0,0CPU 5 ISR count: 0CPU 5 DPC highest execution time (µs): 40,626425CPU 5 DPC total execution time (s): 0,002775CPU 5 DPC count: 494 UPDATE: Problem rozwiązany. Odinstalowałem Norton Antywirusa i chyba wszystko wróciło do normy. Póki co ani jednej zwiechy i programik pokazuje, że wszystko jest w porządku. Edytowane 27 Lipca 2018 przez query96 Cytuj Link to post Share on other sites
Rozwiązanie vicodin 479 Napisano 27 Lipca 2018 Rozwiązanie Udostępnij Napisano 27 Lipca 2018 Program wskazywał na problemy z siecią. Antywirus lub jego zapora mogła być przyczyną. 1 Cytuj Link to post Share on other sites
Recommended Posts
Dołącz do dyskusji
Możesz dodać zawartość już teraz a zarejestrować się później. Jeśli posiadasz już konto, zaloguj się aby dodać zawartość za jego pomocą.