[ Cpt737 @ 27.12.2015. 06:20 ] @
Pozdrav, bio bih jako zahvalan ako bi neko mogao da mi pomogne da resim ovaj problem. Naime, ima vec nekoliko meseci a mozda i duze otkako se ovaj problem pojavio. Ceo kompjuter je postao dosta sporiji, cesto pokrenuti programi odu u not responding i tako "hanguju" po 5-10 sec, a audio distorzije i pad FPS-a se desavaju cak i pri gledanju snimaka/slusanju muzike, na svakih 10-15 sekundi. Prvo sam mislio da je do drajvera, pa brisao, instalirao nove, pokusavao svasta kako bih resio, ali bez ikakvog uspeha. Nakon toga sam se odlucio da oborim ceo sistem(Windows 7 Ultimate x86), ali ni nakon toga problem nije nestao, pa sam pretpostavio da je rec o nekom hardveru koji otkazuje. Prvo na sta sam pomislio je napajanje, pa sam ga skoro i zamenio ali ni to nije resilo problem. Trenutna finansijska situacija mi ne dozvoljava bas da idem tako i na lutriju kupujem komponentu po komponentu kako bih resio problem, pa sam se odlucio da pisem ovde... Mozda ce neko od vas koji se razumete znati da lokalizuje problem... Graficka kartica i CPU se u zadnjih mesec dana malo vise greju, medjutim, graficku sam resio tako sto sam zamenio termalnu pastu(nisam imao dovoljno paste i za CPU, to cu uskoro odraditi takodje). Ali ne verujem da je grejanje uzrok jer se problem pojavio dosta pre nego sto su ove dve komponente pocele da se greju malo vise. Pre par dana sam otkrio softver "LatencyMonitor" koji prijavljuje velik latency, ali ja kao laik ne umem da utvrdim o cemu je rec... Kao "highest measured interrupt to process latency" prijavljuje 2 stvari: 1. ataport.SYS - ATAPI Driver Extension, Microsoft Corporation(uglavnom) 2. dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation(ponekad) Ovako to izgleda: _________________________________________________________________________________________________________ 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:05:01 (h:mm:ss) on all processors. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name: VIPER-PC OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x86) Hardware: P31-DS3L, Gigabyte Technology Co., Ltd. CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz Logical processors: 2 Processor groups: 1 RAM: 2046 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed: 2533 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. _________________________________________________________________________________________________________ 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): 30190.170995 Average measured interrupt to process latency (µs): 3.659736 Highest measured interrupt to DPC latency (µs): 940.992343 Average measured interrupt to DPC latency (µs): 0.865124 _________________________________________________________________________________________________________ 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): 215.495855 Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation Highest reported total ISR routine time (%): 0.395249 Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Total time spent in ISRs (%) 0.549662 ISR count (execution time <250 µs): 364500 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): 1065.316226 Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation Highest reported total DPC routine time (%): 0.230176 Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation Total time spent in DPCs (%) 0.820961 DPC count (execution time <250 µs): 1909842 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-999 µs): 8 DPC count (execution time 1000-1999 µs): 1 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: svchost.exe Total number of hard pagefaults 602 Hard pagefault count of hardest hit process: 403 Highest hard pagefault resolution time (µs): 510515.482037 Total time spent in hard pagefaults (%): 2.723768 Number of processes hit: 21 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 8.007715 CPU 0 ISR highest execution time (µs): 211.891828 CPU 0 ISR total execution time (s): 1.654301 CPU 0 ISR count: 182075 CPU 0 DPC highest execution time (µs): 975.090801 CPU 0 DPC total execution time (s): 3.025816 CPU 0 DPC count: 1668202 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 5.649947 CPU 1 ISR highest execution time (µs): 215.495855 CPU 1 ISR total execution time (s): 1.657964 CPU 1 ISR count: 182425 CPU 1 DPC highest execution time (µs): 1065.316226 CPU 1 DPC total execution time (s): 1.921297 CPU 1 DPC count: 241649 _________________________________________________________________________________________________________ Kompjuter je dosta star, kupljen 2007 godine, tako da me ne bi cudilo da je neka komponenta otkazala. Ali vidim da ovaj LatencyMonitor prijavljuje cak nesto za DirectX, kako to onda nije reseno nakon obaranja sistema? Ja se plasim da mozda graficka ili maticna ploca otkazuju, da li neko ima neku ideju? Hvala jos jednom ako neko ume da prepozna problem... |