Windows Continuously Corrupting

Oct 2, 2018
8
0
10
Hello everyone,

I have an ongoing problem with my PC where windows keeps getting corrupted even when fresh installed. This started back in January and since then windows has been getting corrupted to the point where its unusable every month, and to push it back I would just reinstall windows as it will then be fine for another 3 weeks (ish) until it gets corrupted again.
when Windows gets corrupted the registry just becomes filled with errors and regular blue screens will start happening and I would usually leave this to happen until i would be forced to reinstall windows again.
i figured this issue was due to a piece of hardware being faulty so i ran Memtest 86 which reported back that there aren't any issues with the RAM and I also replaced the motherboard as i thought this would also be a likely component for windows being corrupt, again no luck.

Another issue that I guess is also related so the corrupted windows is that the major windows updates (cumulative updates) would always download and fail to install. this lead me to then installing windows on my HDD instead of SSD but these windows updates continued to fail which made me think that the corrupted windows wasn't due to my SSD.

My PC Specs
ASUS STRIX B250F GAMING Motherboard
Intel Core i7-7700K
EVGA GeForce GTX 1080
Corsair Vengeance 2x8GB

Any help is massively appreciated, Thanks.
 

Ralston18

Titan
Moderator
Which Windows 10 are you using and what version? Where did you get Windows 10?

Use Reliability History and Event Viewer to look for error codes and warnings.

There may be some common, continuous error code or warning as well as some detectable pattern in the error codes and warnings.

Something cumulative.

And watch the timing. May correspond with some routine attempts by a non-windows application to update, phone home, or backup.

Buggy and corrupts everything else.

You might also trying running Windows 10's built in troubleshooters. They may find and fix something - bit of a long shot perhaps but no harm in doing so.
 
Oct 2, 2018
8
0
10


Looking in event viewer the most common errors "399 Database Page Cache, 474 Database Page Cache" which both happen relatively frequently throughout the day. And "login recovery 454, 465 & 552" which occur when i first turn on the PC.
And i have tried the windows troubleshooter, but its definitely one of the hardware components being faulty. Thanks for the help though.

and i have Windows 10 Home Version 1803 OS build 17134.320

 

Ralston18

Titan
Moderator
@actxn.

Agree - sort of:

H/W vs S/W???

Did some googling and found all sorts of links.

The following link was interesting:

https://forums.lenovo.com/t5/ThinkPad-P-and-W-Series-Mobile/Windows-10-ESENT-error-474-I-get-a-few-of-these-a-second-It-says/td-p/3607141

and also the following link in "pursuit" of srudb.dat:

https://www.tenforums.com/general-support/78769-anyone-else-have-srudb-dat-error-all-time.html

Cannot attest to the relevancy per se nor if the poster's actions are truly applicable to your circumstances.

However, likely worth a look on your part and you may spot some other relevant clue or path to take.
 
Oct 2, 2018
8
0
10


initially i bought a copy of windows 2 years ago from CCl and installed it onto the same SSD i use today. earlier this year i bought new parts for a computer and built it using the same SSD i currently use. i just took the SSD out of my old PC and into my current one. since it got corrupted the first time i used the windows media creation tool and would reinstall windows through a USB, and i then did this every month when my windows would become corrupt.
 
Oct 2, 2018
8
0
10


tried another SSD today and the same issues persisted. A bunch of errors in event viewer and after logging in to my user it would just take me to a black screen. ill try running memory diagnostics again for the RAM and leave my PC on for while to see if they find anything.
 

If the same thing happened on the hdd you're doing something wrong. If you actually followed those directions properly you definitely wiped the drive and the issue replicated on another drive, hardware isn't at fault. So the only other two things it could be is the installation media or the person installing the installation media.