m17 R5, DXG_Kernel error after BIOS update from 1.10.1 to 1.13.1

This page at Howtogeek may help. Try installing the newest Nvidia drivers from their site.

Ran all suggested fixes for this issue, nothing worked. Used DDU to wipe nvidia drivers and installed latest version 546.65, no change. Disabled fast boot, nope change. I am 90% sure this is from the BIOS update to 1.13, as when i was on 1.10 none of these issues existed. Please , someone must have had a similar issue with this update, and there must be a way to rollback BIOS.

To receive assistance from Dell chat Technical support, they need to first verify the warranty status. Click the "Get Help Now" icon on the right to start a live chat session. Provide to them the private m17 R5 Service Tag.

"and there must be a way to rollback BIOS."

If the BIOS update contains security updates, you cannot downgrade the BIOS to earlier versions.

The BIOS 1.13.1 stated =

@DELL-Chris M​ Got the same problem and also spoke with dell support but no fix worked.
Do you maybe have information if a new BIOS update release is being planned in the near future?

@Aliibini​ No, we do not get notifications of "future" updates. Like you, we simply check the Drivers & Downloads page to see what is present.

Ah, I see. Thanks for the answer!

Sorry not willing to pay 500+ dollars to fix something i didnt break. Lesson learned will never make another purchase from dell.

The worst of all is that they removed version 1.11 and 1.13 which have this problem, my M17 R5 AMD also has this problem, I found that when connecting the external monitor via HDMI the machine freezes in up to 1 minute, I spoke to the people at Dell but they don't have a solution, as they blocked the installation of version 1.10 when you already have version 1.13.
My solution here was to use the external monitor via the displayport output, this way there are no crashes, it will only have a lower performance because it is always going through the integrated card, when you play, the rtx will be called but going through the integrated one first, like this We don't have the crash, at least we can handle it until the new driver comes out, because they returned the website to the version that worked, which is 1.10, so they are aware of the error, they just don't know how to fix it yet hahaha