M.2 device prevents PCIe x1 capture card operation
M.2 device prevents PCIe x1 capture card operation
Hi everyone, I just bought an Avermedia c985 capture card and have an Asus Prime z370-p motherboard. I'm using both M.2 slots with one SSD and one HDD. The card is placed in the second PCI x1 slot below the graphics card. After installing the official drivers from Avermedia, I got a BSOD with PFN_LIST_CORRUPT right away. Even after reinstalling the drivers (both official and unofficial), the problem persists. I also tried putting the card in another PCI slot, but it still doesn't work. Finally, removing one of the M.2 SSDs resolved the issue. My question is: can I have both M.2 SSDs installed together with the capture card? Or am I missing something? Any help would be greatly appreciated. Thanks. UPD: I noticed missing drivers for two devices—tried Asus official but it still shows as Other.
I've been searching for this setting in the BIOS, but the only PCI reference is in the PCH configuration. It looks like the available options are limited, and it might be using a different name now.
The manual mentions using shared PCIe groups and assigning IRQs for certain cards. Have you explored other x1 slots to check for conflicts? Also, note that the main M.2 slot blocks the first SATA port, so verify your SATA drives aren’t in SATA_1 to avoid issues.
Unfortunately, I'm not sure how much I can help - I just saw it mentioned in the manual. IRQ is short for "interrupt request," and it mainly matters for legacy devices. Unlike with USB, which uses polling (basically, the device is pinged a bunch and asked what it is doing) an IRQ is sent from the device to the CPU, telling it to stop what it's doing to follow a command. Old PS/2 mice and keyboards work this way. The only reason I could see why it could be an issue is if there happened to be a conflict between the card and the M.2, which can happen if they both try to use the same IRQ line. Sort of like PCIe lanes, there's a limit on the number of IRQs that can be used at once. If you are able to get into the BIOS, it is a configuration setting you can try to change to see if it does anything, but if this isn't the root of the problem, I doubt it will help.
Updated: I've connected the capture card to the free x16 port and everything functions correctly.