Blue Screen Roulette: Will My Dell Inspiron Survive Joining A Voice Call Today??? !!

bsodirqlwindows9 replies · 83 views · started
  1. not gonna lie this is driving me nuts 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: teh Dell Inspiron is about two years old and was perfectly stable until roughly a month ago... now it crashes while joining a voice call, sometimes twice in an evening... i havent added any hardware... the only thing i can think of is that i installed some new software for my headset and a VPN client around the same time. could either of those cause this? id rather understand the cause than uninstall things at random. thx in advance to anyone who takes the time to walk me through it. thx in advance!!

    facepalm

    2
  2. hmmmm quick q does the minidump name a specific .sys file, or is it just ntoskrnl.exe every time? ?

    2 2 helpful
  3. checked the reliability monitor: the first crash was two days after i installed the VPN client. that cant be a coincidence.

    1 3 helpful
  4. blueScreenView is a quick way to see several dumps side by side. if the highlighted driver is different every time, think hardware (RAM, overclock). if it's the same .sys every time, think driver.

    0 14 helpful
  5. hmmmm quick q is irql even worth bothering with or should i just leave it

    1 0 helpful
  6. 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.

    2 1 helpful
  7. 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, that's ur suspect.

    0 2 helpful

Reply to this topic

Sign in or create an account to reply.