So I ran MemTest86 and it finished with 0 errors after 4 passes. I also ran sfc /scannow and this is the message I got:
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
EDIT: here's a link to the log itself; I can't seem to make much sense out of it :CBS Log
As SFC scan indicates it found corrupt files and cannot fix some of them then I recommend a fresh install of the OS.
I have encountered situations of corrupted win32 files before and you end up chasing your tale trying to identify the culprit.
If SFC is corrupted, there are easier fixes since op is on 1903
right click start button
choose powershell (admin)
copy/paste this command into the window: Repair-WindowsImage -Online -RestoreHealth
and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC
If you get an error running that asking for source,
you have 2 options
run the source command =
Download a copy of the win 10 iso from Here - create ISO by telling it you want to make DVD - and then mount that ISO in file explorer (see Here) and then copy paste the below command into command prompt (admin)
So, I ended up just doing a fresh install of Windows. and it works now . Though to not take any risks, I kept the nvidia drivers from windows. Stayed away from suspicious drivers previously mentioned. I've been running the PC for a few hours now, trying out gaming, videos, stressing the system etc and all seems to be running like butter. Not a single crash or error. Thanks so much for your help guys.
Well, here's another laugh. I just got a new BSOD ! " Kernal Security Check Failure "
Linking the dump file. DUMP
I am completely lost for words right now ...
Also got another nvd3dum.dll crash in event viewer.
gardenman seems to have ran it through the debugger. Any thoughts ? The crashes seem to happen when I'm playing CS:GO. Sometimes it crashes to desktop with nvd3dum.dll causing it. Sometimes it just BSODs
The drivers I am using ARE the old ones. Didn't use Nvidia at all. Though this might make things interesting :
I remembered that I had updated the BIOS to the latest version (2704) so, out of desperation I decided to roll back a version (2605). So far I haven't had any BSODs or crashes. So to test this further I have put my self in a game online, and left myself in Spectate mode, and now will leave it for a while. After a few hours I'll come back and hopefully I'll still be in-game. Crossing my fingers for this one. Will post update.
Update: So I've been running my system for the past couple of days on this and I have no more BSOD's (fiewww) but, I do have frequent crashes of my CS:GO with the error "Bad_Module_Info" in the Event Viewer. It's a constant one, never a different error, it's been that same one for the past 5-6 games. Any ideas ?
UPDATE: When running a full blend test on Prime95 I get workers 3 & 4 stop running almost immediately after I start the test. But when I run a small fft L1/L2/L3 the stress test runs fine with no errors. It seems that there is a problem when adding the ram and memory controller to the stress test. A friend of mine is bringing his DDR4 RAM later this afternoon and I'll be doing a stress test with his. Will post the results.
So I went into the BIOS and put the Vcore voltage to a fixed 1.4v. Running Prime95 right now and all seems perfectly stable. Voltage stays between 1.406v and 1.438v. No errors on any workers so far. Can we assume that the error we were getting had something to do with voltage ? If so it seems weird that setting a manual one, instead of Auto would have this effect ? Will try testing gaming and see if there are any crashes