Want to debug and learn how to debug Windows 10 BSOD on Dell Latitude

Not sure what your symbol problem is as I just downloaded your zip file, extracted the files then ran windbg against the single .dmp file it contained and it worked with no problems:

Code:

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [F:\Temp\Dumps\amnotworthy\112016-7843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*G:\Symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*G:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff802`5c689000 PsLoadedModuleList = 0xfffff802`5c98e060
Debug session time: Sun Nov 20 10:21:30.431 2016 (UTC - 5:00)
System Uptime: 0 days 21:39:17.080
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.

BugCheck 154, {ffffad010c31d000, ffff9b81410a9420, 2, 0}

Good luck, and thanks for letting me know.

Hi @iamnotworthy,

Welcome to the 10forums :)

The symbol error will go away after some time, it just takes time as you need to download all required symbols what isn't done the first time. In the first period of debugging for me, which was about 1 to 2 weeks, I had to open, close, open, close, etc. the dumps to get rid of the errors (for each dump). Everytime I opened a dump new symbols were downloaded and so my symbol folder grew, after about 1.5 year I have a symbol folder of about 5GB. TBH since I started I have at least loaded 2-10 dumps per day.

As of your issue, the name of the 0x154 (unexpected storage exception) sounds to me partly like a drive issue. When I went through the event logs of the zip you have uploaded I noticed an event that said something in the way of 'a read attempt on sector xxx was retried'. Dumping the raw stack in the dumps revealed a few interesting things that led me think your root issue is (as you now figured it) the hard drive.

I didn't post earlier due to lack of time.

axe0 said:

Hi @iamnotworthy,
after about 1.5 year I have a symbol folder of about 5GB. TBH since I started I have at least loaded 2-10 dumps per day.

maybe you could upload this folder with symbols? So that others could download it and don't have to deal with this issue anymore :)
just an idea though.

I would recommend to download symbol installers from here or here (my onedrive folder having all symbol installers I used), on my pc I have a 50-60GB symbol folder because I downloaded all available symbols for Windows 7 to Windows 10 (no TP's).

UPDATE, will shortly add/replace a link to my 5GB folder, takes some time to upload it with 15Mb/s wifi.

Uploading takes too long currently so I stop the upload.

The events look like app events which don't include system events that are necessary (too).
What I would recommend is to simply run the DM Log Collector, which includes both app and system event logs :)