Does anyone know if dumprep.exe 0 -k actually does or if it's needed in the run section of the registry?
It seems to do a dump on a user's pc at every bootup and will not allow the pc to function properly?
It may be a repeating problem with the machine itself have you checked for any errors in the Event Viewer?
Dumprep.exe is the Windows Error Reporting Dump Reporting Tool after any error it is placed in the Registry automatically to load Dumprep.exe at startup.
You can safely remove it from the registry as Windows will just recreate the entry at the next crash. It is also removed via the Startup items in MsConfig. Doing it that way would give you a popup about Selective Startup which you can ignore and use the check box to dismiss it.
Before you kill the messenger just make sure there is no actual problem with your machine.
Some of these boxes Bill mentions specify whether Windows will write event information to the system log (Event Viewer) when the system stops unexpectedly. I'd keep that one.
Perhaps he means "write debugging information" being set to none?
My thought was a hard issue somewhere. Remove all the dump choices. This should remove as well the dumprep entry in startup.
I do not want to boil a cabbage twice (I have wanted to use this phrase for you since I read it earlier this week).
. do a Disk Cleanup
. do a Disk Defragmentation
. do a chkdsk
Then re-enable the error reporting services.
The entry for dumprep.exe should have cleared on its own. The fact that it did not is my concern, hence the disk testing and removal and reinstall of the error service under XP.
Thanks to everyone for the information. When I first booted this pc, I logged into the network and opened email. I never saw any dump or blue screen. Spybot cleaned a couple things from the registry. I looked thru the run sections under local mach/sw/ms/win/curr ver/ and found that dumprep key. I removed it. I rebooted several more times and never saw any problems. I don't suspect hardware as this pc is brand new and only been in production for a couple of weeks.
If it happens again, I'll follow everyone's suggestions. Strangest thing is that of the few thousand pc's we support, none of the other tech have heard of or seen this problem???
Thanks again for the assistance!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.