Question BSOD: "DRIVER_POWER_STATE_FAILURE" ntoskrnl.exe ?

[jeffreyzhou3]

Hi everyone,

Lately my laptop has started to freeze up randomly (while in the middle of working, while at idle, literally completely randomly) and then bluescreen. During the frozen period I cannot do anything except force power it down by holding the power button. The bluescreen page is so artifacted that I can't read anything off of it, so I installed bluescreenview which shows the error code as "DRIVER_POWER_STATE_FAILURE"

I've tried analyzing the dmp files in windbg, and it seems to be a conflict between the ACPI driver and the AMD I2C device driver (which maybe suggests power management issues?) but nothing I've tried seems to work. My laptop is a Lenovo Slim 7 ProX (6900HS, RTX 3050)

So far, I have tried checking all drivers for updates, updating the BIOS, disabling hard drive sleep in power plan settings, and uninstalling/reinstalling network card drivers, cpu drivers, etc. but nothing has worked. In fact, in the past few weeks, the laptop has started bluescreening much more frequently to the point that in the process of writing this post, it has already bluescreened once. I haven't been able to work for more than a couple hours MAX before it bluescreens again.

I've attatched a handful of dmp files from the minidump folder for anyone to help look at
https://drive.google.com/drive/folders/1BwQmZ6Q_oy9_CySt7MIKJCquGQp2GRFc?usp=sharing

Any help is greatly appreciated.

 

[ubuysa]

These are all power transition failure BSODs, but for different devices. It's true that most are for the AMD I2C device, but there is one for your Radeon 680 and one for the USB3.0 hub driver. Clearly the common denominator is somewhere else.

You say that you've checked for driver updates but there are several updated drivers available on the Lenovo driver site for your laptop that post-date drivers that you have installed, so there are driver updates that you can - and should - install. There is even a critical driver update available for your graphics driver - which you don't have installed. There is also a BIOS update dated April 2024 that you should consider once all other drivers have been updated and the problem remains.

 

[jeffreyzhou3]

These are all power transition failure BSODs, but for different devices. It's true that most are for the AMD I2C device, but there is one for your Radeon 680 and one for the USB3.0 hub driver. Clearly the common denominator is somewhere else.

You say that you've checked for driver updates but there are several updated drivers available on the Lenovo driver site for your laptop that post-date drivers that you have installed, so there are driver updates that you can - and should - install. There is even a critical driver update available for your graphics driver - which you don't have installed. There is also a BIOS update dated April 2024 that you should consider once all other drivers have been updated and the problem remains.

Hi, I tried everything you mentioned, I downloaded basically every driver on the website and went through the installation process, as well as updated the BIOS which took a good amount of time. However after everything was done (I restarted the laptop one more time afterwards) it immediately bluescreened again with the same error. I added 2 more minidumps to the folder linked in my first post.

I got it back up again and scanned for malware, and did a fresh install of all my display drivers using DDU and after doing that it again bluescreened again (see the latest minidump)

I'm starting to suspect that it's a hardware problem which is very unfortunate given that the laptop is very new... Is there anything else I can possibly try?

 

[ubuysa]

I'd like to see more detailed troubleshooting data. Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

 

[jeffreyzhou3]

I'd like to see more detailed troubleshooting data. Can you please download and run the SysnativeBSODCollectionApp and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.

Hi, I ran the program and uploaded the zip to the original directory with my old dmp files. Please let me know if you need anything else and thanks

 

[ubuysa]

I'm puzzled. You said (or implied) in post #3 that you had installed all the latest drivers available from the Lenovo driver website for your laptop. However, in the latest dump (dated 7th July 2024) I can see that two drivers at least have not been updated...

The audio driver RTKVHD64.sys that you have installed is dated 29th August 2023...

1: kd> lmDvmRTKVHD64
Browse full module list
start             end                 module name
fffff801`bd1b0000 fffff801`bd7d9000   RTKVHD64   (deferred)            
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 29 12:48:48 2023 (64EDBF00)
    CheckSum:         00632FD0
    ImageSize:        00629000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Realtek audio driver available from the Lenovo website is dated 25th Jan 2024...

The Nvidia graphics driver nvlddmkm.sys that you have installed is dated 30th August 2023...

1: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff801`abb40000 fffff801`af4ba000   nvlddmkm   (deferred)            
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvlt.inf_amd64_7700852d63aa7e02\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 30 08:25:46 2023 (64EED2DA)
    CheckSum:         0387724E
    ImageSize:        0397A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Nvidia graphics driver available from the Lenovo website is dated 25th Jan 2024 and is labelled as 'critical'...

It's pretty clear just from those two that yu haven't yet updated all of your laptop drivers to the versions available on the Lenovo website. It's VERY important that you do that first.

