Mouse is jumpy after forced Creators Fall update

[snadge]

Hi

every time I sleep my PC then wake it the mouse is jumpy all over the place and can not be used, I have to shutdown & restart the machine?? - its only started since the Fall Creators Update was forcibly installed by Windows 2 days ago, I did install this update a month back but had problems with it so reversed it with my backup images... now 2 days ago windows installed the update without my consent as they are rolling it out now, ever since when I sleep the PC it does this, I need to use sleep too as I use a RAM drive and don't want it writing to my drive every time I shut down, faster startup too...

I've done some research and this seems to be very common and other people are reporting that its the sound driver... but that is not the case here as I've uninstalled it (used windows driver) and installed the VIA Audio Driver and still the same...

Can anyone help?

thanks

 

[Rroff]

Can't help but I had similar but it went away after a couple of days of its own accord :s

I'd grab something like latencymon or some other DPC latency monitor as that might show spiking DPC latency and point at the problem driver.

 

[snadge]

Can't help but I had similar but it went away after a couple of days of its own accord :s

I'd grab something like latencymon or some other DPC latency monitor as that might show spiking DPC latency and point at the problem driver.

Good Idea... didn't think of that, thats what I love about forums - yeah I will get DPC Latency Checker and try and run it next time i wake it

 

[snadge]

I found another mouse (same one) installed twice in DevMgr so ive uninstalled the second one in the list....see how that goes... also it wasnt the CF update, it was just a Cumulitive one when i double checked it

 

[DAS]

If you want to revert to pre-Fall update, you can download a MS file that hides selected updates so it won't force the upgrade on you again.

 

[snadge]

well it hasnt worked and when i reboot it was doing it through windows logon, DPC Checker shows YELLOW constantly with 1090 microseconds on idle...not Ideal!

I need to know how to prevent updates being installed as Im gunna have to revert to reimaging my drive AGAIN (100GB of writes to my SSD every time) and disable updates... or i may install windows 7 as i loathe ten with all its telemetry & constantly writing to disk

 

[snadge]

here are results from Latency Mon

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:00:55 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: MANICMINER
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: Gigabyte Technology Co., Ltd., H77M-D3H
CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 12248 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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): 583.619490
Average measured interrupt to process latency (µs): 8.744971

Highest measured interrupt to DPC latency (µs): 558.662078
Average measured interrupt to DPC latency (µs): 2.096804


_________________________________________________________________________________________________________
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): 137.230
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.063464
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.079392

ISR count (execution time <250 µs): 10655
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): 762.0850
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation

Highest reported total DPC routine time (%): 0.040720
Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 388.13 , NVIDIA Corporation

Total time spent in DPCs (%) 0.154066

DPC count (execution time <250 µs): 39755
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 6
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: latmon.exe

Total number of hard pagefaults 353
Hard pagefault count of hardest hit process: 347
Highest hard pagefault resolution time (µs): 27717.085938
Total time spent in hard pagefaults (%): 0.287771
Number of processes hit: 5


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.624094
CPU 0 ISR highest execution time (µs): 137.230
CPU 0 ISR total execution time (s): 0.175404
CPU 0 ISR count: 10625
CPU 0 DPC highest execution time (µs): 619.590
CPU 0 DPC total execution time (s): 0.285486
CPU 0 DPC count: 34826
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.150249
CPU 1 ISR highest execution time (µs): 66.130
CPU 1 ISR total execution time (s): 0.000597
CPU 1 ISR count: 30
CPU 1 DPC highest execution time (µs): 762.0850
CPU 1 DPC total execution time (s): 0.037843
CPU 1 DPC count: 3003
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.118306
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): 164.61750
CPU 2 DPC total execution time (s): 0.015049
CPU 2 DPC count: 1391
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.083333
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): 110.083438
CPU 3 DPC total execution time (s): 0.003168
CPU 3 DPC count: 541
_________________________________________________________________________________________________________

 

[yashiro]

Which mouse?