Driver Overran Stack Buffer

Question

Greetings everyone,

It's time to make my first forum post since I don't have any other ideas on how to resolve this issue.
I've gotten some BSOD's for the last couple days repeatedly and don't know how to resolve the issue.

I've tried the following:

1. Memory test, both with MemTest86 and Windows Memory Diagnostic, both of which don't find any issues with the system.
2. Uninstalled my graphics driver (NVidia) using DDU in Safe Mode
3. Resetting the whole PC twice and reinstalling Windows 11
4. Giving full write and read access to nvlddmkm.sys (regarding to this Post on Reddit: https://www.reddit.com/r/nvidia/comments/12l01wf/nvlddmkm\_4090\_crash\_solved/?rdt=62746)
5. Checking and updating all drivers that were old or seemed suspicious (date) using WinDbg and the Minidumps
6. Checking both my NVME's (Samsung 970 Pro Plus) using Samsung Magician, which turned out perfect.
7. Updated my BIOS
8. Stress tested my GPU using FurMark2 for 20 minutes without any issues

I attached the Minidump files via the following GoogleDrive Link: https://drive.google.com/drive/folders/17dOygk9rVdZwfiGWcZZdXmVCyQMqvmxs?usp=sharing

My PC Specs

OS: Windows 11 Pro (24H2), 26100.3194
Mobo: MSI Z790 Tomahawk Wifi

CPU: Intel Core i5-13600KF

GPU: ASUS TUF GAMING RTX4070

RAM: 2x 16Gb Corsair Vengeance DDR5 6000mHz
Drives: 2x Samsung SSD 970 Plus (1Tb)

I would be very grateful for any further ideas, so I can resolve this issue before Uni starts and I can rely on my computer again.

Best wishes,
Mark

Answer 1

Glad to help!

Answer 2

Thank you, those settings are correct, since Driver Verifier did not find the problem, and because the system crashes have survived re-installing Windows, most likely, there is an underlying hardware fault causing your system to crash, it would be best to take your system to a PC Shop to have your hardware tested.

Answer 3

Hi Dave,

here are three minidump files with Driver Verifier turned on.

I was able to use my computer roughly for 10 minutes before the crash.
I was watching YouTube Videos and browsed through the Steam Store.

Additionally, I've turned the Driver Verifier off and restarted my computer.

Link to the new Minidumps: https://drive.google.com/drive/folders/1pzUPLg65wH83nM1nuv0rnyP4Cc0UODu8?usp=sharing

Best regards,
Mark

Answer 4

Hi Dave,

Thank you for your quick response!

I managed to add a Restore Point and enabled the Driver Verifier according to the settings you provided in the Link.

Furthermore, I am able to get into my account and use Windows as usual with Driver Verifier enabled. Videos lag a bit but overall I can use my computer as I usually do.

I will continue to do so until I get to a crash and then come back to you (regarding the 36 hours of continuous use).

Again, thank you very much for your support. It means a lot to me.

Best regards,

Mark

Answer 5

Hi, I am Dave, I will help you with this.

Your minidump files mostly indicate generic memory (RAM) corruption as the cause of the crashes, only one indicates the Nvidia drivers as the cause of that crash.

To try to force Windows to show the underlying cause of the crashes, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

Before you run Driver Verifier, please create a new System Restore Point

https://answers.microsoft.com/en-us/windows/for...

---

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail