Crash on Copy (F5)/Move (F6) under Windows 10
Moderators: sheep, Hacker, Stefan2, white
-
- Junior Member
- Posts: 43
- Joined: 2007-07-28, 01:10 UTC
Crash on Copy (F5)/Move (F6) under Windows 10
System: Windows 10 64bit
TC-Version: 9.0a 64bit
Bought a completely new computer.
Everything is absolutely fresh and newly installed.
In addition the system is installed on a M.2 (Samsung 960 Evo) if this matters at all. Just mentioning it because it's a new technology.
While using TC and I use F5/F6, after a while TC crashes using these functions.
When I use Ctrl-C/-V at any time this works always.
The crash happens only after a while of using TC.
Not right from the start.
After restart of TC everything is fine and F5/F6 works perfectly for a limited time. Just after a not detectable time passed the crash is likely to appear.
I have to add that I use settings from earlier versions by the *.ini which puts all started copy/move operations automatically to the background.
Maybe there is a possible source of error.
But doesn't explain why it only stops working after a significant time has passed.
Overall the new Version is great but this is very disturbing because of the insecurity while working.
Is there a possibility to log such errors to come closer to a solution?
TC-Version: 9.0a 64bit
Bought a completely new computer.
Everything is absolutely fresh and newly installed.
In addition the system is installed on a M.2 (Samsung 960 Evo) if this matters at all. Just mentioning it because it's a new technology.
While using TC and I use F5/F6, after a while TC crashes using these functions.
When I use Ctrl-C/-V at any time this works always.
The crash happens only after a while of using TC.
Not right from the start.
After restart of TC everything is fine and F5/F6 works perfectly for a limited time. Just after a not detectable time passed the crash is likely to appear.
I have to add that I use settings from earlier versions by the *.ini which puts all started copy/move operations automatically to the background.
Maybe there is a possible source of error.
But doesn't explain why it only stops working after a significant time has passed.
Overall the new Version is great but this is very disturbing because of the insecurity while working.
Is there a possibility to log such errors to come closer to a solution?
How does the crash look like exactly? Do you get an error message from TC that contains a stack trace? Does it freeze (still too many people out there calling this a crash)? Does it just exit without any errors? Does the Windows Error Reporting pop up ("Program X has stopped working")?
Which copy method do you use (check Settings > Operation > Copy/Delete)?
Regards
Dalai
Which copy method do you use (check Settings > Operation > Copy/Delete)?
Regards
Dalai
-
- Junior Member
- Posts: 43
- Joined: 2007-07-28, 01:10 UTC
- ghisler(Author)
- Site Admin
- Posts: 36782
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Since you are the first with this problem, I need some kind of stack trace. Could you use the tool Procdump to create one for me, please:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows) with Alt+Shift+F5, e.g. procdump.lnk
3. Change the lnk file with alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. Send me the dump from c:\dumps (zipped).
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx
1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows) with Alt+Shift+F5, e.g. procdump.lnk
3. Change the lnk file with alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. Send me the dump from c:\dumps (zipped).
Author of Total Commander
http://www.ghisler.com
http://www.ghisler.com
-
- Junior Member
- Posts: 43
- Joined: 2007-07-28, 01:10 UTC
-
- Junior Member
- Posts: 43
- Joined: 2007-07-28, 01:10 UTC
- ghisler(Author)
- Site Admin
- Posts: 36782
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Unfortunately I cannot find your e-mail. Could you send it to my GMail account too, please? cghisler at gmail dot com. Thanks.
Author of Total Commander
http://www.ghisler.com
http://www.ghisler.com
-
- Junior Member
- Posts: 43
- Joined: 2007-07-28, 01:10 UTC
Re: Crash on Copy (F5)/Move (F6) under Windows 10
Is there a solution for this issue? I have the same on my PC (also Windows 10).
Re: Crash on Copy (F5)/Move (F6) under Windows 10
What is your current TC version ?
And also the exact Windows version ?
Windows 10 Home x64 October 2018 Update, Version 1809 (OS Build 17763.316)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
TC 9.21a x64 and x86, Everything 1.4.1.935 (x64)
Intel(R) Core(TM) i7-4770 CPU @ 3.40GH, 16GB RAM
TC 9.21a x64 and x86, Everything 1.4.1.935 (x64)
- ghisler(Author)
- Site Admin
- Posts: 36782
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Re: Crash on Copy (F5)/Move (F6) under Windows 10
As I wrote above, I need a stack trace to analyze the problem.
Author of Total Commander
http://www.ghisler.com
http://www.ghisler.com