Razer Blade 15” (2020) | RZ09-03519 - WiFi issues, sleep issues, BSOD error | Razer Insider
Skip to main content

Razer Blade 15” (2020) | RZ09-03519 - WiFi issues, sleep issues, BSOD error

A
I'm encountering a set of issues with my Razer Blade 15" (2020), RZ09-03519 model. These all began occurring around the same time.
  • The WiFi adapter will switch off for no apparent reason. Once this happens, I can't turn the adapter back on - pressing the "on" toggle doesn't do anything. Troubleshooting doesn't show any issues except "turn your network adapter on." I've uninstalled and reinstalled the WiFi driver; this did not fix the issue.
  • When I put the laptop in sleep mode (whether by actively selecting "sleep" or by leaving it for long enough), I often can't wake it again. The power light is green and I can hear the laptop doing something, but neither opening the lid nor pressing the power button results in anything showing up onscreen. The only thing I can do is a hard reboot by pressing the power button for 5-10 seconds.
  • Every so often - sometimes 3-4 times in one day - I'll be presented with a Blue Screen of Death error. The error message displayed is DRIVER_POWER_STATE_FAILURE. This often occurs shortly after the wifi switches off. After this, the computer tries to restart, but stays stuck at the Razer logo screen - it's remained there for over half an hour without doing anything. The only way to get it to start fully is to do a hard shutdown and reboot.
I've tried uninstalling and reinstalling the following drivers - both from the system's files (uninstalling, then restarting) and from a download (downloading the drivers from Nvidia/Intel, uninstalling the drivers, rebooting in safe mode, and installing drivers that way).
  • Wifi network adapter driver
  • NVIDIA GPU driver (using built-in tools as well as the DDU tool)
Before installing/reinstalling, I checked for updates; none of those found by Windows Update resolved the issue. I've done a reset of my laptop (keeping files), and installed the latest Intel firmware posted online (here: https://mysupport.razer.com/app/answers/detail/a_id/3919/). I've run the system file checker (using the sfc/scannow command in the command prompt); it did not find any integrity violations. I ran the BlueScreenView utility, and that states the crash was caused by driver ntoskrnl.exe. The stated crash address is ntoskrnl.exe+417d20. The address in stack is ntoskrnl.exe+5c2d47. The bug check string is DRIVER_POWER_STATE_FAILURE. The bug check code is 0x0000009f. Please advise.
Did this topic help you find an answer to your question?
This topic has been closed for comments

4 Replies

A
  • AH2022
  • Author
  • 2 replies
  • August 7, 2022
HTML version of the crash minidump below: [HTML] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <html><head><title>Crash List</title></head> <body> <h3>Crash List</h3> <br><h4>Created by using <a href="http://www.nirsoft.net/" target="newwin">BlueScreenView</a></h4><p><table border="1" cellpadding="5"> <tr><td bgcolor="E0E0E0" nowrap><b>Dump File</b><td bgcolor=#FFFFFF nowrap>080722-12125-01.dmp <tr><td bgcolor="E0E0E0" nowrap><b>Crash Time</b><td bgcolor=#FFFFFF nowrap>8/6/2022 10:59:06 PM <tr><td bgcolor="E0E0E0" nowrap><b>Bug Check String</b><td bgcolor=#FFFFFF nowrap>DRIVER_POWER_STATE_FAILURE <tr><td bgcolor="E0E0E0" nowrap><b>Bug Check Code</b><td bgcolor=#FFFFFF nowrap>0x0000009f <tr><td bgcolor="E0E0E0" nowrap><b>Parameter 1</b><td bgcolor=#FFFFFF nowrap>00000000`00000003 <tr><td bgcolor="E0E0E0" nowrap><b>Parameter 2</b><td bgcolor=#FFFFFF nowrap>ffffa885`dd6c7d70 <tr><td bgcolor="E0E0E0" nowrap><b>Parameter 3</b><td bgcolor=#FFFFFF nowrap>ffffe00c`a6e2f6d0 <tr><td bgcolor="E0E0E0" nowrap><b>Parameter 4</b><td bgcolor=#FFFFFF nowrap>ffffa885`f0df1aa0 <tr><td bgcolor="E0E0E0" nowrap><b>Caused By Driver</b><td bgcolor=#FFFFFF nowrap>ntoskrnl.exe <tr><td bgcolor="E0E0E0" nowrap><b>Caused By Address</b><td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+417d20 <tr><td bgcolor="E0E0E0" nowrap><b>File Description</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Product Name</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Company</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>File Version</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Processor</b><td bgcolor=#FFFFFF nowrap>x64 <tr><td bgcolor="E0E0E0" nowrap><b>Crash Address</b><td bgcolor=#FFFFFF nowrap>ntoskrnl.exe+417d20 <tr><td bgcolor="E0E0E0" nowrap><b>Stack Address 1</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Stack Address 2</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Stack Address 3</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Computer Name</b><td bgcolor=#FFFFFF nowrap>  <tr><td bgcolor="E0E0E0" nowrap><b>Full Path</b><td bgcolor=#FFFFFF nowrap>C:\\WINDOWS\\Minidump\\080722-12125-01.dmp <tr><td bgcolor="E0E0E0" nowrap><b>Processors Count</b><td bgcolor=#FFFFFF nowrap>12 <tr><td bgcolor="E0E0E0" nowrap><b>Major Version</b><td bgcolor=#FFFFFF nowrap>15 <tr><td bgcolor="E0E0E0" nowrap><b>Minor Version</b><td bgcolor=#FFFFFF nowrap>22000 <tr><td bgcolor="E0E0E0" nowrap><b>Dump File Size</b><td bgcolor=#FFFFFF nowrap>6,062,772 <tr><td bgcolor="E0E0E0" nowrap><b>Dump File Time</b><td bgcolor=#FFFFFF nowrap>8/7/2022 2:21:52 PM </table><p> </body></html>[/HTML]
mini2109
  • mini2109
  • Insider
  • 88 replies
  • August 8, 2022
I have the Razer Blade 17 from 2017. I bought a used one and I have similar problems. Constant disconnection of networks, connection problems. The only thing that can actually help if the attempts to update the drivers did not help is changing the wifi module. It is not very expensive and if you have a bit of practice - you should be able to replace it yourself.
A
  • AH2022
  • Author
  • 2 replies
  • August 11, 2022
mini2109
I have the Razer Blade 17 from 2017. I bought a used one and I have similar problems. Constant disconnection of networks, connection problems. The only thing that can actually help if the attempts to update the drivers did not help is changing the wifi module. It is not very expensive and if you have a bit of practice - you should be able to replace it yourself.
Interesting - this resolved the issue for you? How technical is that process? And is there anything to look out for to avoid damaging other parts?
mini2109
  • mini2109
  • Insider
  • 88 replies
  • August 11, 2022
Basically - yes, it helped. Except ... Delivered to the site that was supposed to insert one of the Intel modules (these are recommended). The service started to do something ... and finally put some Qualcom in because other ones (allegedly) did not work. I checked it and in fact - it worked much better ... but it was a bit slower and the range deteriorated a bit. So in my opinion - that solves the problem.
CookiesCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings