Fairly new to TC 8.52, and While using TC 8.52 x64, Multiple times a day I get a error screen that says
DAX error
Access violation at adress xxxxxxx in module SYSNAV~1.dll Read of address FFFFFFFFFFFFF
Typically I get strange results if I ignore the error message, so I just shut down TC then restart
Very irritating.
Any fix? Anyone else seeing this?
John
DAX error in TC 8.52 under Win10 PRo x64
Moderators: Hacker, petermad, Stefan2, white
- ghisler(Author)
- Site Admin
- Posts: 50918
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
SYSNAV~1.dll seems to belong to some shell extension. The problem you have is most probably a faulty shell extension.
To correct it, please try the following:
1. Get the free tool ShellExView:
http://www.nirsoft.net/utils/shexview.html
2. Start it. If using Total Commander 32-bit, you need to get the 32-bit
version, otherwise the 64-bit version of ShellExView
3. Sort the shell extensions by type
4. Disable all context menu shell extensions one by one (you can hide/keep
those belonging to Windows, they are usually OK).
5. Continue until Total Commander stops crashing
6. Now you can re-enable the extensions which don't cause any problems
To correct it, please try the following:
1. Get the free tool ShellExView:
http://www.nirsoft.net/utils/shexview.html
2. Start it. If using Total Commander 32-bit, you need to get the 32-bit
version, otherwise the 64-bit version of ShellExView
3. Sort the shell extensions by type
4. Disable all context menu shell extensions one by one (you can hide/keep
those belonging to Windows, they are usually OK).
5. Continue until Total Commander stops crashing
6. Now you can re-enable the extensions which don't cause any problems
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
I think I found the culprit. Prior to testing and buying Total Commander, I was installing and trying several alternative file management programs, one of which was System Navigator. Doing a search on sysnav*.dll, it winds up that there was only one instance of it on the computer, and that was in the System Navigator folder.
So, I have uninstalled System Navigator and hopefully that will be the end of the problems. If notm then I will shellex and see if the uninstall left any bits and pieces behind
Thanks for the prompt response -
John
So, I have uninstalled System Navigator and hopefully that will be the end of the problems. If notm then I will shellex and see if the uninstall left any bits and pieces behind
Thanks for the prompt response -
John