Skocz do zawartości

Rekomendowane odpowiedzi

Witam wszystkich.

 

Mam problem z notebookiem dell inspiron N7110.

 

Problemem jest bardzo wolne działanie, klatkowanie w grach i że tak powiem '' slow motion '' występuje nawet przy pisaniu tekstu. Czasami po restarcie jest dobrze a czasami dalej tak samo. Nie mam pojęcia od czego to zależy, że raz chodzi płynnie a raz nie.

'Przedstawiam krótką konfigurację sprzętową;

 

intel core i7 2670 QM 2,2 Ghz

geForce GT 525m oraz zintegrowana intel HD graphics family

6 Gb pamięci RAM ddr3

Teraz jest Windows 7 64 bit professional, był już Ultimate, był home edition i na każdym ten problem jest

notebook ma 3 lata jest po gwarancji już.

Sprzęt zadbany. Antywirus jest wykupiony. Wszystkie zbędne funkcje wyłączone, sterowniki wszystkie zainstalowane. Format nic nie zmienia, formatowany jest 2 razy w roku.

 

Proszę mnie pokierować co można podesłać do wglądu i co zrobić żeby rozwiązać ten problem. Będę bardzo wdzięczny za każdą wskazówke, rade.

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

post-258873-142403815607_thumb.pngpost-258873-142403792133_thumb.png

Pokaż SMART dysku

 

Użyłem dzisiaj HD tune , bad sektorów nie ma. Coś jeszcze podać ?

 

A ten test zrobiłem teraz - screen

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Witam

 

Zrób HD tune bez quick scan wtedy on jest w miare dokładny

Możesz też dać screna Crystaldisk

 

Pozdr.

Max119x

Edytowane przez max119x

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Hd Tune, zakładka Health

Proszę wszystko jest w statusie OK post-258873-142403883195_thumb.png

Dodam że zrobiłem jeszcze test za pomocą CMD i zapis oraz odczyt danych partycji C wyszedł podobny ~ 155 MB/s

 

post-258873-142404461249_thumb.png

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Witam

 

Zrób HD tune bez quick scan wtedy on jest w miare dokładny

Możesz też dać screna Crystaldisk

 

Pozdr.

Max119x

 

HD tune bez quick scan robiłem dzisiaj rano i również wyszło bez bad sektorów.

 

Crystal disk info

 

post-258873-142404435816_thumb.png

 

 

 

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Podaj temperatury

 

Jeśli są wporządku to formata zrób

Edytowane przez Killer85

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

1. Aktualizacja BIOSu.

2. Pokaż zużycie Ramu i CPU w IDLE i po włączeniu przeglądarki z jakimś Flashem.

3. Sprawdź opcje zasilania (Zarządzanie energią CPU i jego ustawienia).

Stery na 100% wszystkie?

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Podaj temperatury

 

Jeśli są wporządku to formata zrób

 

Formata robie 2-3 razy w roku i to nic nie zmienia. Temperatury tu nic do rzeczy raczej nie mają. Nawet w spoczynku te zjaawisko występuje gdy temperatury są jak na screenie - załącznik. Podczas obciążenia włączam podstawkę chłodzącą zalmana ZM-NS2000, która redukuje temperature o 3-5 stopni w dół.

 

post-258873-142473551064_thumb.png

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

1. Aktualizacja BIOSu.

2. Pokaż zużycie Ramu i CPU w IDLE i po włączeniu przeglądarki z jakimś Flashem.

3. Sprawdź opcje zasilania (Zarządzanie energią CPU i jego ustawienia).

Stery na 100% wszystkie?

 

 

1. Nie wiem czy ta wersja biosu jest aktualnie najnowsza - patrz screen

2. bez flesha- sama mozilla strona tego forum

 

post-258873-142473426319_thumb.png

post-258873-14247339582_thumb.png

 

 

 

 

 

3.minimalny stan procesora 5 procent, maxymalny 90 procent, chlodzenie - aktywne

 

Tak sterowniki wszystkie wgrane

 

użycie z flashem - odpalony filmik you tube

 

post-258873-142473456074_thumb.png

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Pokażę teraz jak to sie przedstwaia wszystko na przykładze nisko wymagającej gierki brata.

Pozwolę sobie dodać tu 2 linki do filmików na you tube, które przed chwilą zrobilem.

 

