Please follow Arc's steps, if SFC finds corruptions it can't fix, more than 2 tries are useless.
Give these tests a run too.
Pick one for your HDD brand or use Seatools.
RAM (memory) test:
This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+
@Arc: I ran an SFC /Scannow check, all files were found okay. I've also uploaded the msinfo file you requested, and the DriverView logs you wanted to look at. In addition, I also attached two BSoD dump files for you, but I don't believe anything will be unexpected from those.
@Britton30: I ran scans using MemTest and Hitachi's drive fitness test. Both came clean.
Thanks for all the help!
The crash dumps are as usual. Noting is helpful there.
The spldr error is recovered.
Can you tell me what is this?
I have no prior experience about it. It claims to be a network driver, but it is not.Code:================================================== Driver Name : wStLibG64.sys Address : 00000000`00C2F000 End Address : 00000000`00C40000 Size : 0x00011000 Load Count : 1 Index : 61 File Type : Network Driver Description : StdLib Version : 1.4.3.1 Company : StdLib Product Name : StdLib Modified Date : 20-Feb-14 7:53:12 PM Created Date : 20-Feb-14 7:53:12 PM Filename : C:\Windows\system32\drivers\wStLibG64.sys File Attributes : A Service Name : wStLibG64 Service Display Name: wStLibG64 Digital Signature : ==================================================
As I have no earlier experience about it, I searched over google, and found it: Malware scan of wstlibg64.sys (StdLib) e440f0f64fb1579c22e5878039e191a8bc10a7e2 - herdProtect
Scan the system for possible virus infection with the following programs.
If still the BSODs continue to occur, IMHO it will be the best to go for a clean install.
If you have nothing installed during February in this line, then it is some unwanted thing, which should not be there.
Moreover, it says itself to be a network driver, where it is not, at all.
Overall, it is not anything good and anything wanted.
Not being a security expert, I cannot say the last word in this line. But, if the BSODs continue to occur, your best deal will be to perform a clean install only; because it is the best way to remove a malware, provided TDSSKiller scan found nothing.
Not a problem, I'll do a full re-format and re-install windows.
Thank you, both, Arc and Britton30 very much for your time!
Quote