Windows 7 : Crashes - would like help fixing errors in event viewer.

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.

sydney666

Distinguished
Nov 15, 2015
30
0
18,530
Hi,

I have been having a lot of lag and crashes with my pc. Sometimes my games will lag for a moment and then continue. Sometimes they lag so badly I need to reboot the pc to get everything smooth again. I also get delays when typing, but it seems to happen once every hour or so. I also have had the occasional blue screen crash. Sometimes it appears in the event viewer as a stop error and other times nothing shows up. Your help would be much appreciated.

I checked event viewer and I have a few recurring errors and I would like to fix the issue if someone would kindly do so. Obviously I am not sure what is causing

Event Id : 1003

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address 0x50E54942B492. The following error occurred: 0x79. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Event id : 10005

DCOM got error "1053" attempting to start the service AvastVBoxSvc with arguments "" in order to run the server:
{F319F1B8-7587-4146-AF9C-0D6D77819BF1}

Event id : 4614

The COM+ Event System detected an inconsistency in its internal state. The assertion "g_hMaxCommitEvent != 0" failed at line 43 of d:\w7rtm\com\complus\src\events\tier2\notify.cpp. This warning may be expected if the computer is low on resources. If the computer is not low on resources, and these warnings persist, it may indicate a problem in the COM+ Event System.

Event id : ESENT 399

Windows (3452) Windows: The database page read from the file "C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb" at offset 98304 (0x0000000000018000) (database page 2 (0x2)) for 32768 (0x00008000) bytes failed verification. Bit 253917 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.

Event id 1001 (Blue screen) X2

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffffa80095993a0, 0x000000000000ffff, 0x0000000000000000).

and

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa801005c028, 0x00000000be200000, 0x000000000005110a). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 100415-10576-01.


Additional Info;

Swapped out entire RAM (16 gig) with different ram : same errors and issue.

Did a hard drive scan in windows with no errors.

Checked windows files and all seemed fine.

Used CrystalDiskInfo and all ssd reported "good".

I think issue started when I tried to install windows update files and I got my first blue screen - but could be a co-incidence.
 


If you do decide to upgrade to win 10 it will install all new files so in theory it should fix the issue as long as it is an OS issue and not a driver.
 


This error seems to be that something tried to access part of the registry that it did not have permission to access. In your case the Windows readiness tool tried to access part of the registry that it did not have permission to access. As a suggestion try to run this program as administrator to help grant access to programs and files normally restricted.
 


Yes 2 mouse drivers can conflict with each other especially if they are very similar to each other. If you seem to have a hard time uninstalling both drivers you could try Driver Fusion to remove the drivers then reinstall the correct one. This program should be a last ditch effort to remove them as it will not remove registry entry's from them but will remove the drivers themselves.
 


Now we went over 1 other ESet error before and it was caused by the ESet scanning program you had. Is this error teh same as teh one before? Wait one sec, or is it Esent? with the "N"?

Also is your Ethernet driver up to date? <-- just curiosity on this one.
 
No this is ESENT, not ESET - a typo on my behalf.

ESET is the scanner, ESENT is the 399 error saying there might be a catstophic system failure.

This is the error

wuaueng.dll (1756) SUS20ClientDataStore: The database page read from the file "C:\Windows\SoftwareDistribution\DataStore\DataStore.edb" at offset 98304 (0x0000000000018000) (database page 2 (0x2)) for 32768 (0x00008000) bytes failed verification. Bit 221149 was corrupted and has been corrected. This problem is likely due to faulty hardware and may continue. Transient failures such as these can be a precursor to a catastrophic failure in the storage subsystem containing this file. Please contact your hardware vendor for further assistance diagnosing the problem.
 


Eh,

I haven't run this Windows readiness tool.....what program is running it and how can I find and fix the error.

I am a complete n00b.

It just seems that I am in search for the cause of two BSOD and I have 4 errors to help me find clues.

I have fixed 2 of the errors,

All that is left is this windows readiness tool which I doubt is the issue and then the major one ESENT 399.

I am guessing no one knows, because when I do a google search, null comes up and this is frustrating as hell.

Can't I just repair the stupid database thing? I mean the error is VERY specific....but I don't know what hardware causes those errors and I have done countless drive scans and everything is good.

