BSOD happening quite often, apparently caused by pci.sys

[libjet]

I recently installed Windows 7 after discovering that I could, in fact, run it on a Ryzen CPU.
Unfortunately every so often (every hour or so) I get greeted with a big blue screen saying something along the lines of DRIVER_IRQL_NOT_LESS_OR_EQUAL followed by pci.sys
I modified the Windows 7 installation files with DISM to get USB3 to work, but even with different drivers the same error occurs so I believe the modification might be unrelated, although still a big suspicion to me.
Log files generated by "dm log collector" attached below.

 

[libjet]

I think the dm log may be corrupt, so here's a new one made right before another BSOD.

 

[MrPepka]

Run msconfig, select "Boot" page, select "Advanced options", and check "Debug". Accept changes and reboot computer. Later send full memory dump (MEMORY.DMP in C:\Windows) Of course, leave the Driver Verifier turned on

 

[libjet]

Sorry for the delay, here's the memory.dmp. I did turn on Driver Verifier but later turned it off because it brought my PC to a crawl, so if I were to turn it on again how long should I leave it on for? Should I just use standard settings? Thank you.

 

[MrPepka]

Turn it on again, with the same default settings for third-party drivers. So as you set it up before

 

[libjet]

I think I know now why my system was so slow... and it's because it was verifying every driver on my PC, so now it's only checking non-Microsoft drivers except for pci.sys and ntoskrnl.exe, (just in case) which makes it run a lot faster. As for the BSODs, a few more have occurred so I've made a new log file. I also found an unknown device in device manager (AMD USB3 Root Hub) and managed to fix it with a driver file from MSI for my motherboard. Thanks for replying.

 

[MrPepka]

The problematic driver is kprocesshacker.sys. What is visible from the name is the driver from the Process Hacker 2 program. This program has obtained EOL (End of Life) support status, so it is no longer developed and for this reason I recommend uninstalling it and switching to some alternative

 

[libjet]

Thanks, I did notice that whenever I opened Process Hacker as an Administrator it always produced a BSOD, but the error code was 0xC4 instead of the usual 0xD1 BSOD. I also remember getting the BSOD before installing Process Hacker, but I'll see if this fixes it though.

EDIT: After uninstalling Process Hacker 2, the original (0xD1) BSOD is still occurring.

 

[libjet]

(ignore)

 

[MrPepka]

Have you tested RAM modules with memtest86?

 

[libjet]

Hi, I just tested the RAM with memtest86 and the results came back all good. Here's the generated html file if you're interested.

 

[libjet]

Update
All was going pretty well for about 20 hours until my computer had three BSODs in quick succession... and using WhoCrashed it reveals this:

[FONT=Segoe UI, Arial]On Fri 12/07/2019 17:41:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071219-13088-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x1D3C08)
Bugcheck code: 0xD1 (0x64, 0xB, 0x1, 0xFFFFF88000F6EE9B)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 391.35 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 391.35
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 391.35 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
[/FONT]
[FONT=Segoe UI, Arial]On Fri 12/07/2019 17:41:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: [FONT=Segoe UI, Arial]pci.sys[/FONT] (0xFFFFF88000F6EE9B)
Bugcheck code: 0xD1 (0x64, 0xB, 0x1, 0xFFFFF88000F6EE9B)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\pci.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Plug and Play PCI Enumerator
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
[/FONT]
[FONT=Segoe UI, Arial]On Fri 12/07/2019 17:40:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071219-14133-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]pci.sys[/FONT] (0xFFFFF88000E1FE9B)
Bugcheck code: 0xD1 (0x64, 0xB, 0x1, 0xFFFFF88000E1FE9B)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\pci.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Plug and Play PCI Enumerator
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
[/FONT]

This may have uncovered the true cause of the BSOD, although i'm not really sure. How would I go about fixing this? Logs included below.
https://mega.nz/#!eqxkDIKS!5XTTWoDErMRqbr1Ux4_M43tAzHOa61w7Bo6OXYZzgwA (MEMORY.DMP)

 

[MrPepka]

Probably the PCI-E slot in which the graphics card is damaged. You have the option of moving your graphics card to another slot?

 

[libjet]

Huh, I'm really baffled as to what the issue is. I know that it's not a hardware issue, as it works perfectly on Arch Linux and W10, but I really am too lazy to swap the PCI slot, so I don't really know.

 

[libjet]

Update: Recently I decided to try and fix the issue again, as I've been getting as many as 5 BSOD's a day very frequently over the past few months. I searched online and came across Display Driver Uninstaller again, but when I ran the program it told me that I had an NVIDIA driver alongside a Radeon one which I was surprised to see considering I got a new GPU (AMD RX480), and obviously the NVIDIA uninstaller didn't remove everything. After I removed the driver yesterday evening I haven't had a BSOD since, and I'm pretty sure that the NVIDIA graphics driver is the main source of the issue. I will mark this thread solved if I haven't had a BSOD in a weeks time, so hopefully I fixed it.