BSOD loading League of Legends

Remove Eset Antivirus for testing purpose. Replace with MSE.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

 Clean boot

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\debug-ALI-PC-Wed_12_31_2014_235736_67\123114-26488-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03650000 PsLoadedModuleList = 0xfffff800`03893890
Debug session time: Thu Jan  1 09:18:07.301 2015 (UTC + 6:00)
System Uptime: 0 days 4:01:11.113
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800036df8c8, fffff880033474e8, fffff88003346d40}

Probably caused by : ntkrnlmp.exe ( nt!ExIsResourceAcquiredSharedLite+78 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800036df8c8, The address that the exception occurred at
Arg3: fffff880033474e8, Exception Record Address
Arg4: fffff88003346d40, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExIsResourceAcquiredSharedLite+78
fffff800`036df8c8 8b5008          mov     edx,dword ptr [rax+8]

EXCEPTION_RECORD:  fffff880033474e8 -- (.exr 0xfffff880033474e8)
ExceptionAddress: fffff800036df8c8 (nt!ExIsResourceAcquiredSharedLite+0x0000000000000078)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003346d40 -- (.cxr 0xfffff88003346d40)
rax=5b5e2d4d5524334a rbx=fffffa8008267050 rcx=fffffa8008267050
rdx=fffff8a012042140 rsi=fffffa8006737500 rdi=0000000000000000
rip=fffff800036df8c8 rsp=fffff88003347720 rbp=0000000000000000
 r8=fffff8a00f7bc7d0  r9=0000000000000000 r10=fffff88001279700
r11=fffffa80080781c0 r12=0000000000000000 r13=fffffa8008365720
r14=fffff88003347800 r15=0000000000000103
iopl=0         nv up di pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010002
nt!ExIsResourceAcquiredSharedLite+0x78:
fffff800`036df8c8 8b5008          mov     edx,dword ptr [rax+8] ds:002b:5b5e2d4d`55243352=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038fd100
GetUlongFromAddress: unable to read from fffff800038fd1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
nt!ExIsResourceAcquiredSharedLite+78
fffff800`036df8c8 8b5008          mov     edx,dword ptr [rax+8]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880012a8016 to fffff800036df8c8

STACK_TEXT:  
fffff880`03347720 fffff880`012a8016 : fffff8a0`12042010 fffff880`033478e0 fffff8a0`12042140 fffffa80`07849180 : nt!ExIsResourceAcquiredSharedLite+0x78
fffff880`03347750 fffff880`012bfbb7 : fffff880`033478e0 fffffa80`07849180 fffff880`03347800 00000000`00000000 : Ntfs!TxfCheckForFloaterDelete+0x56
fffff880`033477a0 fffff880`01040bcf : fffff880`03347901 fffffa80`0acc0650 fffff880`03348000 00000000`00000002 : Ntfs!NtfsFsdClose+0x677
fffff880`033478a0 fffff880`0103f6df : fffffa80`07657de0 fffffa80`0acc0650 fffffa80`07505f00 fffffa80`0acc0650 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`03347930 fffff800`039c33ce : fffffa80`08365720 fffffa80`075ff970 fffff8a0`14307b30 fffffa80`07657de0 : fltmgr!FltpDispatch+0xcf
fffff880`03347990 fffff800`036cee54 : 00000000`00000001 00000000`00000000 fffffa80`06770c90 00000000`00000000 : nt!IopDeleteFile+0x11e
fffff880`03347a20 fffff800`03965a01 : 00000000`00000000 00000000`0008c081 fffffa80`097072d0 fffffa80`069ddbc0 : nt!ObfDereferenceObject+0xd4
fffff880`03347a80 fffff800`03712311 : fffffa80`097072d8 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0xa1
fffff880`03347ac0 fffff800`037121d5 : 00000000`00000000 00000000`00000080 fffffa80`0671a9e0 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`03347b80 fffff800`0396173a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`03347c00 fffff800`036b68e6 : fffff880`02f65180 fffffa80`06737500 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03347c40 00000000`00000000 : fffff880`03348000 fffff880`03342000 fffff880`033476b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExIsResourceAcquiredSharedLite+78

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  53b9f073

STACK_COMMAND:  .cxr 0xfffff88003346d40 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!ExIsResourceAcquiredSharedLite+78

BUCKET_ID:  X64_0x7E_nt!ExIsResourceAcquiredSharedLite+78

Followup: MachineOwner
---------