Na jednym nich gra chodzi idealnie płynnie a na drugim '' slow motion '' szarpanie obrazu

 

złe działanie

 

 

dobre działanie

 

 

Tutaj nie chodzi tylko o tą paskudną gre tylko o to że tak się dzieje nawet podczas pisania tekstu chociażby na popularnym facebooku, literki pojawiają się stopniowo, ja już dawno je wystukam na klawiaturze a one jeszcze się pokazują pomału

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Nie widzę powodu dla którego minimalny stan procesora nie miałby wynosić 0, a maksymalny 100.

 

Symptomy przypominają trochę ten temat. Może antywirus?

 

 

Możesz spróbować użyć LatencyMon - kliknąć w nim start, normalnie poużywać komputera aby wielokrotnie powtórzył się problem o którym mówisz, następnie zatrzymać zbieranie danych i wkleić zawartość zakładki stats w tag /spoiler/.

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Czy w innych grach jest ok.?

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Nie widzę powodu dla którego minimalny stan procesora nie miałby wynosić 0, a maksymalny 100.

 

Symptomy przypominają trochę ten temat. Może antywirus?

 

 

Możesz spróbować użyć LatencyMon - kliknąć w nim start, normalnie poużywać komputera aby wielokrotnie powtórzył się problem o którym mówisz, następnie zatrzymać zbieranie danych i wkleić zawartość zakładki stats w tag /spoiler/.

 

Mam kaspersky 2013 płatnego.

 

To wynik testu z latency, gdy nacisnąłem start wszystko tak zwiesiło że ledwo udało mi się nacisnąć stop. Przed wciśnięciem start odpalilem film na you tube tylko.

 

REPORT

_________________________________________________________________________________________________________

In Depth Latency Tests has been analyzing your system for 0:02:14 (h:mm:ss) on all processors in the system.

 

Test performed: Tight Loop Latency Test at HIGH_LEVEL IRQL

Tight Loop Latency Test at HIGH_LEVEL IRQL: measure SMIs and CPU stalls. Run test with all maskable interrupts disabled.

NOTE: SMIs that are initiated by software have not been measuded.

 

 

Highest latency measured: 350,21330 µs

This value reflects the highest measured interruption interval of a tight loop spinning at HIGH_LEVEL interrupt request level.

 

 

_________________________________________________________________________________________________________

PER CPU MEASURINGS

_________________________________________________________________________________________________________

Highest latency on CPU 0: 349,74635 µs

Highest latency on CPU 1: 349,74635 µs

Highest latency on CPU 2: 350,21330 µs

Highest latency on CPU 3: 350,21330 µs

Highest latency on CPU 4: 350,21330 µs

Highest latency on CPU 5: 349,74635 µs

Highest latency on CPU 6: 349,74635 µs

Highest latency on CPU 7: 349,27940 µs

 

 

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: RAFIKS-KOMPUTER

OS version: Windows 7 Service Pack 1, 6.1, build: 7601Highest latency on CPU 7: 349,27940 µs

Hardware: Dell System Inspiron N7110, Dell Inc. , Dell Inc., 09G8VY

CPU: GenuineIntel Intel® Core i7-2670QM CPU @ 2.20GHz

Logical processors: 8

Processor groups: 1

RAM: 6038 MB total

 

Czy w innych grach jest ok.?

 

Tak jest w grach sieciowych i w przeglądarce internetowej.

Moim zdaniem to musi być wina czegoś co sie uruchamia wraz ze startem systemu , bo skoro jest źle , zrestartuje lapka i jest dobrze, potem znów zrestartuje i jest źle, to coś w tym jest.

 

 

 

 

Porobiłem screeny procesów i usług działających podczas poprawnej i nie poprawnej pracy laptopa - link

 

procesy i usługi - nie prawidłowe działanie

 

procesy i usługi - prawidłowe działanie

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Uruchomiłeś program "In depth latency tests", a mi chodziło o zwykłego LatencyMon.

Ponawiam prośbę, umieszczaj te informacje w tagi /spoiler/.

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Uruchomiłeś program "In depth latency tests", a mi chodziło o zwykłego LatencyMon.

Ponawiam prośbę, umieszczaj te informacje w tagi /spoiler/.

 

To moge prosić o linka do zwykłego latencymon, bo to co pobrałem też sie nazywało latencymon a jednak to nie to

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Instalator: Klik

