Jump to content

Aida64 Win10 (2004) Crashing


Recommended Posts

Been getting a few crashes in new Windows 10 (2004)
Extreme version 6.25.5400

 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  aida64.exe

WATSON_BKT_EVENT:  BEX

ERROR_CODE: (NTSTATUS) 0xc0000409 - 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.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000004

EXCEPTION_STR:  0xc0000409

BAD_STACK_POINTER:  ffffd5006ecfece8

STACK_TEXT:  
ffffd500`6ecfece8 fffff804`545efe29     : 00000000`00000139 00000000`00000004 ffffd500`6ecff010 ffffd500`6ecfef68 : nt!KeBugCheckEx
ffffd500`6ecfecf0 fffff804`545f0250     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffd500`6ecfee30 fffff804`545ee5e3     : ffffd500`6ecff7c0 00000000`00000000 ffffd500`6ecfea60 00000000`00000000 : nt!KiFastFailDispatch+0xd0
ffffd500`6ecff010 fffff804`54688355     : 00000000`04bcf190 00000000`00403670 ffffd500`6ecff710 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323
ffffd500`6ecff1a0 fffff804`546123c1     : ffffd500`6ecff710 00000000`00000000 fffff488`b76afa00 fffff804`00000003 : nt!RtlpGetStackLimitsEx+0x14b185
ffffd500`6ecff1d0 fffff804`5447a7f6     : fffff488`b76af038 ffffd500`6ecffe20 fffff488`b76af038 00000000`00000000 : nt!RtlDispatchException+0x1df681
ffffd500`6ecff8f0 fffff804`545dedd2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
ffffd500`6ecfffb0 fffff804`545deda0     : fffff804`545eff65 ffffa780`00000000 ffffa7d3`fc600420 ffffa88c`3f17a700 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff488`b76aeef8 fffff804`545eff65     : ffffa780`00000000 ffffa7d3`fc600420 ffffa88c`3f17a700 ffffa88c`3f17a700 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff488`b76aef00 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125


SYMBOL_NAME:  nt!KiFastFailDispatch+d0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.450

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_MISSING_GSFRAME_STACKPTR_ERROR_nt!KiFastFailDispatch

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10
Link to post
Share on other sites
8 hours ago, Metal2Mesh said:

Been getting a few crashes in new Windows 10 (2004)
Extreme version 6.25.5400

What motherboard, CPU and video card(s) do you have in your system?  Do you have Valorant Vanguard installed?

Link to post
Share on other sites

I have 9900K on z390 Maximus xi code. two 2080ti cards.
This is a fresh install of Windows 10 (2014) 

It can happen random times not under load, always ntkrnlmp.exe.

I use aida64extreme to run a beadapanel.
Turned off my overclocks upgraded my bios to Aug18 (1602). Now only xmpII to run the memory at 3600mhz.

This build of windows has been an absolute nightmare. I think they changed the way their kernel connects to the hardware, I don't know not a coder, just a philosopher. I have come to that conclusion cause none of the drivers work right, Nvidia had to make a hot fix version, and even with Chipset drivers the bios sends too much info to windows and there is an event viewer.
Like I said a nightmare, I don't understand why it's not more known, unless everyone is still on 1909.

 

CE3DD5DF-2F72-4F50-9CDB-E6C3E15778B2.jpg

Link to post
Share on other sites

This was my very first BSOD a day later when I installed 2004.
 

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  aida64.exe

