REINSTALLED WINDOWS ON THE HP PAVILION AND THE IRQL BLUE SCREEN CAME RIGHT BACK !!

bsodirqlwindows6 replies · 138 views · started
  1. short version: blue screen, restart, repeat.

    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
    

    longer version: the HP Pavilion is about two years old and was perfectly stable until roughly a month ago. now it crashes while copying files over the network, sometimes twice in an evening. I hvaent added any hardwrae. the only thing I can think of is that I installed some new software for my hedaset and a VPN client around the same time. could either of those cause this? id rather understand teh cause than uninstall things at random. thanks in advance to anyone who takes teh time to walk me through it. thx in advance!!

    5
  2. When exactly did the crashes start compared to installing that new software?

    2 2 helpful
  3. ok so nothing is overclocked as far as i know, but i havent checked teh BIOS since i bought the HP Pavilion.

    0 4 helpful
  4. 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!

    27 6 helpful
  5. yeahhh get teh network adapter dirver straight from teh laptop or motherboard makers support page instead of relying on Windows Update. then repair system files:

    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
    

    fingers crossed 🤞

    17 0 helpful
  6. I'd be careful about jumping straight to Driver Verifier. On a work machine with a deadline it can make things worse for a day. Uninstalling the suspect software first is lower risk.

    thinking

    1 3 helpful
  7. @cobalt_loop holy cow it was the network filter driver. Clean reinstall of the newer VPN build plus the vendors network driver and zero blue screens since. Learned how to read a minidump along the way. cant believe it was that simple lol

    party

    2 5 helpful

Reply to this topic

Sign in or create an account to reply.