dumprep 0 -k
KernalFaultCheck:
%systemroot%\\system32\\dumprep 0 -k
Dumprep.exe = Windows Error Reporting Dump Reporting Tool
Dumprep.exe should be located in %WinDir%\System32. If not it may be some
sort of malware.
[[The Dumprep.exe tool is a non-essential system process that is installed
for third-party use. ]]
You can disable this....
Right click My Computer | Properties | Advanced tab | Under Startup and
Recovery | Settings button | Under System Failure | UNCheck: Write an
event to the system log | Under Write debugging information | Select
(None)
| Click OK | Click Apply | Click OK
Write an event to the system log = dumprep 0 -k
[[Specifies whether Windows will write event information to the system log
when the system stops unexpectedly.
You must be logged on as a member of the Administrators group to set
recovery options.]]
Write debugging information:
[[Specifies what type of information Windows should record when the system
stops unexpectedly, and the name of the file that holds this
information.]]
Dump file:
[[Provides a space for you to type the name of a log file that Windows can
use to write the contents of system memory when the system stops
unexpectedly.
You must be logged on as a member of the Administrators group to set
recovery options.]] %systemroot%\MEMORY.DMP is the default.
If you have other, serious problems, then dumprep 0-k is automatically
enabled.
If you have Error Reporting enabled, this entry may show up for the first
time after your PC has experienced a Windows XP dump crash, or an Office
XP or Internet Explorer 6 crash where you were prompted about sending the
crash results to Microsoft.
To disable Error Reporting....
Right click My Computer | Properties | Advanced tab |
Error Reporting button | Disable error reporting
Also.
Start | Run | Type: services.msc | Click OK |
Scroll down to and double click: Error Reporting Service | Click Apply |
Click OK
--
Hope this helps. Let us know.
Wes
MS-MVP Windows Shell/User
In
Bill G. said:
My computer (XP home SP2) froze and was churning away on 2 versions of
dumprep.exe. It seems to happen when I am modifying or editing large
picture files. A reboot fixes it but its time consuming. Am I doing
something to trigger it or is there a way to avoid it ?
I suspect it may be from re-clicking an action when it doesn't start
fast
enough. A bad habit.
Thanks for the help. You guys are awesome.
BillG