STACK_TEXT:  
ffff9b0b`57bae748 fffff807`172760ba     : 00000000`0000001a 00000000`00000403 ffff9480`000306e8 87000004`1898dc66 : nt!KeBugCheckEx
ffff9b0b`57bae750 fffff807`170ab976     : 00000000`004163bb fffff807`17a50b40 00000000`000000bb 00000000`00000080 : nt!MiDeleteClusterPage+0x16386a
ffff9b0b`57bae830 fffff807`170c1588     : 00000000`00000000 ffff9b0b`57baef20 ffff9b0b`57baef20 00000000`00000000 : nt!MiDeletePteRun+0xb76
ffff9b0b`57baea60 fffff807`17011bfe     : ffff9e8a`531d3900 ffff9480`000308b8 00000000`00000000 00000000`00000003 : nt!MiDeleteVaTail+0x78
ffff9b0b`57baea90 fffff807`17011d10     : 00000000`00000000 ffff9e8a`531d3900 00000000`00000000 00000000`00000000 : nt!MiWalkPageTablesRecursively+0x50e
ffff9b0b`57baeb20 fffff807`17011d10     : 00000000`00000000 ffff9e8a`531d3900 ffff94ca`00000000 00000000`00000010 : nt!MiWalkPageTablesRecursively+0x620
ffff9b0b`57baebb0 fffff807`17011d10     : ffff9b0b`57baee70 ffff9e8a`531d3900 00000000`00000000 00000000`00000020 : nt!MiWalkPageTablesRecursively+0x620
ffff9b0b`57baec40 fffff807`1700e61b     : 00000000`00000000 ffff9e8a`531d3900 00000000`00000000 00000000`00000030 : nt!MiWalkPageTablesRecursively+0x620
ffff9b0b`57baecd0 fffff807`170c22f1     : ffff9b0b`57baee70 ffff9e8a`00000000 00000000`00000002 00000000`00000000 : nt!MiWalkPageTables+0x36b
ffff9b0b`57baedd0 fffff807`170a789f     : 00000000`00000000 00000000`00000060 ffff9e8a`531d39c0 00000000`06116fff : nt!MiDeletePagablePteRange+0x491
ffff9b0b`57baf250 fffff807`1709d9bb     : ffff9e8a`531d3280 00000000`00000000 ffff9e8a`00000000 fffff807`00000001 : nt!MiDeleteVad+0x41f
ffff9b0b`57baf380 fffff807`17465fdc     : ffff9b0b`00000000 00000000`00000000 ffff9b0b`57baf4e0 00000000`00008000 : nt!MiFreeVadRange+0xa3
ffff9b0b`57baf3e0 fffff807`17465c05     : ffff8809`80602a20 01d00060`00000000 00000000`00000000 00000000`00000000 : nt!MmFreeVirtualMemory+0x39c
ffff9b0b`57baf520 fffff807`171ef475     : ffff9e8a`5315f080 fffff807`17040a92 ffff9e8a`43e02340 ffff8809`844a6aff : nt!NtFreeVirtualMemory+0x95
ffff9b0b`57baf580 fffff807`171e19c0     : ffff8850`d983e393 ffff8809`00000000 ec00cee6`3f71e67c 00000000`00000001 : nt!KiSystemServiceCopyEnd+0x25
ffff9b0b`57baf718 ffff8850`d983e393     : ffff8809`00000000 ec00cee6`3f71e67c 00000000`00000001 ffff8809`0000178f : nt!KiServiceLinkage
ffff9b0b`57baf720 ffff8850`d983c5ec     : ffffffff`00000000 ffff9e8a`00000000 00000000`00000000 00000000`00000001 : win32kbase!SURFACE::bDeleteSurface+0x533
ffff9b0b`57baf8f0 ffff8850`d9825eb0     : ffffffff`f905178f ffff8850`d9a18980 00000000`0000178f ffff9b0b`57baf969 : win32kbase!SURFREF::bDeleteSurface+0x14
ffff9b0b`57baf920 ffff8850`da06df26     : 00000000`00cc0020 00000000`ffffffff ffff8809`86754000 00000000`00000000 : win32kbase!NtGdiDeleteObjectApp+0x180
ffff9b0b`57baf9d0 fffff807`171ef475     : 00000000`163039f4 ffff9e8a`00000001 ffff9b0b`57bafa80 ffff9b0b`57bafa80 : win32k!NtGdiDeleteObjectApp+0x16
ffff9b0b`57bafa00 00000000`76fe1cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0009eed8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fe1cfc


SYMBOL_NAME:  win32kbase!SURFACE::bDeleteSurface+533

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.388

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  533

FAILURE_BUCKET_ID:  0x1a_403_win32kbase!SURFACE::bDeleteSurface

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e43cec66-e8fb-2d9a-ab13-a08f8896bed0}

Followup:     MachineOwner
Link to post
Share on other sites

I kept all my dmp files, majority have been aida64 with the ntkrnlmp.exe, which were doing normal things, but this one was Memory Management with win32kbase I believe cause of game controller 2004 did not like. Ran Memory Diagnostics Tool, every checked out fine. I never had problems with anything while running 1909 and my machine was over clocked so all cores at 5ghz.

Microsoft should have called this version of Windows 10 (2020) instead of (2004) LOL

Link to post
Share on other sites
  • 2 weeks later...
On 8/25/2020 at 9:09 AM, Metal2Mesh said:

Hey got rid of 2004, it's a nightmare. I went back to 1909.
If I farted I would get a blue screen. It's ridiculous that MS would release such a POS.

Take care and thanks for a great product.

Thank you for letting us know about the resolution.  Thankfully 2004 is only installed by a handful of our own computers.  I guess Microsoft can see such feedbacks and they're holding back the new update to "plague" all systems :) 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...