BSOD while watch, playing and testing-Driver IRQL and KMODE EXCEPTION

What were the CPU core temps while running OCCT?

The error message can be indicating system RAM or GPU RAM.

Is the DRAM voltage still set to 1.550v?
Change the Cpu/NB Offset Voltage to 1.300v.

Run OCCT again.

If it fails, test your graphics card.
Video Card - Stress Test with Furmark

Two of your last crashes blames or was attributed to OCCT.

Code:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED    (go to top of page)
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
IMAGE_NAME:  dxgkrnl.sys - DirectX Graphics Kernel
FAILURE_BUCKET_ID:  X64_0x1E_dxgkrnl!DxgkCddUnlock+118

Run the dxdiag tool.
DirectX Diagnostic Tool

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.

Let OCCT run for as long as you think you can, then stop it and post the graphs.
As long as it runs the test for several minutes.
Five minutes might give us some information.

Intel Burn test is based on LinPack.

I will continue editing post #25 with the last crash info, so check it a couple of times.

Good info.

Check Post #25 for the additional info and recommended tests to run.

Did you get Linpack stopped?

Hope the new graphics drivers will help, cleaning them up with Driver Sweeper should be a help.

The OCCT graphs look good, voltages seem to be stable.

If you can borrow a graphics card for testing it would help to eliminate the card and verify the PCIe slot on the motherboard.
A PSU can cause a lot of different issues, the OCCT graphs are showing it to be stable so no need for that, might have to come back to it later.
Don't change the CPU until the other testing is done, other components are more likely to be the cause, at this point.

Very relevant interesting news on the mouse, keep the PS2 mouse connected for the testing.
A bad mouse and keyboard can cause a lot of hard to find issues.
If issues continue, find another keyboard to test with.

Good info on the BIOS and drivers.

Run the other tests in post #25, and let me know the results.