Windows 10 2004/20H2: DumpStack.log.tmp slows down computer

[German]On Windows 10 systems with the version 2004 or 20H2 there is a file DumpStack.log.tmp, which in the worst case slows down the computer. A blog reader pointed this out to me. Here is some information on the topic.

A reader hint

Blog reader Alfred Neumann sent me the hint by e-mail after he ran into the problem on a newly updated computer. In his mail he writes.

Today I updated a computer to Win 20h2 and I noticed a file in c:\: "DumpStack.log.tmp".

Had already seen them before but somehow suppressed to look for them again.  Today I looked for it. If you look in the REG under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

sets the value EnableLogFile to 0 you can

a) delete the file C:\DumpStack.log.tmp and

b) the computer runs faster.

Alfred Neumann pointed out that he had mentioned in his comments that TOR starts so slowly. The problem is solved after deleting the file C:\DumpStack.log.tmp.

What is behind DumpStack.log.tmp?

On the Internet, users often ask what is behind the file DumpStack.log.tmp. The whole thing was already introduced in Windows 8 by Microsoft. The file is used when Windows has to write a dump. It is a hidden system file in the root directory C:\ of the Windows drive (see also the explanation in this MS Answers forum thread). Some hints can be found in the posts here and here.

The file cannot be deleted by default because it is under the control of the operating system. Logging to the file can be disabled by a registry operation. To do so, use the key mentioned above:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl

in a registry editor launched with administrative rights. There two 32-bit DWORD values are entered (see also here) to activate logging:

EnableLogFile = 00000001
LogLevel = fffffffd

If the 32-bit DWORD value EnableLogFile is set to 0 and Windows 10 is rebooted, no logging is performed. At the same time you can now delete the file DumpStack.log.tmp.