Windows 10: Constant BSOD errors, yet again

I asked previously on this thread, but seems like the person helping couldn't reach out again.


https://answers.microsoft.com/en-us/windows/forum/all/constant-bsod-errors/2e8b8d6e-cdc9-47ab-82e5-bf260016c15e


While the previous solution worked momentarily, the errors are getting as common as before. And they were increasingly worse after I updated the BIOS. I'm getting watchdog violation, IRQL and kernel related errors. I've complied a folder with the new dump files and kernel dumps, in case that helps. Not sure they will, but I saw them around and since I was getting errors related to the name, I uploaded them too.


https://1drv.ms/u/s!AokLmKI19xeShS8IPLHcelQnq8JG?e=znKVKr


Thank you!

:)

 

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.

 

Constant script errors and slow loading pages in 10 internet explorer 11

I have done the steps listed above. They have not helped and I am still getting constant script errors, along with slow loading pages. Are there any other suggestions?

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.