UI Lagging after computer left running overnight

[Section 8]

Hi guys, I could really use some help here as I'm kinda at a loss for what might be happening here.

 

About two months ago or so, all gfx effects and animations started showing a significant animation lag after I left my computer on overnight. The issue is totally resolved after a reboot, and the system is snappy again. I usually run folding@home overnight, but I've tested it without running folding and the issue still persists.

 

After heaps of investigation, looking at thermals, and quitting processes etc, I managed to rectify the issue by ending the desktop windows manager task (dwm.exe). I saw there is another thread here but it seems in that thread they can actually see GPU usage in terms of % utilization.. For me, there was no GPU usage for the process (1-2%), but it was taking up by far the largest GPU memory of all my processes (400 MB or so at the time) so I figured "what the heck" and killed the process. Suddenly everything was all snappy again.

 

What could possibly be killing the dwm.exe process so much where all UI responsiveness becomes sluggish?

 

Any further steps to narrow down the issue? I'm using the latest NVIDIA drivers and fully patched windows 10.

 

 

Here is my system:

 

Ryzen 3600 (no OC)

16 GB Vengence Pro 3600 (XMP profile enabled)

Corsair RM 750i PSU

Corsair H100i Pro AIO

GTX 1070 (a mild OC on the card here but the issue happens without the OC as well)

Gigabyte X570 Aorus Elite Wifi 

[DailyProcrastinator]

Not sure what could be exactly causing this, but this is why IT loves asking you if you turned it off and back on again. I don't know that I would worry about it. 

[Section 8]

23 hours ago, TheDailyProcrastinator said:

Not sure what could be exactly causing this, but this is why IT loves asking you if you turned it off and back on again. I don't know that I would worry about it. 

 

Hey, thanks for the reply. I'm not worried about it per-se in the sense that its something critical that's stopping anything from running, but it is a huge pain in the ass to have to reboot every morning in order for any program to respond in a timely manner instead of looking like every action has 500ms of lag / that I'm running a remote desktop session.

 

I guess the surefire way to get around it is to just reinstall windows, but I was hoping to be able to track down the issue so it doesn't happen again in the future.

 

Along the same lines and around the same time, my computer curiously stopped being able to enter in an idle state. My screens no longer turn off and my folding@home no longer activates automatically using the "on idle" flag.

 

I ran the below and found that my realtek audio drivers are popping up. Could be because i'm "listening" to the line in port, but haven't quite tested it.

 

I've tried to run an override using

powercfg -REQUESTSOVERRIDE DRIVER "Realtek High Definition Audio" SYSTEM

but this still does not allow my computer to enter idle.

 

I feel like there is some sort of process gone rogue that could be causing both issues, but I cant for the life of me find it. Any suggestions would be really great.

 

 

[DailyProcrastinator]

On 7/4/2020 at 10:05 PM, Section 8 said:

 

Hey, thanks for the reply. I'm not worried about it per-se in the sense that its something critical that's stopping anything from running, but it is a huge pain in the ass to have to reboot every morning in order for any program to respond in a timely manner instead of looking like every action has 500ms of lag / that I'm running a remote desktop session.

 

I guess the surefire way to get around it is to just reinstall windows, but I was hoping to be able to track down the issue so it doesn't happen again in the future.

 

Along the same lines and around the same time, my computer curiously stopped being able to enter in an idle state. My screens no longer turn off and my folding@home no longer activates automatically using the "on idle" flag.

 

I ran the below and found that my realtek audio drivers are popping up. Could be because i'm "listening" to the line in port, but haven't quite tested it.

 

I've tried to run an override using

powercfg -REQUESTSOVERRIDE DRIVER "Realtek High Definition Audio" SYSTEM

but this still does not allow my computer to enter idle.

 

I feel like there is some sort of process gone rogue that could be causing both issues, but I cant for the life of me find it. Any suggestions would be really great.

 

 

 Yeah definitely a bit of an inconvenience for sure. I've had semi weird issues with my XPS in the past when I upgraded the m.2, it was related to Intel storage drivers, and the update kept failing. The ONLY fix was running prompts to end the process, but the final true fix was a complete fresh install of Windows 10 that then allowed for the install of the latest drivers. 

 

