This is not good?

Anyone keen to have a stab @ this?
 If I move the mouse it stalls the Nowtime marker till I stop....GLITCHING LIKE MAD?
Thanx in advance_
 
 
 
 
________________________________________________________________________________________________________
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.....CAN'T FIND THIS? Check for BIOS updates...DONE
LatencyMon has been analyzing your system for 0:06:36 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: Jinxy
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: XPS 630i, Dell Inc, 0PP150
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 4093 MB total

_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2400.0 MHz
Measured CPU speed: 2415.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): 4873.773823
Average measured interrupt to process latency (µs): 11.400827
Highest measured interrupt to DPC latency (µs): 2139.289324
Average measured interrupt to DPC latency (µs): 6.210680

_________________________________________________________________________________________________________
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): 176.726250
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.033439
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.103091
ISR count (execution time <250 µs): 543774
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): 2159.90250
Driver with highest DPC routine execution time: ohci1394.sys - 1394 OpenHCI Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 1.807079
Driver with highest DPC total execution time: ohci1394.sys - 1394 OpenHCI Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 2.369620
DPC count (execution time <250 µs): 2330652
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 60411
DPC count (execution time 1000-1999 µs): 69
DPC count (execution time 2000-3999 µs): 5
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 169
Hard pagefault count of hardest hit process: 45
Highest hard pagefault resolution time (µs): 105626.478750
Total time spent in hard pagefaults (%): 0.085011
Number of processes hit: 7

_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 40.369303
CPU 0 ISR highest execution time (µs): 176.726250
CPU 0 ISR total execution time (s): 1.33610
CPU 0 ISR count: 519603
CPU 0 DPC highest execution time (µs): 2134.706250
CPU 0 DPC total execution time (s): 34.203831
CPU 0 DPC count: 2233801
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3.664366
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): 133.383750
CPU 1 DPC total execution time (s): 0.070439
CPU 1 DPC count: 25651
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6.242962
CPU 2 ISR highest execution time (µs): 159.390
CPU 2 ISR total execution time (s): 0.299012
CPU 2 ISR count: 24171
CPU 2 DPC highest execution time (µs): 2159.90250
CPU 2 DPC total execution time (s): 3.104864
CPU 2 DPC count: 87794
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4.506229
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): 87.131250
CPU 3 DPC total execution time (s): 0.205226
CPU 3 DPC count: 43891
_________________________________________________________________________________________________________

Tried that Leadfoot (& 3 days worth of everything)...is there an issue with these cards?
 
I'm peaking!

Thanx anyways...looks like it's a dead thread, RATS!

I have the same issue with X3.  It didn't exist with X2.

Hi,
Here's another latency monitor utility which may help you identify which process on your machine is introducing latency.
Russ 
 
http://www.thesycon.de/deu/latency_check.shtml
 

The real culprit seems to be:
 
Highest DPC routine execution time (µs): 2159.90250
Driver with highest DPC routine execution time: ohci1394.sys - 1394 OpenHCI Port Driver, Microsoft Corporation
 
That looks like a firewire driver. If you are not using the firewire interface, pull the firewire card out (if it is a separate card), or disable in BIOS. If your audio interface uses firewire, you will need to resolve the DPC latency by determining what else shares the interrupts for the firewire. If you are using a USB interface, you should not need the firewire port.
 
Regards,
Dan
 

If you're on a 64 bit OS it probably is a bit low.

turn off aim assist "X" if you haven't already, see if it helps

Oh, and one more suggestion - it's easier to get specific answers if you ask specific questions. "This is Not Good?" could be a thread about what to do if a cat pukes into your keyboard.

I have the same issue with X3.  It didn't exist with X2.


I have X3 and X2 on my home PC. They both do the Now Time marker thing.
 
It's worse in X3. It won't move in X3 until I stop moving the mouse. But only when the mouse is in Track View. If the cursor is outside the TV, no problem.
GREM


Interesting no glitch...thanx Grem...It's gotta be the NVidia card!


 

cake should publish a "known issues " list

dcumpian
Well, since you need the firewire port, you have to make sure it isn't sharing the same bus as the USB port that your mouse is plugged in to. If the firewire port is on a separate PCIe card, try moving it to a different slot. Otherwise, try moving the mouse to a different USB port, preferably one that is on a different bus.
 
If you can't resolve the issue by moving things around, and your firewire port is on the motherboard, I would suggest that you purchase a PCIe firewire card and disable the port on the motherboard.
 
Regards,
Dan
 

Not only is that an excellent point, but gives me an excuse to remind people that if you're going to buy a card for your mobo to get additional FireWire or USB ports, DO NOT get a combo card with both. Get one or the other. If you need both, get two cards.