Jump to content

Patyfatycake

Member
  • Posts

    7
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    New Zealand

Everything posted by Patyfatycake

  1. from what I see from the trace the system is now ok. What do you mean with the 500? My nvidia drivers were jumping to around 500, Il keep monitoring it to see if happens again. Thanks again for your help.
  2. well very rarely my mouse gets disconnected from the USB now(i cant get an average its that rare) and my gfx card is jumping around 500, is that quite common? Thanks for your help.
  3. Edit: Latest Xperf. http://www.mediafire.com/?4hobrjnxb1yzyp1 My fresco logic drivers are already the latest. Fresco Logic xHCI USB3.0-3.5.100.0 Which matches the website http://www.frescologic.com/support.php Also i managed to solve the high isr I believe by getting a certain wireless drivers(I will confirm this when i get home from work and get you a latest xperf).
  4. The xperf file is over a very small period of time where my mouse was temporarily frozen(Little each way), if you need a longer one let me know. http://www.mediafire.com/?zb8dpks74a88qy6
  5. The only devices which share an IRQ are An overnight log _________________________________________________________________________________________________________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 7:10:16 (h:mm:ss) on processors 0,1,2 and 3. _________________________________________________________________________________________________________SYSTEM INFORMATION_________________________________________________________________________________________________________Computer name: LEWISKWONG-PCOS version: Windows 7 , 6.1, build: 7600 (x64)Hardware: Gigabyte Technology Co., Ltd., X79-UD3CPU: GenuineIntel Intel® Core i7-3820 CPU @ 3.60GHzLogical processors: 8Processor groups: 1RAM: 16332 MB total _________________________________________________________________________________________________________CPU SPEED_________________________________________________________________________________________________________Reported CPU speed: 3600.0 MHzMeasured CPU speed: 2305.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): 14243.036133Average measured interrupt to process latency (µs): 5.086741 Highest measured interrupt to DPC latency (µs): 14241.613934Average measured interrupt to DPC latency (µs): 1.217769 _________________________________________________________________________________________________________ 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): 657.574167Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation Highest reported total ISR routine time (%): 0.062222Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation Total time spent in ISRs (%) 0.097536 ISR count (execution time <250 µs): 34988674ISR count (execution time 250-500 µs): 0ISR count (execution time 500-999 µs): 614ISR 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): 14253.13250Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation Highest reported total DPC routine time (%): 0.030304Driver 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.082323 DPC count (execution time <250 µs): 78863763DPC count (execution time 250-500 µs): 0DPC count (execution time 500-999 µs): 26290DPC count (execution time 1000-1999 µs): 15DPC count (execution time 2000-3999 µs): 10DPC 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 371Hard pagefault count of hardest hit process: 111Highest hard pagefault resolution time (µs): 292116.3450Total time spent in hard pagefaults (%): 0.000679Number of processes hit: 8 _________________________________________________________________________________________________________ PER CPU DATA_________________________________________________________________________________________________________CPU 0 Interrupt cycle time (s): 395.874130CPU 0 ISR highest execution time (µs): 570.125833CPU 0 ISR total execution time (s): 128.506695CPU 0 ISR count: 26417386CPU 0 DPC highest execution time (µs): 14253.13250CPU 0 DPC total execution time (s): 96.497211CPU 0 DPC count: 72219238_________________________________________________________________________________________________________CPU 1 Interrupt cycle time (s): 103.057376CPU 1 ISR highest execution time (µs): 0.0CPU 1 ISR total execution time (s): 0.0CPU 1 ISR count: 0CPU 1 DPC highest execution time (µs): 256.954167CPU 1 DPC total execution time (s): 0.189743CPU 1 DPC count: 54182_________________________________________________________________________________________________________CPU 2 Interrupt cycle time (s): 159.170990CPU 2 ISR highest execution time (µs): 14.888333CPU 2 ISR total execution time (s): 0.032037CPU 2 ISR count: 12604CPU 2 DPC highest execution time (µs): 204.529167CPU 2 DPC total execution time (s): 2.242563CPU 2 DPC count: 618491_________________________________________________________________________________________________________CPU 3 Interrupt cycle time (s): 289.594863CPU 3 ISR highest execution time (µs): 657.574167CPU 3 ISR total execution time (s): 72.900627CPU 3 ISR count: 8559298CPU 3 DPC highest execution time (µs): 661.170833CPU 3 DPC total execution time (s): 71.089743CPU 3 DPC count: 5998177_________________________________________________________________________________________________________
  6. Have rolled back wireless card drivers,updated,Full power options,Upgraded graphics card drivers,Bios drivers latest. Edit3: New output _________________________________________________________________________________________________________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:04:38 (h:mm:ss) on processors 0,1,2 and 3. _________________________________________________________________________________________________________SYSTEM INFORMATION_________________________________________________________________________________________________________Computer name: LEWISKWONG-PCOS version: Windows 7 , 6.1, build: 7600 (x64)Hardware: Gigabyte Technology Co., Ltd., X79-UD3CPU: GenuineIntel Intel® Core i7-3820 CPU @ 3.60GHzLogical processors: 8Processor groups: 1RAM: 16332 MB total _________________________________________________________________________________________________________CPU SPEED_________________________________________________________________________________________________________Reported CPU speed: 3600.0 MHzMeasured CPU speed: 2252.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): 4390.043130Average measured interrupt to process latency (µs): 6.403892 Highest measured interrupt to DPC latency (µs): 4388.620931Average measured interrupt to DPC latency (µs): 1.231445 _________________________________________________________________________________________________________ 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): 644.070Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation Highest reported total ISR routine time (%): 0.059616Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation Total time spent in ISRs (%) 0.166314 ISR count (execution time <250 µs): 937116ISR count (execution time 250-500 µs): 0ISR count (execution time 500-999 µs): 22ISR 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): 607.768333Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation Highest reported total DPC routine time (%): 0.056810Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation Total time spent in DPCs (%) 0.190041 DPC count (execution time <250 µs): 1310269DPC count (execution time 250-500 µs): 0DPC count (execution time 500-999 µs): 5DPC 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: osu!.exe Total number of hard pagefaults 8Hard pagefault count of hardest hit process: 6Highest hard pagefault resolution time (µs): 33480.581667Total time spent in hard pagefaults (%): 0.004428Number of processes hit: 2 _________________________________________________________________________________________________________ PER CPU DATA_________________________________________________________________________________________________________CPU 0 Interrupt cycle time (s): 3.536192CPU 0 ISR highest execution time (µs): 441.203333CPU 0 ISR total execution time (s): 1.326228CPU 0 ISR count: 284154CPU 0 DPC highest execution time (µs): 215.38250CPU 0 DPC total execution time (s): 1.147852CPU 0 DPC count: 778739_________________________________________________________________________________________________________CPU 1 Interrupt cycle time (s): 1.401502CPU 1 ISR highest execution time (µs): 0.0CPU 1 ISR total execution time (s): 0.0CPU 1 ISR count: 0CPU 1 DPC highest execution time (µs): 19.446667CPU 1 DPC total execution time (s): 0.000673CPU 1 DPC count: 390_________________________________________________________________________________________________________CPU 2 Interrupt cycle time (s): 3.237139CPU 2 ISR highest execution time (µs): 160.958333CPU 2 ISR total execution time (s): 0.173386CPU 2 ISR count: 277787CPU 2 DPC highest execution time (µs): 221.513333CPU 2 DPC total execution time (s): 1.041002CPU 2 DPC count: 287776_________________________________________________________________________________________________________CPU 3 Interrupt cycle time (s): 5.748659CPU 3 ISR highest execution time (µs): 644.070CPU 3 ISR total execution time (s): 2.200240CPU 3 ISR count: 375197CPU 3 DPC highest execution time (µs): 607.768333CPU 3 DPC total execution time (s): 2.038176CPU 3 DPC count: 243369_________________________________________________________________________________________________________ Edit2: Rolling back to older drivers does not fix the problem. Edit: Wireless card causing the problems although it still does jump some but my mouse remains fine. Hey, Recently I have been having some problems with my mouse freezing randomly (Win7 64bit) and discovered the about my latency jumps. Can you please help me resolve it? Old one
×
×
  • Create New...