Minidump file reader

I've read the article and while I agree with most of it, there's a few things that I would note. BSODs are caused by 3rd party drivers or bad hardware. It's an extremely rare occasion if ever when it's actually caused by a Microsoft driver. BlueScreenView can be useful in the scenario described in the article.

But, it usually only provides general information and rarely points directly to a driver. But even then, it's a rare occasion when it shows the actual driver that is causing the issue. And if the issue is hardware, expect even more confusing results. A bad RAM module will often point at multiple different drivers in the dump files when none are really to blame. However, both applications can be used to help aim you in a direction of figuring out what the actual cause is. The Windows Memory Diagnostic is known to be a weak memory tester.

It's not completely useless. If it shows an error, that tells you to find other ways to test the RAM. It's much better to use memtest86 from the start, and test 1 RAM module at a time. These tests will last hours 4 passes should be the minimum testing length. Overall I give the article a thumbs up. Better testing tools should be listed. Also, if the issue is hardware other than RAM, it could have listed a few of the tools used to test other hardware such as Prime95 for CPU testing, or hard drive testing software such as Hard Disk Sentinel, etc.

Overall, don't expect the dumps to tell you the exact problem because they rarely do. About Memory Diagnostic When it reboots into Windows it does so without so much as a fair-thee-well. So other than sitting throughout the entire test, how do you determine if there were It can take a VERY long time sitting there watching the screen to see if it reports an error, especially if you run it through multiple cycles for confidence using all the tests.

Are there any suggestions to help find errors The only way I know is to search through the Windows Event Log which can be pretty frustrating in it's own right. And also, I've always considered BSOD diagnosing something of value mainly for developers, especially device driver developers. Us average users, even if having a diagnoses of the BSOD, will probably only be able to fix it by 1 removing any overclocks 2 uninstalling whatever was most recently installed or updated or 3 reset windows.

But fixes that entail digging into the internals of Windows, including registry edits, are frequently beyond us anyway. Admin said:. IIRC in so long I cannot remember exactly when. I do recall that the last one I had was caused by an overclocking experiment I was running. You should run a memory test first since it is easy to do that by pressing the Start button and type mdsched which will run the Windows Memory Diagnostic program.

Two years late, but I created an online dump file analysis website called DebugLearn debuglearn. You can submit your dump file online for analysis. BlueScreenView is lightweight and easy to use. You just unpack it out of the zip and double click on the exe similar to sysinternal tools like process explorer. This user looks like he learned about computers after the introduction of the iPhone. Stefan H 2 years ago.

HAL Admin 2 years ago. Rikhasi 2 years ago. Vineet Garg 3 years ago. Alexey 3 years ago. James 7 months ago. Gordan 5 months ago. Benrras 4 years ago. Peter 5 years ago. HAL Admin 5 years ago. Stinkie 5 years ago. Hank brown 5 years ago. If you have any questions, please feel free to share your questions or comments on the comment box below.

Net Programming. Share this:. Tags: Diagnostics Tools. Topics that you may also interested. Hex2dec — Convert Hex value to Decimal and vice-versa. DiskView — The graphical disk image viewer tool. We will be happy to hear your thoughts. Leave a reply Cancel reply.