Później w programach masz dwa skróty: Jeden do LatencyMon (LatencyMon\LatMon.exe), drugi do In Depth Latency Tests (LatencyMon\IDLT.exe).

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Instalator: Klik

Później w programach masz dwa skróty: Jeden do LatencyMon (LatencyMon\LatMon.exe), drugi do In Depth Latency Tests (LatencyMon\IDLT.exe).

 

Jednak miałem , tylko nie wiedziałem że dwie aplikacje w jednym są w sumie.

Testowałem bez tego problemu w grach, bo jakoś ostatnio mam szczęście i nie mogę trafić na problem, ale przeglądanie stron jest uciążliwe zawsze, bo przy każdym zdjęciu jakie sie pojawia , przewijam rolką strone i sie freezuje na sekunde przy kazdym zdjęciu.

 

A o to te wyniki z zakładki stats.

 

________________________________________________________________________________________________________

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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:56 (h:mm:ss) on all processors.

 

 

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: RAFIKS-KOMPUTER

OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)

Hardware: Dell System Inspiron N7110, Dell Inc. , Dell Inc., 09G8VY

CPU: GenuineIntel Intel® Core i7-2670QM CPU @ 2.20GHz

Logical processors: 8

Processor groups: 1

RAM: 6038 MB total

 

 

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2192,0 MHz

Measured CPU speed: 717,0 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.

 

 

_________________________________________________________________________________________________________

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): 5235,968813

Average measured interrupt to process latency (µs): 17,645167

 

Highest measured interrupt to DPC latency (µs): 3208,916230

Average measured interrupt to DPC latency (µs): 3,657599

 

 

_________________________________________________________________________________________________________

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): 379,038321

Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

 

Highest reported total ISR routine time (%): 0,058267

Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

 

Total time spent in ISRs (%) 0,118815

 

ISR count (execution time <250 µs): 560960

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-999 µs): 1

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): 3258,687956

Driver with highest DPC routine execution time: portcls.sys - Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation

 

Highest reported total DPC routine time (%): 0,119268

Driver with highest DPC total execution time: USBPORT.SYS - Sterownik portów USB 1.1 i 2.0, Microsoft Corporation

 

Total time spent in DPCs (%) 0,554787

 

DPC count (execution time <250 µs): 3600989

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 7161

DPC count (execution time 1000-1999 µs): 14

DPC count (execution time 2000-3999 µs): 2

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 1635

Hard pagefault count of hardest hit process: 669

Highest hard pagefault resolution time (µs): 523649,431113

Total time spent in hard pagefaults (%): 0,812727

Number of processes hit: 11

 

 

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 31,197224

CPU 0 ISR highest execution time (µs): 379,038321

CPU 0 ISR total execution time (s): 3,386184

CPU 0 ISR count: 560961

CPU 0 DPC highest execution time (µs): 3258,687956

CPU 0 DPC total execution time (s): 13,404648

CPU 0 DPC count: 2595457

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 9,530398

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): 140,179288

CPU 1 DPC total execution time (s): 0,242359

CPU 1 DPC count: 136475

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 5,071562

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): 233,875912

CPU 2 DPC total execution time (s): 0,503737

CPU 2 DPC count: 162080

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 11,483218

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): 393,049270

CPU 3 DPC total execution time (s): 0,329425

CPU 3 DPC count: 135726

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 9,454997

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): 299,573905

CPU 4 DPC total execution time (s): 0,402250

CPU 4 DPC count: 152197

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 8,099188

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): 155,671077

CPU 5 DPC total execution time (s): 0,237626

CPU 5 DPC count: 133560

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 11,481376

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): 233,957117

CPU 6 DPC total execution time (s): 0,426057

CPU 6 DPC count: 154645

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 8,331515

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): 159,166971

CPU 7 DPC total execution time (s): 0,265058

CPU 7 DPC count: 138026

_________________________________________________________________________________________________________

 

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Czy system posiada wszystkie aktualizacje? (SP1+wszystko, co pokazuje się w windows update).

 

Z jakich urządzeń podłączonych do laptopa korzystasz?

 

Około 1600 twardych błędów stron w ciągu 6 minut to bardzo dużo. Z jakiego oprogramowania korzystałeś i w jakim stopniu pamięć ram była zapełniona?

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Czy system posiada wszystkie aktualizacje? (SP1+wszystko, co pokazuje się w windows update).

 

