I have been having random memory dumps that have generated "minixxxxx.dmp" files. I have been told the the dumpchk.exe "tool" in the system tools file will :
Open the mini.dmp file which in turn will give me the memory location and help to identify the driver or command file that initiated the "halt" command to the CPU(s). From there, I am told, I can take this information, go to MS Support website and check their data base for the recommended "fix".
For the life of me I cannot get dumpchk to "read" the .dmp files!
Has anyone here done this?
Regards,
jaybird
Has anyone here used dumpchk.exe?
-
- Posts: 13
- Joined: Wed Jan 04, 2006 3:02 am
- Location: Scotland
- Contact:
Malcolm
http://webtrakker.info
http://webtrakker.info
-
- Posts: 13
- Joined: Wed Jan 04, 2006 3:02 am
- Location: Scotland
- Contact:
Malcolm
http://webtrakker.info
http://webtrakker.info
-
- Posts: 13
- Joined: Wed Jan 04, 2006 3:02 am
- Location: Scotland
- Contact:
Malcolm
http://webtrakker.info
http://webtrakker.info
That is what I was thinking when I first logged in.
Oh well, think its fixed now.
webtrakker,
First, welcome aboard. Then...many of us have found after we hit submit it is best to wait maybe 2 seconds then hit the BACK button to avoid making embarassing multiple posts. For what its worth, most of us learned that lesson the hard way.
There are *almost* no bad BP6s. There are mostly bad caps.
No BP6s remaining
Athlon 2800
Sempron 2000
ViaCPU laptop with Vista.(Works great after bumping ram to 2Gig)
P-III 850@100
No BP6s remaining
Athlon 2800
Sempron 2000
ViaCPU laptop with Vista.(Works great after bumping ram to 2Gig)
P-III 850@100