Windows 10: Constant BSOD with different codes

Hiya, ive ahd my pc for orughly two years and Ive been plagued on and off by a large ammount of BSOD that happen seemingly at random. Rarely if ever have i crashed doing system intensive tasks like gaming or rendering. I seem to crash for unknown reason and have attempted to solve this myself but im at my wits end here. Ive rechecked and updated drivers, updated BIOS, removed any software that may have been the issue.Recently i followed Driver Verifier "guide" https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c98

:)

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.

 

BSOD with differents error code

hi, im just finished all these steps, but after the restart suddenly my pc is having another BSOD with error code KERNEL_MODE_HEAP_CORRUPTION. This is not the first time it happens, before this, im trying a several guide to fix my BSOD, whenever i finished
it, it seems like my pc having another BSOD with different error code. Here's the new minidump files :

https://drive.google.com/file/d/12XpiqTZne3i3foGhQ7C8gLHeF6IRwoqB/view?usp=sharing

Thanks for ur response

 

Constant BSOD even on stock default

As others have addressed, we need the BSOD code, looks something like OxO.....124 or similar.
Without the code or the error listed above the stop code, we are all just taking pot shots at your issue.

I agree if its all of a sudden, its likely ram and as Frick addressed, its very easy to test and verify with memtest 86+ in DOS.