Can't figure out issue.

So just recently I've been having a problem with programs crashing. Either they stop working or just straight up close with no warning. This was Firefox and Skype as well as other things such as video games, even Minecraft. I gave up and decided to do a fresh reinstall of Windows, but some of the problems carried over. Skype is now stable, as well as Firefox (after turning off hardware acceleration for flash), and even Minecraft is now stable after going back to an older version of Nvida drivers. The majority of other things just refuse to stay open for more than a minute. This leads me to believe that it has to do with my hardware, but I'm absolutely lost as to what part it could be. I suspect my video card, of course, but I have mixed signals as a few things that would use it still run fine.

Other points:
Hard drive is completely new, and problems from the old hard drive are the same.
Nod32 detects no viruses.
Ran Intel CPU diagnostics which passed.
Ran memtestx86 which seemed to pass.

Specs:

Operating System
Windows 7 Ultimate (x64) Service Pack 1 (build 7601)
Install Language: English (United States)
System Locale: English (United States)
Installed: 6/12/2014 10:15:55 PM
Boot Mode: Legacy BIOS in UEFI (Secure Boot not supported)

Processor a
3.47 gigahertz Intel Core i5-3570K
256 kilobyte primary memory cache
1024 kilobyte secondary memory cache
6144 kilobyte tertiary memory cache
64-bit ready
Multi-core (4 total)
Not hyper-threaded

Main Circuit Board b
Board: ASUSTeK COMPUTER INC. P8Z77-V LK Rev X.0x
Serial Number: 131118942501637
Bus Clock: 102 megahertz
UEFI: American Megatrends Inc. 1402 03/21/2014

Memory Modules c,d
2000.40 Gigabytes Usable Hard Drive Capacity
1859.78 Gigabytes Hard Drive Free Space

msi DVD-RW DH24AS ATA Device [Optical drive]

ST2000DM001-1CH164 [Hard drive] (2000.40 GB) -- drive 0, s/n Z340X5DY, rev CC29, SMART Status: Healthy 8138 Megabytes Usable Installed Memory

Memory Modules c,d
Slot 'ChannelA-DIMM0' is Empty
Slot 'ChannelA-DIMM1' has 4096 MB
Slot 'ChannelB-DIMM0' is Empty
Slot 'ChannelB-DIMM1' has 4096 MB

Local Drive Volumes
c: (NTFS on drive 0) 2000.40 GB 1859.78 GB free



Any help would be greatly appreciated.

 

Have you tried to run System File Checker? sfc /scannow in an elevated command prompt.

 

Is the software & games that keep crashing actually compatible with Windows 7 64-bit?

Check your installed versions & check on the developer sites to confirm they are compatible with Windows 7 64-bit.

You can also have problems if the version of Net framework you have installed isn't high enough to support the program you are running, developer should advise a specific Net Framework needed to run the software or game.

 

This is on a fresh install of Windows, but I did it anyway just to be sure and it didn't find any violations.

Also, Firefox Plugin Container still sometimes crashes, but not as often.

Its almost every program that uses graphics it seems, but some programs like Firefox crash as well. This makes me think its hardware related as crashes are broad.

I made sure to install .NET 4.5 while going through all the Windows updates.

 

Hard to say if it's hardware or not, drivers perhaps given your clean install did change what was crashing. Has your desktop been crashing (blue screen) & causing reboots?

Do you recall if you installed any new programs/games or drivers just prior to this starting to happen? Just wondering if you installed the same drivers & programs (versions) again on the clean install which would allow the problem to persist.

Here's a couple other things you can look at that might direct you to finding an answer.

Open up & check the Windows "Event Viewer" which is found in Control Panel under Administrative Tools. Easier way to access event viewer, go to start + run & type cmd, in the command prompt that opens type "eventvwr".

Click on the items listed in the left panel & any events will be displayed in the right panel. Then just double click an event to open it up & see more details. You are looking for events with a red X error or yellow warning. Occassional errors & warnings are common with Windows machines.

You can also check the DirectX Diagnostic Tool, go to start + run & type "dxdiag".

 

Woah now. There are 408 Administrative Events listed here. Most of them are warnings, but there are plenty of errors in here as well. Most of the warnings are the same thing over and over again, however. I'll paste the most recent warning, an example of a game crashing, and a .NET error for you to look over.

Warning1:
A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 4

The details view of this entry contains further information.

Application Error:
Faulting application name: aion.bin, version: 4514.1127.512.8162, time stamp: 0x537018c3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000003
Faulting process id: 0x994
Faulting application start time: 0x01cf89d54dea29ae
Faulting application path: C:\Program Files (x86)\NCSOFT\Aion\bin64\aion.bin
Faulting module path: unknown
Report Id: 09b732b3-f5d3-11e3-82f6-ac220b5251a9

.NET Error:
Application: NexusClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IOException
Stack:
at System.IO.__Error.WinIOError(Int32, System.String)
at System.IO.FileStream.Init(System.String, System.IO.FileMode, System.IO.FileAccess, Int32, Boolean, System.IO.FileShare, Int32, System.IO.FileOptions, SECURITY_ATTRIBUTES, System.String, Boolean, Boolean, Boolean)
at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare, Int32, System.IO.FileOptions, System.String, Boolean)
at System.IO.FileStream..ctor(System.String, System.IO.FileMode, System.IO.FileAccess, System.IO.FileShare)
at System.IO.File.OpenWrite(System.String)
at Nexus.Client.Util.Downloader.FileWriter.WaitForData()
at Nexus.Client.Util.Threading.TrackedThread.RunThread()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

Warning1 is what shows up most often. Am I mistaken in thinking that my processor is failing?

 

Don't be to hasty on the Processor being at fault.

Have a look at this thread it applies to win8 which uses WHEA rather than Event Veiwer which is used in previous windows versions. But the information still encompasses win7-XP-Vista.

http://social.technet.microsoft.com...vent-id-18-microsoft-windows-whea-logger.aspx

Also check out this thread.

http://techreport.com/forums/viewtopic.php?f=29&t=92752

You can Google both the below phrases from your posted info for more links.

"A corrected hardware error has occurred"
"Corrected Machine Check"

Did you happen to get the "Event ID: number" (example Event ID: 10016). You can Google these event id numbers & find a great deal of information.

 

The Application Error is for the game Aion you have installed. Aion doesn't list win7 64-bit as being supported, from their website OS support = Windows XP (SP3) Windows XP x64 (SP2), Vista (SP2), Windows 7 (SP1)

Your .NET Error is the result of Nexus Mod Manager you have installed for games. It's an IO error that occurs when the application fails to read or write to a file. The application is open source & such can be buggy at times.

If there's an auto update feature for Nexus Mod Manager disabling it might help.

 

It seems to have stabilized after fiddling with some of the bios settings. I can only think that it was regulating the power incorrectly to something. Not sure what, the CPU power was unchanged.
Everything seems to have been fixed, though.

Thanks everyone for your time in helping me! If I could thank you twice I would!