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

Discussion in 'Operating Systems' started by mbk1969, May 7, 2013.

  1. Chrysalis

    Chrysalis Master Guru

    Messages:
    373
    Likes Received:
    90
    GPU:
    RTX 3080 FE
    Hi, thanks for the updated file.

    I have bad news but also an interesting find.

    So the updated file is still the same problem, but then I decided to try the compatibility flags just to see if anything would happen.

    If I choose either win7 or win8 compatibility in exe properties it works, no message and I see all devices. This also on the previous v3 file as well.

    Given this works on my other 2 devices I have a feeling it is something I have done on this PC so I ask you to not worry too much about this, and I will try and find out what I may have done, and even if I cannot at least I have a workaround now.
     

    Attached Files:

  2. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    I can try one another thing. I made change in code that enumerates registry subkeys` names for PCI devices (first stage). Now I can try to change code which dives into individual subkeys (second stage). It will be quick (brb)...

    PS This can give you the idea on what registry key is "locked"...
     
  3. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
  4. Chrysalis

    Chrysalis Master Guru

    Messages:
    373
    Likes Received:
    90
    GPU:
    RTX 3080 FE
    I tried it again, it is the same, admin mode, has the error and limited devices, if I enable win8 compat mode it works normally. Thanks.

    I just started checking every device in registry, and found one that has no permissions stored, so we have the culprit, I will copy permissions from the rest and report back.
     

  5. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    OK.

    Problem is each device`s registry key has deep tree of children keys traversed by utility, like:
    VEN_10DE&DEV_10F8&SUBSYS_139F10DE&REV_A1
    4&170e5b98&0&0100
    Device Parameters
    Interrupt Management
    Affinity Policy
    MessageSignaledInterruptProperties​
    - each one can trigger the access error.
     
  6. Chrysalis

    Chrysalis Master Guru

    Messages:
    373
    Likes Received:
    90
    GPU:
    RTX 3080 FE
    I have fixed it as best as I can, and the app works again properly, thank you.

    The bad device was the nvme device, and I can work out how it got broken, a while back this driver got corrupted and I restored it using DISM and SFC, but I guess this didnt do the registry properly. I copied the permissions for each child key as you listed the same as whats in other devices, and everything seems good now, fingers crossed I didnt break anything else. :)

    Thank you for the time you spent on this.
     

    Attached Files:

    mbk1969 likes this.
  7. xen

    xen Guest

    Messages:
    1
    Likes Received:
    0
    GPU:
    RTX 2080 Ti
    My MSI mode settings will not save in MSI utility. Even upon restarting the program, all checkboxes are unchecked. Any ideas?
     
  8. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    1. If you are talking about "PCI Express Root Port" devices then do not touch them.
    2. Go to registry key related to particular device (double click on it in utility) and see whether "MSISupported" registry value (in "Device Parameters\Interrupt Management\MessageSignaledInterruptProperties" key) is changed with each click in checkbox (do not forget to refresh regedit window with value).
     
  9. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    @xen

    A sudden thought: do you actually click "Apply" button after you changed something - MSI checkbox or interrupt priority?
     
  10. Warkratos

    Warkratos Member Guru

    Messages:
    130
    Likes Received:
    149
    GPU:
    RTX 3060 Ti
    Just downloaded the v3 utility, when loaded, my devices are all in MSI mode, but all checkbox are unchecked, tried v2 and it is working fine. Noticed that if I check any of the checkbox on v3, my regedit opens for that device.
     

  11. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    Thanks. I managed to reproduce that on my work rig...
     
  12. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    fluffi444, empleat, MoKiChU and 2 others like this.
  13. Warkratos

    Warkratos Member Guru

    Messages:
    130
    Likes Received:
    149
    GPU:
    RTX 3060 Ti
  14. Risedo

    Risedo Member

    Messages:
    16
    Likes Received:
    1
    GPU:
    ASUS STRIX-GTX970
    @mbk1969
    sorry for my bad English
    Can you give me some help?
    Today I try to change my win 8.1 SSD(SATA AHCI Controller) to msi
    and I can't go into my system again (blue screen)
    I know the issue from SSD to msi
    BTW:Can't boot safe mode

    Fortunately, I have dual systems
     
    Last edited: Mar 31, 2021
  15. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    Win 8.1 has a feature to boot into last known good configuration.
    Continuously press and release "F8" during BIOS boot screen to launch the Windows boot menu, and there should be that boot feature
    https://www.techrepublic.com/blog/w...d-startup-options-provide-major-improvements/
     

  16. Risedo

    Risedo Member

    Messages:
    16
    Likes Received:
    1
    GPU:
    ASUS STRIX-GTX970
    Thank your help.
    I try it but not working.
    So I change my AHCI to IDE
    now I can boot my win 8.1
    [​IMG]

    so I try goto regedit find MessageSignaledInterruptProperties

    I delete it not working and try change MSISupported to 0 not working too (still bluescreen)
     
  17. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    @Risedo

    It can be that SATA controller is represented by two different devices in AHCI and IDE modes.
     
  18. Risedo

    Risedo Member

    Messages:
    16
    Likes Received:
    1
    GPU:
    ASUS STRIX-GTX970
    @mbk1969
    I know it
    [​IMG]
    I sure I find AHCI devices
     
  19. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    @Risedo
    After some searching "PCI\VEN_8086&DEV_8C02" is the HWID for SATA controller in AHCI mode. And "PCI\VEN_8086&DEV_8C00" is the HWID for SATA controller in IDE mode

    PS A bit late with response...
     
  20. mbk1969

    mbk1969 Ancient Guru

    Messages:
    15,543
    Likes Received:
    13,561
    GPU:
    GF RTX 4070
    @Risedo

    Which driver is in use for SATA controller - MS default or Intel one?
     

Share This Page