Vorpx Service High Cpu Usage

Homepage Forums Technical Support Vorpx Service High Cpu Usage

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #220998
    drowhunter
    Participant

    im seeing 13% cpu usage, on the Vorpx Service, even though im not using Vorpx and it is not running.

    #220999
    Ralf
    Keymaster

    Might be some annoying AV program’s fault. if you happen to use anything else than Windows’ built in Defender, get rid of it.

    #221006
    subroutine
    Participant

    I had exactly the same issue with 24.1.0 when it was made available and I only have windows defender. Never figured out what was causing it so reverted back to 21.3.5, which works fine.

    #221073
    Benedict81
    Participant

    I’ve noticed this too, on my rig it hovers around 6% when nothing is running. Running the latest version 24.1 whatever… How do I revert back to earlier version? Might try that just because tinkering :) No AV, just Win Defender.

    #222104
    Warrie
    Participant

    Same issue here. CPU usage around 10%. I uninstalled Vorpx, hope this will get fixed in a future patch.

    #222108
    Ralf
    Keymaster

    Under normal circumstances the service should not consume any noteworthy CPU time.

    However, there currently is a fairly stupid bug that can occasionally cause this after lock/unlock, waking up from standby or similar events. Unless your issue is caused by something else, it should be fixed in the next update.

    If you still experience this issue in vorpX 25.1.2, which will be out shortly, let me know.

    #222112
    Warrie
    Participant

    Hi Ralf, I had the high CPU usage starting randomly, without my pc going to sleep mode. Suddenly I would hear my fans blow harder, I checked task manager and saw VorpX with a high CPU usage. One time it was even 90% usage. I only use the standard Windows Defender.

    #222113
    Ralf
    Keymaster

    I can’t really think of much else than the bug I described above, 90% sound particularly weird as that would mean the service used almost all your cores, which it never does. At worst it should occupy one core when said bug occurs. Let’s see how things turn out after the next update. Keep me posted once the next version is out.

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.

Spread the word. Share this post!