BSOD - Seems to only happen during a League of Legends game

Till now we are getting only one evidence of failure, that is Intel(R) 82579V Gigabit Network Connection.

Code:

fffff880`035222d8  fffff880`05ea7ff6Unable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
 e1c62x64+0x21ff6

Description here: Driver Reference Table - e1c62x64.sys

Try to find updates from https://downloadcenter.intel.com/default.aspx

Let us know the results.
______________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8800352AFB0

EXCEPTION_RECORD:  fffff880035238b8 -- (.exr 0xfffff880035238b8)
ExceptionAddress: fffff800030cd5bf (nt!KiTimerExpiration+0x000000000000019f)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88003523960 -- (.trap 0xfffff88003523960)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000d041571b2 rbx=0000000000000000 rcx=00000000000577ce
rdx=00000000000000ce rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030cd5bf rsp=fffff88003523af0 rbp=00000000000577ce
 r8=fffffa800c848490  r9=00000000000000c1 r10=00000000000000ce
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerExpiration+0x19f:
fffff800`030cd5bf 0f85e4feffff    jne     nt!KiTimerExpiration+0x89 (fffff800`030cd4a9) [br=0]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030ba57e to fffff800030c2b50

STACK_TEXT:  
fffff880`03522998 fffff800`030ba57e : fffffa80`0c841b30 fffff880`04901199 fffff880`03523110 fffff800`030eda90 : nt!KeBugCheck
fffff880`035229a0 fffff800`030ed75d : fffff800`032d1374 fffff800`0320e260 fffff800`0304d000 fffff880`035238b8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`035229d0 fffff800`030ec535 : fffff800`03212038 fffff880`03522a48 fffff880`035238b8 fffff800`0304d000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03522a00 fffff800`030fd4e1 : fffff880`035238b8 fffff880`03523110 fffff880`00000000 fffff880`034fb180 : nt!RtlDispatchException+0x415
fffff880`035230e0 fffff800`030c2202 : fffff880`035238b8 0000000d`04155700 fffff880`03523960 fffff880`034fef48 : nt!KiDispatchException+0x135
fffff880`03523780 fffff800`030c0b0a : fffff880`034fb180 fffff880`034fe380 fffff880`034fb180 fffff800`030e1ae4 : nt!KiExceptionDispatch+0xc2
fffff880`03523960 fffff800`030cd5bf : 00000000`000196c2 00000000`0001e41f 00000000`00000000 00000000`00006bef : nt!KiGeneralProtectionFault+0x10a
fffff880`03523af0 fffff800`030cd3c7 : 00000004`528240c1 00000004`000577ce 00000004`528240ad 00000000`000000ce : nt!KiTimerExpiration+0x19f
fffff880`03523b90 fffff800`030ba88a : fffff880`034fb180 fffff880`035060c0 00000000`00000000 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff880`03523c40 00000000`00000000 : fffff880`03524000 fffff880`0351e000 fffff880`03523c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`030ba57e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

You are welcome :)
If there is any further issue, let us know.

It is still the network driver that is failing. So it may be something that is causing a pressure on it. I would suggest you to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.