Windows: Line-Based vs. Message Signaled-Based Interrupts. MSI tool.

It is. We should ask device manufacturer why max limit is 5 while actual number of IRQs is 11.

 

Max has to be implemented in the driver for a value to be respected.

 

It is possible that msi mode will give worse performance than standard mode?

 

According to reports in this thread it is possible.

 

How about nvme express driver limit is 257 but max limit is 33 should i change something?

 

Since actual number of IRQs is not equal to both limits just ignore them.

 

Hi Guys, I have a question is everything correct, do I have to modify anything?
Should i change standard nvm express controller from high to undefined ?
I am looking for the lowest latncey for fps games.
Thanks!

 

Looks fine.

 

(Someone correct me if I am wrong) *but*

as long as your NVME is above Gen2 then the chances of any significant or even noticeable reduction in your end-to-end system latency is closer to 0% than 1%

Once DirectStorage is used by devs, we may get a chance to actually experience Gen4's speeds


@mbk1969 I thought it was your recommendation to leave the Priorities as-is if its default value is 'defined'

 

Even shorter - to leave the Priorities as-is.

 

I've seen a couple videos from this guy here n there and overall I think he's got a good track record,
but if he's recommending this to 100,00's of people he really should benchmark compare (on vs off) before someone like me starts head-casing about it, don't you think?



nice little shout out for you. Well deserved!
(I don't think the video starts at the point i set if it's embedded here. go right to 11:16 )

 

Problem with Priority tweak is we don`t know the details, the mechanics. And we don`t know how to estimate whether device drivers actually respect the tweak.
And of course, only extensive tests (on each rig) can show the effect of tweaks.

 

I have some new entries in msi_util_v2, which never used to be there!

E.g. first is pci-e controller, but if msi is already on for GPU, would there be any need to turn this on a wonder? I don't want to experiment with that!

Rest don't remember what is for...

 

If all is working then do not touch PCI-E controller. And better use v3 of MSI tool.

 

So uh, somewhat unrelated but this is a PSA warning to at least those with Intel I225V NICs and who recently upgraded from old 1.x.x.x drivers to the latest 2.1.1.7 or similar versions.

Assigning interrupt affinity of the NIC to say only the P cores of a 12900k (threads 0 thru 15) will result in BSOD when booting up Win11 with a "System thread exception not handled" error.

Apparently the new drivers either have a bug or don't allow overriding of thread/core affinity masks...

Good thing System Restore works decently.

 

the NetAdapterCX drivers are faulty anyway, they randomly enter error state (Resource available Error) and cease working.

the latest Wired Driver package includes both versions, so just use the latest 1.x.x.x and its rock solid.

 

I just updated my 1225v3 controller with latest (1.1.3.28) version, seems good. I am on Win10 so I think the 2.xxx versions are Win11 only.

 

Interesting. What symptoms would a user notice, e.g., intermittent LAN disconnection, latency spikes?
Would we be able to see (or configure to see) the errors in some Event Viewer log?

I'm just curious because I haven't seen any issues (other than interrupt affinity per above) after a couple days of using the 2.1.1.7 driver. *knock on wood*

 

Mine!!!!i put all msimode

 

Do you actually connect some storage device to SATA controller?
Do you actually connect some USB device to ASMedia USB controller?
If not then you can disable them n BIOS.