Save Dump EVERY time I load XP

[Guest]

Hi,

My computer has been fine and still is for the most part. The problem
currently is that EVERY time I bootup I see the system event "Save Dump"
although I had no trouble with the previous Windows session nor did I have
any problems booting up the current Windows session.

It all started after I ran PCMark05's 16MB Write test with my RAM at 1T, and
BSOD which is somewhat normal apparently as it runs fine with my RAM at 2T. I
am not the first to report this so I thought nothing of it. I removed the
"dumprep 0 -k" from MSConfig and changed my timing back to 2T and the PCMark
test runs fine, but I noticed that XP was still loading savedump.exe at
bootup and showing the same system event (and ALWAYS shows this exact thing).

The event is: The computer has rebooted from a bugcheck. The bugcheck was:
0x0000008e (0xc000001d, 0xf30f23ab, 0x80550263, 0x00000000). A full dump was
not saved. (The first time this same error occurred the dump WAS saved.)

I have run Prime95 with my system for over 6 hours successfully and I ran
Memtest86 through all of its tests successfully. I have even tried a system
restore to what I think was before the first error from the same exact issue,
but I STILL see the Save Dump on bootup! Every operation I have tried in XP
is flawless, and bootup and shutdown move smoothly, and I have really only
seen BSOD's when doing the EXACT operation I described with PCMark which
isn't so uncommon with others who tried. Even with my RAM at 1T, my system
was flawless (as long as I didn't run that memory test), so I kind of believe
that PCMark has the issue, and if my system didn't keep doing the Save Dump I
wouldn't care about PCMark. I am just trying to get to the bottom of the Save
Dump problem!

Thanks in advance,
Andrew

 

[Wesley Vogel]

dumprep 0 -k

KernalFaultCheck:
%systemroot%\\system32\\dumprep 0 -k

Dumprep.exe = Windows Error Reporting Dump Reporting Tool

[[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

The Windows XP-based computer may run slowly and you may receive Dumprep.exe
error
messages
http://support.microsoft.com/default.aspx?scid=kb;en-us;899870

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Guest]

Well, thanks for the automated solution, but it's not that I wanted to find
out how to "pretend" that the Save Dump was not occurring (i.e. disabling
write event to system log); I wanted to get at why it was happening in the
first place.

Anyway, I figured it out on my own. After XP created memory.dmp the first
time in the Windows directory, it seems that that would trigger the Save Dump
event in the system log (and savedump.exe to start as well). Once I removed
the memory.dmp file from that directory I haven't seen the error again.

dumprep 0 -k

KernalFaultCheck:
%systemroot%\\system32\\dumprep 0 -k

Dumprep.exe = Windows Error Reporting Dump Reporting Tool

[[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

The Windows XP-based computer may run slowly and you may receive Dumprep.exe
error
messages
http://support.microsoft.com/default.aspx?scid=kb;en-us;899870

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi,

My computer has been fine and still is for the most part. The problem
currently is that EVERY time I bootup I see the system event "Save Dump"
although I had no trouble with the previous Windows session nor did I have
any problems booting up the current Windows session.

It all started after I ran PCMark05's 16MB Write test with my RAM at 1T,
and BSOD which is somewhat normal apparently as it runs fine with my RAM
at 2T. I am not the first to report this so I thought nothing of it. I
removed the "dumprep 0 -k" from MSConfig and changed my timing back to 2T
and the PCMark test runs fine, but I noticed that XP was still loading
savedump.exe at bootup and showing the same system event (and ALWAYS
shows this exact thing).

The event is: The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000008e (0xc000001d, 0xf30f23ab, 0x80550263, 0x00000000). A full
dump was not saved. (The first time this same error occurred the dump WAS
saved.)

I have run Prime95 with my system for over 6 hours successfully and I ran
Memtest86 through all of its tests successfully. I have even tried a
system restore to what I think was before the first error from the same
exact issue, but I STILL see the Save Dump on bootup! Every operation I
have tried in XP is flawless, and bootup and shutdown move smoothly, and
I have really only seen BSOD's when doing the EXACT operation I described
with PCMark which isn't so uncommon with others who tried. Even with my
RAM at 1T, my system was flawless (as long as I didn't run that memory
test), so I kind of believe that PCMark has the issue, and if my system
didn't keep doing the Save Dump I wouldn't care about PCMark. I am just
trying to get to the bottom of the Save Dump problem!

Thanks in advance,
Andrew

 

[Wesley Vogel]

That will teach you to keep your machine cleaned up.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Well, thanks for the automated solution, but it's not that I wanted to
find out how to "pretend" that the Save Dump was not occurring (i.e.
disabling write event to system log); I wanted to get at why it was
happening in the first place.

Anyway, I figured it out on my own. After XP created memory.dmp the first
time in the Windows directory, it seems that that would trigger the Save
Dump event in the system log (and savedump.exe to start as well). Once I
removed the memory.dmp file from that directory I haven't seen the error
again.

dumprep 0 -k

KernalFaultCheck:
%systemroot%\\system32\\dumprep 0 -k

Dumprep.exe = Windows Error Reporting Dump Reporting Tool

[[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

The Windows XP-based computer may run slowly and you may receive
Dumprep.exe error
messages
http://support.microsoft.com/default.aspx?scid=kb;en-us;899870

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Hi,

My computer has been fine and still is for the most part. The problem
currently is that EVERY time I bootup I see the system event "Save Dump"
although I had no trouble with the previous Windows session nor did I
have any problems booting up the current Windows session.

It all started after I ran PCMark05's 16MB Write test with my RAM at 1T,
and BSOD which is somewhat normal apparently as it runs fine with my RAM
at 2T. I am not the first to report this so I thought nothing of it. I
removed the "dumprep 0 -k" from MSConfig and changed my timing back to
2T and the PCMark test runs fine, but I noticed that XP was still
loading savedump.exe at bootup and showing the same system event (and
ALWAYS shows this exact thing).

The event is: The computer has rebooted from a bugcheck. The bugcheck
was: 0x0000008e (0xc000001d, 0xf30f23ab, 0x80550263, 0x00000000). A full
dump was not saved. (The first time this same error occurred the dump
WAS saved.)

I have run Prime95 with my system for over 6 hours successfully and I
ran Memtest86 through all of its tests successfully. I have even tried a
system restore to what I think was before the first error from the same
exact issue, but I STILL see the Save Dump on bootup! Every operation I
have tried in XP is flawless, and bootup and shutdown move smoothly, and
I have really only seen BSOD's when doing the EXACT operation I
described with PCMark which isn't so uncommon with others who tried.
Even with my RAM at 1T, my system was flawless (as long as I didn't run
that memory test), so I kind of believe that PCMark has the issue, and
if my system didn't keep doing the Save Dump I wouldn't care about
PCMark. I am just trying to get to the bottom of the Save Dump problem!

Thanks in advance,
Andrew