Z jakich urządzeń podłączonych do laptopa korzystasz?

 

Około 1600 twardych błędów stron w ciągu 6 minut to bardzo dużo. Z jakiego oprogramowania korzystałeś i w jakim stopniu pamięć ram była zapełniona?

 

Need for speed most wanted, tibia, cabal online, fear combat,skype, gg, conquer online, office 2010, deamon tools, ventrillo, team speak a tak po za tym nic szczególnego.

Tak windows update cały czas na bieżąco z aktualizacjami. Nawet świeżo po formacie ten problem występował, formatowalem ostatnio całość systemowy '' c '' oraz '' d '' z moimi plikami i przypisywałem pojemność do partycji.

Do laptopa podłączone mam tylko głośniki 2.1, mysz i podstawkę zalmana chłodzącą gdy jest potrzeba to włączam ją.

Maxymalnie pokazywało mi raz 4 Gb pamięci zajętej.

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

W DPCs nie powinno być w ogóle takich wpisów:

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 7161

DPC count (execution time 1000-1999 µs): 14

DPC count (execution time 2000-3999 µs): 2

DPC count (execution time >=4000 µs): 0

A jeżeli nawet, to kilka, a nie takie ilości. Odłącz wszystko i zrób podobny test, możliwe że myszka "gryzie" :E

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

W DPCs nie powinno być w ogóle takich wpisów:

 

A jeżeli nawet, to kilka, a nie takie ilości. Odłącz wszystko i zrób podobny test, możliwe że myszka "gryzie" :E

odłączyłem wszystko od lapka, z tym że tym razem miałem odpaloną tylko mozille firefox, żadnych gier, a to wyniki

 

Baterie mam cały czas wyciągniętą bo jej nie używałem ani razu od dnia zakupu notebook'a. To nic nie szkodzi ?

 

Program zaleca wyłączyc throtting a na tej stronie jak wyłączyć cpu throtting doradzają by ustwić minimum i maximum stan procesora na 100 procent. Tak też zrobiłem.

 

Wykonałem też krok 7-my z tego artykułu artykuł

 

 

_________________________________________________________________________________________________________

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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:07:07 (h:mm:ss) on all processors.

 

 

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: RAFIKS-KOMPUTER

OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)

Hardware: Dell System Inspiron N7110, Dell Inc. , Dell Inc., 09G8VY

CPU: GenuineIntel Intel® Core i7-2670QM CPU @ 2.20GHz

Logical processors: 8

Processor groups: 1

RAM: 6038 MB total

 

 

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2192,0 MHz

Measured CPU speed: 522,0 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.

 

 

_________________________________________________________________________________________________________

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): 9970,007327

Average measured interrupt to process latency (µs): 16,429197

 

Highest measured interrupt to DPC latency (µs): 1588,589056

Average measured interrupt to DPC latency (µs): 2,605420

 

 

_________________________________________________________________________________________________________

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): 146,949361

Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

 

Highest reported total ISR routine time (%): 0,008597

Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

 

Total time spent in ISRs (%) 0,016119

 

ISR count (execution time <250 µs): 61291

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): 10140,143248

Driver with highest DPC routine execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

 

Highest reported total DPC routine time (%): 0,01660

Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

 

Total time spent in DPCs (%) 0,066641

 

DPC count (execution time <250 µs): 389756

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 68

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

 

Total number of hard pagefaults 801

Hard pagefault count of hardest hit process: 437

Highest hard pagefault resolution time (µs): 93889,583942

Total time spent in hard pagefaults (%): 0,062906

Number of processes hit: 9

 

 

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 5,980103

CPU 0 ISR highest execution time (µs): 146,949361

CPU 0 ISR total execution time (s): 0,551176

CPU 0 ISR count: 61291

CPU 0 DPC highest execution time (µs): 10139,942518

CPU 0 DPC total execution time (s): 1,809590

CPU 0 DPC count: 329574

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 2,448510

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): 182,834854

CPU 1 DPC total execution time (s): 0,032012

CPU 1 DPC count: 5134

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 2,369176

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): 136,101734

CPU 2 DPC total execution time (s): 0,050547

CPU 2 DPC count: 8020

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 2,044196

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): 73,351734

CPU 3 DPC total execution time (s): 0,028613

