Windows 10 BSOD Debug Please

[Starcruiser]

Will one of you fine folks please !analyze my minidump? Normally I would do it myself, but I seem to be having a problem with my debugger... (https://msdl.microsoft.com/download/symbols is not a valid store - lol what)
https://1drv.ms/u/s!AlUHt7prder-hw0WMbeRdlhZvvZS

 

[Colif]

the debugger hasn't been working correctly since the creators edition was released, you might get a better answer if you ask on this forum and follow posting instructions at the top: https://www.tenforums.com/bsod-crashes-debugging/

Hopefully MIcrosoft will fix it, they also broke DISM

I mean, you could try driver verifer if you want to
you can try running driver verifer, just read the instructions carefully. It is part of win 10 designed to find misbehaving drivers. It will cause BSOD, that is its job since it tests drivers.

Once it bsod, run Who crashed and see what driver it reveals - it can at least still read the dumps

note: sometimes this will put you into a boot loop so it helps to have a win 10 installer handy to get out again
download the Windows 10 media creation tool and use it to make a win 10 installer on USB

The instructions to stop it are in the link above I will show u anyway
change boot order so USB is first, hdd second
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose command Prompt
type verifer /reset and press enter
restart PC

 

[Starcruiser]

DISM too? Wow MS, way to break two major tools at once.
Thanks for the info. I'm glad it's not just on my end. I guess I'm putting off my custom Windows 10 image too for now...
I miss the days of opting out of updates. Nothing in the "creator's update" interested me in the slightest.