Question Computer BSODing very often with WHEA errors! I'm stumped!

May 8, 2021
14
0
10
0
CPU: Ryzen 7 3700 x
GPU: EVGA 3080 FTW3
RAM: 16GB Corsair DDR4 @ 2400Hz
Motherboard: ROG Strix B550-F Gaming

I've tried a few things ranging from getting the latest windows updates to using DDU uninstaller for a fresh clean install of graphics drivers, I've tried to look at my Blue Screen View but it only says that it was a NT Kernel & System error, i.e.) ntoskrnl.exe+5b557c & PSHED.dll+10a4 (Platform specific hardware error driver) & storport.sys+5a79c (Microsoft Storage Port Driver)

I tried to do a Driver verifier detector and while it did BSOD there was no .sys to identify in the stop code, but going back to the BlueScreenView after using a restore point, there's a new address in red called ene.sys+1d93 (NT Kernal & System) Any ideas on what I should do next? I'm willing to provide any info I can to help get this fixed, I just want to game man!
 
May 8, 2021
14
0
10
0
enable windows driver verifier with all customized tests , just exlude Randomized low resources simulation. After few hours open cmd with admin rights and type this command:
verifier /querysettings
once done press CTRL + A and CTRL + C
then paste it here (CTRL + V) in thread
I noticed while selecting the drivers to verify, that the ene.sys driver is both an unknown provider and an unknown version, just thought I’d note that since that was in red in my Blue Screen View after the first driver verify test.
 
May 8, 2021
14
0
10
0
enable windows driver verifier with all customized tests , just exlude Randomized low resources simulation. After few hours open cmd with admin rights and type this command:
verifier /querysettings
once done press CTRL + A and CTRL + C
then paste it here (CTRL + V) in thread
I want to make sure I’m doing this test correctly, after hitting finish it tells me to restart my computer for it to start working, upon restarting it tries to boot but I get a BSOD that says DRIVER VERIFIER DETECTED VIOLATION, and it tries to boot again. It does this about three times until my pc automatically stops and tries to diagnose the problem then it makes me use a restore point. How do I keep it running for several hours if that’s the case? Just keep resetting the PC?
 
May 8, 2021
14
0
10
0
I tried to open the ene.sys file in Microsoft Word to try and view the digital signature and make sure it was valid but I got an error saying “Sorry, we couldn’t find your file. Was it moved, renamed, or deleted? (C:\\Windows\System32\drivers\ene.sys)”
Am I looking too deep into ene.sys, or am I on the mark?
 
May 8, 2021
14
0
10
0
Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>verifier/querysettings

Verifier Flags: 0x00000000

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[ ] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

None

C:\WINDOWS\system32>



Been running about 3 hrs
 
May 8, 2021
14
0
10
0
Got a new thing on BSOD after running the verifier a few times, What failed: LGBusEnum.sys

I guess I don’t know much about running verifier if those results aren’t what you were looking for. I ran it and restarted my computer, it went through two extra long boot cycles that BSOD’d like it should. Only on this last run did it show the LGBusEnum.sys. I did as instructed with the command prompts ran as an administrator and that’s the result it gave me. As I run it one more time, and do verifier/querysettings it still shows nothing is flagged. Not sure where to go from here besides checking out LGBusEnum.sys
 
May 8, 2021
14
0
10
0
Microsoft Windows [Version 10.0.19042.928]
(c) Microsoft Corporation. All rights reserved.

C:\Users\mawel>verifier/querysettings

Verifier Flags: 0x03bfefbb

Standard Flags:

[X] 0x00000001 Special pool.
[X] 0x00000002 Force IRQL checking.
[X] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[X] 0x00000020 Deadlock detection.
[X] 0x00000080 DMA checking.
[X] 0x00000100 Security checks.
[X] 0x00000800 Miscellaneous checks.
[X] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[X] 0x00002000 Invariant MDL checking for stack.
[X] 0x00004000 Invariant MDL checking for driver.
[X] 0x00008000 Power framework delay fuzzing.
[X] 0x00010000 Port/miniport interface checking.
[X] 0x00040000 Systematic low resources simulation.
[X] 0x00080000 DDI compliance checking (additional).
[X] 0x00200000 NDIS/WIFI verification.
[X] 0x00800000 Kernel synchronization delay fuzzing.
[X] 0x01000000 VM switch verification.
[X] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Extensions:

wdm: rules.all
ndis: rules.default

