The Furmark temps and test look good.
Move the RAM card to slot #1.
If OCCT says it failed it should generate the graphs, if it had enough time before the blue screen.
Look for the OCCT graphs in C:\(your user name)\My Documents\OCCT folder.
Run OCCT Power Supply test, it uses LinPack and tests graphics, set it to test for 20 minutes before you start it.
Let's try this as you mentioned it passed Linpack before.
Is your PC Power and Cooling PSU model a Silencer or Silencer MK II?
If OCCT won't run and generate the graphs, you may want to replace, for testing, some of the hardware components, can you borrow some for testing?
I would recommend in this order, graphics card, PSU, and since you have a CPU available for testing, you might as well try it also.
You last 6 crashes:
Code:
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_IncIoRequestCount+c3 )
PROCESS_NAME: prime95.exe
IMAGE_NAME: USBPORT.SYS
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION - An exception happened while executing a system service routine.
Usual causes: System service, Device driver, graphics driver, ?memory
Probably caused by : nvlddmkm.sys ( nvlddmkm+1e2854 )
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME: OCCT.exe
IMAGE_NAME: nvlddmkm.sys
FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+1e2854
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkCddUnlock+118 )
PROCESS_NAME: csrss.exe
IMAGE_NAME: dxgkrnl.sys
FAILURE_BUCKET_ID: X64_0x1E_dxgkrnl!DxgkCddUnlock+118
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_iSetState+2a )
PROCESS_NAME: prime95.exe
IMAGE_NAME: USBPORT.SYS
FAILURE_BUCKET_ID: X64_0x1E_USBPORT!USBPORT_Xdpc_iSetState+2a
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8 )
PROCESS_NAME: prime95.exe
IMAGE_NAME: USBPORT.SYS
FAILURE_BUCKET_ID: X64_0x1E_USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+1c8
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bugcheck.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Xdpc_Worker+1d9 )
PROCESS_NAME: prime95.exe
IMAGE_NAME: USBPORT.SYS
FAILURE_BUCKET_ID: X64_0x1E_USBPORT!USBPORT_Xdpc_Worker+1d9
Most of these are caused by Prime95 and OCCT testing programs. Blaming the USBPORT may be due to a device connected to a USB port.
First crash: Do you have another keyboard and mouse you can use for testing?
The USBPORT is blamed, IO request.
If you have any other USB devices connected, remove them for testing, let me know what they are if you have any.
Second crash: blames the graphics driver.
Problem Devices;
ATK0110 ACPI UTILITY ACPI\ATK0110\1010110 39
AsIO ROOT\LEGACY_ASIO\0000 This device is not present, is not working properly, or does not have all its drivers installed.
AsUpIO ROOT\LEGACY_ASUPIO\0000 This device is not present, is not working properly, or does not have all its drivers installed.
AsIO - Asus PCProbe Utility
AsUpIO - ASUS hardware monitoring software related
Have you updated all the drivers from your motherboard support site?
Asus M5A88-m support
What BIOS version are you using?
The latest is M5A88-M BIOS 1401 - 2012.09.11, the description is 'Improve system stability'.
Update to this version if you don't have it now.
Have you ran a HDD test?
Download and run Seatools on your HDD.
How to use SeaTools for Windows
Short Drive Self Test and Long Drive Self Test.
To be sure none of the Win7 system files are corrupt run the System File Checker.
SFC /SCANNOW Command - System File Checker
Use Option Two, and #2 To Scan and Repair System Files
If it says it can't fix files with errors, re-boot and run it a minimum of three times with re-boots after each run.
It does the repairs when re-booting.