This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I was trying to play HD2 but it kept crashing on me, so I fiddled with my BIOS settings to see if I was over heating at first, but when that didn't work I went back to my default PC settings but now my other games start to pull up this stop code error. I tried looking at past questions on this topic, but I am having a hard time understanding. When I pull up my C:/Windows/minidump file its last record was 12/5/23 yet I'm crashing in 5/17/24. when I open the file it says, "Debugging Kernel crashdumps is not supported".
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Just in case this helps, I made a google drive containing all of the known crashdumps I have that are of today. https://drive.google.com/drive/folders/12JJAB0aXDgi0S3vfB9IvWy76_vLUhZVq?usp=sharing willing to accept any help for this, I don't know what I'm doing for the most part but I will continue to scour the forums on this, I saw that Sakiko has helped others with similar issues, and I will try and use them as reference for possible fixes to an extent.
its been a few hours, I followed the link you had sent and started the verifier process through cmd, restarted the PC and it booted up just fine. I tried running all the other applications I was having trouble with and they still crash as I had expected but nothing is coming up in the minidump file. I do however have a crashdump file that is being updated through every crash. I haven't had a blue screen crash since, but the crashdump is located in ...AppData/Local/Crashdumps. Would any of those logs be of use?
To collect information faster, we may need to enable the driver verifier.
Please first create a restore point for your system, then please refer to this article: https://learn.microsoft.com/en-us/windows-hardw... to enable driver verifier. In the third step select "Automatically select all drivers installed on this computer", wait for a couple of new blue screens and then collect 2-3 new dump files and share the new dump files with me.
If the computer has any automatic overclocking features enabled (including XMP, PBO, etc.) or manual overclocking, please restore the defaults first.
Driver verifier puts heavy pressure on the drivers in your system to troubleshoot drivers that are in poor condition or misbehaving. It is normal for your computer to run slowly after driver verifier is turned on. The computer will also crash more frequently and generate dump files during this process.
If your system fails to boot after driver verifier is turned on, please restore via the restore point.
I was able to change the minidump field successfully, what would be the next step on figuring out what to do, I have also taken a look at my drivers and checking for updates, but everything seems to be up to date as there are no discrepancies in my software update history
Hello, I'm here to help.
The minidump should be enabled by default, to check this, go to: Settings - System - Advanced System Settings, click on “Advanced - Settings” and change “Write debugging information” to “Small memory dumps”.
If you have any questions, please feel free to let me know. This is not a live chat channel and I may be in a different time zone than you. As a result, replies may be delayed and I may respond minutes to hours later.
