[SOLVED] BSOD while heavy use of pc

[jhollis505]

Hello, I've build a new pc recently and have been having some issues. When I first built it, and while trying to play Deus Ex: Mankind Divided, I kept getting BSODs. I followed some info online (it was a couple of weeks ago and don't remember what I did besides updating some drivers), then my pc was working just fine. I ordered a new nvme ssd and did a fresh install of Windows 10 on it. Now I'm playing RDR 2 and am having the same issue, however, updating drivers did not correct the issue. I have tested two sets of ram with the system, both tested without errors. However, the ram I currently have in the pc, I have made the timings in the bios what they are rated for and tuned the Infinity Fabric to 1600mhz. I did try the ram out at the default settings for bit and the pc was running fine while playing RDR 2 for about a hour (it takes roughly 15 to 30 mins for the BSOD to happen), but I didn't have them on default for too long. My gpu and cpu are not overclocked. I have tested both of them with AIDA64 without issue. The only other game I have installed and have played is Prey 2017 and I have played that game for hours without having a BSOD. Any help is appreciated. And if any more info is needed, let me know. Thank you.

Here is the OneDrive link for 3 DMP files, MSinfo32, and Aida64 Summery: https://1drv.ms/u/s!AtKNBFgpKtoErFd7TPM_ipmRoXOB?e=dALiGC

Also, the newest DMP was made following info from using driver verifier, the other two were made from enabling minidumps.

Other info that might not be included with summery:
RAM: XPG Z1 3200 AX4U320038G16A-DBZ
SSD: XPG SX8200 Pro 2TB
Nvidia driver 461.92

 

[Colif]

Driver verifer blames ene.sys
ene.sys = rgb drivers for motherboard. Maybe try updating them, I guess through Armoury?

other 2 BSOD are WHEA errors, they don't blame anything in particular which is normal.

conversion of dumps - https://jsfiddle.net/6jc4weqt/show

Its stormy here so I will look at dumps more later.

 

[jhollis505]

There wasn't an update for Armoury Crate. I have uninstalled it (my rgb works without the app). I'll try to replicate the BSOD without Armoury Crate.

 

[jhollis505]

I got another BSOD. I uploaded the dmp file to OneDrive.

https://1drv.ms/u/s!AtKNBFgpKtoErFd7TPM_ipmRoXOB?e=zqf4DE

 

[gardenman]

Hi, it's easier for us if you create a new folder each time you upload new dumps. Otherwise we have to try to figure out which ones we've looked at and which ones we haven't by going back and looking at previous posts. Thanks. I think I got it this time.

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/ejrcnpm4/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032021-5875-01.dmp (Mar 20 2021 - 15:13:54)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 3 Hour(s), 13 Min(s), and 46 Sec(s)

Possible Motherboard page: https://rog.asus.com/us/motherboards/rog-crosshair/rog-crosshair-viii-hero-model/
You have the latest BIOS already installed, version 3302.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[jhollis505]

I'm back again with one more dmp: https://1drv.ms/u/s!AtKNBFgpKtoErF6131dEm9BtI5LI?e=bUfBQv

Just to double check, I put my ram timings on AUTO in the bios. While playing RDR 2, I received another BSOD. After about a hour of play, windows crashed without a BSOD. So I booted up RDR 2 again to replicate the crash to try to make it blue screen. It did. Hopefully the extra file may of use.

Thank you.

 

[Colif]

Its not going to get any better weather wise for the next week so i will be in when I can.

WHEA - Windows Hardware Error Architecture
Error called by CPU but not necessarily caused by it
Can be caused by any hardware or sometimes hardware driver
can be caused by overclocking - you don't have any
Can be caused by overclocking software, so remove things like Asus AI Suite, MSI Afterburner, Asus GPU Tweak 2. MSI Gaming APP
Can be caused by heat

Older versions of AI Suite included an older version of this file

Apr 09 2019

AsIO2.sys

Asus Input Output driver

I am not aware of any BSOD caused by this version but I just thought I mention it as ASio.sys was a cause of WHEA errors.
You also have this one

Dec 15 2020

AsIO3.sys

ASUS Input Output driver

which also has no history of causing WHEA so might be okay

there should be a new version of Icue
new version of realtek lan drivers, 3rd link under windows header - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

I wonder what this is part of as it shows in all the WHEA errors

Sep 09 2005

ssgdio64.sys

ATI Diagnostics Hardware Abstraction System driver

Obviously I know its AMD but part of what, I have an X570 motherboard (not Asus) and I don't have that running in my drivers.

do you have the chipset drivers installed? I don't see much AMD there.
https://www.amd.com/en/support/chipsets/amd-socket-am4/x570


ene.sys is still on PC, you may have removed the RGB app but as of a WHEA report after I mentioned it, its still showing.
I don't know if you can stop it using https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

 

[jhollis505]

I recall installing chipset drivers. I might have gotten them for the motherboard manufacture website. I just checked on asus's website and they have an old chipset driver: 2.11.26.106 . On the link you sent, the chipset driver is : 2.13.27.501 . So I installed the newest chipset driver.

I also looked at the autoruns link. When I run the autoruns program, I can't find ene.sys . I have included a screenshot: https://1drv.ms/u/s!AtKNBFgpKtoErGBzy7Uz95UOlEZp?e=dvE8Qf

 

[Colif]

at first i thought it hadn't worked and then i realised you had searched for ene and it wasn't showing it.

what rgb do you have, before we remove this? ene is used by a bunch of companies, Corsair doesn't but many of the motherboard makers use it in their rgb products. So anything else apart from Motherboard and Corsair?

the only way i found to remove it is delete it in safe mode. The RGB program should have removed it.
Go to C:\Windows\System32\drivers folder, and then check if “ene.sys” file is present.
reboot the system into safe mode*, and then go to the same folder and delete the “ene.sys” file

*go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose startup options
click the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode

 

[gardenman]

The newest dump is WHEA 124 also. Results: https://jsfiddle.net/1ydqcsfk/show You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032121-5937-01.dmp (Mar 21 2021 - 01:54:39)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 0 Hour(s), 04 Min(s), and 18 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

i hate WHEA error, its very rare they actually tell me anything
2 types
Type 1

STACK_TEXT:
ffffcf00d1e8d938 fffff8006a6b3a6a : 0000000000000124 0000000000000000 ffffab8319150028 00000000bc000800 : nt!KeBugCheckEx
ffffcf00d1e8d940 fffff800688d15b0 : 0000000000000000 ffffab8319150028 ffffab83167fda40 ffffab8319150028 : nt!HalBugCheckSystem+0xca
ffffcf00d1e8d980 fffff8006a7b55fe : 0000000000000000 ffffcf00d1e8da29 ffffab8319150028 ffffab83167fda40 : PSHED!PshedBugCheckSystem+0x10
ffffcf00d1e8d9b0 fffff8006a6b5391 : ffffab831eeb8bd0 ffffab831eeb8bd0 ffffab83167fda90 ffffab83167fda40 : nt!WheaReportHwError+0x46e
ffffcf00d1e8da90 fffff8006a6b5703 : 000000000000000f ffffab83167fda90 ffffab83167fda40 000000000000000f : nt!HalpMcaReportError+0xb1
ffffcf00d1e8dc00 fffff8006a6b55e0 : ffffab83166fdac8 0000000000000000 ffffcf00d1e8de00 0000000000000000 : nt!HalpMceHandlerCore+0xef
ffffcf00d1e8dc50 fffff8006a6b4b25 : ffffab83166fdac8 ffffcf00d1e8def0 0000000000000000 0000000000000000 : nt!HalpMceHandler+0xe0
ffffcf00d1e8dc90 fffff8006a6b72e5 : ffffab83166fdac8 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHandleMachineCheck+0xe9
ffffcf00d1e8dcc0 fffff8006a70ca29 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalHandleMcheck+0x35
ffffcf00d1e8dcf0 fffff8006a604cfa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x9
ffffcf00d1e8dd20 fffff8006a6049b7 : 0000000000000000 0000000000000000 000001c7c3429114 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffcf00d1e8de60 00007ff7945b9b0d : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
0000003d6ffcf4a0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff7945b9b0d Type 2 STACK_TEXT: ffffb5816c68d938 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : nt!KeBugCheckEx

type 1 shows me lots of actions but they all lead to an error and don't show a driver name
Type 2 tells me even less.

last 2 have been type 2's but they think its a windows driver to blame.

I don't know if ene.sys is cause of whea errors but it did set Driver verifer off, so have to resolve it before we can be sure.
curious why my quote is not working right

 

[jhollis505]

I followed your instructions and deleted ene.sys . I replicated the BSOD and have a new dmp: https://1drv.ms/u/s!AtKNBFgpKtoErFd7TPM_ipmRoXOB?e=dUVBtY

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/7rob1wmt/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032121-6046-01.dmp (Mar 21 2021 - 14:41:25)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 0 Hour(s), 29 Min(s), and 17 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

I was going to use the AIDA info to fill in rest of details but you not sharing it now - yes, I know what gardenman said, i didn't expect you to un share before i looked. It doesn't matter now.

CPU - AMD Ryzen 7 5800X - tested in AIDA
MB - Asus ROG CROSSHAIR VIII HERO latest BIOS
RAM: XPG Z1 3200 AX4U320038G16A-DBZ - how did you test it?
SSD: XPG SX8200 Pro 2TB
What GPU?
Any other storage?
What PSU?
What else?

well, it wasn't ene.sys
searching for ssgdio64.sys finds another thread I was in where it ended up being the CPU to blame. Still trying to figure out what its part of. Its ATI Diagnostics. ATI were merged into AMD years ago, I don't know why it is on here. ATI were graphics cards, you have an Nvidia card. Trying to figure out what its part of leads me to many bsod reports
ATI Diagnostics Hardware Abstraction System driver.
seems its part of Ryzenmaster, still strange as I have it installed and I don't see that driver.
try updating Ryzenmaster, I did a few days ago, newest version dated March (you can update it via its settings)

