Bsod crashing pc randomly few times every day

Oct 2, 2017
10
0
510
0
Help me realize what's the problem, I think it's HDD but I don't want to buy new SDD only to turns out I still have same problem

When I boot my pc it either gets stuck at asus board screen or it leads me to bios where it's never ending cycle. If I press button to turn off pc and start it again it somehow fixes the loop and gets me to my desktop like everything is fine.

During the work time sometimes my pc would freeze, freeze is happening after some strange noise from my pc tower. I'll describe this like- it wants to boot something but it fails l quickly followed up with bsod with error g unexpected store exception or critical process died or kernel something...
Is this HDD as I suppose coz it can be part of booting and since it's really old or is it a Smith else.

My guess is its HDD which is pretty old and now it has probably bad sectors which when pc tries to read it fails.

I did firewall full scan 0 errors, sfc 0errors and chdsk also everything fine, but when I right clicked partition and went in option to check disk drive it found few errors and supposedly it should be repaired but bsod still happen
 
Oct 2, 2017
10
0
510
0


few errors and warnings

error1: Windows cannot access the file C:\Windows\System32\sysmain.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\sysmain.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C000000E
Disk type: 3


error2:Faulting application name: svchost.exe_SysMain, version: 10.0.16299.15, time stamp: 0x9c786b9a
Faulting module name: ntdll.dll, version: 10.0.16299.64, time stamp: 0x493793ea
Exception code: 0xc0000006
Fault offset: 0x000000000001ef8d
Faulting process id: 0xd18
Faulting application start time: 0x01d36df3c6189072
Faulting application path: C:\WINDOWS\system32\svchost.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8e39ef5a-f7c3-49cb-b49e-246dd87a5436
Faulting package full name:
Faulting package-relative application ID:

error3:License Activation (slui.exe) failed with the following error code:
hr=0xC004F074
Command-line arguments:
RuleId=502ff3ba-669a-4674-bbb1-601f34a3b968;Action=AutoActivateSilent;AppId=55c92734-d682-4d71-983e-d6ec3f16059f;SkuId=2de67392-b7a7-462a-b1ca-108dd189f588;NotificationInterval=1440;Trigger=UserLogon;SessionId=1

warning1: Certificate for local system with Thumbprint 6c b8 05 d4 64 92 b2 eb c4 a9 d1 40 de e2 1c e5 f2 9a aa 6f is about to expire or already expired.

error4:Log Name: Application
Source: ESENT
Date: 12/5/2017 4:35:23 PM
Event ID: 552
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-3CDVHL3
Description:
wuaueng.dll (3824,R,0) SUS20ClientDataStore: The log file at "C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log" is corrupt with reason 'ValidSegmentAfterEmpty'. Last valid segment was 241, current segment is 244. The expected checksum was 8510406795903462392 (0x761b09e40be56bf8) and the actual checksum was 8510406795903462392 (0x761b09e40be56bf8). The read completed with error-code 0 (0x00000000). If this condition persists then please restore the logfile from a previous backup.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" ></Provider>
<EventID Qualifiers="0">552</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-12-05T15:35:23.957907500Z" ></TimeCreated>
<EventRecordID>7816</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-3CDVHL3</Computer>
<Security ></Security>
</System>
<EventData>
<Data>wuaueng.dll</Data>
<Data>3824,R,0</Data>
<Data>SUS20ClientDataStore: </Data>
<Data>C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log</Data>
<Data>ValidSegmentAfterEmpty</Data>
<Data>241</Data>
<Data>244</Data>
<Data>8510406795903462392 (0x761b09e40be56bf8)</Data>
<Data>8510406795903462392 (0x761b09e40be56bf8)</Data>
<Data>0 (0x00000000)</Data>
</EventData>
</Event>

error5:wuaueng.dll (3824,R,0) SUS20ClientDataStore: Corruption was detected during soft recovery in logfile C:\WINDOWS\SoftwareDistribution\DataStore\Logs\edb.log. The failing checksum record is located at position . Data not matching the log-file fill pattern first appeared in sector isec 244 reason ValidSegmentAfterEmpty. This logfile has been damaged and is unusable.
 
Oct 2, 2017
10
0
510
0


i didnt should i ? does that mean i should open my pc and just swap sata cables, coz i use 1 sata cable for 1 hard drive and 2nd sata cable for 2nd hard drive or there is no need?
 
Sometimes a faulty SATA data cable will make the system drive appear to be faulty. Testing with a different SATA data cable is to determine whether or not the data cable may be the cause. It's much cheaper to replace a faulty SATA data cable than to replace an HDD or SSD.
 
Oct 2, 2017
10
0
510
0
OK problem still seems to be occurring tho there is one more thing that may show that it's not hardware issue but system issue.

I recently got new pc, I didn't reinstall OS I just installed new components on old OS and installed drivers for new pc. Can this be problem with software and maybe hardware isn't faulty at all? Recently=3 months

Also u get this error when I try to boot pc sometimes https://imgur.com/gallery/ehfRc
 


That was important info you left out of your original post. A fresh install of the OS is always recommended especially if the motherboard has been replaced.

Try performing a fresh install of the OS and see if that resolves any of the problems.
 

Similar threads


TRENDING THREADS