You do appear to be running the latest BIOS however.

 

[jeffreyzhou3]

I'm puzzled. You said (or implied) in post #3 that you had installed all the latest drivers available from the Lenovo driver website for your laptop. However, in the latest dump (dated 7th July 2024) I can see that two drivers at least have not been updated...

The audio driver RTKVHD64.sys that you have installed is dated 29th August 2023...

1: kd> lmDvmRTKVHD64
Browse full module list
start             end                 module name
fffff801`bd1b0000 fffff801`bd7d9000   RTKVHD64   (deferred)           
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 29 12:48:48 2023 (64EDBF00)
    CheckSum:         00632FD0
    ImageSize:        00629000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Realtek audio driver available from the Lenovo website is dated 25th Jan 2024...

The Nvidia graphics driver nvlddmkm.sys that you have installed is dated 30th August 2023...

1: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff801`abb40000 fffff801`af4ba000   nvlddmkm   (deferred)           
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvlt.inf_amd64_7700852d63aa7e02\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 30 08:25:46 2023 (64EED2DA)
    CheckSum:         0387724E
    ImageSize:        0397A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Nvidia graphics driver available from the Lenovo website is dated 25th Jan 2024 and is labelled as 'critical'...

It's pretty clear just from those two that yu haven't yet updated all of your laptop drivers to the versions available on the Lenovo website. It's VERY important that you do that first.

You do appear to be running the latest BIOS however.

My apologies, I believe I only reinstalled the AMD integrated graphics drivers instead of doing the NVIDIA ones as well.

Also, a few months ago the original Realtek wifi/bt card failed, so I replaced it with the Intel AX210, hence I probably got it confused with the audio driver instead.

I'll run and install these two drivers and see if the issue persists.

Thanks for all the help

 

[jeffreyzhou3]

I'm puzzled. You said (or implied) in post #3 that you had installed all the latest drivers available from the Lenovo driver website for your laptop. However, in the latest dump (dated 7th July 2024) I can see that two drivers at least have not been updated...

The audio driver RTKVHD64.sys that you have installed is dated 29th August 2023...

1: kd> lmDvmRTKVHD64
Browse full module list
start             end                 module name
fffff801`bd1b0000 fffff801`bd7d9000   RTKVHD64   (deferred)           
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
    Image name: RTKVHD64.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Aug 29 12:48:48 2023 (64EDBF00)
    CheckSum:         00632FD0
    ImageSize:        00629000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Realtek audio driver available from the Lenovo website is dated 25th Jan 2024...

The Nvidia graphics driver nvlddmkm.sys that you have installed is dated 30th August 2023...

1: kd> lmDvmnvlddmkm
Browse full module list
start             end                 module name
fffff801`abb40000 fffff801`af4ba000   nvlddmkm   (deferred)           
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvlt.inf_amd64_7700852d63aa7e02\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Aug 30 08:25:46 2023 (64EED2DA)
    CheckSum:         0387724E
    ImageSize:        0397A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Yet the most recent Nvidia graphics driver available from the Lenovo website is dated 25th Jan 2024 and is labelled as 'critical'...

It's pretty clear just from those two that yu haven't yet updated all of your laptop drivers to the versions available on the Lenovo website. It's VERY important that you do that first.

You do appear to be running the latest BIOS however.

It bluescreened again shortly after so I reran the sysnative app and updated the zip in the google drive. Let me know if you find anything, and thanks

 

[ubuysa]

I asked you to update ALL drivers please. I only picked those two as an example, your wireless driver has an update too - most drivers do have updates there. There are many areas on that driver update page where updated drivers are available. With a problem like this it is essential that all drivers are as up to date as you can get them so please go through every option on the driver update page and update all drivers. In particular be certain that the chipset drivers and the touchpad drivers are updated.

• Does this happen both on mains power and on battery only?
• Do you use an external mouse?

 

[jeffreyzhou3]

I asked you to update ALL drivers please. I only picked those two as an example, your wireless driver has an update too - most drivers do have updates there. There are many areas on that driver update page where updated drivers are available. With a problem like this it is essential that all drivers are as up to date as you can get them so please go through every option on the driver update page and update all drivers. In particular be certain that the chipset drivers and the touchpad drivers are updated.

• Does this happen both on mains power and on battery only?
• Do you use an external mouse?

I really tried updating every single driver for my laptop but it still bluescreens. I do use an external bluetooth mouse as well as bluetooth headphones regularly. However I've stopped using them entirely and the issue still persists.

I noticed however that the issue only really happens in a few scenarios:

