BSOD queueing in LoL error 0x0000000a

[xsylx]

BSOD idling at League of Legends client

Recently ran into this error while being idle on the League of Legends client (not playing) with no other processes running. I was sure that there were no other process since I just restarted the computer and the first thing I opened was League of Legends. After using my phone for a minute I got the BSOD. Here is the dump file please help!

 

[xsylx]

As topic stated, got another one while queueing with no background processes.
Help please and thanks in advance!

 

[Arc]

For how long you are using the Razer mouse? Is the BSOD anyhow crashes with the mouse disconnected?

Your crash dumps are not showing any finite probable cause. In such a situation, it is better 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.

 

[xsylx]

Hi and thanks for the quick reply.
I've been using the Razer mouse for 3 to 4 months now, and the mouse is connected all along while the BSOD happened. I will try Driver Verfifier and let you know the results.
However, after manging to find and finish a game of LoL without errors and going afk to get some stuff (~20sec), i came back to another error, this time its bccode 124 :S

 

[xsylx]

Got this BSOD almost instantly with DV on and the first few seconds I opened LoL.

 

[Arc]

It is a stop ox124.

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 860c9024, b6200048, 2010a}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 860c9024, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6200048, High order 32-bits of the MCi_STATUS value.
Arg4: 0002010a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  LolClient.exe

CURRENT_IRQL:  1f

STACK_TEXT:  
807cd8ac 82a12fcd 00000124 00000000 860c9024 nt!KeBugCheckEx+0x1e
807cd8e8 82b0c7ec 860bf051 860c9024 82ab2770 hal!HalBugCheckSystem+0xab
807cd918 82a1327f 860ca550 82a20e40 c87afd27 nt!WheaReportHwError+0x230
807cda2c 82a13371 860ca550 860ca5a0 00000002 hal!HalpMcaReportError+0x3b
807cda50 82a1348d 00000000 860ca5a0 00000000 hal!HalpMceHandler+0x8b
807cda70 82a135d6 00000000 860ca550 807cdb90 hal!HalpMceHandlerWithRendezvous+0x4b
807cda80 82a095f5 00000000 48fbb508 fbdffcdf hal!HalpHandleMachineCheck+0x34
807cdb90 82a06261 00000000 807c8750 ffbfefff hal!HalpMcaExceptionHandler+0x87
807cdb90 00000000 00000000 807c8750 ffbfefff hal!HalpMcaExceptionHandlerWrapper+0x89


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

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

1: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM)2 Duo CPU     T9600  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 2793
1: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=954]
BiosMajorRelease = 15
BiosMinorRelease = 15
FirmwareMajorRelease = 14
FirmwareMinorRelease = 18
BiosVendor = Hewlett-Packard
BiosVersion = 68PHT Ver. F.0F
BiosReleaseDate = 12/02/2010
SystemManufacturer = Hewlett-Packard
SystemProductName = HP ProBook 4310s
SystemFamily = 103C_5336AN
SystemVersion = F.0F
SystemSKU = VK259PA#AB4
BaseBoardManufacturer = Hewlett-Packard
BaseBoardProduct = 7016
BaseBoardVersion = KBC Version 14.12

Follow the guide: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696