Toad 2025 R1 – Repeated EAccessViolation (EurekaLog) crashes even after config reset

Hi there,

I’m encountering repeated crashes in Toad for Oracle 2025 R1, and noticed others were resolved when provided call stack/logs. Appears each may be different, so posting mine here. Thanks.

Issue:
Toad crashes frequently with a EurekaLog dialog:
EAccessViolation
Access violation at address XXXXXXXX in module 'Toad.exe'
Read of address 0000000000000000

Crashes occur:

  • While working in editor tabs (even simple actions like typing)
  • Sometimes shortly after launch
  • Not consistently tied to a specific connection or query

Current Behavior

  • Application becomes unstable during normal use (editor interaction)
  • Crashes can happen multiple times in a short period
  • Occurred even after restarting the system
  • Also observed instability alongside other UI components (not limited to Toad)

What has been attempted

  • Cleared recovery/autosave/temp files
  • Reset Toad.ini (forced clean rebuild)
  • Started with a clean profile
  • Tested across different connections (DEV vs PRD)
  • Avoided restoring recovery documents
    Despite this, crashes are still occurring.

Support Info

  • Error generated via EurekaLog (7.12.x hotfix 5)
  • Able to provide:
    • full .el crash report
    • Call Stack section (most relevant)
    • Toad.ini (new vs previous if helpful)
  • This behavior began after a system BSOD (May 15), which may have left Toad in an inconsistent state (recovery/config). However, crashes are still occurring even after clearing autosave and rebuilding Toad.ini.
  • Also, another program had access violation issues, but has since recovered.
  • I can try installing latest Toad 2026, but it has to go through an assessment process and migrate my key repos etc.. over, don't want to bring the issue over. please advise, thanks.

Thanks in advance — happy to provide call stack or logs if that helps isolate the issue.

