REINSTALLED WINDOWS ON THE HOME-BUILT RYZEN PC AND THE IRQL BLUE SCREEN CAME RIGHT BACK

bsodirqlwindows22 replies · 616 views · started
  1. I was copying files over teh network on my home-built Ryzen PC when teh screen went blue for the third time this week. Same message every time:

    Your PC ran into a problem and needs to restart. We're

    Your PC ran into a problem and needs to restart. We're
    just collecting some error info, and then we'll restart for
    you.
    42% complete
    For more information about this issue and possible fixes, visit
    our support site.
    
    If you call a support person, give them this info:
    Stop code: IRQL_NOT_LESS_OR_EQUAL
    

    It counts to 100%, reboots, and everything looks fine again until the next time. Ive already run Windows Update and teh system tray says all drivers are up to date. I honestly dont know whether to blame the hardware or the software at this point. Where do I even start with this stop code? I can run commands and install tools if someone points me in the right direction. I just dont want to wipe the whole home-built Ryzen PC and lose a weekend if this turns out to be smth simple.

    4
  2. ok but when exactly did teh crashes start compaerd to installing that new software?

    5 0 helpful
  3. Checked the reliability monitor: the first crash was two days after i installed the VPN client. That cant be a coincidence. hope thats enough info 😅

    40 0 helpful
  4. BlueScreenView is a quick way to see several dumps side by side. If teh highlighted driver is different every time, think hardware (RAM, overclock) 😭 If its the same .sys every time, think driver.

    thumbsup

    2 0 helpful
  5. ahh classic IRQL_NOT_LESS_OR_EQUAL almost always means a kernel-mode driver touched memory it shouldnt at a raised IRQL. Install WinDbg from the Microsoft Store, open the newest file in C:\Windows\Minidump, and run:

    !analyze -v
    

    Look at MODULE_NAME and IMAGE_NAME. if it names something like a VPN filter driver or a network driver, thats your suspect.

    0 6 helpful
  6. oh ive been there lol if teh dumps are inconclusive, enable Driver Verifier to force the bad driver to show itself:

    verifier /standard /all
    

    Reboot and use the PC normally. When it crashes, teh dump should name the driver. Turn it off afterwards with verifier /reset. make a restore point first because it can cause a boot loop.

    0 5 helpful
  7. ok so following, having the same problem fingers crossed 🤞

    15 0 helpful
  8. Get the network adapter driver straight from teh laptop or motherboard maker's support page instead of relying on Windows Update. Then repair system files:

    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    
    0 1 helpful
  9. yeahhh following, having the same problem fingers crossed 🤞

    9 9 helpful
  10. dont rule out RAM. run mdsched.exe for a quick pass, or better, MemTest86 from a USB stick for at least a few passes, faulty memory can produce IRQL crashes that point at random drivers each time. good luck man!

    5 0 helpful
  11. oh ive been there lol since it lines up with new VPN and headset software, uninstall both completely, reboot, and see if teh crashes stop. VPN clients install network filter drivers and those are a classic source of this stop code. hope that helps :)

    0 3 helpful
  12. Respectfully, I wouldn't blame the VPN yet. I've seen identical dumps caused by a dying RAM stick. Run MemTest86 overnight before uninstalling half your apps.

    20 0 helpful
  13. is ryzen even worth bothering with or should i just leave it. spent since tuesday on copying and im still not done

    2 0 helpful

Reply to this topic

Sign in or create an account to reply.