• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How to read a minidump file

K

KingDog

Member
I know this might be elementary, but I can't figure out how to open one of these files to read it.

Secondly, figuring out what it might be indicating is another story.

Gettiing random reboots.
Ran Memtest. Looks like one stick is bad.
Removed it. Other stick is fine. Memtest now good.

Still getting occassional random reboot.
I am guessing some driver issue?
Temps OK, voltage OK, no overclocking, newer install of Win XP Pro SP2

Any help is appreciated.

Anybody want to read my minidump file for fun? 🙂
 
Update. I ran memtest again with the remaining memory module for about 9-10 hours.
I had one error.
May be a anomaly-not sure.

Before with the other bad memory stick- I got errors right away within 5 tests.
This one was on Test 31 or something after 8 hours.
 
No such thing as an anomaly.

Unlike nearly every other software based hardware diagnostics you cannot get a false positive with memory testing. It is possible for bad memory to go undetected but it is not possible for good memory to be flagged as bad.

If you got an error, then you have an error.
 
and to open a minidump file you'll need to download the free debugger from Microsoft.


windbg

be sure to get your symbols set right. Run a !analyze -v in the debugger once you have it open. It will make a best guess as to your problem. You can't really do anything more with a minidump...not enough data.
 
Unlike nearly every other software based hardware diagnostics you cannot get a false positive with memory testing. It is possible for bad memory to go undetected but it is not possible for good memory to be flagged as bad.
Click to expand...

I don't doubt you in almost cases but it seems odd that Memtest ran without errors with the remaining stick for probably 8 hours or so until it got the single reported error and had no other errors after that for another hour or two.

I also ran the Windows Memory Diagnostic test today during day which Mushkin suggests.
It ran for 10 hours with no errors.
I will try Memtest again to see what happens.

I wonder about the Mobo at this point. I may grab some known good ram and run it and see what happens also.



 
we can't dismiss the error but there are some possible causes that are less cause for concern.

If you had a power fluctuation during the test that would be 'ok'.

If you ran another 10hrs with no errors the one error we saw earlier might be safely ignored.


How is system stability day to day?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top