Razer Blade 14 (2022) BSOD when unplugged | Razer Insider
Skip to main content

I have a Razer Blade 14 (2022) laptop that works perfectly when plugged in. However, as soon as I try to use my laptop whilst not plugged in it starts to BSOD alongside artifacting on the screen.

Here are some of the error codes that I've been keeping track of after the crashes:

  • IRQL Not Les or Equal ntoskrnl.exe error

  • Driver Overran Stack Buffer

  • Kmode Exception Not Handled

  • Driver IRQL Not Less or Equal

  • fltmgr.sys

  • APC Index Mismatch

  • Page Fault in Nonpaged Area

So far, I've tried fixing these issues by updating my bios, reinstalling my graphics drivers with ddu, using the command prompt, and turning off power saver mode. So far, none of these have been working.

Also, I've ran MemTest86 and everything seemed fine with my ram.

Attached is a zip file with some minidumps: https://www.mediafire.com/folder/r2mhgmroqszx4/Minidump

If any info is needed like specs, let me know!

Hi QUARTZrushMauve849,

I understand that you're experiencing issues BSOD with your Razer Blade 14 (2022) when switching to battery power. The blue screen errors you're encountering indicate a potential problem with drivers or hardware, especially since they only occur when the laptop is not plugged in. To further isolate the issue, please do the troubleshooting in this article. If this doesn’t help, PM me and fill in the details below so I can escalate you concern to our Laptop Support Team and initiate a case on your behalf.

  • MSinfo logs.
  • Windows version.
  • Send a screenshot of the Nvidia and Intel Driver versions. Press Windows+R on your keyboard. Type in DXDIAG into the run command text box and hit OK. Then click on YES. Click on the Display 1 and 2 tabs and look for the graphics driver version on the right side.
  • Photo of the BIOS main tab.

Save the shareable files via any online drive account listed here. Also, fill in the details:

  • Full Name:
  • Email:
  • Phone number:
  • Country:
  • Product serial number:
  • Shortvideo showing the issue:


*Thread locked to curb the conversation to PMs.

CookiesCookie settings