slaps self, I should have mentioned Ryzen Master in list of overclocking programs. I forget not everyone has it just to check temperatures & usage since Task Manager has no idea how fast my CPU really is. Might want to take it off if you don't use it.

 

[jhollis505]

I uninstalled Ryzen Master. I got a new dmp: https://1drv.ms/u/s!AtKNBFgpKtoErGUoSxlqL36eV33k?e=iFR2kz

After doing all that you have told me, the game does seem to take longer to BSOD. I can actually get through a mission because it BSOD.

 

[jhollis505]

GPU: Gigabyte 3070 gaming oc
PSU: Seasonic PX-850
No other storage on this install of windows. I did have more on the previous install.
New link for summery (just in case): https://1drv.ms/u/s!AtKNBFgpKtoErGe0r4lfyLmxRb-2?e=DE5B19

I tested the ram with Testmem5 v0.12, OCCT, AIDA62, and MemTest86. I went on some forums to find the best memory tester and all of popped up.

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/thjn2a1o/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	032121-6031-01.dmp (Mar 21 2021 - 16:01:04)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	AuthenticAMD (Process: RDR2.exe)
Uptime:	0 Day(s), 1 Hour(s), 19 Min(s), and 05 Sec(s)

Suggestion: Run some CPU tests. Whether Prime95 or something else.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[jhollis505]

I have used AIDA64 to test the cpu, but I think that might have been before the fresh install. Just to double check,, I'm running MemTest86 right now while I'm at work. I'll update when I get back home.

EDIT: MemTest 86 completed with 0 errors

 

[jhollis505]

I'm also going to run Prime95 tomorrow while at work. Any suggestions as to which torture test to do?

 

[Colif]

Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

i can't fault a PX 850, I have a 750 myself. One day I will find a failed Seasonic PSU but it hasn't happened yet

running out of tests if you run memtest already

i have seen this cause BSOD recently which seemed unlikely

Jun 12 2020

cpuz150_x64.sys

CPUID driver

I almost said that bsod was 2 days ago but then remembered I am only person in Tuesday so far.
Did you update Icue?
this can be used to overclock

Jan 19 2020

MsIo64.sys

MSI Gaming App driver

 

[jhollis505]

I ran the blend test on Prime95 for 4 hours with no errors. I wasn't gonna be home so I stopped the test.

I have updated Icue. If the Msi64.sys is part of afterburner, I don't believe I have that installed.

I'll follow the instructions for the Prime95 link and I'll update.

EDIT: I googled Msio64.sys and I can't find anything about it being a MSI gaming app driver. There isn't much info I can find on it. From what I saw, the small amount of info is pointing to Viper ddr4 ram. That's weird. I didn't see anything about MSI and I don't have Viper ram. The two kits I had spoke about are Corsair and G skill.

EDIT 2: I have included a screenshot of file explorer with any MSIO file: https://1drv.ms/u/s!AtKNBFgpKtoErGlWew5d8ApT9FLR?e=erIPsR

 

[jhollis505]

Also, I've been on a few other forums and they have suggested using BlueScreenView to view the dmp files. I don't know if this is a good program to use but I just got BSOD and used the program to view it. BSV shows "Caused By Driver: ntoskrnl.exe" and "Caused By Address: ntoskrnl.exe+3f5c50". I also looked at the other dmp files and they say the same thing. Should I be worried about this?

 

[Colif]

Msio64.sys appears to be another rgb driver, is part of a few programs, Asrock RGB (Asrock & Asus seem to share lots of things). I found this which seems to suggest its an Asus program. - https://answers.microsoft.com/en-us...ng-files/22f45e32-3abf-4e07-aad1-ee72445ff713

I would remove all Asus programs, most of the programs you get from motherboard makers seem to cause problems.

have you run any 3rd party driver updaters? I don't want you to, just curious.

if you want to try another website, I would suggest https://www.tenforums.com/bsod-crashes-debugging/ as they won't suggest Bluescreenview

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

 

[jhollis505]

I went ahead and deleted MSIO64.sys in safe mode. I'll try to replicate the BSOD again and update.

The only Asus programs I have are: ASUS Framework Service 2.0.2.2 and ASUS Motherboard 1.05.16 . Should I go ahead and uninstall them?

On this install, I haven't used any 3rd party driver updaters. On the prior install, I did. There were a couple of forums that suggested to, however, after doing that, I found many people saying not to.

When I made my initial post, I did make some posts on other forums. I haven't had an issue like this before and wasn't sure where the best place was to get some help, but this forum has been the only place to get any replies. So I'm very happy with my experience here.

 

[jhollis505]

I got another BSOD after deleting MSIO64.sys: https://1drv.ms/u/s!AtKNBFgpKtoErGsoyBIBUfwFztYi?e=tToAmW