System detected an overrun of a stack-based buffer in this application


  1. empleat
    Posts : 582
    Windows 10 Pro 64 bit 19044.1706
       New #1

    System detected an overrun of a stack-based buffer in this application


    No malware detected, i did system repair from usb not long time ago and didn't do anything on my pc. Why i have already this garbage ??? It happens when i try access focus assist menu from windows setting. Gonna try sfc and dism. But i don't want repair again, it is exhausting to do that every day literally ! Is always something. Someone know better solution ?
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #2

    There are log collectors used in another forum room.
    Run V2 and upload results into this thread.

    BSOD - Posting Instructions
      My Computer
    Quote Quote

  4. empleat
    Posts : 582
    Windows 10 Pro 64 bit 19044.1706
    Thread Starter
       New #3

    I don't know if you wanted that, just for info. I have no bsod btw.
    System detected an overrun of a stack-based buffer in this application Attached Files
      My Computer
    Quote Quote

  6. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #4

    empleat said:
    I don't know if you wanted that, just for info. I have no bsod btw.
    The logs displayed 25 recent BSOD.

    For the problem with the application > post a support ticket with the company

    1) Run the DM log collector and upload results directly into this thread:
    BSOD - Posting Instructions

    2) List all installed
    a) antivirus software
    b) spyware
    c) drive encryption software

    3) What was tweaking.com used to troubleshoot?

    4) Post a share link using one drive, drop box, or google drive for:
    Code:
    16/02/2020 10:40:36 pm    597.77 C:\Windows\LiveKernelReports\WFP-20200216-2240.dmp



    5) Open administrative command prompt and type or copy and paste:
    6) sfc /scannow
    7) dism /online /cleanup-image /restorehealth
    8) sfc /scannow
    9) chkdsk /scan
    10) wmic recoveros set autoreboot = false
    11) wmic recoveros set DebugInfoType = 7
    12) wmic recoveros get autoreboot
    13) wmic recoveros get DebugInfoType
    14) bcdedit /enum {badmemory}

    15) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    16) Make sure that there is no over clocking while troubleshooting

    17) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    18) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

    19) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    20) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate
    How to use SeaTools for Windows | Seagate Support US

    21) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
    > if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive
      My Computer
    Quote Quote

  7. empleat
    Posts : 582
    Windows 10 Pro 64 bit 19044.1706
    Thread Starter
       New #5

    Wait what ??? Must be wrong... I haven't bsod very long time... My pc isn't crashing, no problems otherwise strange...
      My Computer
    Quote Quote

  8. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #6

    When there are unexpected shutdowns and restarts they may or may not create dump files.

    Steps can be made to increase the likelihood of creating dump files.

    These were BSOD that failed to create dump files:

    Code:
    Event[16]:
  Log Name: System
  Source: volmgr
  Date: 2020-01-25T19:42:43.745
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
Crash dump initialization failed!

    Code:
    Event[102]:
  Log Name: System
  Source: volmgr
  Date: 2020-01-25T19:50:12.698
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
Crash dump initialization failed!

    Code:
    Event[210]:
  Log Name: System
  Source: volmgr
  Date: 2020-01-26T13:25:45.261
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
Crash dump initialization failed!

    Code:
    Event[7832]:
  Log Name: System
  Source: volmgr
  Date: 2020-02-16T22:47:39.667
  Event ID: 46
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
Crash dump initialization failed!





    These were also displayed in the logs:


    Code:
    Event[2464]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-01-30T01:23:04.516
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: user-PC
  Description: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Code:
    Event[9640]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2020-02-24T03:43:01.895
  Event ID: 41
  Task: N/A
  Level: Critical
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: user-PC
  Description: 
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Code:
    Event[2452]:
  Log Name: System
  Source: EventLog
  Date: 2020-01-30T01:23:25.278
  Event ID: 6008
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: user-PC
  Description: 
The previous system shutdown at 1:20:16 AM on ?1/?30/?2020 was unexpected.
    Last edited by zbook; 29 Feb 2020 at 13:34.
      My Computer
    Quote Quote

  9. empleat
    Posts : 582
    Windows 10 Pro 64 bit 19044.1706
    Thread Starter
       New #7

    That doesn't make any sense what so ever. No unexpected reboots , no bsod. I am on my pc during day and i am not afk. Than i shutdown pc at night. I restarted at one point a lot, when i was trying to install linux as dualboot. But no crashes, or bsod, or unexpected shutdowns, what so ever !!!!

    I will have new pc and i don't feel like doing all of these, which is shot into dark, so i let it go.
      My Computer
    Quote Quote

  10. FreeBooter
    Posts : 5,330
    Windows 11 Pro 64-bit
       New #8

    Perform clean boot state.

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
      My Computer
    Quote Quote

  12. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #9

    New PC should not be having BSOD.

    Typically Return Merchandise Authorizations (RMA) are sought.

    If it is no longer under warranty they can be troubleshooted.
      My Computer
    Quote Quote

 

  Related Discussions
On a Windows 10 desktop today there was this error message... “The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application“ Any...
After i restarted pc, i got this error message... pop out window was titled: Logonui.exe. And message was: system detected overrun of stackbased overflow. Than i got black screen and i had to do hard restart... I checked dism both check health and...
BSOD Driver Overran stack buffer
in BSOD Crashes and Debugging

I get the Driver overran stack buffer error with BSOD randomly sometimes while gaming (rust, dishonored, Skyrim, civ 5, and most any other game). I have manually updated the drivers for my motherboard, video card, and peripheries. I also randomly...
driver overan stack buffer bsod
in BSOD Crashes and Debugging

My HP Split laptop bought in 2013 crashes regularly with different BSOD messages, I used CHKDSK /F to confirm both the c: ssd and d: hdd are ok. The crashes occur when I remove the keyboard and hdd so I can use the screen and ssd as a tablet. I...
Driver Overran Stack Buffer
in BSOD Crashes and Debugging

Please help while I was using my laptop then suddenly blue screen happened with error saying Driver_Overran_Stack_Buffer. I don't know what cause it. I don't want to reformat o restore my laptop for I might lose my programs.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 İ Designer Media Ltd
All times are GMT -5. The time now is 13:59.
Find Us




Windows 10 Forums