PC Keeps Crashing

MaybeOnAHotdog

Reputable
Dec 14, 2015
13
0
4,510
Hey everyone

Sorry for the concise post but I have to be quick in case my system crashes.

Recently suffered some crashes, got to the point where I couldn't load to Windows or use start-up repair and reset my windows so I created a Windows installation on a USB drive, reformatted all of my drives and completely reinstalled Windows.

The crashes were IRQL_NOT_LESS_OR_EQUAL and DRIVER_OVERRAN_BUFFER_STACK along with lots of other BSOD stop codes.

I thought the issue was memory related, ran Windows Memory Diagnostics multiple times with no signs of fault, and so removed 3 of 4 sticks in case.

After reinstalling Windows I still face some crashes but believe it's a driver issue.

Ran sfc/scannow in elevated CMD:

C:\Windows\system32>sfc/scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.

Here is the CBS log:

HERE

System Specs are:
i7-4790K@stock
F3-1866C9Q-32GXM (running 1×8GB)
650W PSU
Asus Strix GTX980Ti
Asrock Motherboard
2×256GB SSDs for boot and storage

Where can I go from here?
 


I have a corsair keyboard so that makes sense, can you tell me how I can update it, do I just need a newer version of the WinRing0x64.sys file?

EDIT* I searched for the WinRing0x64.sys file and it shows up in my RealTemp installation folder. I use the app to check my CPU temps, is there multiple WinRing0x64 files?
 
I dont think its a keyboard, it's Corsair Link according to Google

I would also uninstall the program this file uses NTIOLib_X64.sys.

Some CPU Core unlocker program. Or Afterburner. This driver is 5 yrs old. It maybe part Of MSI Liveupdate

There's only 1 WinRing0x64.sys file in this dmp file

Well either update realtemp or uninstall it. Old drivers can crash windows, and this driver is a known cause of crashes





 


Okay the NTIOLib_X64.sys is part of MSI Supercharger I had installed which came with my motherboard driver CD, I uninstalled that.

The only WinRing0x64.sys file I can find is in the RealTemp installation folder but I remove that also.

Are those the only two files you can see which may be causing issues? What is helpful the CBS logs or the minidump files? Should I rerun the sfc/scannow command or is that useless here?

Thanks for the help so far
 
Dont use the windows memory program to test the ram it's too short and useless. use memtest

Avoid installing any programs (from the cd or site) , except the chipset drivers, and LAN and audio, if you want. And updated sata drivers.

If you want. Any programs that let you overclock, charge USB devices faster WILL crash your system sooner or later

Whatever is on the cd/dvd is probably out of date. Get updated drivers from the mobo maker's site
 


Okay should I install all RAM sticks, memtest, and then run a test using that?

Also I am up to date with Windows Update, Java, Graphics drivers, what else should I make sure is up to date, those three are the main software I've ever thought to update and I've never faced issues up untill now?
 
Here It'll be easier / better if you test a stick at a time. If it brings up errors in memtest, you'll know which stick is faulty

You may have to run each stick for say 20-30 passes to see if any errors come up

If you use Java, make sure the latest version is the only version thats installed. Uninstall ALL previous versions

If you've got the latest version, and any previous version of Java, the previous versions still have vulnerabilities
 


Tested 1st stick in DIMM1 after 18 mins elapsed time on pass 0 I have 19 errors so will place this stick at fault and test another.

 


I checked 1 more stick of RAM and after 1 pass there were no errors. I have to be premature because I will be RMAing the memory as a whole I just need the PC running to start the RMA process and even at this stage it is multitudes more stable than the faulty stick.

Hopefully the memory issue is the only fault causing the crashes but if not I will update the thread.

Thanks for all the help Paul NZ really saved me a lot of stress is there any way I can commend you