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

What water cooler are you using?

Have you been checking your temperatures?
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.
Make sure you have the latest version of CoreTemp downloaded and installed.


Can you download 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
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages are.

Did your run Windows memtest or memtst86+?
Better to use memtest86+, for minimum of 7 full passes.
RAM - Test with Memtest86+
You can try this later if required, post the above information first.

That's 111 crash dump files.
I'll take a look at the last few.

Code:

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_UsbIocDpc_Worker+143 )
SYMBOL_NAME:  USBPORT!USBPORT_Core_UsbIocDpc_Worker+143
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Core_UsbIocDpc_Worker+143
------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION 
Usual causes:  System service, Device driver, graphics driver, ?memory
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME:  Core Temp.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!HANDLELOCK::vLockHandle+51
-------------------------------------------------------------------------------------------------------------------------------------
Same as the first one, above.
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
SYMBOL_NAME:  USBPORT!USBPORT_Xdpc_Worker+1d9
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Xdpc_Worker+1d9
-------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
SYMBOL_NAME:  nt!KiPageFault+260
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
-------------------------------------------------------------------------------------------------------------------------------------
Same as the first one, above.
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessDpcCompletedPacket+3a5 )
PROCESS_NAME:  javaw.exe
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0x1E_dxgmms1!VidSchiProcessDpcCompletedPacket+3a5

With the information you gave, I agree this is a hardware issue.
Let's run some hardware tests, first you need to check the CPU temps.

What USB devices do you have connected?

Uninstall your current version of CoreTemp and install the new version from the link above.

Have you updated all the drivers from your motherboard support site?
Uninstall all the Asus utilities, these are known to cause crashes, your event logs are full of errors caused by these utilities.

CPU temps look good, AMD usually run cool.

Install the raid/ahci drivers, doesn't matter if you're using RAID or not, AHCI and RAID drivers are also for single hard drives.

Your first post says you have two RAM cards, CPUZ is showing you have only one.
Have all these crashes happened with only one RAM card?

Open CPUZ, run Prime95 for a couple of minutes, then post the CPU tab.
I want to see the CPU voltage under load, 1.475v is high for auto setting.

Once we confirm the Vcore, bump the DRAM voltage to 1.550v and the Cpu/NB Offset Voltage-1.200v.

Then run the OCCT stress test.
OCCT stability checking tool
Run the CPU:OCCT test for at least 30 minutes, be sure to monitor your CPU and GPU temps.
Set the time before you start.
When its done, pass or fail, it will make some graphs. Post these here as they are useful for analyses.

If you get any BSoDs upload them, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
Just include the last 10 dump files when you upload, this will make the file smaller.

Which RAM test did your run previously?
Windows memtest or memtest86+?

The raid/ahpi drivers should install by double clicking on them.
If they don't tell me the file extension.

Did memtest86+ crash when you ran the tests?

Did you adjust the DRAM voltage to 1.550v and the Cpu/NB Offset Voltage to 1.200v?
If not you can do it now.

The reason I got new RAM was that when I was testing my old RAM, memtest86+ found errors and crashed and I had to recovery bios. Memtest hasn't crashed with the new RAM though. Going to run Memtest86+ tonight to get more than the 5 passes.

And under the Driver folder in the .zip file raid and ahpi each have a .cat, .inf, and two .sys files. Theres also a "make disk folder", but that doesnt have a win7 folder.

Anyway, going to go change those voltages.

Edit: Well added .100v to the CPU/NB Offset Voltage and set the DRAM Voltage to 1.550v. Weird that they are modified differently.

Then should I run the OCCT Stress test?

Did you get the OCCT graphs after it failed?
Post them here if you have them.

Your last crashes.

Code:

STOP 0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Usual causes:  Device driver
PROCESS_NAME:  cpuocct64.exe - OCCT stability test program
FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874
-----------------------------------------------------------------------------
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.
PROCESS_NAME:  cpuocct64.exe - OCCT stability test program
FAILURE_BUCKET_ID:  X64_0x1E_USBPORT!USBPORT_Core_iCompleteDoneTransfer+9a

Turn off Driver verifier and run OCCT again.
Driver Verifier - Enable and Disable

From your System Event Logs.
These are Asus Utilities drivers and are causing problems.

Code:

Event[26259]:
  Log Name: System
  Source: Service Control Manager
  Date: 2012-09-19T12:54:43.272
  Event ID: 7026
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Veggies-PC
  Description: 
The following boot-start or system-start driver(s) failed to load: 
AsIO
AsUpIO

Event[26339]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2012-09-19T17:19:15.594
  Event ID: 219
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Veggies-PC
  Description: 
The driver \Driver\MTsensor failed to load for the device ACPI\ATK0110\1010110.

Uninstall all the Asus utilities, these are known to cause crashes, your event logs are full of errors caused by these utilities.
I have seen many crashes as a result from these utilities, all motherboard utilities do not have good drivers and cause serious problems and a lot of crashes.