Does Windows save BSOD reports on the affected PC?

I know there is the online Microsoft page about troubleshooting BSOD errors and that the Windows 10 BSOD Troubleshooter no longer exists. But I wonder if the SO saves some sort of report for these errors on the PC itself. If yes, where?

I just got a BSOD and took a picture, but it is blurred and I can't read its text with smaller letters. It seems to me it reads UNEXPECTED STORE EXCEPTION.

Attachment 279684

Any idea? TIA.

Windows 10 Pro 1909 18363.836

Please see posting instructions.

In addition to the excellent suggestions above, BSOD's can (but don't always) save different reports. It depends on a bunch of different things (is it hardware or software, does it occur too ealry in the boot to capture, etc) More detailed info on how BSOD's and crash dump files are generated is here: BSOD Crash Dump Generation
- most important are the dump files, found in either C:\WIndows\MEMORY.DMP (overwritten each time you get a BSOD) and in C:\WIndows\Minidump (filenames are datestampted so they're not overwritten. They require Debugging Tools for Windows (and a bit of experience) to massage them into revealing the errors.
- WER reports (and in MSINFO32's WER section)
- Reliability Monitor
- Event Viewer - System logs
- and other reports

The reports asked for in the Posting Instructions (a pinned topic at the top of this forum) will let us get started on figuring it out. Here's a link to it: BSOD - Posting Instructions

Sorry I didn't see there is this specific area for BSOD. That's why I asked if Windows saves reports. My first reaction was to know about that, thinking I myself would then take a report and try to find solutions online. I had no idea such reports could be sent here for analysts. I was pessimistic about having to send it to Microsoft itself (bad past help experiences). Today is Friday, a very busy day for me, so I'll check on the instructions later. Thank you!

We'll be here when you're ready.
If you have any questions about what we do - feel free to ask.

Before I started the process of using the log collector, I needed to work on a design job. I was using CorelDRAW 2017, Chrome 83.0.4103.61 64-bit (with about four tabs open), Winamp 5.6.6.3516, and a couple of File Explorer folders open. I was editing the CorelDRAW file when the system froze. It was not a BSOD, but I had to force it to turn off, then turned it on again. No special message appeared after rebooting, only when I opened Chrome it asked if I wanted to restore the closed tabs.

File attached. Thanks again.

- - - Updated - - -

Right after I sent you that file, I started to work again and got a new BSOD, this time with the code Driver IRQL not less or equal.

So I made a new log file.

The logs were in a foreign language and were not able to be scanned.
Please use English as the default language and upload a new V2:

https://www.tenforums.com/tutorials/...dows-10-a.html
Change Display Language in Windows 10


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


13) Make sure that there is no over clocking while troubleshooting

11) Sometimes there are problems in the bios that produce BSOD

The BIOS: Versão/data do BIOS Intel Corp. SOX5810J.86A.4598.2009.1211.1321, 11/12/2009

12) Please check to see if this is the most up to date version

13) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

14) To ensure that there are no improper bios settings please reset the bios

15) Create a brand new restore point.
Create System Restore Point in Windows 10

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)


16) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

17) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

18) Post a share link for: C:\windows\memory.dmp

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
25/05/2020 14:31:11    686,45 C:\Windows\MEMORY.DMP

19) Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

20) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Since it's a long list of tasks, and I need to work on the design job I mentioned earlier, I will have to wait till I finish this job.

But I ran the SFC command and it reported corrupted files and a successful fix. I also ran the first DISM command on the list, and it reported no corruption.

I did it without changing the system language, because it would take me more time. When I finish my design job I'll do all these tasks.

BlueScreenView two reports related the two BSODs as caused by driver ntoskrnl.exe.

The first has a blank Bug Check String. The second has DRIVER_IRQL_NOT_LESS_OR_EQUAL.

And both report Caused By Address ntoskrnl.exe+1c2390.

I wonder if there is a solution for this particular driver alone.

Paultx said:

Since it's a long list of tasks, and I need to work on the design job I mentioned earlier, I will have to wait till I finish this job.

But I ran the SFC command and it reported corrupted files and a successful fix. I also ran the first DISM command on the list, and it reported no corruption.

I did it without changing the system language, because it would take me more time. When I finish my design job I'll do all these tasks.

BlueScreenView two reports related the two BSODs as caused by driver ntoskrnl.exe.

The first has a blank Bug Check String. The second has DRIVER_IRQL_NOT_LESS_OR_EQUAL.

And both report Caused By Address ntoskrnl.exe+1c2390.

I wonder if there is a solution for this particular driver alone.

Ntoskrnl is related to the Windows operating system and does not display information about misbehaving drivers or malfunctioning hardware.
When possible please follow the earlier steps to troubleshoot the BSOD.