Windows 10: Clean game crashes + Blue screens

Lately I have had the issue that my games keep crashing without any error's or bugreports, just crashing cleanly to my windows desktop. Furthermore, about a week later when that started happening, my computer started having bluescreens while I was playing games. At first I thought it had to do with VALORANT, because it started happening around the time that game came out, but it quickly started happening in other games as well.

I use the program WhoCrashed, and they state it has something to do with drivers of hardware.sys. I'm not sure what this means exactly.

Here are my system information and crash dumps:


System Information:

Computer name: DESKTOP-BPLIPOH

Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z390-E GAMING
CPU: GenuineIntel IntelR CoreTM i7-9700K CPU @ 3.60GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 34273611776 bytes 31,9GB

Crash Dumps according to WhoCrashed:

On Tue 23-6-2020 22:37:31 your computer crashed or a problem was reported

crash dump file: C:\Windows\Minidump\062320-18890-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
Bugcheck code: 0xA 0x0, 0x2, 0x0, 0xFFFFF8076E85CA3C
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 Wed 1-7-2020 15:27:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070120-21218-01.dmp
This was probably caused by the following module: hardware.sys hardware
Bugcheck code: 0x1000007E 0xFFFFFFFFC000001D, 0xFFFFF80088C957FB, 0xFFFFF48CA0126208, 0xFFFFF48CA0125A50
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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_THREAD_EXCEPTION_NOT_HANDLED_M

On Fri 3-7-2020 01:20:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe nt!memset+0xA7435
Bugcheck code: 0xF7 0xFFFFBE8B58F7B200, 0x76B56E7F4133, 0xFFFF894A9180BECC, 0x0
Error: DRIVER_OVERRAN_STACK_BUFFER
Bug check description: This indicates that a driver has overrun a stack-based buffer.
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 Fri 3-7-2020 01:20:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070320-13828-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x1C23A0
Bugcheck code: 0xF7 0xFFFFBE8B58F7B200, 0x76B56E7F4133, 0xFFFF894A9180BECC, 0x0
Error: DRIVER_OVERRAN_STACK_BUFFER
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 driver has overrun a stack-based buffer.
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.

Conclusion

4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

hardware.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

:)

 

Random apps and games crashes with error 0xc0000005 and blue screens

Since the end of July 2019 my apps and games (including windows services) have been crashing randomly, the windows event log lists these crashes with error 0xc0000005, here's an example for the game Verdun (other apps and games crash with the same error):

Faulting application name: Verdun.exe, version: 2019.2.4.15146, time stamp: 0x5d65bc48

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00003ffca4ea3081

Faulting process ID: 0x1760

Faulting application start time: 0x01d5859441ddbe1a

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\WW1GameSeries\Verdun\Verdun.exe

Faulting module path: unknown

Report ID: 47476bd7-22fa-4760-b22b-07598c183ba1

Faulting package full name:

Faulting package-relative application ID:

I have also been having random blue screens with the errors PAGE_FAULT_IN_NON_PAGED_AREA and CRITICAL_PROCESS_DIED.

I have used windows Driver Verifier and I managed to get some blue screens that point to the clipsp.sys driver but I don't think the content of the blue screen contains everything meaningful.

The crashes do not seem to happen in Safe Mode.

In the past months I have tried almost everything:

• Clean boot
• Updated windows to latest version
• Used all tools to check integrity or corruption like sfc, chkdsk, ecc.
• Clean reinstalled windows multiple times
• Replaced RAM modules
• Replaced motherboard

The crashes still happen. Since I have no idea what is causing these crashes my next step will be replacing the CPU...

 

PC Games crashing randomly, Chrome Crashing, and Frequent Blue Screens

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that games are crashing and Chrome is not working on your computer. I’ll certainly assist you with the issue.



However, please let us know:

• Do you receive any error message when the games crash?
  
• What error message do you get when the PC crashes to Blue Screen?
  
• Which build version of Windows 10 is installed on the computer? To check type:
  winver in the search bar on the Taskbar and hit
  Enter.
  

As you are receiving Aw snap error in Chrome, I would suggest you to refer the troubleshooting steps mentioned in the Google article

Fix "Aw, Snap!" page crashes and other page loading errors and see if that helps.



You may also want to boot the computer in to clean boot and see if the Games/PC crashes.



Performing a clean boot will start the computer with minimal set of drivers and programs, to determine whether a background program is causing the issue. Some of the Startup programs will not load after performing a clean boot on the computer.
However, that functionality will return when you reset the computer to start normally after finishing the troubleshooting.



To perform a clean boot on the computer refer to the article How to perform a
clean boot in Windows.



If performing a clean boot fixes the issue then, please refer to the section
How to determine what is causing the problem after you do a clean boot
to check which program is causing the issue.



Note: Please refer the section Reset the computer to start normally after clean boot troubleshooting
to boot the computer in to normal mode after troubleshooting.



If you are receiving a Blue Screen error on the computer, I would suggest you to share the dump files so that we can analyze them and get to the root cause of the issue. To share the files Navigate to
C:\Windows\Minidump, upload the files to OneDrive and share the OneDrive link.



We await your response.



Regards,

Nikhar Khare

Microsoft Community - Moderator

 

Crash/blue screen

Hi

I assume from the title of your post Crash/Blue Screen that the PC has crashed and produced a *BSOD=[Blue Screen Of Death] =Blue Screen; and that the PC recovered from this; if and when you see the Blue Screen write the Stop Code down; recover the PC or use one that is working to access the net and look up the Stop Code.

nb: You may be able to view this with a [*BlueScreenView] application, google for this.

Edit Link - Blue screen of death (STOP error) information in dump files.

Description
===========

BlueScreenView scans all your minidump files created during 'blue screen
of death' crashes, and displays the information about all crashes in one
table. For each crash, BlueScreenView displays the minidump filename, the
date/time of the crash, the basic crash information displayed in the blue
screen (Bug Check Code and 4 parameters), and the details of the driver
or module that possibly caused the crash (filename, product name, file
description, and file version).
For each crash displayed in the upper pane, you can view the details of
the device drivers loaded during the crash in the lower pane.
BlueScreenView also mark the drivers that their addresses found in the
crash stack, so you can easily locate the suspected drivers that possibly
caused the crash.

atb

Law-II