Windows 10: Constant BSOD while Starting Computer

So, for the past two months, I have been getting constant BSOD with numerous STOP Codes such as CRITICAL_PROCESS_DIED, PAGE_FAULT_IN_NON_PAGED_AREA,MEMORY MANAGEMENT, INTERNAL POWER ERROR and KERNEL MODE HEAP CORRUPTION.


I have already clean booted my PC, Run SFC, DISM and CHKDSK. I also have run Windows Memory Diagnostic tool and MemTest86 for 4 hours.

I have the latest version of Windows and the latest drivers installed. Here is my WhoCrashed report-



On Mon 30-11-2020 08:24:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\113020-10500-01.dmp
This was probably caused by the following module: fltmgr.sys 0xFFFFF8021A9D86AD
Bugcheck code: 0x50 0xFFFF93027FFAFC00, 0x0, 0xFFFFF8021A9D86AD, 0x2
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 30-11-2020 08:24:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys 0xFFFFF8021A9D86AD
Bugcheck code: 0x50 0xFFFF93027FFAFC00, 0x0, 0xFFFFF8021A9D86AD, 0x2
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 29-11-2020 08:34:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112920-9312-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x13A 0x9, 0xFFFF800B6E000000, 0xFFFF800B80FB8C60, 0x0
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 28-11-2020 09:59:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112820-10234-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1A 0x41790, 0xFFFF958006591F00, 0x62, 0x63
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A page table page has been corrupted.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver. This problem might also be caused because of overheating thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25-11-2020 19:49:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112620-10750-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0xA0 0x107, 0xA, 0xFFFF9E8D307ADC70, 0x0
Error: INTERNAL_POWER_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the power policy manager experienced a fatal error.
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 24-11-2020 20:25:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112420-9890-01.dmp
This was probably caused by the following module: hardware.sys hardware
Bugcheck code: 0x1A 0x41792, 0xFFFFFE3FFCFAEC88, 0x2, 0x0
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver. This problem might also be caused because of overheating thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT


Note- These occurred after the Clean Install I did. I had the same problems before t he clean install. I am unable to solve the problem and it's frustrating. I want to solve this problem as soon as possible.

:)

 

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 CONSTANT RESTART LOOP

Hi,

This issue might occur due to an old or corrupted graphics driver. Since you are experiencing a constant restart loop, we suggest that you follow the Startup Repair steps below:

• Turn off your computer.
• Turn on your computer. As soon as you see the Windows logo with the spinning dots, press and hold down the power button until your computer turns off. Do this process
  twice.
• Turn on your computer for the third time, and let it load.
• It should give you the message: Preparing Automatic Repair.
• On the next screen that would appear, click on Advanced Options.
• Select Troubleshoot.
• Go to Advanced Options.
• Click on Startup Repair.
• Wait for the repair to finish.

We would appreciate it if you could get back to us and provide us your feedback.

 

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?