Sign in

it only crashes when joining a voice call. that has to be a clue, right??

bsodirqlwindows5 replies · 274 views · started
Reply
  1. Jade Schmidt
    @jschmidt

    okay, Im officially frustrated. my Dell Inspiron has been blue screening with IRQL_NOT_LESS_OR_EQUAL, and it always seems to happen while joining a voice call, heres what it looks like:

    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

    i have a deadline on Friday and i can't trust this machine to stay up for more than a couple of hours lmao i found a minidump folder but i have no idea how to read those files. Any help reading the tea leaves would be hugely appreciated. There's no overclocking software or anything fancy installed, just a normal setup 🙏 If there's a tool that reads those dump files for a beginner, i'm all ears. thx in advance!!

    5
  2. Selin
    @quiettrace-id

    im literally losing my mind here lol this thread is gold what am i doing wrong??

    2 7 helpful
  3. Malik Haddad
    @malikh405

    hmmm since it lines up with new VPN and headset software, uninstall both completely, reboot, and see if the crashes stop. VPN clients insatll network filter drivers and those are a classic source of this stop code. worked for me anyway 🤷

    2 0 helpful
  4. Hugo S.
    @hsorensen

    ahh classic IRQL_NOT_LESS_OR_EQUAL amlost always means a kernel-mode driver touched memory it shouldnt at a raised IRQL. Install WinDbg from teh 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 drievr, thats ur suspect. fingers crossed 🤞

    0 1 helpful
  5. Hugo Rossi
    @hugor167
    in reply to @hsorensen

    id 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 sofwtare first is lower risk. just my 2 cents

    6 0 helpful

Reply to this topic

Sign in or create an account to reply.