- If my laptop has just woken from hibernation, and I plug in the power cable, it freezes for 2-3 minutes, then bluescreens.
- If my laptop has just woken from sleep and I plug in the power, it freezes and crashes, but not every time, probably 70% of the time.
- If my laptop is awake and I am in the middle of using it, and I plug in OR unplug and replug in the power it crashes about half the time.

The issue is really so random I have no clue how to even begin approaching the problem...

 

[ubuysa]

That sounds very much like some sort of hardware issue to me, because the common denominator there is plugging in the power. I'd like you to start Windows in Safe Mode whilst on battery - use Safe Mode without Networking. You won't be able to do anything useful because Safe Mode loads a stripped-down version of Windows with only critical drivers and services loaded, typically no third-party drivers are loaded. This will mean that some devices may not work properly (or at all), your display will be low resolution for example, because you'll be using the Windows basic display driver and you'll have no Internet access because the network adapter drivers are not loaded.

Once it's booted into Safe Mode and is stable, plug in the power and see what happens. Then try unplugging the power and see what happens. If it BSODs in either case then it's pretty definitely a hardware problem.

I don't know for sure whether Sleep and/or Hibernation are supported in Safe Mode, somehow I doubt it. But it's worth trying to Sleep and/or Hibernate it in Safe Mode on battery and see whether you can. When it resumes from Sleep or Hibernate plug in the power again and see whether it BSODs. Then uplug the power and see whether it BSODs.

Although Safe Mode is largely useless for doing any real work, because it's a stripped-down pristine copy of Windows that's loaded, any BSODs you see will almost certainly be hardware.

 

[jeffreyzhou3]

That sounds very much like some sort of hardware issue to me, because the common denominator there is plugging in the power. I'd like you to start Windows in Safe Mode whilst on battery - use Safe Mode without Networking. You won't be able to do anything useful because Safe Mode loads a stripped-down version of Windows with only critical drivers and services loaded, typically no third-party drivers are loaded. This will mean that some devices may not work properly (or at all), your display will be low resolution for example, because you'll be using the Windows basic display driver and you'll have no Internet access because the network adapter drivers are not loaded.

Once it's booted into Safe Mode and is stable, plug in the power and see what happens. Then try unplugging the power and see what happens. If it BSODs in either case then it's pretty definitely a hardware problem.

I don't know for sure whether Sleep and/or Hibernation are supported in Safe Mode, somehow I doubt it. But it's worth trying to Sleep and/or Hibernate it in Safe Mode on battery and see whether you can. When it resumes from Sleep or Hibernate plug in the power again and see whether it BSODs. Then uplug the power and see whether it BSODs.

Although Safe Mode is largely useless for doing any real work, because it's a stripped-down pristine copy of Windows that's loaded, any BSODs you see will almost certainly be hardware.

So I tried starting in safe mode and let it idle for a while periodically plugging and unplugging the power cord, but nothing could cause it to crash. I booted back into normal mode and started using the laptop as normal, but yet again it bluescreened, and this time I never even touched the power cable. This time instead of DRIVER_POWER_STATE_FAILURE it gave dpc_watchdog_violation

I also noticed that my USB-C ports have started losing functionality. External displays no longer work with any usb c adapter.

I also looked online and found many people having the same issue on the same laptop:

https://answers.microsoft.com/en-us...n-laptop/d50d56e3-bb23-43d2-bec5-8d42cd6b040f

https://answers.microsoft.com/en-us...therwise/7147e5e0-d264-4bd4-b962-106511d0b68d

Not exactly sure what to do here...

 

[ubuysa]

Ah now that's good news (in a way) because is strongly indicates that this is a software issue and not a hardware issue. It's generally not wise to look for others with the same problem, the 0x9F BSOD is quite common and has MANY potential causes, so it's unlikely that somebody else's issue will be the same as yours.

There are actually a couple of ways we could go now, so don't despair, we still have troubleshooting options left. I'm going to first suggest that you enable Driver Verifier because this will require the least input and effort from you. If Driver Verifier doesn't highlight a problem driver then we'll move on to the other technique (which is way more time consuming).

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

 

[jeffreyzhou3]

Ah now that's good news (in a way) because is strongly indicates that this is a software issue and not a hardware issue. It's generally not wise to look for others with the same problem, the 0x9F BSOD is quite common and has MANY potential causes, so it's unlikely that somebody else's issue will be the same as yours.

There are actually a couple of ways we could go now, so don't despair, we still have troubleshooting options left. I'm going to first suggest that you enable Driver Verifier because this will require the least input and effort from you. If Driver Verifier doesn't highlight a problem driver then we'll move on to the other technique (which is way more time consuming).

