![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 33%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGQ%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIL%3C/text%3E%3C/svg%3E)
This may be a hardware or software problem.
Right-click Start, select Event Viewer, expand Windows at the left and select System journal.
Right-click on System and select "Save…" to get evtx file. Do not use any filtering, informational events may be meaningful too. Share this file to OneDrive for analysis.
Share several memory minidumps to OneDrive for analysis as described at https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/how-to-post-crash-dumps-after-blue-screen-of-death/5b11c5c7-5903-45b8-8348-0fbee6b2ba6e