Crucial SSD mx 200 – cykliczne skoki latencji

Jeśli masz problem związany z komputerem stosowanym w domowym lub profesjonalnym studiu, to tu jest odpowiednie miejsce, aby się nim zająć.
docadoca
Posty: 26
Rejestracja: czwartek 25 kwie 2013, 00:00

Crucial SSD mx 200 – cykliczne skoki latencji

Post autor: docadoca » wtorek 10 sty 2017, 20:26

Witam,


 


Zakupilem powyzszy dysk i zaczely sie moje problemy. Mowiac jak najkrocej: Dropy i wywalanie co chwila sterownikow ASIO w DAW. DPC Latency checker pokazal cyklicznie powtarzajace sie skoki latencji. Chce podkreslic, ze JEDYNE co zmienilo sie w komputerze, to ow dysk. ALE! Nie chce wykluczac od razu mozliwosci, ze problem tkwi jednak w nowo postawionym OS-ie. Prosze o sugestie, co moglbym sprawdzic (i czym) w dzialaniu dysku i samego OS-a. Pozostaly sprzet nalezy wykluczyc. Posiadam w tej chwili oba OS-y – stary (na HDD) i nowy (na SSD). Na starym OS-ie problem nie wystepuje!


 


Ehhh... nie ma tu mozliwosci dodawania zalacznikow wiec nie wiem, jak mam Wam to pokazac... W DPC skoki wystepuja co 4 slupki. Raport z LatenyMoon musze wkleic normalnie do tresci posta. Z gory dzieki za pomoc:)




 


Specyfikacja PC:


 


MB - asus p8 h67-m lx/si


 


CPU – intel core i5 2400 3.1 Ghz


 


RAM -kingstonDDR3 16 GB 1333 MHz


 


HDD – Samsung 1 TB 4500 r.p.m.


 


SSD Crucial mx 200 Sata III2.5 cala


 


Interface audio – Essi Maya44 PCI/Presonus firestudio firewire 26/26


 


OS -  Windows 7 ultimate x64


 


DAW - Cubase 5.1


 


LatencyMoon:


 


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


 



_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MUSICMACHINE
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASUSTeK COMPUTER INC., P8H67-M LX
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Logical processors: 4
Processor groups: 1
RAM: 16104 MB total


 



_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3093 MHz
Measured CPU speed: 1 MHz (approx.)


 


Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


 


WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.


 


 


 


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.


 


Highest measured interrupt to process latency (µs): 3225,906839
Average measured interrupt to process latency (µs): 2,891715


 


Highest measured interrupt to DPC latency (µs): 146,993292
Average measured interrupt to DPC latency (µs): 0,615998


 



_________________________________________________________________________________________________________
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): 44,319431
Driver with highest ISR routine execution time: USBPORT.SYS - Sterownik portów USB 1.1 i 2.0, Microsoft Corporation


 


Highest reported total ISR routine time (%): 0,053349
Driver with highest ISR total time: USBPORT.SYS - Sterownik portów USB 1.1 i 2.0, Microsoft Corporation


 


Total time spent in ISRs (%) 0,072707


 


ISR count (execution time <250 µs): 760603
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): 3060,927255
Driver with highest DPC routine execution time: USBPORT.SYS - Sterownik portów USB 1.1 i 2.0, Microsoft Corporation


 


Highest reported total DPC routine time (%): 0,393921
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,530329


 


DPC count (execution time <250 µs): 3739222
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): 4
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: explorer.exe


 


Total number of hard pagefaults 20968
Hard pagefault count of hardest hit process: 6592
Highest hard pagefault resolution time (µs): 500433,315551
Total time spent in hard pagefaults (%): 1,233224
Number of processes hit: 13


 



_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 13,227959
CPU 0 ISR highest execution time (µs): 44,319431
CPU 0 ISR total execution time (s): 1,291713
CPU 0 ISR count: 760603
CPU 0 DPC highest execution time (µs): 3060,927255
CPU 0 DPC total execution time (s): 9,091023
CPU 0 DPC count: 3699387
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,957027
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): 96,967346
CPU 1 DPC total execution time (s): 0,165083
CPU 1 DPC count: 24432
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5,386591
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): 205,205302
CPU 2 DPC total execution time (s): 0,083877
CPU 2 DPC count: 7876
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 5,178003
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): 3051,344326
CPU 3 DPC total execution time (s): 0,081846
CPU 3 DPC count: 7531
_________________________________________________________________________________________________________




docadoca
Posty: 26
Rejestracja: czwartek 25 kwie 2013, 00:00

Re: Crucial SSD mx 200 – cykliczne skoki latencji

Post autor: docadoca » środa 11 sty 2017, 23:27

Licznik wskazuje jedna odpowiedz (od teraz powinne byc dwie), ale jej nie widze:O Lol, nie kumam tego forum:D


docadoca
Posty: 26
Rejestracja: czwartek 25 kwie 2013, 00:00

Re: Crucial SSD mx 200 – cykliczne skoki latencji

Post autor: docadoca » środa 18 sty 2017, 03:00

Naprawde Nikt??


ODPOWIEDZ