What is dumprep.exe? Why is KernelFaultCheck dumprep 0 -k in MSCONFIG Startup?

You might be a careful person who regularly scans their computer for viruses, checks for windows updates, clears temporary files, defrags the hard drive and will also make sure that your startup is not loaded with programs. But as we know, Windows startup is one of the most common system areas for malicious software to insert itself as it’s launched every time you start your computer, and it can be a bit of a concern finding something in there you don’t recognize. One entry you might notice that one day appears in the System Configuration Utility (MSConfig) is a new startup item called KernelFaultCheck with the command:

%Systemroot%\System32\dumprep 0 -u 


%Systemroot%\System32\dumprep 0 -k

Whether this is a legitimate startup item or not, just the name itself makes this entry look rather suspicious.

dumprep startup entry

So, is dumprep.exe a virus and how did it get into into my startup programs? Why even after removing the dumprep entry from startup does it come back automatically? If you would like to know what dumprep.exe is and how to permanently removing it from startup, the text below will help you.

Firstly, you’ll be pleased to know the dumprep program is not a virus and is actually part of the Windows operating system. When a serious Windows error is detected, the dumprep.exe program is called to log the fault and then write the error details to a text file. When the error is logged, you will then be prompted to send the text file containing the error information to Microsoft for analysis. The Dumprep.exe tool is a non-essential system process that is installed for third-party use.

There usually 2 switches associated with the dumprep.exe. The “-k” argument is a kernel fault check and “-u” is a user fault check. Since Microsoft has mentioned that dumprep.exe is a non-essential system process, it can be disabled safely without causing any problems.

To disable dumprep.exe from startup, go to Control Panel -> System -> Advanced tab -> click the Settings button in the Startup and Recovery section. At Write debugging information, click the drop down menu, select (none) and click OK. For ease of use , you can simply download and run this registry file which will automatically disable it for you.

disable write debugging

Next, click the Error Reporting button at the bottom and select “Disable error reporting“. You can leave the option “But notify me when critical errors occur” checked. Click OK to close Error Reporting window. You can disable Error reporting automatically by downloading and running this .reg file.

disable error reporting

Go to Run and type msconfig. Check if dumprep.exe still exists in the list or not. If it is still there, run regedit and navigate to:


Select the KernelFaultCheck entry name and delete it. Then Restart your computer. If you’re not comfortable in the registry, use this reg file to delete the dumprep entry. Alternatively, there are various other ways to remove the entry using any piece of third party software that lets you edit the registry startup items, such as the great tool CCleaner, which is an essential cleaning/optimizing program to have. Simply run the program and go to Tools -> Startup -> Windows, select the dumprep line and click Delete.

remove dumprep startup entry in ccleaner

If dumprep.exe still gets automatically added into startup after disabling error reporting and writing debugging information, that means your computer has experienced a blue screen error and memory dump before. You need to Search for the MEMORY.DMP file and delete it. Usually the MEMORY.DMP file is located at Windows folder. Once you delete the dump file from Windows, dumprep.exe will no longer appear in MSConfig.

18 Comments - Write a Comment

  1. Eddie 13 years ago
  2. Iris 13 years ago
  3. Rahul Shah 14 years ago
  4. nnn 14 years ago
  5. samir 14 years ago
  6. xera216 14 years ago
  7. no1rick 14 years ago
  8. archit 14 years ago
  9. Beavis 15 years ago
  10. vmckrish 15 years ago
  11. vic 15 years ago
  12. Andrew 15 years ago
  13. joe joe 15 years ago
  14. TEd Choate 16 years ago
  15. Quinn 16 years ago
  16. jekkelinho 16 years ago
  17. webcadre 16 years ago
  18. Abhishek 16 years ago

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.