question about a startup item....

http://www.castlecops.com/s1033-dumprep_0_kdumprep_0_u.html
this is in my startup items under msconfig and has never been there before…what is it and what caused it-and should i do what it says to do ??? ::slight_smile:
from sysinfo.org http://www.sysinfo.org/startuplist.php?letter=D&filter=&count=50&offset=300
dumprep 0 -k N dumprep 0 -k Used in connection with memory dumps - you can disable these by - right clicking on My Computer, selecting Properties and then the Advanced tab. Click on the Settings button in ‘Startup and Recovery’. In the bottom pane - under ‘Write debugging information’ - click on the down arrow and then select ‘None’ - OK your way out

This appears from time to time to me… specially after BSODS (not that frequently, thanks God!) or software installation problems (freezes, etc.).
As far I know, it manages the dump files, and I just remove them when WinPatrol alerts me about a new startup item is being added.
I want to know more too, to see if I`m doing something wrong…

you can disable these by - right clicking on My Computer, selecting Properties and then the Advanced tab. Click on the Settings button in ‘Startup and Recovery’. In the bottom pane - under ‘Write debugging information’ - click on the down arrow and then select ‘None’ - OK your way out
already did the above…it that ok and the item in startup is not check…whats the best thing to do ???

Prevent dumprep from running http://www.auctionsieve.com/blog/2005/11/prevent-dumprep-from-running.html
Say you have a rogue/frozen program and you go to the Task Manager and click on End Process.
You know how sometimes it then takes ages to take effect?
And then it asks if you want to send an error report to microsoft?
(And of course you always say ‘No’)
Well all that time is spent creating the report via the dumprep.exe program. And if it’s something like IntelliJ that’s crashed, the dumprep process size itself balloons out to an equivalent memory size.
This is another case where I finally got annoyed by this one too many times.
So I did a search. Turns out you can turn it off very simply.
Control Panel->System->Advanced tab->Error Reporting->Disable error reporting.

AFAIK dumprep is completely unnecessary at start up and can use a lot of resources, sometimes running multiple instances.

Like Tech, I use WinPatrol to disable it.

don’t have scotty the dog on here at present so i will leave it unchecked in start item and do this-you can disable these by - right clicking on My Computer, selecting Properties and then the Advanced tab. Click on the Settings button in ‘Startup and Recovery’. In the bottom pane - under ‘Write debugging information’ - click on the down arrow and then select ‘None’ - OK your way out
is that ok ??? ::slight_smile:
thanks keith :wink:

I’ve never tried it that way but sysinternals is usually a reliable source.

scotty is on patrol again and here is the startup screen

right clicking on My Computer, selecting Properties and then the Advanced tab. Click on the Settings button in 'Startup and Recovery'. In the bottom pane - under 'Write debugging information' - click on the down arrow and then select 'None' - OK your way out
already did that previously mentioned so i guess i'm ok click on to enlarge ::)

@ drhayden1
I can’t recall ever having disabled this on start-up and it isn’t in my startup tab of msconfig.

Have you installed anything recently, like the AusLogics System Information program that I think you mentioned or certainly has been mentioned in the forums recently. That might have some settings to check.

I would suggest you ‘don’t’ select ‘None’ as an option in Write debugging information, but choose the Small memory dump (64KB) as even that might be of some help in resolving problems, for those that know how to interpret it. The Alwil team often ask for dumpreps and if you don’t have anything you can’t help them and they can’t help you (or it makes it more difficult). It isn’t as if these dumprep.dmp files take up much space and they are overwritten by default.

On one problem avast solved (outpost firewall and avast clash on pausing standard shield to do a security scan, avast froze on trying to resume standard shield). I had the dumprep set to Complete memory dump at 1 GB of RAM this created a huge file that I had to burn to CD and mail to them. But, it helped them to pin down the problem and give me a work around. This is a valuable tool that you shouldn’t disguard just to save a bit of HDD space and as I say no startup entry on my system with this enabled.

Have you installed anything recently, like the AusLogics System Information program that I think you mentioned or certainly has been mentioned in the forums recently. That might have some settings to check.
yes i did install it :) and i will go back tn change none to the small dump like you mentioned-seems the better way after the mentioned the issues ::) and i stll have that dumprep 0 -k in my msconfig startup items unchecked but scotty(winpatrol)doesn't show it in the pic in above post ;) i had to check yes to that applet in the below pic to change back the settings i guess ??? ::) click on pic to enlarge....

This is referring to something entirely different, your PageFile size, if you have disabled the pagefile or set it to 0 then as it says it might not be able to create the dump information. I don’t know if this is just a general warning or whether it actually checks the pagefile size on C: is large enough for the task to be completed.

So in the same screen check the Performance, Settings,Advanced, Virtual Memory, Change, to see what the sizes are, see image, note I have mine split over two HDDs one small fixed size one on C: to try to avoid fragmentation.

i have mine set to system managed size davidr not custom recommended by hp on this laptop computer ::slight_smile: :o
this is not my quad piece of junk i’m working with here :slight_smile:

Yes it looks like this is just a default popup/reminder and it doesn’t actually check if the pagefile size is large enough.