📎 AI Summary:
The thread discusses a Windows 10 system experiencing repeated "driver overran stack buffer" errors during startup, which eventually resolved after several attempts. The original poster seeks advice on diagnosing the issue, including locating dump files and ensuring proper dump settings; a contributor suggests checking dump configuration and drive health. The conversation also covers enabling the pagefile to facilitate dump creation, with the original poster confirming it is enabled. Overall, the thread reflects troubleshooting efforts for a startup error, with recommendations for system checks and configuration adjustments.
D

dusty1000

New Member
Member details
Joined
Mar 14, 2018
Messages
12
Thread Author #1
PC attempted startup many times, reporting different errors, but "driver overran stack buffer" repeated several times. No previous history of problems since installing 10 over 1 year ago. Eventually started after multiple attempts over several hours, but I had not changed any settings. All windows updates had been installed many days prior to this issue.

PC has now worked without problems for several hours, but I am reluctant to turn it off!

Any advice much appreciated.
 

Attachments

Solution
kemical
Hi,
can you please double check your settings:

Open the run application.
Type sysdm.cpl in the run box and click ok.
Look across the top of the system properties box for 'Advanced' and click that.
Look for 'Startup and Recovery' near the bottom and click 'settings'.
Near the bottom you'll see a drop down menu under the heading 'write debugging information'.
In the drop down menu choose ' small memory dump (256KB)'
Under 'small dump directory' make sure it says %SystemRoot%\Minidump.
Click ok and your good to go.

Did you realise your motherboard has no driver support past Windows 7?

I tried to find you a storage driver but the last driver is for win 7 only:
GA-EP45T-DS3R (rev. 1.0) | Motherboard - GIGABYTE Global

Can you...
Sort by date Sort by votes
kemical

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
#21
I see you wrote the above a while ago, have you managed to get back into the bios?

If not try resetting your bios by removing the battery for a minute or so. 30 seconds is usually long enough but a minute is a definite.
Hopefully your bios will default to ide.

I think in your case you may have to reinstall windows after enabling ahci which I know your not happy about doing. Hopefully the bios reset will get you back to square one.
(just make sure the bios time is set correctly after the interruption.
 

Upvote 0 Downvote
You must log in or register to reply here.