The error is popping up about 10 times a day and when it does I seem to get lag in whatever I am doing for a short period. On two occasions this error was followed up by a BSOD. I know it says it's repairing its own error - of that corrupted bit or whatever - but how can I stop the same bit from screwing up again?


 
I agree that the issue is the ESent 399 error and not the readiness tool as you just ran the tool to tell if the PC is ready for Win 10. Yes you must have run the Windows Readiness tool because of your statement made "I tried to run the Windows Update Readiness Tool, but I can't tell if it worked. It is meant to take about 15 minutes to run, but it ran for less than a minute. this this is just for clarification so you and I are talking about the same program. :)

For the Esent error I will keep looking into it But the info you just posted leads back to the Windows Updater Module. THe drivers this should use, someone please correct me if I'm wrong are Drivers for the HDD, meaning south bridge for controlling the HDD , Ethernet driver for accessing the internet, north Bridge or Intel's version of it, DMI I think the initials are could be wrong though, RAM used for storing info between the CPU and the other components of the PC. I think that covers it, So please try uninstalling these drivers and reinstalling to root out a corrupt driver.

If changing out tall of t4he drivers for these Items do not help then It would be a software issue, code corruption, causing the issue and will need to either be replaced by SFC/Scannow or use of teh disk to reinstall the corrupted files from a known good source.

Curiosity: when you scanned the disk did you include the command of /f ? as in Chkdisk /f or even better Chkdisk /r? these added commands (/f) fix bad sectors or (/r) repair, bad name, move readable data to a known good sector of the HDD. This is to eliminate a Bad sector or bad Disk on the system.
https://technet.microsoft.com/en-us/magazine/dd637756.aspx
 
Geez I must have run it, I have run so many things and I hadn't slept for 24 hours that I must have gotten confused. I just checked back and yes I did run it but I only ran it once, or maybe twice but the error popped up quite a few times.

I didn't use a command for the chksdk, I used it from windows, my computer from C:/ and selected the option to repair automatically and then I had to reboot. It ran for about 25 minutes upon reboot. It didn't find any issues. Does it matter if I have SSD's or not? I have 2 SSD's in a raid 0 configuration.

Pretty confusing stuff.
 
AVG and TDSKiller picked up a virus on my system - 3 files were infected - all from my mouse drivers. Even though I uninstalled the drivers it said they were still active. The files have been permanently deleted and shredded by AVG.

However since the deletion I have been getting temporary blinking from my monitor - but it's as though the video card driver is screwing up. Not sure what is going on. Maybe I should have just cleaned those files than to delete them?

Since the deletion of the viruses and reboot I get, as stated that random blinking and this error followed by a lot of services failing, then restarting.

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7601.18933, time stamp: 0x55a6a1d1
Exception code: 0xc0000005
Fault offset: 0x00000000000170b2
Faulting process id: 0x6e4
Faulting application start time: 0x01d123b98e912e47
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: e74cc495-8fac-11e5-a5ac-50e54942b492


I am thinking of just re-installing windows when I go to windows 10.
 
System has been running fine now after the AVG virus scanner deleted the virus. The mouse drivers were to blame. Who would have thought it, I mean I got it directly from Steel Series. No wonder I had issues with my mouse and keyboard - with huge delays sometimes with typing or clicking in games.

I did another chkdsk /r after the last BSOD and it fixed a lot of stuff. It said there were inconsistencies with my hard disk drives and that I could just continue without a scan, but it was in my best interest to do the system recovery. It basically said that, but I just put it in my own words.

After the chkdsk /r as stated it found A LOT of issues, especially after I deleted the mouse drivers and the other 2 files - I think one was from the keyboard as well or a video driver I dunno. It's the three I posted previously.

Anyway system is running much faster, no more lag and I am a happy camper.

Thanks for the help.

SOLUTION FOR GOOGLING PURPOSES FOR ANYONE WITH BSOD DUE TO ESENT 399...

TLDR VERSION:

Just so everyone knows, if you get a ESENT (399) error, IT IS NOT ESET THE VIRUS SCANNER! It basically means there is a driver that is causing the issue with your windows system. I basically found the issue by running VERIFIER.exe from windows. Just make sure you follow the guides I think which were posted in this forum and make sure you do a system restore point. The verifier program will BSOD every time it encounters a virus or other issues with drivers and then you can use the program "who crashed" to read your system minidump file.

I then found the files in which were causing the BSOD and virus scanned them and then had them deleted by my virus scanning software.

PROBLEM SOLVED!



 
Status
Not open for further replies.

TRENDING THREADS