Question / Help Realtemp says 100% cpu usage, Task Manager says 0%

[Haliinen]

Hi, I don't know where to get help regarding this issue but I'm giving it a chance here in case someone else has experienced the same thing.

I recently got a Micomsoft SC-512N1-L capture card and it works great, it functions normally and everything is good. But when the capture card is initialized, RealTemp (a CPU temp monitoring program) reports a CPU usage of 100% whilst Windows Task Manager reports 0%, what should I believe? This does not only happen in AmaRecTV, it happens anywhere as long as I initialize the capture card somewhere, be it in OBS, XSplit, etc.. The CPU usage goes back to normal again in RealTemp when I close AmaRecTV or remove the source from OBS or XSplit.

Anyone got a clue what is going on? RealTemp may be buggy perhaps? This worries me a slight bit. D:

Peace

EDIT: CPU-Z 1.67.1 reports the same thing as RealTemp btw.

 

[Haliinen]

Okay, so a bit of research when I initialize the capture card it prevents the CPU from entering the low power C1 state (which is the idling state)... It could perhaps be poor drivers but is there a way to prevent this from happening? I tried to change the power plans while running AmaRecTV but it didn't help unfortunately.

EDIT: lol, i fixed it by getting the latest drivers from their website, then changing the power plans helped!

 

[Lain]

Hey haliinen, haven't seen you in a long time (which may be a good thing because being on the forums usually means something's wrong). Thanks for letting us know what is was though, glad it was fixed. Micomsoft actually makes some really good devices usually.

 

[Haliinen]

Hey haliinen, haven't seen you in a long time (which may be a good thing because being on the forums usually means something's wrong). Thanks for letting us know what is was though, glad it was fixed. Micomsoft actually makes some really good devices usually.

Hello Jim! Yes, I was very confused by this! And yes I haven't been on the forums a lot the past 6-7 months! I'm overwhelmed by this capture card, I'm glad I waited out until something like this was released. A moderator recommended me to get this capture card and I did and I can't be thankful enough to him for letting me know a capture card like this existed. I tried searching around for newer drivers on the Internet, but couldn't find them, then I tried harder and finally found them. So if anyone else has this issue just get the latest drivers, change power plans while AmaRecTV (or any other software) is running and you're good to go. So yeah the drivers were to blame, I'm happy they sorta fixed it anyway!