Sometimes, in a PC i've installed TC, it crashed with no reason. I have noticed that most of the time it crashed when i tried to access a drive via the drive selection combo using the mouse. When i open the drives combo, it opens normally but when i hover over the list (drive A: specifically), i get the error message. I finally decided to write down the error message and post it here:
Exception EAccessViolation in module TOTALCMD.EXE at 0002FAF2.
Access violation at address 00430D1E. Read of address 00000028.
When i press OK, TC closes. If i try to execute it again and do the same thing, i get the error message again. If i logout from Windows and login again, TC works just fine!
This happens under a fresh setup of Win2000 Server SP4 with only a few applications installed. I have not noticed such a behavior under Win2KPro.
Occasional TC crash under unknown circumstances (W2KServer).
Moderators: Hacker, petermad, Stefan2, white
Occasional TC crash under unknown circumstances (W2KServer).
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
Re: Occasional TC crash under unknown circumstances (W2KServ
Happened again. This time, "Read of address 00000428."wanderer wrote:Exception EAccessViolation in module TOTALCMD.EXE at 0002FAF2.
Access violation at address 00430D1E. Read of address 00000028.
UPDATE: And again. Address 44004128.
No antivirus at all.Sir_SiLvA wrote:which applications are installed
Steganos? AntiVir-Software?
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
- ghisler(Author)
- Site Admin
- Posts: 50541
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
This is a known mouse driver bug, which causes Windows to send invalid mouse messages to comboboxes. Unfortunately I couldn't reproduce it myself, so I cannot write a workaround - the error also seems to happen in a place in Windows where I have no influence.Sometimes, in a PC i've installed TC, it crashed with no reason. I have noticed that most of the time it crashed when i tried to access a drive via the drive selection combo using the mouse. When i open the drives combo, it opens normally but when i hover over the list (drive A: specifically), i get the error message.
Solution: Use the drive buttonbar instead of the dropdown list, or the dropdown list with Alt+F1 <Letter> only, or try to find an updated mouse driver.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
ghisler(Author) wrote:This is a known mouse driver bug, which causes Windows to send invalid mouse messages to comboboxes. Unfortunately I couldn't reproduce it myself, so I cannot write a workaround - the error also seems to happen in a place in Windows where I have no influence.
Solution: Use the drive buttonbar instead of the dropdown list, or the dropdown list with Alt+F1 <Letter> only, or try to find an updated mouse driver.

- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
- SanskritFritz
- Power Member
- Posts: 3693
- Joined: 2003-07-24, 09:25 UTC
- Location: Budapest, Hungary
Thanx for the tip. I'll try it.SanskritFritz wrote:2wanderer
You also might give KatMouse a try.
- Wanderer -
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Normally using latest TC on:
x32: WinXPx32 SP3 (very rarely nowadays).
x64: Clients/Servers - Win10/Win11 and Win2K16 to Win2K22, mainly Win10 though.