BSOD playing league of legends. I feel like I'm going insane.

Games tend to stress-test RAM very effectively :) - and they tend to use more RAM than normal applications.
It's always possible that this relates to RAM in the graphics area, rather than in the ordinary system RAM (VRAM is more difficult to test - someone else may be able to help there) - again, Games tend to stress-test it more effectively. :)

Some hardware tests to run. I know it's a repeat of memtest.

Graphics card:
https://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html#post866972


Hard drive(s):
Pick one for your HDD brand or use Seatools.
7 Free Hard Drive Testing Software Tools


RAM (memory):
This will require memtest on a bootable CD or USB stick.
RAM - Test with Memtest86+

Hi Britton,

Ran the furmark test for 8 mins. reached 90c and laptop auto-shutdown. No artifacts.

Did I pass?

Half, no artifacts is good but the shut down and 90C is a fail. You might want to check for dust in all vent holes/grilles and blow or vacuum them out.

Just a note. All test you do could give faulty results until the overheating problem is solved. In my opinion the over heating problem must be taken care of first.

Can you fill in your system specs?
Seems like a hardware issue, it's difficult to make suggestions if we don't know what you have.
You can use this program to find them: Speccy Free System information Utility
Then enter them in the 'My System Specs' drop box at the lower left of any of your posts.

Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.
We need these on every crash report you upload, these will tell us trends, what you have done that may be helping.

The graphics card test failure is likely the cause of your crashes, clean your cooling system.

Which hard drive do you have and what tests did you run?
Each HDD testing program has several tests, different tests may be needed, most people don't run the long tests but, they are usually the ones that are required.

Your laptop is overheating.
There are a lot of these.

Code:

Event[33624]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Power
  Date: 2012-11-06T16:26:39.215
  Event ID: 89
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
ACPI thermal zone ACPI\ThermalZone\TZ00 has been enumerated.             
_PSV = 0K             
_TC1 = 0             
_TC2 = 0             
_TSP = 0ms             
_AC0 = 344K             
_AC1 = 328K             
_AC2 = 0K             
_AC3 = 0K             
_AC4 = 0K             
_AC5 = 0K             
_AC6 = 0K             
_AC7 = 0K             
_AC8 = 0K             
_AC9 = 0K             
_CRT = 373K             
_HOT = 0K             
_PSL - see event data.

Event[33629]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 0 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33630]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 2 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33631]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 4 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33632]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 6 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33633]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 1 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33634]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 3 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33635]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.089
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 5 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

Event[33636]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Processor-Power
  Date: 2012-11-06T16:26:40.182
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: harrrryyyyyyy88
  Description: 
Processor 7 in group 0 exposes the following:

3 idle state(s)
8 performance state(s)
8 throttle state(s)

This can affect your laptop is several ways, in order to analyze the possible crash causes we need to start eliminating all issues on your system. This is the only way we can find the cause or multiple causes of your crashes.
Clean the fans and vents.
We see a lot of laptops with i7 CPUs and discrete graphics overheating.
For testing purposes disable Turbo mode in your BIOS, this may stop the crashes.


iTunes is causing problems, this is a common problem.
There are a lot of these as well, try uninstalling and re-install with updated version if available.

Code:

Event[43739]:
  Log Name: Application
  Source: Bonjour Service
  Date: 2012-11-17T11:38:50.000
  Event ID: 100
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: harrrryyyyyyy88
  Description: 
Task Scheduling Error: m->NextScheduledEvent 7020

Most of the crashes have a common theme of RAM issues, agree with the guys above, run memtest86+ for a full 7 passes. This will take a while, best to run overnight.
You can stop the test if you get any errors.
Some of your crashes:

Code:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!PoIdle+52a
----------------------------------------------------------------------------------------------------------------------
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes:  Device driver, memory, kernel
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
LAST_CONTROL_TRANSFER:  from fffff800034daae9 to fffff88007db8c61
FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!PoIdle+52a
----------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
Probably caused by : NETIO.SYS ( NETIO!WfpRefreshEntryLru+a5 ) - Network I/O Subsystem
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
FAILURE_BUCKET_ID:  X64_0xD1_NETIO!WfpRefreshEntryLru+a5
----------------------------------------------------------------------------------------------------------------------
STOP 0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED 
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800f403137
FAILURE_BUCKET_ID:  X64_0x3D_nt!KiInterruptHandler+29

Driver verifier crashes:

Code:

STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Usual causes:  Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,
This is a very common bugcheck.
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 ) - DirectX Graphics MMS
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
IMAGE_NAME:  dxgmms1.sys
FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
----------------------------------------------------------------------------------------------------------------------
STOP 0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 
Usual causes:  Device driver, ?Memory
Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+83 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  League of Lege
IMAGE_NAME:  memory_corruption
FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_nt!MiCheckSpecialPoolSlop+83

These are also RAM related, it possibly can be graphics card RAM.
Clean your cooling system before running this test or it will just crash.
Run the OCCT GPU test.
OCCT stability checking tool
Run the GPU:3D 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.