Driver Verifier subjects selected drivers (typically all third-party drivers) to extra tests and checks every time they are called. These extra checks are designed to uncover drivers that are misbehaving. If any selected driver fails any of the Driver Verifier tests/checks then Driver Verifier will BSOD. The resulting minidump should contain enough information for us to identify the flaky driver. It's thus essential to keep all minidumps created whilst Driver Verifier is enabled.

To enable Driver Verifier do the following:

1. Take a System Restore point and/or take a disk image of your system drive (with Acronis, Macrium Reflect, or similar). It is possible that Driver Verifier may BSOD a driver during the boot process (some drivers are loaded during boot). If that happens you'll be stuck in a boot-BSOD loop.

If you should end up in a boot-BSOD loop, boot the Windows installation media and use that to run system restore and restore to the restore point you took, to remove Driver Verifier and get you booting again. Alternatively you can use the Acronis, Macrium Reflect, or similar, boot media to restore the disk image you took.

Please don't skip this step. it's the only way out of a Driver Verifier boot-BSOD loop.

2. Start the Driver Verifier setup dialog by entering the command verifier in either the Run command box or in a command prompt.

3. On that initial dialog, click the radio button for 'Create custom settings (for code developers)' - the second option - and click the Next button.

4. On the second dialog check (click) the checkboxes for the following tests...

• Special Pool
• Force IRQL checking
• Pool Tracking
• Deadlock Detection
• Security Checks
• Miscellaneous Checks
• Power framework delay fuzzing
• DDI compliance checking

Then click the Next button.

5. On the next dialog click the radio button for 'Select driver names from a list' - the last option - and click the Next button.

6. On the next dialog click on the 'Provider' heading, this will sort the drivers on this column (it makes it easier to isolate Microsoft drivers).

7. Now check (click) ALL drivers that DO NOT have Microsoft as the provider (ie. check all third-party drivers).

8. Then, on the same dialog, check the following Microsoft drivers (and ONLY these Microsoft drivers)...

• Wdf01000.sys
• ndis.sys
• fltMgr.sys
• Storport.sys

These are high-level Microsoft drivers that manage lower-level third-party drivers that we otherwise wouldn't be able to trap. That's why they're included.

9. Now click Finish and then reboot. Driver Verifiier will be enabled.

Be aware that Driver Verifier will remain enabled across all reboots and shutdowns. It can only be disabled manually.

Also be aware that we expect BSODs. Indeed, we want BSODs, to be able to identify the flaky driver(s). You MUST keep all minidumps created whilst Driver Verifier is running, so disable any disk cleanup tools you may have.

10. Leave Driver Verifier running for 48 hours, use your PC as normal during this time, but do try and make it BSOD. Use every game or app that you normally use, and especially those where you have seen it BSOD in the past. If Windows doesn't automatically reboot after each BSOD then just reboot as normal and continue testing. The Driver Verifier generated BSODs are these...

• 0xC1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
• 0xC4: DRIVER_VERIFIER_DETECTED_VIOLATION
• 0xC6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
• 0xC9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
• 0xD6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
• 0xE6: DRIVER_VERIFIER_DMA_VIOLATION

If you see any of these BSOD types then you can disable Driver Verifier early because you'll have caught a misbehaving driver.

Note: Because Driver Verifier is doing extra work each time a third-party driver is loaded you will notice some performance degradation with Driver Verifier enabled. This is a price you'll have to pay in order to locate any flaky drivers. And remember, Driver Verifier can only test drivers that are loaded, so you need to ensure that every third-party driver gets loaded by using all apps, features and devices.

11. To turn Driver Verifier off enter the command verifier /reset in either Run command box or a command prompt and reboot.

Should you wish to check whether Driver Verfier is enabled or not, open a command prompt and enter the command verifier /query. If drivers are listed then it's enabled, if no drivers are listed then it's not.

12. When Driver Verifier has been disabled, navigate to the folder C:\Windows\Minidump and locate all .dmp files in there that are related to the period when Driver Verifier was running (check the timestamps). Zip these files up if you like, or not as you choose. Upload the file(s) to the cloud with a link to it/them here (be sure to make it public).

Apologies for the late update, I've been busy lately.

I have yet to run the driver verifier, but I have experimented a bit and found something. The freezing and bluescreening ONLY happens when I am running on the integrated GPU. If I go into NVIDIA control panel and switch to "Use NVIDIA gpu only," the laptop can be used extensively without any issues. I've been using only the dGPU for the past few days.

The only problem is that the battery drains much faster and the laptop runs hotter using the dGPU at all times obviously. Could it still be a driver issue with the Radeon Graphics?

 

[ubuysa]

Chec with the AMD Driver & Support tool that your chipset and iGPU drivers are up to date.

 

[jeffreyzhou3]

Just to update anyone else with the same or similar issue, the issue still couldn't be fixed and I've just gotten a new laptop for now.