I would like to know if there's any way to make Windows 10 show more details when crashing like Windows 7 did. In Windows 10, the Blue Screen of Death:

enter image description here

hides the parameters of the kernel panic:

enter image description here

The MSDN article Blue Screen Data explains how to attach a debugger in the section titled "Reading Bug Check Information from the Debugger".


I have a BSOD issue right now (Microsoft Support forums post). If you can help with it it would be great.

We do need the actual log files (called .dmp files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, what was responsible, etc.

Answered own question from Microsoft

Thanks for the help I just had to reinstall my windows using the UEFI method. It seems my BIOS firmware has buggy legacy support - I think. When I'm using UEFI method to boot into a new version of Ubuntu there are no kernal panics. Everything runs smoothly.

  • Are you referring specifically to BSOD errors or general crash information like dump files?
    – Abraxas
    Commented Feb 4, 2016 at 5:12
  • Specifically BSOD way to debug error at the point it occurs Commented Feb 4, 2016 at 5:24
  • 1
    Please don't link to problem descriptions that are off-site. Include the information in your question using the edit link.
    – DavidPostill
    Commented Feb 4, 2016 at 13:55
  • Be sure you are running the current version of your audio drivers, your current BSOD, is caused by IntcDAud.sys which is an Intel driver.
    – Ramhound
    Commented Feb 4, 2016 at 19:11

2 Answers 2


"I would like to know if there's any way to make Windows 10 show more details when crashing like windows 7 did"

Yes you can.

Navigate to this registry entry


Create a new DWORD value named DisplayParameters and set to 1

Restart and next time is BSOD's it will show you the old bluescreen with error message.


The other answer does provide a way to get a more verbose blue screen message. However, post-event (as you may miss the screen showing up), it still outputs dump files in the same way that older versions of Windows did with more information. You can read these dumps using WinDbg Debugging Tools for Windows, or NirSoft BlueScreenView - an easier to use alternative that has the ability to mock up a blue screen like the one you're referring to.

Blue screen dumps are, by default, saved in %SystemRoot%\MEMORY.DMP for Complete Memory Dumps, or in %SystemRoot%\Minidump as Minidumps. You can change this setting by pressing Win+X -> System -> Advanced System Settings -> Startup and Recovery Settings. The dropdown box at the bottom states what you're currently using. I would recommend Minidumps as this way you can keep several of them without them overwriting each other.

  • Thankyou can you answer the next question? Commented Feb 4, 2016 at 5:23
  • @PasinduPerera Use BlueScreenView to find out the driver names and bugcheck error codes from your dumps and we may be able to help. The PAGE_FAULT_IN_NONPAGED_AREA bugcheck code typically points to bad memory, often RAM or hard drive. It may be worth running a MemTest86+ live disk over the machine, and testing the hard drive for errors. This topic is a bit too broad though, there are infinite reasons you may be getting blue screens.
    – Jonno
    Commented Feb 4, 2016 at 5:28
  • @PasinduPerera - If you want help with your current BSOD, then provide the details here, not on a third-party website.
    – Ramhound
    Commented Feb 4, 2016 at 19:04
  • @Jonno - Except there is a way to display the information.....
    – Ramhound
    Commented Feb 4, 2016 at 19:05
  • @Ramhound Thanks - learn something new every day. Removed all the incorrect information from my answer.
    – Jonno
    Commented Feb 5, 2016 at 3:09

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .