Question PC will hard restart, hard freeze, and BSOD with no display ?

[Hurmoya]

Hello, I've been having this problem with my pc since Diablo 4 got released so around June of last year. It started happening after I moved my pc to housesit for a family member and when I was playing diablo 4 for the first time it would hard restart, (Screens go black and pc restarts), sometimes when this happens there will be a BSOD behind the black screen I can see in event viewer later.

Around fall of last year it blue screened multiple times in one day and the next day it only booted in recovery mode. I had to use the system restore to get some files off it before wiping the drive. Even after completely reinstalling windows it still persisted. It usually only happens when I'm playing games and seems to be almost random. I've had stretches where it works completely fine for a month then all of a sudden for a few days it's just unusable for games.

Here are my specs:
CPU: Ryzen 9 5900x
Cooler: Dark Rock Pro 4
GPU: Gigabyte 2060 super
Mobo: Gigabyte X570S Aorus Master
Ram: Corsair Vengeance LPX 8gb x4
PSU: Corsair RM850x
Storage: Samsung 980 Pro m.2 1TB & 2TB

Here's what I've done so far

Stress tested CPU and GPU, nothing happened temps were fine.
Scanned for corrupted files
Ran memtest86
Updated chipset drivers
Updated video drivers with DDU
Got a new surge protector

During my testing I couldn't get the problem to happen again. However, since my testing, especially today, it has done BSODS, Hard froze, and done black screen restarts. Any help will be much appreciated.

 

[CountMike]

Hello, I've been having this problem with my pc since Diablo 4 got released so around June of last year. It started happening after I moved my pc to housesit for a family member and when I was playing diablo 4 for the first time it would hard restart, (Screens go black and pc restarts), sometimes when this happens there will be a BSOD behind the black screen I can see in event viewer later.

Around fall of last year it blue screened multiple times in one day and the next day it only booted in recovery mode. I had to use the system restore to get some files off it before wiping the drive. Even after completely reinstalling windows it still persisted. It usually only happens when I'm playing games and seems to be almost random. I've had stretches where it works completely fine for a month then all of a sudden for a few days it's just unusable for games.

Here are my specs:
CPU: Ryzen 9 5900x
Cooler: Dark Rock Pro 4
GPU: Gigabyte 2060 super
Mobo: Gigabyte X570S Aorus Master
Ram: Corsair Vengeance LPX 8gb x4
PSU: Corsair RM850x
Storage: Samsung 980 Pro m.2 1TB & 2TB

Here's what I've done so far

Stress tested CPU and GPU, nothing happened temps were fine.
Scanned for corrupted files
Ran memtest86
Updated chipset drivers
Updated video drivers with DDU
Got a new surge protector

During my testing I couldn't get the problem to happen again. However, since my testing, especially today, it has done BSODS, Hard froze, and done black screen restarts. Any help will be much appreciated.

First thing to heck is what BSODs were all about.
https://www.resplendence.com/whocrashed
Then Google the results.

 

[Hurmoya]

First thing to heck is what BSODs were all about.
https://www.resplendence.com/whocrashed
Then Google the results.

I ran the whocrashed. Since I reset my pc last fall it only has 4 dump files it could find. I've crashed more then that but most of the time the dump file creation fails on the crash. I'm thinking about updating my bios since I have a pretty old version and seeing if that fixes anything. Here's the analyzed minidumps, some of them are weird.

Crash dump file:	C:\Windows\Minidump\111023-14265-01.dmp (Minidump)
Bugcheck code:	0xD1(0xFFFFF8021B5CD694, 0x2, 0x8, 0xFFFFF8021B5CD694)
Bugcheck name:	DRIVER_IRQL_NOT_LESS_OR_EQUAL
Driver or module in which error occurred:	vgk.sys (Unloaded_vgk.sys+0x2D694)
Description:	Vanguard kernel-mode driver
Product:	Vanguard Driver
Company:	Riot Games, Inc.
Bug check description:	This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver. 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: vgk.sys (Vanguard kernel-mode driver, Riot Games, Inc.).
Google query:	vgk Riot Games, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

This one happened a while ago and I just uninstalled vanguard off my pc and all was well.

Crash dump file:	C:\Windows\Minidump\100423-11250-01.dmp (Minidump)
Bugcheck code:	0x5(0xFFFFA886AF93C080, 0xFFFFA886BC89B0C0, 0x1, 0x0)
Bugcheck name:	INVALID_PROCESS_ATTACH_ATTEMPT
Bug check description:	This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

Crash dump file:	C:\Windows\Minidump\031624-11515-01.dmp (Minidump)
Bugcheck code:	0x7F(0x8, 0xFFFF9E01267D1E70, 0xFFFFFE07766B9018, 0xFFFFF8052BC0D451)
Bugcheck name:	UNEXPECTED_KERNEL_MODE_TRAP
Bug check description:	This bug check indicates that the Intel based CPU generated a trap and the kernel failed to catch this trap.
Analysis:	Double Fault indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow), which means that there is a driver consuming too much stack space or there are too many drivers attached in the same stack. This is likely a software problem, but it may also be caused by faulty hardware. Read this article on thermal issues

This one is strange to me since I have an AMD cpu not an intel cpu.

This is the black screen restart that happened last night. The actual blue screen information said something about "IP_MISALIGNED_AuthenticAMD.sys"

I tried doing some research into it but whocrashed didn't give me too much information on which drivers to research besides the vanguard one which I already had deleted. So I'm a little lost on where to go from here. Later today I probably will run the BIOS update unless I can figure out how to narrow things down more. My current BIOS version is F2 and the newest is F6. Thank you for your help and showing me this tool. Hopefully I can get this PC stable.

 

[Hurmoya]

I ran the whocrashed. Since I reset my pc last fall it only has 4 dump files it could find. I've crashed more then that but most of the time the dump file creation fails on the crash. I'm thinking about updating my bios since I have a pretty old version and seeing if that fixes anything. Here's the analyzed minidumps, some of them are weird.

Crash dump file:	C:\Windows\Minidump\031624-11515-01.dmp (Minidump)
Bugcheck code:	0x7F(0x8, 0xFFFF9E01267D1E70, 0xFFFFFE07766B9018, 0xFFFFF8052BC0D451)
Bugcheck name:	UNEXPECTED_KERNEL_MODE_TRAP
Bug check description:	This bug check indicates that the Intel based CPU generated a trap and the kernel failed to catch this trap.
Analysis:	Double Fault indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow), which means that there is a driver consuming too much stack space or there are too many drivers attached in the same stack. This is likely a software problem, but it may also be caused by faulty hardware. Read this article on thermal issues

This one is strange to me since I have an AMD cpu not an intel cpu.

Crash dump file:	C:\Windows\Minidump\111023-14265-01.dmp (Minidump)
Bugcheck code:	0xD1(0xFFFFF8021B5CD694, 0x2, 0x8, 0xFFFFF8021B5CD694)
Bugcheck name:	DRIVER_IRQL_NOT_LESS_OR_EQUAL
Driver or module in which error occurred:	vgk.sys (Unloaded_vgk.sys+0x2D694)
Description:	Vanguard kernel-mode driver
Product:	Vanguard Driver
Company:	Riot Games, Inc.
Bug check description:	This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver. 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: vgk.sys (Vanguard kernel-mode driver, Riot Games, Inc.).
Google query:	vgk Riot Games, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL

This one happened a while ago and I just uninstalled vanguard off my pc and all was well.

Crash dump file:	C:\Windows\Minidump\100423-11250-01.dmp (Minidump)
Bugcheck code:	0x5(0xFFFFA886AF93C080, 0xFFFFA886BC89B0C0, 0x1, 0x0)
Bugcheck name:	INVALID_PROCESS_ATTACH_ATTEMPT
Bug check description:	This generally indicates that the thread was attached to a process in a situation where that is not allowed. For example, this bug check could occur if KeAttachProcess was called when the thread was already attached to a process (which is illegal), or if the thread returned from certain function calls in an attached state (which is invalid).
Analysis:	This is a typical software problem. Most likely this is caused by a bug in a driver.

This is the black screen restart that happened last night. The actual blue screen information said something about "IP_MISALIGNED_AuthenticAMD.sys"

I tried doing some research into it but whocrashed didn't give me too much information on which drivers to research besides the vanguard one which I already had deleted. So I'm a little lost on where to go from here. Later today I probably will run the BIOS update unless I can figure out how to narrow things down more. My current BIOS version is F2 and the newest is F6. Thank you for your help and showing me this tool. Hopefully I can get this PC stable.

Got the problem to recreate on Dark and Darker. It was the exact same problem as the one last night. Freezes for half a second then screens go black, pc stays on (probably doing the bsod), and then restarts. It also hard froze around 30 mins after rebooting while just on the browser and discord, had to hard restart it.

 

[CountMike]

Got the problem to recreate on Dark and Darker. It was the exact same problem as the one last night. Freezes for half a second then screens go black, pc stays on (probably doing the bsod), and then restarts. It also hard froze around 30 mins after rebooting while just on the browser and discord, had to hard restart it.

Got the problem to recreate on Dark and Darker. It was the exact same problem as the one last night. Freezes for half a second then screens go black, pc stays on (probably doing the bsod), and then restarts. It also hard froze around 30 mins after rebooting while just on the browser and discord, had to hard restart it.

Definitively hardware or incompatibility problem, New firmware may solve it.

 

[Hurmoya]

Definitively hardware or incompatibility problem, New firmware may solve it.

Updated the BIOS, spent a couple hours playing with no issues, then had a hard freeze. Not sure where to go from here.

 

[Hurmoya]

Updating the BIOS seems to have helped with the black screens. But the PC still freezes and BSODs. Right now I'm trying it with only my 2nd monitor (1080p, 60hz) and so far it appears to be stable. But I will test it more thoroughly.