First, can you tell us what SSD you have?
This is important.
Your last crash is STOP 0x00000116: VIDEO_TDR_ERROR, again.
What NVidia graphics driver version are you using?
Update it if it's not the current driver, be sure to completely delete the current driver first, use Driver Sweeper.
If it is the latest driver, completely delete the current driver first, use Driver Sweeper, download and install the last known working driver.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800728b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004eec188, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+6ec188
fffff880`04eec188 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`061bcb88 fffff880`0412d000 : 00000000`00000116 fffffa80`0728b010 fffff880`04eec188 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`061bcb90 fffff880`04100867 : fffff880`04eec188 fffffa80`061f0000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`061bcbd0 fffff880`0412ce0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0728b010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`061bcc80 fffff880`04037ec1 : fffffa80`06263220 00000000`00000080 00000000`00000000 fffffa80`0620d230 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`061bcd00 fffff800`03135fee : 00000000`fffffc32 fffffa80`061e1060 fffffa80`039ed040 fffffa80`061e1060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`061bcd40 fffff800`02e8c5e6 : fffff880`0308f180 fffffa80`061e1060 fffff880`0309a040 fffff880`01227384 : nt!PspSystemThreadStartup+0x5a
fffff880`061bcd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+6ec188
fffff880`04eec188 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+6ec188
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c6d3530
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
Old, out of date drivers:
Code:
AtiPcie.sys Tue May 05 23:00:22 2009
Get the latest chipset driver from Asus.
Have you updated all the motherboard drivers from the Asus website?
Don't use the drivers on the CD/DVD, they are old versions.
Second to last crash was STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880043f3d29, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003103100
0000000000000028
CURRENT_IRQL: 2
FAULTING_IP:
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`043f3d29 f0834b2808 lock or dword ptr [rbx+28h],8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff880030b7990 -- (.trap 0xfffff880030b7990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800532e860
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043f3d29 rsp=fffff880030b7b20 rbp=fffff88005fa6160
r8=000000004f444648 r9=0000000000000000 r10=00000000ffffffff
r11=00000000ced7c162 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
usbohci!OHCI_PollAsyncEndpoint+0x37d:
fffff880`043f3d29 f0834b2808 lock or dword ptr [rbx+28h],8 ds:e000:00000000`00000028=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed01e9 to fffff80002ed0c40
STACK_TEXT:
fffff880`030b7848 fffff800`02ed01e9 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`030b7850 fffff800`02ecee60 : fffffa80`059d1b98 fffffa80`058f2960 fffffa80`051461a0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`030b7990 fffff880`043f3d29 : 00000000`00000000 fffffa80`058f2c30 00000000`00000000 fffff880`05fa6000 : nt!KiPageFault+0x260
fffff880`030b7b20 fffff880`043f5737 : fffffa80`058f2ba8 fffffa80`058f2960 00000000`00000000 fffffa80`051461a0 : usbohci!OHCI_PollAsyncEndpoint+0x37d
fffff880`030b7b80 fffff880`04464e8b : 00000000`00000002 fffffa80`058f2960 fffffa80`051461a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`030b7bb0 fffff880`044699d1 : 00000000`00000010 00000000`00000004 fffffa80`058f2960 fffffa80`05146050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`030b7be0 fffff880`04475077 : fffffa80`051461a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`030b7c40 fffff880`04465f89 : fffffa80`05146050 00000000`00000000 fffffa80`05146a02 fffffa80`05146a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`030b7ca0 fffff800`02edc0ac : fffff880`0308f180 fffffa80`05146a18 fffffa80`05146a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b7cd0 fffff800`02ec896a : fffff880`0308f180 fffff880`0309a040 00000000`00000000 fffff880`04465db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b7d80 00000000`00000000 : fffff880`030b8000 fffff880`030b2000 fffff880`030b7d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci!OHCI_PollAsyncEndpoint+37d
fffff880`043f3d29 f0834b2808 lock or dword ptr [rbx+28h],8
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbohci!OHCI_PollAsyncEndpoint+37d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0bff
FAILURE_BUCKET_ID: X64_0xD1_usbohci!OHCI_PollAsyncEndpoint+37d
BUCKET_ID: X64_0xD1_usbohci!OHCI_PollAsyncEndpoint+37d
Followup: MachineOwner
---------
The crash file blamed a Windows OHCI USB Miniport Driver.
This is likely the result of the problem and not the cause.
Third from last crash was STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA, This indicates that invalid system memory has been referenced.
This was the first since you re-installed Windows.
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6999c000030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002e7127b, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b9100
fffff6999c000030
FAULTING_IP:
nt!MiAgeWorkingSet+1d1
fffff800`02e7127b 488b19 mov rbx,qword ptr [rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
TRAP_FRAME: fffff880031eb7c0 -- (.trap 0xfffff880031eb7c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=fffff6999c000030
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e7127b rsp=fffff880031eb950 rbp=000000199c000033
r8=0000000000000001 r9=fffffa8003b7cec8 r10=0000000000000005
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiAgeWorkingSet+0x1d1:
fffff800`02e7127b 488b19 mov rbx,qword ptr [rcx] ds:fffff699`9c000030=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e313bf to fffff80002e86c40
STACK_TEXT:
fffff880`031eb658 fffff800`02e313bf : 00000000`00000050 fffff699`9c000030 00000000`00000000 fffff880`031eb7c0 : nt!KeBugCheckEx
fffff880`031eb660 fffff800`02e84d6e : 00000000`00000000 fffff699`9c000030 00000000`00001000 00000980`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`031eb7c0 fffff800`02e7127b : 00000003`00000000 b2f00000`1a385867 00000000`00000000 00000000`0000332f : nt!KiPageFault+0x16e
fffff880`031eb950 fffff800`02f02ac5 : fffffa80`03b7cec8 fffff880`00000001 00000000`00000001 fffff880`031ebbb0 : nt!MiAgeWorkingSet+0x1d1
fffff880`031ebb00 fffff800`02e71826 : 00000000`000005ed 00000000`00000000 fffffa80`00000000 00000000`00000006 : nt! ?? ::FNODOBFM::`string'+0x4d786
fffff880`031ebb80 fffff800`02e71cd3 : 00000000`00000008 fffff880`031ebc10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`031ebbd0 fffff800`03121fee : fffffa80`03abca60 00000000`00000080 fffffa80`039d3040 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`031ebd40 fffff800`02e785e6 : fffff880`02f63180 fffffa80`03abca60 fffff880`02f6e040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031ebd80 00000000`00000000 : fffff880`031ec000 fffff880`031e6000 fffff880`031eb700 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiAgeWorkingSet+1d1
fffff800`02e7127b 488b19 mov rbx,qword ptr [rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiAgeWorkingSet+1d1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1
BUCKET_ID: X64_0x50_nt!MiAgeWorkingSet+1d1
Followup: MachineOwner
---------
There is a known issue with the AMD IMC (Integrated Memory Controller) with RAM frequencies above 1333MHz.
I hope AMD will solve this soon.
Run memtest86+ again, I have seen it pass several times and then throw errors, that means the RAM settings need adjusted.
Run it with both RAM cards installed.
RAM - Test with Memtest86+
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your CPU temperatures?
You mentioned that you have, what are the CPU temps?
Use Core Temp, to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.