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

Hi @iamnotworthy,

Welcome to the 10forums *Smile

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.

 

maybe you could upload this folder with symbols? So that others could download it and don't have to deal with this issue anymore *Smile
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.

 

axe0, thanks a lot for letting me know this. I'll keep you posted.

Not sure if it's related to hard drive crashes (which I know are usually physical/mechanical) but I have replaced the Intel Management Engine Interface and the Intel graphics card drivers, and I now seem surprisingly stable. No BSOD in 38 hours. I will still send into Dell, but this laptop does seem stable at the moment. I had of course updated those drivers to latest previously but this time I did an uninstall/reinstall instead of an install on top of existing. So hard to isolate cause and affect on this stuff. Appreciate your help in looking at my minidump files and hope my Symbols file grows big and strong soon.

 

After 48 hours of no BSOD, got another one.

I ran this command

qe System "/q:*[System[(Level=1 or Level=2)]]" /f:text /RD:TRUE /C:4 > eventfile3.txt

to get all the Event Viewer errors going back to mid-November. I've attached that file.

If anybody sees anything that might cause BSOD, I'd appreciate your help.

This BSOD did not generate a minidump, even though I am pretty sure I have the settings right to create minidumps. I do have a MEMORY.DMP file but it's too big (138 MB zipped) to upload to this site.

 

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 *Smile

 

axe0, is that different from the tool I used to create the file that I attached in the first post on this thread? When I googled it, it seems to be the same tool that one is told to use before posting on this forum. If so, that file is in the opening post for this thread. Or are you suggesting I run the tool again to see if there is new info? Thanks.

 

If you send it back, I would backup your data. From the dump it looks like the BSOD is likely from your hard drive. The exception is occurring during a memory page fault which means the memory manager is trying to load data from the hard drive.

The NTSTATUS code 0006 is an invalid handle (pointing to nothing)

 

With the zip that is already uploaded the new information isn't present. Unless you would want us to provide the same analysis it is recommended to run the tool again.

 

Got it. Sorry I didn't realize that obvious point. Here's the new version, attached.
I do have a backup and I am in touch with Dell to get a new imaged drive to replace this one. Weird thing is I'm more stable now than before...last BSOD took over 48 hours after previous one...and now again I have been healthy for full day. Before that, BSODs were a few a day minimum. I was really hoping it was driver or something because reinstalling all my software on a new drive will be a pain.
Thanks to all for assists. Much appreciated.