[Feature Request] Set Message-Signaled Interrupts

[chrcoluk]

I noticed this option when using it earlier, and it did confuse me, because on my system by "default" MSI is enabled on my Nvidia GPU, I left the box unticked and it was still enabled after updating the driver.

So the default is system based. The option should perhaps be renamed to "forcefully enable MSI", as on compatible system's MSI is enabled anyway.

 

[W1zzard]

Good idea, has anyone else noticed that this is on by default now?

 

[Coldblackice]

Yes, I've also been seeing it on by default now, and was wondering if I was the only one.

 

[eidairaman1]

Wow haven't had to deal with irql in a decade now

 

[Mussels]

Seems on by default with a negative number here, generic install without using Nvcleaninstall

 

[phaolo]

For me it wasn't MSI by default on Win7 with the old driver v419.17.
And Nvcleanstall with 466.77 failed to set it too, for some reason, so I had to use the MSI utility.

 

[W1zzard]

Win7

I think there's an issue with NVCleanstall + MSI on Windows 7, I have to admit I only tested on Windows 10, and assumed W7 would be the same

 

[phaolo]

I think there's an issue with NVCleanstall + MSI on Windows 7, I have to admit I only tested on Windows 10, and assumed W7 would be the same

If NVCleanstall created a log somewhere, I could check it.
Maybe that's because of the error I was getting about the registry access.

 

[trparky]

I keep getting this error message when trying to build a custom installation package.

Doesn't matter where I try to save it, it gives me that error message.

Edit
OK, it works fine if you save the resulting custom installation package into the same folder as NVCleanstall is installed in but anywhere else produces that error message. My suggestion is to remove the option to choose a location to save the file if it results in that kind of error message. Better to just save it a default location and be done with it and then allow the user to move it elsewhere after the Explorer window is opened to the location of the file.

 

[W1zzard]

My suggestion is to remove the option to choose a location to save the file if it results in that kind of error message

Seems to be a bug, should be easy to fix

 

[Tyr808]

So what's the consensus on which, if any, devices should be set to "High" priority?

And what might be any noticeable effects for something being set as "High" priority vs. undefined? In a best-case/worst-case scenarios, if necessary.

Were you ever able to figure this out? I did a ton of research and found an unsubstantiated claim that it was better, but that's about it.

I see that my samsung NVME drive is on high by default and everything else is undefined. I used to be the type to tweak damn near everything and I do love finding improvements but I'm also more careful about changing things I don't understand these days, haha.

 

[Chaython]

Were you ever able to figure this out? I did a ton of research and found an unsubstantiated claim that it was better, but that's about it.

I see that my samsung NVME drive is on high by default and everything else is undefined. I used to be the type to tweak damn near everything and I do love finding improvements but I'm also more careful about changing things I don't understand these days, haha.

It's far more important when using virtualization.
Setting high priority, simply means it's high priority, it takes priority over other interrupts. :s
When running windows in a kvm with vfio, msi interrupt tasking is important. Though enabling msi interrupts in default is more important than priority levels.
If you experience, more frequent audio popping/crackling, it's likely due to higher latency. If your random reads/writes in nvme storage is lower than expected it may be because of latency.
Setting MSI, allows the device to write an interrupt, without waiting for response, greatly reducing the hiccup/stutter.
Using VFIO/KVM without a dedicated io thread pin, had hitching in games. Setting MSI made it more stuttery than hitching. :x

 

[Edwired]

Quiet interesting to know why my gtx 1050ti oc is hitching and stuttering on Asus P6X58D-E. Just hoping if the MSI util fixes the problem. What happened to the github link and no sign of the v4 file can't seem to find it anywhere

 

[Aleqaiser]

Quiet interesting to know why my gtx 1050ti oc is hitching and stuttering on Asus P6X58D-E. Just hoping if the MSI util fixes the problem. What happened to the github link and no sign of the v4 file can't seem to find it anywhere

I looked around and apparently, the author's GitHub account was terminated.
He explained the situation on his GitLab account.

CHEF-KOCH / About my GitHub Account Termination · GitLab

Background why GitHub decided to hide my private Account from public. I post it to avoid people smearing my name with misinformation.

gitlab.com

 

[Oshim]

Hi everyone,

Hope I can wake up this thread again...

So I installed the NVIDIA latest driver (522.25) with MSI enabled through NVCleanstall.

I was wondering what those really high IRQ numbers meant - now I know, it's the MSI - below screenshot:

But my question is the following - is it better to keep the GPU with that crazy IRQ number or uncheck MSI in the MSI Utility . exe?

For example I had my HD Audio Driver at IRQ 16 and 17 and I disabled MSI for the GPU and enabled it for HD Audio Driver. The audio driver went to those crazy IRQ numbers and the GPU (RTX 3080) came at IRQ 16 which I feel should be the right place for it without any conflicts.

Please let me know if I am correct or wrong in my assumptions and if wrong please explain why.

Thanks!

P.S. My conflicts look like this, please let me understand if these are real conflicts or nothing to worry about:

 

[W1zzard]

It’s a negative number

 

[Oshim]

Thanks W1zzard, but does the GPU have to be on a negative number or not?

Thanks!

 

[W1zzard]

No idea if it "has" to be on a negative IRQ, I don't think so. Negative IRQ numbers indicate MSI is in use, not an error

 

[THU31]

@Oshim

Enabling MSI for my GPU has solved several issues for me, like stutters in certain games and frame skips during video playback (these showed up when I switched from Pascal to Turing).

Currently I enable it for all devices and see no reason not to. I also set high interrupt priority for the GPU and HD Audio Controller.

 

[Oshim]

@Oshim

Enabling MSI for my GPU has solved several issues for me, like stutters in certain games and frame skips during video playback (these showed up when I switched from Pascal to Turing).

Currently I enable it for all devices and see no reason not to. I also set high interrupt priority for the GPU and HD Audio Controller.

Does this look right...?

Also, shouldn't there be any device on the regular (positive number) IRQs?

 

[THU31]

Looks pretty much the same as mine.

This app only shows devices that support MSI, so if you enable MSI for all of them, they will all have negative IRQs. All devices that do not support MSI will have positive IRQs. I have not seen any recommendations to disable MSI for any of the supported devices.

 

[Sora]

For me the GPU is always in MSI mode automatically after installing the driver with this tweak.

Only the HD Audio Controller defaults to LineBased.

Nvidia doesn't install a HD Audio controller, it installs an Endpoint driver.

MSI will persist on this device across all nvidia driver updates.

Good idea, has anyone else noticed that this is on by default now?

only Geforce 30 series on desktop, Quadros and notebooks

 

[THU31]

Nvidia doesn't install a HD Audio controller, it installs an Endpoint driver.

MSI will persist on this device across all nvidia driver updates.

I always use DDU when updating drivers, so High Definition Audio Controller always resets for me (msi is unchecked and priority changes to undefined).

 

[Sora]

I always use DDU when updating drivers, so High Definition Audio Controller always resets for me (msi is unchecked and priority changes to undefined).

futile exercise.

 

[Assimilator]

My RTX 2070S on Win10 has MSI enabled but a positive IRQ, so the "negative IRQ == MSI enabled" correlation no longer seems correct.