Windows 10: Getting constant bsod error on windows 10

I recently installed windows 10 on my pc and I am getting blue screen error. I tried debugging some of the mini dump files on Windbgmy first time debugging and I got drive errors specifically . so I installed the latest intel RST drivers but now I am getting multiple BSOD crashes sometimes twice a day and start up issues. I tried many solutions but none of them do anything. do all the crashes indicate drive error? or are there issues on the motherboard? here is the link to the mini dump files. The file also includes some frequently occuring Event viewer logs and some that happen before each

:)

 

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?

 

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.

 

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.