Windows audio device graph isolation ~ CPU overload handles bug

Razer.Speedcr0ss
Hey there! That is odd. We don't have any ongoing issue with our Razer Synapse 3.0 similar to that. Is it still happening after reinstalling your computer's operating system and Razer Synapse 3.0? We recommend submitting feedback by clicking your Razer Synapse 3.0 profile photo at the top-right corner so our Development Team will be notified.

It very much is still going on. I reinstalled it completely with installing this time only Razer Synapse 3.0 (before I had both Razer Synapse 2.0 and 3.0). And shortly it occured again, spiked up to 200 000+ and after forced closed the WADGI (Windows audio device graph isolation) and it's back to 68 000. However there is a very strange thing that I have no explanation for.. My windows cannot shutdown itself fully, I have completely no idea why. When I shutdown my computer, then turn it back on, the time that it's staying up always stays, so it can end up up to 3 days even tho I shut it down for like 8 times in that whole time. But when restarting it, then it seems to work (sometimes).

I'm not gonna go ahead and say that it must be something to do with razer but I have nothing else that may enhance the sound other than the EQ I'm using through Razer Synapse. And that seems to be the only thing that the bug occurs over with. And I have no hook ups on what is with the CPU up time so..

I'm gonna go ahead and contact the razer support through email to investigate this further with them. And try finding some other help on Tomshardware forum.

Razer.Speedcr0ss
It sounds like a hardware issue. By the way, are you using a Razer laptop? Does the delay in shutting down your PC happen even when Razer Synapse 3.0 is uninstalled? I'm about to say that you can use a previous System Restore point to isolate a possible software glitch, however, if you did the factory reset on your PC, then there's no point doing it. And yes, we recommend contacting our Support Team via email or Chat by clicking this link. Ensure to select your preferred country at the top-right corner of the page. Feel free to send me a PM should you need further assistance.

Hm I can't do a full test in regards of getting the handles bug. But I can rule out that razer Synapse 3.0 doesn't affect the corrupted shutdown. (It's not a delay but more of a stasis where it doesn't reset the timer for an unknown reason. as of now it shows over a day of up time even tho I just shutdown 2 times fully the whole system.) So it might not even be Razer at all and that is slightly good to know..
But if it's the hardware, then that could be a problem.
Oh and no, I'm using my own put together computer.

Razer.Speedcr0ss
Thanks for confirming this with us. But hey, we're hoping that your PC it still okay. Please run MSConfig, and select "Service Tab" and click on "Hide All Microsoft Services box" at the bottom left then click apply. Click on "Start-up Tab" and click on "Open Task Manager" and select "Startup Tab" and disable all non-Razer and Microsoft programs and restart your PC. Please refer to the screenshots below and see if it helps:

Alright, so I did pretty much exactly like that and made some screenshots of it too.

But it pretty much didn't do anything at all. Just some how increased amount of Handles after restarting it without services that I disabled..

1# https://imgur.com/ZHBUloY Before shutdown
2# https://imgur.com/YxI7KOy After shutdown

I've already posted this problem regarding corrupted shutdown and the weird handles bug on Tomshardware forum. So far no response there..

However I can say that as far as the week went after I posted here, the handles bug hasn't repeated yet. Only the corrupted shutdown is still there..

Razer.Speedcr0ss
Gotcha! Thanks for the images. Have you tried disabling the remaining services after clicking the "Hide Microsoft Services" under your Startup tab? If the issue persists, please contact Microsoft and to get more conclusive information about the issue. I would also suggest running a disk check and research on commands like DISM (Deployment Image Servicing and Management) and SFC (System File Check) to know if there is an error that is contributing to your computer's shutting down behavior.

Good idea actually, I will contact them.

But I did the scans and it found nothing at all. And no I haven't disabled all the services as it probably wouldn't be such a good idea maybe..