BSOD happening quite often, apparently caused by pci.sys

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Professional x64
       #1

    BSOD happening quite often, apparently caused by pci.sys


    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.
      My Computer


  2. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #2

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


  3. Posts : 188
    Windows 8.1 Enterprise x64
       #3

    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
      My Computer


  4. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #4

    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.
      My Computer


  5. Posts : 188
    Windows 8.1 Enterprise x64
       #5

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


  6. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #6

    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.
      My Computer


  7. Posts : 188
    Windows 8.1 Enterprise x64
       #7

    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
      My Computer


  8. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #8

    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.
    Last edited by libjet; 10 Jul 2019 at 12:12.
      My Computer


  9. Posts : 10
    Windows 7 Professional x64
    Thread Starter
       #9

    (ignore)
      My Computer


  10. Posts : 188
    Windows 8.1 Enterprise x64
       #10

    Have you tested RAM modules with memtest86?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:18.
Find Us