BSOD playing Planetside2 Error 0x0000003b ladfGSRamd64.sys

I get this BSOD when I play Planetside2 after about 35 minutes of gameplay. I have found that if I turn off Shadowplay in the Nvidia GeForce Experience I can extend that time to around 6 hours, but I don't like that. It still ends up BSOD eventually, and it's quite random.

In the game, I will start to hear garbled noise like a lower toned version of the sound I should hear. When that happens it's like a warning to slow down. If I stop what I'm doing and wait a second, it will right itself and I'll be ok. If I hear this in a larger fight or in a situation where I can't control the noise levels it seems to go over the edge and BSOD.

Here is what I have done in no particular order:

• Clean install of Nvidia graphics, personally deleting all the files
• Clean install of Logitech Gaming Software, personally deleting all the files
• Trying an older version of my graphics drivers I knew worked previously
• Different Shadowplay settings
• Updated some motherboard drivers
• Installed Samsung Magician for my SSD
• Installed CoreTemp to see heat and performance
• Installed MSI Afterburner and Kombuster to check GCard heat and performance
• Tested the RAM with Windows Memory Test (it got to %100 and then resumed to the OS, so I think that means it passed?)
• Tried screaming at headphones
• Threatened the graphics drivers and LGS drivers
• Lost hope
• EDIT: /sfc /scannow said no errors (forgot to mention I did that)

Like I said above, if I turn off shadowplay I can play uninterrupted for a very long time, but it still eventually, frequently, kicks me out. I should also mention that my parents limit my internet connection, which makes nvidia geforce experience weird and won't let me touch shadowplay at all. It won't even show the option when I'm offline. Either way, I BSOD with or without internet, but I don't want to since I can keep playing Planetside2 as long as I stay connected. The block only limits it to new connections, so if I don't BSOD I can keep playing PS2 even though I am blocked.


PS: The dm log collector didn't work right on my PC, I hit "any button" and it made a folder called SFdebugFiles which only has text in the hosts.txt file and the updatelog.txt file, and once I hit "any button" the second time the folder disappears and I get no zip file.


Thank you for any help you have!
Calvissuperman

The dump files do indicate that is the faulting driver but that's not a 100% guarantee that is the finite cause

If you cant update it try removing it (if only temporarily) to see if that helps the situation and regain system stability