Random BSODs, and crashes consistently.

[GrayTheWolf]

I am not sure what the issue is, it is extremely frustrating when I can't figure out what the issue is. I have been getting crashed for a week or so now. It started while during a game, my screen would just go white and audio would get all distorted. I thought my issue was my graphics card drivers, which I rolled back to no avail. So, I reinstalled windows. I didn't even get the drivers installed before windows got a BSOD while doing 93 windows updates. After it rebooted and reverted all those changes, I now get random game crashes all the time, which has corrupted a few game saves. I refuse to play any more games until I have this figured out. I have also cleared CMOS and stuff. Here are my specs:

• i5 3570k overclocked to 4.4 GHz
• EVGA 660 Ti
• Gigabyte Z77X-UD5H-WB
• A few HDDs and an SSD

I think I will try to boot over to OS X or Ubuntu and see how my stability is there.
Then I guess I will try to remove my 660 Ti and see if the drivers were the problem.

 

[Arc]

Hello GrayTheWolf.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

One dump indicates WHEA_UNCORRECTABLE_ERROR (124) and the other one indicates PAGE_FAULT_IN_NONPAGED_AREA (50). So the first thing is to do here is to check for the stability of RAM modules. Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Are you overclocking?

CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
[COLOR=Red]CurrentSpeed: 3403[/COLOR]

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Let us know the results.
________________________________________________________________
BSOD ANALYSIS:

BugCheck 124, {0, fffffa800d939028, f2005ec0, 10005}

Probably caused by : GenuineIntel

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck 50, {fffffb2e4ef4a41a, 0, fffff80002ca0100, 7}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+540 )

Followup: MachineOwner
---------

 

[GrayTheWolf]

Thanks so much for the reply. I have 2 types of RAM in my system, 8 GB of Corsair Vengeance, and 8 GB of G-Skill. Hopefully RAM is the issue, that would be a quick fix. The first thing I will do is swap around RAM. I will try just the Corsair, and then just the G-Skill.

 

[Arc]

Oops!
Remove that RAM that you added later. Let the computer run with the original RAM, and see how it is running. Report us.

 

[GrayTheWolf]

Oops!
Remove that RAM that you added later. Let the computer run with the original RAM, and see how it is running. Report us.

I have had the same RAM setup for the 8 month life of the computer. But I have 2 different brands. They have the same specs so it should be fine. I had 2 bluescreens while using the Corsair Vengeance only, and I snagged a picture of the screen:

Running the G-Skill RipJaws only now, seeing what it does.

 

[GrayTheWolf]

Well, no bluescreen, but my game crashed with the G-Skill.

All overclocking has been removed.

 

[GrayTheWolf]

So, overclock removed, things seem stable now. Weird that I have been running a 4.4 GHz OC for almost a year. I guess it just became too much for the board to handle.

 

[Arc]

Now observe how it is running. If there are further BSODs with this no overclock state, let us know.