Good troubleshooting so far.
Have you check the SSD firmware for an update?
Those RAM settings in BIOS should be OK, we may need to check them again later.
When you run memtest86+ you need to run for 7 full passes, best to run overnight.
Leave both RAM cards installed for this test.
For reference:
RAM - Test with Memtest86+
You've had 8 crashes since your last upload.
Code:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: X64_0xA_nt!KiInsertQueue+1d0
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
IMAGE_NAME: dxgmms1.sys
FAILURE_BUCKET_ID: X64_0xD1_dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
PROCESS_NAME: TESV.exe
IMAGE_NAME: dxgmms1.sys
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VidMmCloseAllocation+35
--------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL
Usual causes: Device driver, ?Memory
PROCESS_NAME: msiexec.exe
FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+1ed
The second and third crashes listed above are DirectX related.
Do the DirectX fix linked in koolkat77's post.
The forth crash is blaming Microsoft's Windows Installer program, likely not the cause.
Could be a program you installed causing the crash, did you get a crash while installing something?
System Event Logs:
There are a lot of these.
Code:
Event[8568]:
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 2012-06-06T22:36:43.587
Event ID: 26
Task: N/A
Level: Information
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: Gaberalt-PC
Description:
Processor 0 in group 0 exposes the following:
3 idle state(s)
0 performance state(s)
8 throttle state(s)
From the App Event Log, confirming
Event[29364]:
Log Name: Application
Source: Microsoft-Windows-WMI
Date: 2012-09-05T17:20:31.000
Event ID: 10
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Gaberalt-PC
Description:
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
This is indicating your CPU is overheating.
What CPU cooler do you have?
Use
Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Code:
Event[10422]:
Log Name: System
Source: Service Control Manager
Date: 2012-06-07T13:41:29.485
Event ID: 7030
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Gaberalt-PC
Description:
The LogMeIn Hamachi Tunneling Engine service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.
Event[10423]:
Log Name: System
Source: Service Control Manager
Date: 2012-06-07T13:41:29.535
Event ID: 7009
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Gaberalt-PC
Description:
A timeout was reached (30000 milliseconds) while waiting for the LogMeIn Hamachi Tunneling Engine service to connect.
Event[10424]:
Log Name: System
Source: Service Control Manager
Date: 2012-06-07T13:41:29.535
Event ID: 7000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Gaberalt-PC
Description:
The LogMeIn Hamachi Tunneling Engine service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
This driver is out of date.
Code:
hamachi.sys Thu Feb 19 2009 - LogMeIn Hamachi Virtual network interface driver
This program is known to cause problems with Windows 7.
Update the program or uninstall for testing.
Code:
Event[14459]:
Log Name: System
Source: Disk
Date: 2012-06-17T19:55:50.587
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Gaberalt-PC
Description:
The driver detected a controller error on \Device\Harddisk2\DR2.
Which port is your SSD connected to?
Your System Event Logs stop on Date: 2012-08-14.
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwite events as needed (oldest events first)'
Click OK.
If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.
When you install a new graphics driver you should always uninstall the driver and run Driver Sweeper to get rid of the old driver before you install the new driver.
Let us know if you have any questions.