CPU 3 DPC count: 4942

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 2,618963

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): 10140,143248

CPU 4 DPC total execution time (s): 0,177174

CPU 4 DPC count: 11561

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 2,246290

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): 128,509580

CPU 5 DPC total execution time (s): 0,019775

CPU 5 DPC count: 3921

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 1,564797

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): 151,305201

CPU 6 DPC total execution time (s): 0,049991

CPU 6 DPC count: 8425

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3,601635

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): 168,079836

CPU 7 DPC total execution time (s): 0,111045

CPU 7 DPC count: 18250

_________________________________________________________________________________________________________

 

 

 

 

TO wyniki po dwóch zabiegach, które zrobiłem odnośnie procesora, również bez podłączonych urządzeń i na samej mozilli firefox.

 

 

_________________________________________________________________________________________________________

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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:15 (h:mm:ss) on all processors.

 

 

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: RAFIKS-KOMPUTER

OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)

Hardware: Dell System Inspiron N7110, Dell Inc. , Dell Inc., 09G8VY

CPU: GenuineIntel Intel® Core i7-2670QM CPU @ 2.20GHz

Logical processors: 8

Processor groups: 1

RAM: 6038 MB total

 

 

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2192,0 MHz

Measured CPU speed: 1453,0 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.

 

 

_________________________________________________________________________________________________________

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): 8818,329799

Average measured interrupt to process latency (µs): 25,243970

 

Highest measured interrupt to DPC latency (µs): 550,065793

Average measured interrupt to DPC latency (µs): 1,217719

 

 

_________________________________________________________________________________________________________

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): 564,366332

Driver with highest ISR routine execution time: i8042prt.sys - Sterownik portu i8042, Microsoft Corporation

 

Highest reported total ISR routine time (%): 0,027643

Driver with highest ISR total time: i8042prt.sys - Sterownik portu i8042, Microsoft Corporation

 

Total time spent in ISRs (%) 0,053686

 

ISR count (execution time <250 µs): 291540

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-999 µs): 25

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): 10101,866788

Driver with highest DPC routine execution time: ACPI.sys - Sterownik ACPI dla systemu NT, Microsoft Corporation

 

Highest reported total DPC routine time (%): 0,03040

Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

 

Total time spent in DPCs (%) 0,094191

 

DPC count (execution time <250 µs): 1230258

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 2

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

 

Total number of hard pagefaults 3191

Hard pagefault count of hardest hit process: 1934

Highest hard pagefault resolution time (µs): 339221,270073

Total time spent in hard pagefaults (%): 0,774950

Number of processes hit: 14

 

 

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 15,296658

CPU 0 ISR highest execution time (µs): 564,366332

CPU 0 ISR total execution time (s): 1,612431

CPU 0 ISR count: 291557

CPU 0 DPC highest execution time (µs): 263,200730

CPU 0 DPC total execution time (s): 2,486634

CPU 0 DPC count: 1191234

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 10,970747

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): 157,718066

CPU 1 DPC total execution time (s): 0,025306

CPU 1 DPC count: 1154

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 1,681781

CPU 2 ISR highest execution time (µs): 1,503650

CPU 2 ISR total execution time (s): 0,000002

CPU 2 ISR count: 3

CPU 2 DPC highest execution time (µs): 235,658759

CPU 2 DPC total execution time (s): 0,10170

CPU 2 DPC count: 21286

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 12,381055

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): 0,0

CPU 3 DPC total execution time (s): 0,0

CPU 3 DPC count: 0

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 3,616387

CPU 4 ISR highest execution time (µs): 0,718978

CPU 4 ISR total execution time (s): 0,000001

CPU 4 ISR count: 2

CPU 4 DPC highest execution time (µs): 10101,866788

CPU 4 DPC total execution time (s): 0,079592

CPU 4 DPC count: 4617

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 3,345624

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

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 9,628242

CPU 6 ISR highest execution time (µs): 0,775547

CPU 6 ISR total execution time (s): 0,000002

CPU 6 ISR count: 3

CPU 6 DPC highest execution time (µs): 184,801095

CPU 6 DPC total execution time (s): 0,120401

CPU 6 DPC count: 9953

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 9,172247

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): 154,398266

CPU 7 DPC total execution time (s): 0,015360

CPU 7 DPC count: 2018

_________________________________________________________________________________________________________

 

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

