Windows 10: How to read dump files?

I just got my first BSOD!

I wasn't quick enough to note down the full error as Windows did a crash dump, but I did notice the offending file was an Atheros driver. This was confirmed by Control Panel | Reliability Monitor

Source
Windows

Summary
Shut down unexpectedly

Date
‎24/‎11/‎2015 10:35

Status
Report sent

Problem signature
Problem Event Name: BlueScreen
Code: 1000007e
Parameter 1: ffffffffc0000005
Parameter 2: fffff800dd3dfbe1
Parameter 3: ffffd0002093c938
Parameter 4: ffffd0002093c150
OS version: 10_0_10240
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.10240.2.0.0.256.48
Locale ID: 2057

Extra information about the problem
Bucket ID: AV_athurx!Hw11HeartBeatCallBack


I've used the DM Log Collector to get the DMP file, but I'd quite like to study it myself, and send relevant parts to Alfa (who make the offending Wi-Fi adaptor with the Atheros chipset).

:)

 

WinDBG Debuggee not connected

Yes i did! I was reading the dumps with the link by its side. I am very keen on learning how to read these dumps and will be glad to try your recommendations

Here are the dump files

https://1drv.ms/f/s!ArEigW8sE3Q-kDjt56Ii3W-yVXly

 

Freezing screen crash

Hi Someone will read your dump files. Here's a program I use. It will read your dump files for you. Let me know how things go!

Download WhoCrashed Free Home Edition - MajorGeeks

 

You can look here WinDBG - Install Configure - Windows 10 Forums

It is quite easy really. Install WinDBG from the ADK, Associate .dmp with WinDBG, put in the symbol path, copy your MEMORY.dbg file to the desktop and open it.

99 times out of 100 it will tell you that some driver is in error. Otherwise it will generally be overclocking, hardware or antivirus.

If you see "probably caused by xxxx.sys" then you can go to this site Driver Reference Table - npf.sys (replacing the =npf.sys with whatever the debugger shows)

 

Thanks, I got the info attached and sent it to Alfa...

I've also figured out the error was: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED athurx.sys

 

Not exactly true, it is more 90/100 times that a driver is causing problems. Memory problems are very common so then you'll see 'probably caused by: memory_corruption' or something similar and even then it doesn't have to be the modules but some settings.

It is quite easy to configure Windbg, but it takes a lot from one to actually proper read dump files.