Can you post the call stack? Steps to do that.

  1. When you a dialog similar to this:
  2. Uncheck "Restart" (if present and checked), then click where it says "click here"
  1. You'll then see something like this:

  1. Check "Copy to clipboard" (don't just make a screen shot of it like I did!) and click OK.
  2. Come back here and paste the contents on your clipboard, or email it to me at john.dorlon@quest.com

Hi John, thanks for the prompt reply.
My version of Toad doesn't display the messageboxes you showed.
I simply get the EurekaLog 7.12.0.5 hotfix 5 crash report message box, informing me to send the specific Toad_Internal_Crash.el file to technical support of Toad.exe/

please advise, further, thanks.

Hi,

When you say you "started with a clean profile" what do you mean exactly? If it was something other than Utilities -> Manage User Settings -> Reset to a clean set of user files from the base installation, try this:

  1. Start Toad and don't make a connection
  2. Go to Utilities -> manage user settings
  3. Choose "Reset to a clean set of user files from the base installation"
  4. If you want to keep your connections or anything in the "Recover" list, you can check whatever items you want in there. I suggest keeping it to a minimum to improve your chances of this fixing the problem. Just choosing "connections" should be fine.

Feel free to send your toad.el file to the email address I posted above

Hi John,

Thanks for the prompt reply. My version of Toad doesn't display the message boxes you showed. I simply get the EurekaLog 7.12.0.5 hotfix 5 crash report message box, informing me to send the specific Toad_Internal_Crash.el file to technical support of Toad.exe/

here is contents of that file, hope that helps,
Btw, I tried to rename "user files" directory and restart, which I wasn't able to test long enough since I was missing too many items (i.e. connections) and reverted back. so please omit that one. I just attempted your user manager -> reset and kept only connections, but it also crashed. Testing now, with the reset and no connections migrated.

Also, it may have started after a BSOD experienced on May-15. However, I was using Toad after that without issues, so may only the last two days problematic.

EurekaLog 7.12.0.5 hotfix 5 Enterprise 29 00000000000000000000000000000000 00000000000000000000000000000000 0000000000000000000000000000000000000000 CD00CA58735B47F2B235CB31DA0494AD

Application:

1.1 Start Date : 46162.6500
1.2 Name/Description: Toad.exe

Exception:

2.1 Date : 46162.6502
2.2 Address: 77504772 [ntdll.dll:00064772] ntdll.RtlTryEnterCriticalSection
2.5 Type : [CreateThreadHook] EAccessViolation
2.6 Message: Access violation at address 77504772 in module 'ntdll.dll'. Write of address FFFFFE64
Access violation at address 77504772 in module 'ntdll.dll'. Write of address FFFFFE64
2.7 ID : 00006827
2.11 Sent : 0

Custom Information:

9.1 Stage: CreateThreadHook
9.2 Message: Access violation at address 77504772 in module 'ntdll.dll'. Write of address FFFFFE64
9.3 GetLastError: 0
9.4 Internal EurekaLog Exception Address: 00000000
9.5 Internal EurekaLog Exception Type: EAccessViolation
9.6 Internal EurekaLog Exception Message: Access violation at address 77504772 in module 'ntdll.dll'. Write of address FFFFFE64
9.7 ExceptAddr: 77504772 [ntdll.dll:00064772] ntdll.RtlTryEnterCriticalSection
9.8 ExceptObj.ClassName: EAccessViolation
9.9 ExceptObj.Message: Access violation at address 77504772 in module 'ntdll.dll'. Write of address FFFFFE64
9.10 Active User Exception Address: 00000000
9.11 Active User Exception Type:
9.12 Active User Exception Message:
9.13 Last Thread Exception Address: 00000000
9.14 Last Thread Exception Type:
9.15 Last Thread Exception Type:
9.16 Main Thread: 15604
9.17 Current Thread: MAIN

Call Stack Information:

* Internal Crash Call Stack: *
038B304C [Toad.exe:0017304C] EBase.InternalErrorSet 2139[860]
0396D1D9 [Toad.exe:0022D1D9] EThreadsManager.CreateThreadHook 1494[473]
7753AC60 [ntdll.dll:0009AC60] ntdll. (possible RtlInterlockedCompareExchange64+496)
7753AC2F [ntdll.dll:0009AC2F] ntdll. (possible RtlInterlockedCompareExchange64+447)
7750D531 [ntdll.dll:0006D531] ntdll. (possible RtlUnwind+657)
77519601 [ntdll.dll:00079601] ntdll. (possible KiUserExceptionDispatcher+33)
774E8D8B [ntdll.dll:00048D8B] ntdll.RtlDosApplyFileIsolationRedirection_Ustr
037879BC [Toad.exe:000479BC] ELowLevel.EnterCriticalSectionTimeout 7766[28]
03783CC5 [Toad.exe:00043CC5] ELowLevel.IsInsideDLLMain 4062[149]
03787A7A [Toad.exe:00047A7A] ELowLevel.EnterCS 7811[106]
03787CDE [Toad.exe:00047CDE] ELowLevel.LockThreadsRead 7889[30]
039715BC [Toad.exe:002315BC] EThreadsManager.TThreadsManager.Purge 3911[44]
03970EC6 [Toad.exe:00230EC6] EThreadsManager.TThreadsManager._ThreadData 3679[182]
0396F4E6 [Toad.exe:0022F4E6] EThreadsManager.TThreadsManager.SetEurekaLogStateInThread 2539[150]
0396F13C [Toad.exe:0022F13C] EThreadsManager.SetEurekaLogStateInThread 2385[12]
039877D7 [Toad.exe:002477D7] EDebugInfo.GetLocationInfo 803[87]
03BD9DC0 [Toad.exe:00499DC0] EExceptionHook.DefaultGetRoutineDescription 1718[48]
03971CBA [Toad.exe:00231CBA] EThreadsManager.TEurekaThreadData.PostCreate 4167[58]
0396FA46 [Toad.exe:0022FA46] EThreadsManager.CreateThreadHandler 2792[934]
0374CF6A [Toad.exe:0000CF6A] System.BeginThread
0396F208 [Toad.exe:0022F208] EThreadsManager.TThreadsManager.IsEurekaLogActiveInThread 2425[120]
059C14CD [Toad.exe:022814CD] ThreadedQueryEngine.TThreadedQueryEngine.ODACExecute 743[737]
0388FEEC [Toad.exe:0014FEEC] System.Classes.TThread.Create
0374CF6A [Toad.exe:0000CF6A] System.BeginThread
0396D173 [Toad.exe:0022D173] EThreadsManager.CreateThreadHook 1471[371]
0374CF6A [Toad.exe:0000CF6A] System.BeginThread
0388FEEC [Toad.exe:0014FEEC] System.Classes.TThread.Create
0388FDD8 [Toad.exe:0014FDD8] System.Classes.TThread.Create
059C1A80 [Toad.exe:02281A80] ThreadedQueryEngine.TQueryThread.Create 944[56]
059C0E14 [Toad.exe:02280E14] ThreadedQueryEngine.TThreadedQueryEngine.CreateQueryThread 531[16]
059C14CD [Toad.exe:022814CD] ThreadedQueryEngine.TThreadedQueryEngine.ODACExecute 743[737]
059C115D [Toad.exe:0228115D] ThreadedQueryEngine.TThreadedQueryEngine.Execute 636[129]
08527C23 [Toad.exe:04DE7C23] ConnectionObjects.TConnectObject.LoadHighlightObjects 13111[451]
084EA98F [Toad.exe:04DAA98F] ConnectionObjects.TConnectionManager.NewConnection 2389[1067]
084E9F73 [Toad.exe:04DA9F73] ConnectionObjects.TConnectionManager.NewConnection 2122[439]
07F39871 [Toad.exe:047F9871] mainform.TfrmMain.ReConnectSessionClick 3833[41]
086C958D [Toad.exe:04F8958D] dxBar.TdxBarItem.DoClick 22276[53]
086C9527 [Toad.exe:04F89527] dxBar.TdxBarItem.DirectClick 22266[59]
086D99A3 [Toad.exe:04F999A3] dxBar.TdxBarItemControl.ControlUnclick 29206[287]
086DDB8E [Toad.exe:04F9DB8E] dxBar.TdxBarButtonControl.ControlUnclick 31438[90]
086F2F6A [Toad.exe:04FB2F6A] dxBar.TCustomdxBarControl.DoLButtonUp 41637[234]
086F14C6 [Toad.exe:04FB14C6] dxBar.TCustomdxBarControl.WMLButtonUp 40863[42]
039F238E [Toad.exe:002B238E] Vcl.Controls.TControl.WndProc
03D00541 [Toad.exe:005C0541] dxHooks.TdxSystemHook.ProcessHookProcs
03D00351 [Toad.exe:005C0351] dxHooks.dxSystemCBTHook
759DFE0D [user32.dll:0002FE0D] user32. (possible TranslateMessage+349)
039C255D [Toad.exe:0028255D] Vcl.Graphics.FreeMemoryContexts
039F7104 [Toad.exe:002B7104] Vcl.Controls.TWinControl.ControlAtPos
039F71C0 [Toad.exe:002B71C0] Vcl.Controls.TWinControl.IsControlMouseMsg
039F7A43 [Toad.exe:002B7A43] Vcl.Controls.TWinControl.WndProc
086E1345 [Toad.exe:04FA1345] dxBar.TdxBarSubMenuControl.IsInternal 33098[21]
086F42A2 [Toad.exe:04FB42A2] dxBar.TCustomdxBarControl.GetEquivalentParentBar 42281[10]
086F316D [Toad.exe:04FB316D] dxBar.TCustomdxBarControl.CanProcessMouseMessage 41704[29]
086F23A2 [Toad.exe:04FB23A2] dxBar.TCustomdxBarControl.WndProc 41278[474]
039F6F08 [Toad.exe:002B6F08] Vcl.Controls.TWinControl.MainWndProc
03893E18 [Toad.exe:00153E18] System.Classes.StdWndProc
759E384D [user32.dll:0003384D] user32. (possible GetMessageTime+2141)
759D4241 [user32.dll:00024241] user32. (possible CallWindowProcW+1985)
759D3EF4 [user32.dll:00023EF4] user32. (possible CallWindowProcW+1140)
77516FFA [ntdll.dll:00076FFA] ntdll.NtCallbackReturn
759DEB7E [user32.dll:0002EB7E] user32. (possible GetWindowThreadProcessId+494)
759D2A53 [user32.dll:00022A53] user32. (possible DispatchMessageW+1187)
76C8117A [win32u.dll:0000117A] win32u.NtUserGetProp
759DDDCC [user32.dll:0002DDCC] user32. (possible GetPropW+156)
759D25BB [user32.dll:000225BB] user32.DispatchMessageW
03B282BB [Toad.exe:003E82BB] Vcl.Forms.TApplication.ProcessMessage
03B282FE [Toad.exe:003E82FE] Vcl.Forms.TApplication.HandleMessage
03B2863D [Toad.exe:003E863D] Vcl.Forms.TApplication.Run
087F6FA8 [Toad.exe:050B6FA8] Toad.initialization 2183[756]
771A7BA7 [KERNEL32.DLL:00017BA7] KERNEL32.BaseThreadInitThunk
7750C519 [ntdll.dll:0006C519] ntdll. (possible RtlInitializeExceptionChain+105)
7750C49A [ntdll.dll:0006C49A] ntdll. (possible RtlClearBits+186)
------------------

Modules Information:

Processes Information:

Assembler Information:

Registers:

Hi,

Thanks for the details. Renaming the User Files folder isn't enough because if you do that, Toad will import settings from an older install (if there is one). Manage User Settings is the best way to reset.

Judging from the call stack, it looks like when Toad goes to run a SQL to get a list of object names for highlighting, there is some problem, but the details of the problem are unknown because the exception handling logic (Eurakalog) throws an exception of its own, so the details of the original exception are lost.

You could turn off object name highlighting (options -> Editor -> Display, uncheck everything in the "Highlight Object names" box) to prevent that code from running, but it seems like there is some deeper problem here, and you may just get a different error at that point.

Maybe the BSOD is relevant, I don't know. You could try removing/reinstalling Toad, but I don't know for sure if that's going to do any good. If you do that, I would make sure to delete (or at least rename so Toad can't find) old settings files. Then if it works you could re-import connections manually.

Update: After resetting the Toad user profile a second time and clearing Edge cache, the issue has not reoccurred under normal use so far.

However, similar crashes were also observed in Edge/Copilot and other applications with ntdll.dll faults, suggesting this may have been environmental rather than Toad-specific.

Currently monitoring.

Regards,
Pierson