Other than trying to uninstall and re-install related drivers the only other fix may be a complete fresh install pf Windows unfortunately. Any other fix in my mind would likely be more of a time commitment anyways, just annoying to deal with though. 

 

This is why Linus is much better. Kinda amazing how Windows continues to have many issues, although IMO the overall Windows 10 usability and experience has gotten a lot better in the last 2-years, but stuff like this is very frustrating.

[Section 8]

1 hour ago, TheDailyProcrastinator said:

 Yeah definitely a bit of an inconvenience for sure. I've had semi weird issues with my XPS in the past when I upgraded the m.2, it was related to Intel storage drivers, and the update kept failing. The ONLY fix was running prompts to end the process, but the final true fix was a complete fresh install of Windows 10 that then allowed for the install of the latest drivers. 

 

Other than trying to uninstall and re-install related drivers the only other fix may be a complete fresh install pf Windows unfortunately. Any other fix in my mind would likely be more of a time commitment anyways, just annoying to deal with though. 

 

This is why Linus is much better. Kinda amazing how Windows continues to have many issues, although IMO the overall Windows 10 usability and experience has gotten a lot better in the last 2-years, but stuff like this is very frustrating.

 

To be honest, I would probably be running linux if it wasn’t for gaming. I know linux gaming has gotten much better, but it still isn’t quite there in terms of polish and Nvidia support.

 

*sigh* was hoping to avoid a re-install.

 

no last ditch suggestions?

[DailyProcrastinator]

On 7/6/2020 at 1:46 AM, Section 8 said:

To be honest, I would probably be running linux if it wasn’t for gaming. I know linux gaming has gotten much better, but it still isn’t quite there in terms of polish and Nvidia support.

Yeah I agree, and I have become decently immersed in the Microsoft ecosystem especially with work. 

 

On 7/6/2020 at 1:46 AM, Section 8 said:

*sigh* was hoping to avoid a re-install.

 

no last ditch suggestions?

Other than the un-install and re-install of the problem drivers I can't think of any other logical fix unfortunately. A very annoying solution of course.

[Section 8]

2 hours ago, TheDailyProcrastinator said:

Yeah I agree, and I have become decently immersed in the Microsoft ecosystem especially with work. 

 

Other than the un-install and re-install of the problem drivers I can't think of any other logical fix unfortunately. A very annoying solution of course.

 

alright then, thanks for the help!

[DailyProcrastinator]

39 minutes ago, Section 8 said:

alright then, thanks for the help!

No worries, hope you get it sorted out!

[Section 8]

On 7/8/2020 at 11:23 AM, TheDailyProcrastinator said:

No worries, hope you get it sorted out!

So, I was a bit stubborn and tried to fix the damn thing and I think I found the culprit. I've got a few attached internal drives and turns out one had completely failed.

I looked at the event viewer and found that I was getting series of warnings stating "The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000043) was retried"

 

Checked out the disk management utility, turns out disk3 was uninitialized and couldn't be mounted.

 

Found disk3, unplugged the SATA and power cables, and then tested out running the system overnight and folding@home. morning came along, and it was just as snappy as when I left it.

[DailyProcrastinator]

12 hours ago, Section 8 said:

So, I was a bit stubborn and tried to fix the damn thing and I think I found the culprit. I've got a few attached internal drives and turns out one had completely failed.

I looked at the event viewer and found that I was getting series of warnings stating "The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000043) was retried"

 

Checked out the disk management utility, turns out disk3 was uninitialized and couldn't be mounted.

 

Found disk3, unplugged the SATA and power cables, and then tested out running the system overnight and folding@home. morning came along, and it was just as snappy as when I left it.

Awesome, I mean I knew the issue was potentially solvable without a fresh OS install, but it was just something that required more digging, and my guess was that it could take more time over an OS re-install, bu glad you sorted it out!