Windows 10: Constant BSOD with multiple reason codes

I am having mutliple and random BSOD failures, aslo complete freezing that shows no screen and gives no minidump information. I am trying anything and everything and so far I have been unable to find the reason. I have followed a lot of information from other posts on this tech help and have used 'WhoCrashed' to get further information from my minidumps - I have also changed windows settings to give the full information on each minidump


Im starting to get somewhere now, however I now dont know how to fix or even find the driver being reported.


Any help would be greatly appreciated! Thanks!


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 06/04/2020 11:11:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040620-6421-01.dmp
This was probably caused by the following module: hardware.sys hardware
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF8040A89737E, 0xFFFFA587A8369D10, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 SYSTEM_SERVICE_EXCEPTION



On Mon 06/04/2020 11:11:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys hardware
Bugcheck code: 0x3B 0xC0000005, 0xFFFFF8040A89737E, 0xFFFFA587A8369D10, 0x0
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 SYSTEM_SERVICE_EXCEPTION



On Sun 05/04/2020 00:20:26 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040520-6484-01.dmp
This was probably caused by the following module: hal.dll hal+0x48188
Bugcheck code: 0x124 0x0, 0xFFFF950B03FEB028, 0xB2000000, 0x14
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture WHEA.
This is 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 Sun 05/04/2020 19:21:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040520-6187-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2360
Bugcheck code: 0xA 0x24EFBD9BEEF5, 0x2, 0x0, 0xFFFFF800483C97DB
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 05/04/2020 17:38:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040520-6640-01.dmp
This was probably caused by the following module: hal.dll hal+0x48188
Bugcheck code: 0x124 0x0, 0xFFFFAA06F6DD9028, 0xB2000000, 0x14
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture WHEA.
This is 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 04/04/2020 22:44:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040420-6406-02.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C2360
Bugcheck code: 0x50 0xFFFFFFFFFFFFFF84, 0x2, 0xFFFFF8007CC3644C, 0x2
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



:)

 

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 when coming out of sleep, multiple error codes

Thanks for the assistance, I've run all the necessary steps. It looks like there might be an issue found when running that first command. I have also installed all the driver updates recommended by the dell support check.

You can find the logs of the command prompt window in the cmd.log file

cmd logs.txt

 

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.