Motherboard Monitor is a resource HOG!
 

For some reason, MBM only uses around 4,900K when I start it, but each day it runs, it uses up more and more resources. The other day, after 1 week of it running, I noticed it was using up 191,000K and my PC was going way too damn slow because of it. I shut MBM down and then started it again and it was at 4,900K and my PC sped up again. Just now I checked it and it was around 58,000K, so I shut it down and restarted it.

I'm wondering why it continues using more resources the longer it runs, and if anyone else has this same problem.

:confused:

Memory leak?

I checked the bottom of my case and I don't see any memory juice, so I don't think that's the problem. :p

It probably keeps a running total or somethin and each time you run it, it keeps on storing the info. If you can, see if you can get a control panel for the program and turn off some of the logging or what not. Just an uneducated guess.

Yeah, I'd say that some type of log is being stored.

Either way, are you overclocked or something? I never use mobo monitors unless I'm overclocking and am testing out CPU temps while being under loads, etc. I'd uninstall it if ya can't find the problem. I think the program WCPUID keeps a lot of mobo info and is much less of a resource hog. I don't know which info you want from the monitor, so it might not help. :(

-Lasereth

Lasereth, I like to keep MBM running all the time simply because I'm a temp freak and always keep an eye on that. I'm not overclocking, but I run my fans low to keep them quiet so they don't cool as much as they could. As soon as I get my new end table PC mod done, it should be so silent that you won't be able to hear anything at all, so I might crank up the fans and turn off MBM if I can't fix the problem with it.

a memory leak is where a program claims memory to do something, and doesn't release it properly. it does the same thing over, and grabs more memory, and doesn't release it... etc etc... eventually you run out.

long and short of it, use a diff program & see if that helps. may be an inherent flaw in your software.

It's a bug in MBM. I used to use it but had the same problems you had.