RMClock uses too much CPU

With my P8400, RMClock uses 5+% of the CPU all the time, almost definitely because of the monitors. Is there any way to disable those?

 

You can make it refresh less, I dont think you can completely disable though.

If you have a flat voltage curve, use throttlestop instead of RMclock.

Throttlestop uses way less CPU.

 

Does it even make a difference in performance at all?

 

After reboot it is only using 1-2%, but I'd still like to know how to make it refresh less.

 

It seems like after my computer crashes do to the voltage being to low, upon reboot rmclock uses a lot more of the CPU.

Also, I can run the stability test orthos for hours, but it isn't until after I stop it and start doing regular stuff does the computer crash when the voltage is too low.

 

On my T5550 task manager reports that RMClock CPU usage hovers between 0 and 1% with only 5M mem usage, so I would say not significantly.

 

Even with all monitors enabled on my laptop, my RMClock CPU usage is less than 1%. Are you sure your voltage settings, or even RMClock, is responsible for the system crashing?

 

Oh definitely. When I said that it crashes after I stop it, it is within several seconds after I stop it that it crashes.

I also think that a lot of the CPU usage is due to the program stepping up or down the clocks, which doesn't happen when the CPU is at full load, so there shouldn't be much performance detriment.

 

If you disable RMClock from running at all (boot w/o RMClock), will the computer continue to run after being stressed?

 

I think I figured it out. My clock speed will periodically jump to like 2.5GHz and I think it is at these instances that sometimes cause the BSOD. I modded an RMClock registry file so it thinks my top multiplier is 9x, and it registers a 9x multiplier when the clock jumps to 2.5GHz. However, 9x would only be around 2.4GHz.

 

I take that back, it is jumping to around 2.4GHz which is what it would be for 9x multiplier. So my crashing happens at one of these instances, which occur frequently when I run furmark.