Computer CPU0 core 100%, Audio cracks and dpc/isr latency - System interrupts

[cwsink]

I've been trying to get a better grasp of what frametime measures and what might affect it. This video seems like a good summary of what I'm understanding it to be and what sort of system attributes need to be considered to optimize the frametime. Have you already tried what is described in the video?

I'm really not seeing anything in the trace that suggests your system is struggling but the traces aren't capturing GPU peformance data. I suspect some detailed optimization of graphics settings is what is needed.

 

[Delta280]

I've been trying to get a better grasp of what frametime measures and what might affect it. This video seems like a good summary of what I'm understanding it to be and what sort of system attributes need to be considered to optimize the frametime. Have you already tried what is described in the video?

I'm really not seeing anything in the trace that suggests your system is struggling but the traces aren't capturing GPU peformance data. I suspect some detailed optimization of graphics settings is what is needed.

Hey so a couple of things happened while I was trying to use Media eXperience Analyzer. I noticed Battlefield V wasn't running as well, and I went to go check task manager and yet again, my CPU0 core was being maxed out. I thought this was Battlefield V doing it, so I exited to desktop and it was still being utilized by the process system interrupts. This problem hasn't happened since before August 28th, and I'm stunned that it's happening now given I did absolutely nothing except the trace, which seems odd as I have made traces before without this issue getting brought up (I don't think the traces are causing this problem). Anyways, I will use DDU and update my drivers as I now know the issue is still present and perhaps my drivers are corrupt.

Here is my trace using the profile for Media eXperience Analyzer in Battlefield V: Media eXperience Analyzer Trace.zip

Here is task manager when I was playing Battlefield V: Screenshot
Here is process explorer showing the kernal time for cpu cores when I was playing Battlefield V: Screenshot

Here is task manager when I was at desktop: Screenshot

 

[Delta280]

I've been trying to get a better grasp of what frametime measures and what might affect it. This video seems like a good summary of what I'm understanding it to be and what sort of system attributes need to be considered to optimize the frametime. Have you already tried what is described in the video?

I'm really not seeing anything in the trace that suggests your system is struggling but the traces aren't capturing GPU peformance data. I suspect some detailed optimization of graphics settings is what is needed.

I caught a trace at desktop with not much running in the background with the system interrupts process happening: general.etl.zip. Also, I tried to update to new drivers but to no avail. My colors actually changed, which was a common issue I was having when I upgraded to Windows v1903. This problem was discussed here:

https://www.reddit.com/r/Windows10/comments/bfbovn/_/elgn92k

. Although thats not really a priority right now, its strange since the cursor problem doesn't happen on driver version 436.08, but on 436.48 it does.

 

[Delta280]

I've been trying to get a better grasp of what frametime measures and what might affect it. This video seems like a good summary of what I'm understanding it to be and what sort of system attributes need to be considered to optimize the frametime. Have you already tried what is described in the video?

I'm really not seeing anything in the trace that suggests your system is struggling but the traces aren't capturing GPU peformance data. I suspect some detailed optimization of graphics settings is what is needed.

Alright sorry for the many replies, disregard the info about the color changed I talked about in the last post. Colors are normal on latest drivers, but still getting the cpu0 core maxed out:

 

[Delta280]

I've been trying to get a better grasp of what frametime measures and what might affect it. This video seems like a good summary of what I'm understanding it to be and what sort of system attributes need to be considered to optimize the frametime. Have you already tried what is described in the video?

I'm really not seeing anything in the trace that suggests your system is struggling but the traces aren't capturing GPU peformance data. I suspect some detailed optimization of graphics settings is what is needed.

Hello? I am having the system interrupts problem after upgrading my graphics card driver. Any help would be appreciated as this thread hasn't been replied to in over a month.

 

[cwsink]

There will be a performance hit while capturing a trace but I’ve never seen it be the cause of an interrupt storm. As far as the latest general.etl file, it's very much the same as the “trace (2).zip” etl file from your original post. There are an excessive number of interrupts being generated on core 0; over 12 times as many ISRs as DPCs being generated which seem to be coming from both the GPU and audio components. I'm not sure it's relevant but the trace configuration properties suggest your computer has setup the RTX 2060 and an Intel audio device to share an IRQ (16). Although not ideal it really shouldn’t be a problem in and of itself - but it does make me wonder if there’s a correlation.

Is your system using Intel audio, Realtek audio, or something else? Have you tried uninstalling/reinstalling the audio software/drivers? I’m wondering if doing so might cause IRQ 16 to no longer be shared. If that doesn’t help, I’d suspect a faulty GPU that is acting up intermittently and try a different GPU to see if the problems stop. Have you tried the system with the old GPU since your original post?

 

[Delta280]

There will be a performance hit while capturing a trace but I’ve never seen it be the cause of an interrupt storm. As far as the latest general.etl file, it's very much the same as the “trace (2).zip” etl file from your original post. There are an excessive number of interrupts being generated on core 0; over 12 times as many ISRs as DPCs being generated which seem to be coming from both the GPU and audio components. I'm not sure it's relevant but the trace configuration properties suggest your computer has setup the RTX 2060 and an Intel audio device to share an IRQ (16). Although not ideal it really shouldn’t be a problem in and of itself - but it does make me wonder if there’s a correlation.

Is your system using Intel audio, Realtek audio, or something else? Have you tried uninstalling/reinstalling the audio software/drivers? I’m wondering if doing so might cause IRQ 16 to no longer be shared. If that doesn’t help, I’d suspect a faulty GPU that is acting up intermittently and try a different GPU to see if the problems stop. Have you tried the system with the old GPU since your original post?

My system is using realtek high definition audio. I recently noticed there was also another high definition audio device, so I disabled that as well.

About the gpu, I'll need to try it this weekend when I get the chance. It's strange though that it would be a hardware problem since sometimes it's running fine. In that month period I was NOT encountering the problem, but a day after I installed the Nvidia RDR2 game ready driver, the problem came back after about an hour of cpu uptime.

 

[Delta280]

There will be a performance hit while capturing a trace but I’ve never seen it be the cause of an interrupt storm. As far as the latest general.etl file, it's very much the same as the “trace (2).zip” etl file from your original post. There are an excessive number of interrupts being generated on core 0; over 12 times as many ISRs as DPCs being generated which seem to be coming from both the GPU and audio components. I'm not sure it's relevant but the trace configuration properties suggest your computer has setup the RTX 2060 and an Intel audio device to share an IRQ (16). Although not ideal it really shouldn’t be a problem in and of itself - but it does make me wonder if there’s a correlation.

Is your system using Intel audio, Realtek audio, or something else? Have you tried uninstalling/reinstalling the audio software/drivers? I’m wondering if doing so might cause IRQ 16 to no longer be shared. If that doesn’t help, I’d suspect a faulty GPU that is acting up intermittently and try a different GPU to see if the problems stop. Have you tried the system with the old GPU since your original post?

Also before I switch gpus should I use ddu, shutdown, and then switch gpus or get the system interrupts problem occur and then switch gpus?

 

[Delta280]

There will be a performance hit while capturing a trace but I’ve never seen it be the cause of an interrupt storm. As far as the latest general.etl file, it's very much the same as the “trace (2).zip” etl file from your original post. There are an excessive number of interrupts being generated on core 0; over 12 times as many ISRs as DPCs being generated which seem to be coming from both the GPU and audio components. I'm not sure it's relevant but the trace configuration properties suggest your computer has setup the RTX 2060 and an Intel audio device to share an IRQ (16). Although not ideal it really shouldn’t be a problem in and of itself - but it does make me wonder if there’s a correlation.

Is your system using Intel audio, Realtek audio, or something else? Have you tried uninstalling/reinstalling the audio software/drivers? I’m wondering if doing so might cause IRQ 16 to no longer be shared. If that doesn’t help, I’d suspect a faulty GPU that is acting up intermittently and try a different GPU to see if the problems stop. Have you tried the system with the old GPU since your original post?

Also before I switch gpus should I use ddu, shutdown, and then switch gpus or get the system interrupts problem occur and then switch gpus?

 

[cwsink]

I'd just swap the GPUs and see if PNP can resolve the changes correctly. If Device Manager shows problems with the GPU then use DDU in safe mode followed by an install of the latest Nvidia driver. If the problems continue with the old GPU please make another trace using that GPU. The general trace seems to be able to show the interrupt problem so it should be sufficient.

 

[Delta280]

I'd just swap the GPUs and see if PNP can resolve the changes correctly. If Device Manager shows problems with the GPU then use DDU in safe mode followed by an install of the latest Nvidia driver. If the problems continue with the old GPU please make another trace using that GPU. The general trace seems to be able to show the interrupt problem so it should be sufficient.

Ok will do, and thanks again! I get all nervous when opening my PC, and if I do have to RMA I'm worried that evga won't do it since if had the card since late June

 

[Delta280]

I'd just swap the GPUs and see if PNP can resolve the changes correctly. If Device Manager shows problems with the GPU then use DDU in safe mode followed by an install of the latest Nvidia driver. If the problems continue with the old GPU please make another trace using that GPU. The general trace seems to be able to show the interrupt problem so it should be sufficient.

Update: checked what sound I have manufacturers (HP) website, and it says: integrated audio

• Audio Codec: ALC3863-CG
• High Definition (Azalia) 5.1 channel audio support
• Audio jack presence detection

 

[cwsink]

Do you remember where you got the audio driver you're currently using? It appears to have a timestamp of 8/24/2017 (version 6.0.1.8237) but the most recent version available on the HP product support page for your computer has a timestamp of 9/19/2016 (version 6.0.1.7936). Newer is usually better but not always. Did you use HP Support Assistant? It might have a newer version not available on the support site which got installed. Or maybe Windows Update has a newer version that it installed. If it was Windows Update I'd be tempted to give you a link to an even newer installer although I'm not 100 percent certain it will work for your audio components.

 

[Delta280]

Do you remember where you got the audio driver you're currently using? It appears to have a timestamp of 8/24/2017 (version 6.0.1.8237) but the most recent version available on the HP product support page for your computer has a timestamp of 9/19/2016 (version 6.0.1.7936). Newer is usually better but not always. Did you use HP Support Assistant? It might have a newer version not available on the support site which got installed. Or maybe Windows Update has a newer version that it installed. If it was Windows Update I'd be tempted to give you a link to an even newer installer although I'm not 100 percent certain it will work for your audio components.

I used realteks main website to update, but I'll try to use what was on hp's website as well (here is a link to driver downloads for my PC: HP ENVY Desktop - 750-427c Software and Driver Downloads | HP® Customer Support)

 

[cwsink]

There have been audio issues on some systems after a major Windows 10 update gets installed. I had such a problem going from 1709 to 1803, if I recall correctly. I was able to fix it by using a driver package from the Microsoft Update Catalog. It requires downloading, unpacking, and then updating the driver through Device Manager if you're comfortable doing that. The package is here (version 6.0.8791.1) but like I said before, I'm not 100 percent sure it's compatible with your device. If it's not, the Device Manager installation process should just give a message along the lines of "Windows has determined that the best driver for this device is already installed." I used 7-Zip to unpack the cab file. I'd imagine other tools can also unpack cabs but I haven't tried any others.

edit: This video shows the process but the links it lists are outdated.

 

[Delta280]

There have been audio issues on some systems after a major Windows 10 update gets installed. I had such a problem going from 1709 to 1803, if I recall correctly. I was able to fix it by using a driver package from the Microsoft Update Catalog. It requires downloading, unpacking, and then updating the driver through Device Manager if you're comfortable doing that. The package is here (version 6.0.8791.1) but like I said before, I'm not 100 percent sure it's compatible with your device. If it's not, the Device Manager installation process should just give a message along the lines of "Windows has determined that the best driver for this device is already installed." I used 7-Zip to unpack the cab file. I'd imagine other tools can also unpack cabs but I haven't tried any others.

edit: This video shows the process but the links it lists are outdated.

Yeah if I'm not mistaken the system interrupts issue was not present on windows v1703. 1803 and 1903 have the issue present. I upgraded so I could utilize rtx capabilities and now RDR2 requires v1903.