Windows 10 DRIVER_OVERRAN_STACK_BUFFER

[TehBlackNinja]

I recently purchased a new monitor that can support 1440p 144Hz G-Sync, and whenever I launch some games, my PC receives the BSoD message DRIVER_OVERRAN_STACK_BUFFER.
How can I fix this?

 

[viveknayyar007]

Hello TehBlackNinja

Can you please try the suggestion given here and see if this works?

Feel free to reply in case further assistance is needed.

Cheers!!

 

[TehBlackNinja]

Hello TehBlackNinja

Can you please try the suggestion given here and see if this works?

Feel free to reply in case further assistance is needed.

Cheers!!

Sorry that didn't check your message in time. But I decided to just reinstall windows instead just to be sure.

But thank you for the suggestion.

 

[TehBlackNinja]

Hello TehBlackNinja

Can you please try the suggestion given here and see if this works?

Feel free to reply in case further assistance is needed.

Cheers!!

Back to square one. Still getting BSoD DRIVER_OVERRAN_STACK_BUFFER. Tried the suggestion, but it didn't help. Do you know anything else I could try?

 

[johnbl]

start cmd.exe as an admin, then run
verifier.exe /standard /all
reboot
if verifier finds a bad driver it will bugcheck and produce a memory .dmp file that names the driver you should update.

use bluescreenview.exe or whocrashed.exe to get the driver name.
when done testing turn off verifier with the comand:
verifier.exe /reset

you can also put your memory dmp file on a server like microsoft one drive and post a link.

 

[TehBlackNinja]

start cmd.exe as an admin, then run
verifier.exe /standard /all
reboot
if verifier finds a bad driver it will bugcheck and produce a memory .dmp file that names the driver you should update.

use bluescreenview.exe or whocrashed.exe to get the driver name.
when done testing turn off verifier with the comand:
verifier.exe /reset

you can also put your memory dmp file on a server like microsoft one drive and post a link.

I've tried another fix at the moment.

As I have 2 monitors. One G-Sync 144Hz and the other non G-Sync 60Hz, I've plugged both of them into my dedicated GPU, Where as I used to have the 144Hz monitor in the GPU and the 60Hz in my integrated GPU. It seems that the two drivers could have been conflicting with each other. And have also uninstalled the drivers for the iGPU.

So I'm seeing that that works for me. If not, then I'll try your solution.

 

[TehBlackNinja]

start cmd.exe as an admin, then run
verifier.exe /standard /all
reboot
if verifier finds a bad driver it will bugcheck and produce a memory .dmp file that names the driver you should update.

use bluescreenview.exe or whocrashed.exe to get the driver name.
when done testing turn off verifier with the command:
verifier.exe /reset

you can also put your memory dmp file on a server like microsoft one drive and post a link.

Still getting BSoD. Tried out your suggestion and kept getting BSoD during startup. Was able to get the minidump for both the DRIVER_OVERRAN_STACK_BUFFER and the new one.

Onedrive URL

It said the main issue DRIVER_OVERRAN_STACK_BUFFER is linked to nvlddmkm.sys. But I've reinstalled my Nvidia drivers with DDU at least 10 times in the past 7 days.

 

[johnbl]

should figure out why I could not read your BIOS info from your memory dump.
you might scan for rootkits, and provide info about the motherboard/machine.

I would assume your stack overrun will be ok when you update the 3 GPU drivers to a matching build.

-------------
second bugcheck: verifier checked the drivers for common programming mistakes, found that
avast! Virtualization Driver was using a user mode handle as a kernel mode handle called a bugcheck because of the mistake. (programmers do this because it works MOST of the time, when it does not work it tends to corrupt memory of other drivers. Just bad practice for a driver) Here was the driver name:
\SystemRoot\system32\drivers\aswSnx.sys Wed Sep 16 08:39:29 2015

took 3 seconds for verifier.exe to find this problem, shame on the developers of aswSnx.sys
I would uninstall or update the product if they made a fix. otherwise you will have to exclude the driver from verifier.exe to continue testing your system for other problems.

I could not read the BIOS info in this bugcheck also.
---------
looking at your crash dump, looks like the nvidia driver is being corrupted, it complained about a security cooking being incorrect.
you have 3 nvidia drivers for your graphics card, one looks like it is mismatched to the build.

\SystemRoot\system32\drivers\nvhda64v.sys Thu Apr 16 12:03:16 2015
\SystemRoot\system32\DRIVERS\nvlddmkm.sys Fri Oct 02 19:08:52 2015
C:\Program Files\NVIDIA Corporation\NvStreamSrv\NvStreamKms.sys

so I am thinking that nvhda64v.sys from april is your problem, you should update the high definition audio driver for your nvidia card. (i scanned my system for the driver and I have a much newer version than you)
(or just make sure you select it when you reinstall the current video drivers. this driver provides HDMI and displayport sound support for speakers inside of your monitor via the video cable, you can disable the driver after you update if you do not have speakers in your monitor)

here are some other problems with your system. most likely unrelated to the cause of this bugcheck:

you might also want to update your old
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC driver
\SystemRoot\system32\DRIVERS\Rt64win7.sys Wed Jan 08 01:01:36 2014
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
(new version from yesterday.)
old network drivers tend to mess up nvidia graphics drivers because of the problems they introduce to the streaming software.
old drivers can also mess up antivirus software for the same reason.

you also have some old logitech wingman software driver from 2010 you might want to update it or remove it
\SystemRoot\system32\drivers\WmXlCore.sys Tue Apr 27 13:09:26 2010
\SystemRoot\system32\drivers\WmVirHid.sys Tue Apr 27 13:08:53 2010

I was unable to read the BIOS info from the memory dump, this often indiacte you have a old or custom bios
you might check with the motherboard vendor to see if there is a BIOS update.

 

[TehBlackNinja]

I've seem to have gotten my PC stable for a couple days now. It seems to be the G-Sync option in the Control Panel. Putting it on Windowed and Fullscreen seemed to fix it instead of just Fullscreen mode.