kolejny test latencymon tym razem podczas występowania problemu, wróciłem z pracy włączyłem laptopa no i jest tragicznie znów

 

 

 

_________________________________________________________________________________________________________

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:18 (h:mm:ss) on all processors.

 

 

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: RAFIKS-KOMPUTER

OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)

Hardware: Dell System Inspiron N7110, Dell Inc. , Dell Inc., 09G8VY

CPU: GenuineIntel Intel® Core i7-2670QM CPU @ 2.20GHz

Logical processors: 8

Processor groups: 1

RAM: 6038 MB total

 

 

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 5607,0 MHz

Measured CPU speed: 3715,0 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.

 

 

_________________________________________________________________________________________________________

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): 3238,918887

Average measured interrupt to process latency (µs): 8,118797

 

Highest measured interrupt to DPC latency (µs): 440,998428

Average measured interrupt to DPC latency (µs): 1,129777

 

 

_________________________________________________________________________________________________________

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): 58,37150

Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

 

Highest reported total ISR routine time (%): 0,008317

Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

 

Total time spent in ISRs (%) 0,019664

 

ISR count (execution time <250 µs): 471314

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): 317,256287

Driver with highest DPC routine execution time: portcls.sys - Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation

 

Highest reported total DPC routine time (%): 0,053397

Driver with highest DPC total execution time: USBPORT.SYS - Sterownik portów USB 1.1 i 2.0, Microsoft Corporation

 

Total time spent in DPCs (%) 0,164001

 

DPC count (execution time <250 µs): 2693911

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 203

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

 

Total number of hard pagefaults 1030

Hard pagefault count of hardest hit process: 370

Highest hard pagefault resolution time (µs): 202709,973604

Total time spent in hard pagefaults (%): 0,15890

Number of processes hit: 10

 

 

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 9,735586

CPU 0 ISR highest execution time (µs): 58,37150

CPU 0 ISR total execution time (s): 0,595046

CPU 0 ISR count: 471287

CPU 0 DPC highest execution time (µs): 317,256287

CPU 0 DPC total execution time (s): 4,175678

CPU 0 DPC count: 2442736

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 4,270901

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): 55,554842

CPU 1 DPC total execution time (s): 0,076068

CPU 1 DPC count: 25640

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 1,829018

CPU 2 ISR highest execution time (µs): 0,462279

CPU 2 ISR total execution time (s): 0,000001

CPU 2 ISR count: 2

CPU 2 DPC highest execution time (µs): 68,732656

CPU 2 DPC total execution time (s): 0,207429

CPU 2 DPC count: 65710

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 5,344363

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): 62,694311

CPU 3 DPC total execution time (s): 0,083809

CPU 3 DPC count: 24027

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 4,227495

CPU 4 ISR highest execution time (µs): 0,316747

CPU 4 ISR total execution time (s): 0,0

CPU 4 ISR count: 1

CPU 4 DPC highest execution time (µs): 111,389335

CPU 4 DPC total execution time (s): 0,130154

CPU 4 DPC count: 44645

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 3,836635

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): 75,018370

CPU 5 DPC total execution time (s): 0,062801

CPU 5 DPC count: 18180

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 4,291086

CPU 6 ISR highest execution time (µs): 0,403781

CPU 6 ISR total execution time (s): 0,000005

CPU 6 ISR count: 24

CPU 6 DPC highest execution time (µs): 100,385233

CPU 6 DPC total execution time (s): 0,158570

CPU 6 DPC count: 50705

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3,353156

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): 57,488853

CPU 7 DPC total execution time (s): 0,068430

CPU 7 DPC count: 22471

_________________________________________________________________________________________________________

 

Edytowane przez rafiksman

Udostępnij tę odpowiedź


Odnośnik do odpowiedzi
Udostępnij na innych stronach

Jeśli chcesz dodać odpowiedź, zaloguj się lub zarejestruj nowe konto

Jedynie zarejestrowani użytkownicy mogą komentować zawartość tej strony.

Zarejestruj nowe konto

Załóż nowe konto. To bardzo proste!

Zarejestruj się

Zaloguj się

Posiadasz już konto? Zaloguj się poniżej.

Zaloguj się

  • Ostatnio przeglądający   0 użytkowników

    Brak zarejestrowanych użytkowników przeglądających tę stronę.

×
×
  • Dodaj nową pozycję...