Extremely high cpu usage (please help)

I’ve been getting extremely high CPU usage and the game is literally unplayable. The Game ran smooth and all very good during season 5 but with this new DLC everything is not only stuttery but to the point of freezing and unplayable, I literally can’t play the game because of this.

Task manager is showing = 100% CPU Usage , while HWMonitor is showing = 73.5% CPU Utilization

Something is clearly wrong, thing is, I noticed a post on reddit about a reinstall fixing the problem, but it didn’t work for me. link

Now, I’m pretty unsure on what’s going on with the Diablo IV game but if I remember correctly ‘Diablo IV’ didn’t show as ‘Diablo IV Retail’ to me before…

RES Tested: 1080P DLAA, DLSS Performance, DLSS Quality
QUALITYs Tested: MID, HIGH, LOW
FPS CAP tested: 200, 150, 120, 100 (I use to play around 180+fps no problems) now It still reaches, but its unplayable due to the huge freezes/stutter due to the cpu being 100%, and even if I put a 100 fps cap, it still is unplayable…

PC SPECS:
PROCESSOR: INTEL I5 13400F 13TH GEN
MOTHERBOARD: AORUS B660 MASTER DDR4 RGB
RAM: KINGSTON FURY DDR4 RGB 3200MHZ 16GB
GPU: EVGA FTW3 ULTRA GEFORCE RTX 3080 10GB

NVME: WESTERN DIGITAL BLUE SN550 NVME 2TB (using this)

2 Likes

I had an identical issue on my gaming laptop way back in Season two. One thing to test would be to go into your power options in windows and change your max processor state to less than 100%. I dont recall what I had used that worked but start with 95%. It should prevent the game from full maxing cpu utilization and stop the whole system from choking. Let me know what happens. I will try to look up my old post about it from back then.

1 Like

This was my post back then. Looks like I went with 90% on max state for CPU. Worth a try as its a 2 second setting change. Let me know if there is any questions.

3 Likes

I’m going to try this, but I do remember having it change before a long long time ago.
it’s set to 99% currently , I’m trying both 90% and 95% now

edit: Tried this. Is not this apparently, I place it at 90% and the cpu kept going to 100%, the same when using 95% of course.

I’m starting to believe this is a misscomunication between my cpu and the diablo IV game.

My pc can run other games super smooth including Wukong & Silent Hill 2

1 Like

Yeah i have the same issue. I’m at 100% cpu usage almost constantly with just Diablo. I’m going to try reinstalling the game later. I’m above the recommended specs so. Whether I have everything on low or everything on high it makes no difference.

Lowering your max frame rate should reduce CPU usage.

Your spec is similar to mine, and you’re right, it shouldn’t have the CPU pegged.

This is a longshot, but go into bnet, modify the game install to uncheck high-resolution textures. That lowers load more on the GPU but it will help CPU as well. The 3080 (I run one too) has a rough time on high-res textures.

Thanks this actually helped with my low end gaming pc. Im no longer 100% cpu usage

Same here, Solid 100pct CPU usage when logged in since the patches started for season 6. I have had disconnects porting to major cities since the launch of the game. Never had CPU issues though. Running an Intel I5 6500 and AMD RX 6600XT 32 GB Ram. I have tried everything from changing performance plan to setting all in game settings to low, uninstalled, reinstalled, modified install to not include high detail graphics. etc. I can log in and play, but I cannot use discord or any other chat software as the game isn’t leaving enough processing for anyone to hear me or for me to hear them. All other games from steam, epic and blizzard run without issue. CPU is not overheating nor is the graphics card. I do not know what else to try.

Last season someone had this issue and the fix that worked for them was deleting the Blizzard and Battle.net folders in %localappdata% and repairing the files after. It may require a reboot to take effect.

I appreciate the tip; however, it did not solve the issue with D4. Every other game I have runs with normal CPU usage except D4. Have a great weekend.

I’m experiencing the same issue. This only happens with D4 during the login. I’ve tested all my other Blizz games: SC, HOTS, WoW and Overwatch and also PUBG and all run great. However when I launch D4 I can make is as far as the character screen before my entire system becomes fully unresponsive. Started a few days ago.

@Sayer

Is it just your CPU usage or the temps also? Usually the two can be related and temps are more problematic.

You can check the temps with HWmonitor

If the temps are spiking, I posted this last week and it helped someone else, give it a try. You can always set it back. You will have to google the regedit to make it visible.

2 Likes

Update BIOS for new Intel Microcode Voltage and AVX2 workload adjustments, set new Intel Default profile in BIOS, change SVID Behavior from Intel Failsafe back to Auto, turn off Motherboard’s signature branded Auto Overclocking that is always set to on (Auto) by default without notifying the user, set XMP Profile if relevant, always use XMP II if multiple profiles are preset.

2 Likes

Haha I just remembered I forgot to check this setting :rofl:, but I think it is off, I remember vaguley wanting all overclocks off when I built the machine outside of the factory OC on my GPU.

1 Like

It should never be set to On or Auto by default. Motherboard Manufacturer’s should not be doing this, but they do anyway.

It blew my mind after fixing all this mess and then seeing my CPU pulling 1.1-1.2V max under heavy load with temps barely reaching 75c during a stress test.

1 Like

Oh I know it shortens the life of the processor. But my machine is always on…so there really has not been an opportunity to check the bios for me since the last thread.

Do it right now. Then it’s done and over with. If you hold Shift when you click restart you can use the Win10 boot options to reboot right into the bios on most systems.

It’ll say Reboot to UEFI

I’m on Win11Pro…but yeah I know how to get to it. I will probably need to do a Windows update at some point. Like I said I am about 80% sure I disabled it when I first booted up the machine.

Never hurts to be 100% sure of things.

1 Like