Hi,
I was wondering if anyone knew any general "Rules of thumb" / heuristics when looking at a crash file that would indicate it was a hardware problem.
Periodically, over the years I have been looking at those files, but could only really make a "best guess".
Is a full crash dump file required to form the conclusion that the crash is due to hardware?
Cheers.
Here are some articles :
https://www.windowscentral.com/how-open-and-analyze-dump-error-files-windows-10 (https://www.windowscentral.com/how-open-and-analyze-dump-error-files-windows-10)
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files)
https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file (https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file)
This guy knows everything about crash dumps
he published lots of good materials
https://leanpub.com/u/DmitryVostokov (https://leanpub.com/u/DmitryVostokov)
Quote from: Vortex on March 22, 2024, 05:16:21 AMHere are some articles :
https://www.windowscentral.com/how-open-and-analyze-dump-error-files-windows-10 (https://www.windowscentral.com/how-open-and-analyze-dump-error-files-windows-10)
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/crash-dump-files)
https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file (https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/read-small-memory-dump-file)
Thanks for that.
It is finding hardware faults in the bug check files that is the most difficult thing.