Random desktop BSODs (Page faults) in Windows 7

Shaq

Contributor
Joined
Nov 20, 2018
Posts
41
I've run SFC,SFCfix and SURT and attached the logs. There are a few corruptions that they can't fix. The mshta.exe file that SFCfix is having troubles with checks out as the same Sha-1 as the system32 version.
 

Attachments

Could you help me with the SFC problems or do I need to create another thread in the update forum for those?
 
You need to create a new thread in the Windows Update section as you've done previously. Are you having BSOD issues?
 
They are pretty rare. Every couple of days or after a few reboots in one day I'll have one. It is always when the PC isn't really doing anything like on the desktop, never under a significant load. I figured I would try to get rid of the SFC problems while I do some troubleshooting and cleaning of TSR programs and see if that works and if not I'll continue this thread.
 
They are pretty rare. Every couple of days or after a few reboots in one day I'll have one.
I wouldn't say having a crash every couple of days is rare. Please provide the dump file as suggested so we can investigate the issue.
 
The EneTechIo driver appears to be causing an invalid page fault, I'm not sure what program or device it is associated to, but from what I can find it's developed by Ene Technology Inc. Looks like they produce wireless chargers?

Rich (BB code):
13: kd> lmvm ene
Browse full module list
start             end                 module name
fffff880`10bb4000 fffff880`10bbc000   ene      T (no symbols)           
    Loaded symbol image file: ene.sys
    Image path: ene.sys
    Image name: ene.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri May  8 07:07:19 2020 (5EB4F717)
    CheckSum:         0000E8E9
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
 
Should there be a process in memory linked to it? I don't see anything right now. I haven't installed a wireless charger. Maybe I will disable some of the bluetooth services since I don't have it on this PC. I bought a bluetooth USB dongle that I never could get to work, although that was a month or so before I started getting the BSOD.
 
It looks like ene.sys was installed with my new RGB RAM so I don't think that is the reason. WHen I first started getting the Page fault I tested my RAM and got occasional errors so I bought a new set of RAM but it didn't fix it. Ene.sys was installed after I was getting them.
 
ene.sys is the driver causing the problem; it must have been installed along with some device if not a program.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top