Crash 671 - Additional info for likely related ntdll crash (Rename + Evaluator)

I just submitted a crash report for ID 671 (I'll paste below for context), but afterwards noticed something else that might be relevant.

The first time when the crash happened accidentally, the crash seems to have been in shell32.dll and Opus gave the prompt about the crash and offered to restart. So the crash log in 671 was for the very first accidental crash.

However, for the reproduction steps I described, while that still does produce a crash, I'm not sure if it's the exact same crash, because in the Windows event logs the manually-induced crash seems to instead be in ntdll.dll, not shell32.dll like the very first one.

Importantly, this also does not cause Opus to display the crash prompt and does not create a reportable error log like the very first one did, Opus simply restarts.

I assume they're related, but if you can't get the shell32.dll crash through the steps described and only ntdll.dll, that's why. There might have been some other factor the very first time it happened, like maybe I didn't fully press them simultaneously, but rather just one very soon after the other or something, not sure. I'll post the windows event viewer log for the ntdll.dll crash below too.


Original Report:

I seem to be able to reliably re-produce this crash by selecting a file in the lister, then pressing F2 to rename, then with F2 still held down, simultaneously press the F3 key, which I have bound to the following evaluator block via "Preferences > File Operations > Renaming Files > Control Keys". (It's meant to move the cursor to the end of the file stem)

if (len(valstem) > 0 && len(valstem) < len(value)) {
selstart = len(valstem);
selend = len(valstem);
}

I discovered this after I apparently accidentally fat-fingered both the F2 and F3 keys while going to rename a file with F2. I wasn't intending to press them both.

Current system information:
Directory Opus 13.20.2 (Beta) Build 9410 x64
OS 10.0 (B:26200 P:2 T:1) SP 0.0


Event viewer log for the manually-induced crash which mentions ntdll.dll and might not have been included in the crash report:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error"
		          Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}"/>
		<EventID>1000</EventID>
		<Version>0</Version>
		<Level>2</Level>
		<Task>100</Task>
		<Opcode>0</Opcode>
		<Keywords>0x8000000000000000</Keywords>
		<TimeCreated SystemTime="2025-12-22T17:50:30.6083825Z"/>
		<EventRecordID>217807</EventRecordID>
		<Correlation/>
		<Execution ProcessID="44312"
		           ThreadID="38340"/>
		<Channel>Application</Channel>
		<Computer>JOE-PC</Computer>
		<Security UserID="[REMOVED]"/>
	</System>
	<EventData>
		<Data Name="AppName">dopus.exe</Data>
		<Data Name="AppVersion">13.20.2.0</Data>
		<Data Name="AppTimeStamp">694334e9</Data>
		<Data Name="ModuleName">ntdll.dll</Data>
		<Data Name="ModuleVersion">10.0.26100.7462</Data>
		<Data Name="ModuleTimeStamp">9225342c</Data>
		<Data Name="ExceptionCode">c0000374</Data>
		<Data Name="FaultingOffset">00000000001176b5</Data>
		<Data Name="ProcessId">0x4438</Data>
		<Data Name="ProcessCreationTime">0x1dc736b631c3b57</Data>
		<Data Name="AppPath">C:\Program Files\GPSoftware\Directory Opus\dopus.exe</Data>
		<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
		<Data Name="IntegratorReportId">9be9a6a3-2815-406d-af2f-5c5713367bc9</Data>
		<Data Name="PackageFullName"/>
		<Data Name="PackageRelativeAppId"/>
	</EventData>
</Event>