Verified Drivers:

amdpsp.sys
symefasi64.sys
ccsetx64.sys
ironx64.sys
symevent64x86.sys
dokan1.sys
cimfs.sys
symnets.sys
srtspx64.sys
idsvia64.sys
hwinfo64a.sys
glckio2.sys
ene.sys
eectrl64.sys
bhdrvx64.sys
asio3.sys
asio2.sys
e2f68.sys
nvlddmkm.sys
amdpcidev.sys
amdgpio2.sys
amdgpio3.sys
nvvad64v.sys
nvmoduletracker.sys
nvvhci.sys
corsairvbusdriver.sys
amdtools64.sys
rtkvhd64.sys
nvhda64v.sys
lvbflt64.sys
lvrs64.sys
lvuvc64.sys
dump_dumpstorport.sys
dump_stornvme.sys
dump_dumpfve.sys
amdryzenmasterdriver.sys
corsairllaccess64.sys
cpuz150_x64.sys
msio64.sys
iomap64.sys
corsairvhiddriver.sys
ndis.sys
netadaptercx.sys
mbbcx.sys
wificx.sys
wdiwifi.sys

C:\Users\mawel>






Damn dude, I swear i did this multiple times and never had these options flagged. My bad bro im not trying to waste your time!
 

Colif

Win 10 Master
Moderator
run autoruns.sys to stop ene from running at startup, if you have any rgb software it can still start it - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

LGBusEnum.sys
is part of the logitech drivers, so remove LGS/G Hub or update them


WHEA - Windows Hardware Error Architecture. Its an error called by CPU but not necessarily caused by it
Can be any hardware, and sometimes device drivers.
can be caused by heat
can be caused by overclocking so remove any you have
can be caused by overclocking software so programs like MSI Afterburner, AMD Ryzen Master, Asus AI Suite, Intel extreme tuning utility - if you have any, remove it.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
WHEA errors seldom show their cause in dumps. but you can always hope. Most of the time its the same text and not very revealing.
 
May 8, 2021
14
0
10
0
run autoruns.sys to stop ene from running at startup, if you have any rgb software it can still start it - https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns


is part of the logitech drivers, so remove LGS/G Hub or update them


WHEA - Windows Hardware Error Architecture. Its an error called by CPU but not necessarily caused by it
Can be any hardware, and sometimes device drivers.
can be caused by heat
can be caused by overclocking so remove any you have
can be caused by overclocking software so programs like MSI Afterburner, AMD Ryzen Master, Asus AI Suite, Intel extreme tuning utility - if you have any, remove it.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
WHEA errors seldom show their cause in dumps. but you can always hope. Most of the time its the same text and not very revealing.
Yea, I removed G-Hub and ene.sys and my PC worked fine for two days, that's two more days than it usually does. It suddenly crashed today randomly watching a YouTube vid. Somehow ene.sys was back on my computer again. I'll be sure and get right on changing ene.sys in auto run, as for temps and overclocking, I reverted everything back to default values and my AIO has always done a great job of keeping my PC from getting hot, Got rid of all my Afterburner soft ware and overclocking stuff long ago too. I'll do the minidump thing to and I'll come back with any updates.
 

Colif

Win 10 Master
Moderator
ene is just rgb, it would be weird for it to crash PC while you run YouTube.

if you set PC up for minidumps I can have a look to see what drivers were running at time it crashed.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it
 
May 8, 2021
14
0
10
0
ene is just rgb, it would be weird for it to crash PC while you run YouTube.

if you set PC up for minidumps I can have a look to see what drivers were running at time it crashed.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it
After running Memtest for what seemed to be forever, all 8 passes came back with 0 errors, i guess im glad thats one less thing to be worried about!
 

Colif

Win 10 Master
Moderator
dump conversion - https://jsfiddle.net/beudn9aj/show

first 2 are the ene crashes, it appears its not running on Monday's crash. shame there are so many more drivers installed on the 3rd dump compared to previous 2.

Norton, I used to use it um... about 15 years ago. Have you updated it as I would have thought it have newer files than Feb 2020 by now. I assume you need to pay for another years subscription or something to get newer. You could remove and use Defender until we figure out cause.

you may have removed ene.sys but
Apr 22 2019GLCKIO2.sysASUS RGB driver
remains and might be part of problem if it expects ene to be there.
 

ASK THE COMMUNITY

TRENDING THREADS