How to view the cause of BSOD through windows logs and reliability history ?

In the following link you can download the latest BIOS:

https://www.msi.com/Motherboard/support/B450M-PRO-VDH-MAX

In the link for the BIOS updates there is a link at the top you can click on that will take you to a Youtube video how to update the BIOS.

The first thing to do is to identify the error. Blue screen errors have a number code (that typically starts with 0x000 ...) and a title (that LOOKS_LIKE_THIS.)

Next, you need to make note of the exact time (down to the minute) of when you blue screen occurred. This is important because events in Event Viewer are listed in order of time.

Now you can open Event Viewer and find your error. You don't need to look beyond its main interface. Your blue screen code will be there as an Error.

Reliability History is just theater.

A memory dump is just that - the complete contents of RAM. It doesn't tell you what went wrong; it only gives you some information that may or may not mean anything.

The basic problem you're going to run into is this:

Microsoft never intended for users to fix their own computers. Blue screen error codes and error titles were written for software developers, not for you and me. Software developers know the code they wrote, so they are the people who can diagnose problems. You'll see (if you haven't already) that even when you know what an error code and/or an error title means, that still doesn't explain what went wrong. It gives you a high level idea of where to look for the cause of the problem. That can be very useful to a software developer, who knows the code, but to you and me it means very little.

Over time, the combined wisdom of multiple, successful guesses has lead to possible solutions that a regular user can try. You can try those if you want, but you're still working from guesses, just more educated guesses.

The only chance that a regular user has to solve a blue screen error - without a successful guess - is to be continuously aware of what the computer was doing at the time a blue screen error occurred, and to remember any recent changes you made to the computer before the blue screen occurred. That gives you the best chance to relate cause and effect.

Unfortunately, many people posting here with blue screen errors have made multiple unfortunate changes to their computers to the point where it becomes very difficult to relate cause and effect; or they may not complain about a blue screen error until it has been happening for weeks or months, by which time it becomes very difficult to remember what might have caused the problem in the first place; or they see multiple blue screen errors, which makes it very difficult to match a cause with an effect.

Even without knowing cause and effect, there's still at least one way for everyone to get a handle on whether or not a blue screen error is caused by an update: Microsoft publishes the details of every update including known problems caused by the update. Everyone can consult this information (either the geek version or the normal person's version) and see whether their computer is affected by a known problem with an update.

Hi,

It may help to look at the minidump files from the blue screen crashes.

Can you zip up the minidump files in the C:\Windows\Minidump folder and make available (provide link) via a public folder on OneDrive or similar site.

Here's a link on using OneDrive:

http://windows.microsoft.com/en-ca/onedrive/sha...

If you have problems zipping the minidump files copy the minidump files to another location such as a folder on the Desktop.

Also, you do not necessarily have to zip up the minidump files, you can upload them one at a time.