A lot of BSODs every day, especially playing League of Legends

Hello everyone. I've been getting various BSODs and crashes for a couple of weeks now and I'm desperate to find the cause, I don't know what to do. When it all started, I took my laptop to a guy who fixes computers and he told me that my RAM were broken, so he replaced 2GB of RAM (I have 4GB) and gave it back the day after. It fixed like ~90% of all those crashes but I still get various BSODs like MEMORY_MANAGEMENT, DRIVER_IQRL_NOT_LESS_OR_EQUAL or my computer just freezes in the middle of the game or just while surfing the internet and it's really annoying. What could be the problem? I attached the .zip file from that SF diagnostic tool but it seems that I don't have any minidumps for some reason. In the Event Viewer it says Unable to produce a minidump file from the full dump file. I hope you can help me, thanks.

Edit: Just got 3 BSODs in a row (in like 5 minutes), got only 2 minidumps, though. Please take a look.

Hello tevas.

Your BSOD dumps are not showing any probable finite cause.

Scan the system for possible virus infection with the following programs.

Code:

fffff880`02f22b80 fffff880`01072242 ataport!IdeCompleteScsiIrp+0x62
fffff880`02f22bb0 fffff880`0106ce32 ataport!IdeCommonCrbCompletion+0x5a
fffff880`02f22be0 fffff880`01075805 ataport!IdeTranslateCompletedRequest+0x236
fffff880`02f22d10 fffff880`01075104 ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02f22e40 fffff800`02cd62fc ataport!IdePortCompletionDpc+0x1a8

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.


If both the virus scans and the memtest comes to be free from errors, 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. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
____________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80068959a0, fffffa8006895a30, 4090005}

Probably caused by : rdyboost.sys ( rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmIoCtxWorkItemComplete+330 )

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

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa80068959a0, The pool entry we were looking for within the page.
Arg3: fffffa8006895a30, The next pool entry.
Arg4: 0000000004090005, (reserved)

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


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec6100
GetUlongFromAddress: unable to read from fffff80002ec61c0
 fffffa80068959a0 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002dc1cae to fffff80002c8ec00

STACK_TEXT:  
fffff880`03731b18 fffff800`02dc1cae : 00000000`00000019 00000000`00000020 fffffa80`068959a0 fffffa80`06895a30 : nt!KeBugCheckEx
fffff880`03731b20 fffff880`015bf7a4 : fffff880`015ce870 00000000`041508a3 fffff880`644d6d73 00000000`00000000 : nt!ExDeferredFreePool+0x12da
fffff880`03731bd0 fffff880`015be416 : fffffa80`060345e0 fffffa80`04a09010 fffffa80`068959d0 fffff880`015b862e : rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmIoCtxWorkItemComplete+0x330
fffff880`03731c60 fffff880`015b743e : fffffa80`04a09010 fffffa80`060345e0 00000000`00000080 fffffa80`04a09010 : rdyboost!SmWorkItemFree+0x10e
fffff880`03731ce0 fffff800`02f2cede : 00000000`00000000 fffff800`00000000 fffffa80`04a03410 fffffa80`03b67040 : rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0x176
fffff880`03731d40 fffff800`02c7f906 : fffff800`02e09e80 fffffa80`04a03410 fffffa80`049537b0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03731d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmIoCtxWorkItemComplete+330
fffff880`015bf7a4 eb0b            jmp     rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmIoCtxWorkItemComplete+0x33d (fffff880`015bf7b1)

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  rdyboost!SMKM_STORE_MGR<SMD_TRAITS>::SmIoCtxWorkItemComplete+330

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rdyboost

IMAGE_NAME:  rdyboost.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7982e

FAILURE_BUCKET_ID:  X64_0x19_20_rdyboost!SMKM_STORE_MGR_SMD_TRAITS_::SmIoCtxWorkItemComplete+330

BUCKET_ID:  X64_0x19_20_rdyboost!SMKM_STORE_MGR_SMD_TRAITS_::SmIoCtxWorkItemComplete+330

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

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f1000000001, 2, 1, fffff80002cd1e4e}

Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00001f1000000001, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cd1e4e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f03100
GetUlongFromAddress: unable to read from fffff80002f031c0
 00001f1000000001 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiSignalSynchronizationObject+4e
fffff800`02cd1e4e 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0

TRAP_FRAME:  fffff88002f226a0 -- (.trap 0xfffff88002f226a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00001f1000000001 rbx=0000000000000000 rcx=0000002078746341
rdx=fffff88008574908 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cd1e4e rsp=fffff88002f22830 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffffa8004a01c80
r11=fffffa800695f240 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt!KiSignalSynchronizationObject+0x4e:
fffff800`02cd1e4e 488908          mov     qword ptr [rax],rcx ds:00001f10`00000001=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccb1a9 to fffff80002ccbc00

STACK_TEXT:  
fffff880`02f22558 fffff800`02ccb1a9 : 00000000`0000000a 00001f10`00000001 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f22560 fffff800`02cc9e20 : fffffa80`0517a050 fffffa80`05aa6bd0 fffffa80`03b369c0 fffff880`08574910 : nt!KiBugCheckDispatch+0x69
fffff880`02f226a0 fffff800`02cd1e4e : 00000000`00000000 00000000`00000000 00000000`0000010a fffff800`02dcb3e0 : nt!KiPageFault+0x260
fffff880`02f22830 fffff800`02cd0246 : 00000000`00000002 00000000`00000030 00000000`00000000 fffffa80`04a8d000 : nt!KiSignalSynchronizationObject+0x4e
fffff880`02f22880 fffff880`01222004 : 00000000`00000000 00000000`00000000 fffffa80`06b66c00 fffffa80`06549168 : nt!KeSetEvent+0x106
fffff880`02f228f0 fffff800`02ccf5c1 : fffffa80`06b66f2b fffffa80`04a94040 fffffa80`06b66c60 fffffa80`06b66c60 : Ntfs!NtfsMasterIrpSyncCompletionRoutine+0x20
fffff880`02f22920 fffff880`019b3bce : 00000000`00010011 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02f22a10 fffff800`02ccf5c1 : 00000000`00000000 fffffa80`05e7bcd0 fffffa80`05e7bcd0 fffff880`03e1011b : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02f22a90 fffff880`0107241a : 00000000`00000010 00000000`00000001 fffffa80`052f1b80 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02f22b80 fffff880`01072242 : fffffa80`052f1b80 fffffa80`05d99000 fffffa80`05da6ea8 fffff880`04898b13 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02f22bb0 fffff880`0106ce32 : 00000000`00000002 00000000`00000000 fffff880`02f22c20 fffff880`048aaf77 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02f22be0 fffff880`01075805 : fffffa80`048e51a0 fffffa80`052f1b80 00000000`00000000 fffff880`048f53bf : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02f22d10 fffff880`01075104 : fffffa80`048e51a0 00000000`00000000 fffffa80`048e51a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02f22e40 fffff800`02cd62fc : fffff880`009ea180 fffffa80`00001d2a fffffa80`048e5050 fffffa80`048e5118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f22f00 fffff800`02cced05 : befff7ff`ffefffff fffffa80`06d54a50 00000000`00000000 fffff880`01074f5c : nt!KiRetireDpcList+0x1bc
fffff880`02f22fb0 fffff800`02cceb1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`037148e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CLASSPNP!TransferPktComplete+1ce
fffff880`019b3bce 837c243002      cmp     dword ptr [rsp+30h],2

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  CLASSPNP!TransferPktComplete+1ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME:  CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7929b

FAILURE_BUCKET_ID:  X64_0xA_CLASSPNP!TransferPktComplete+1ce

BUCKET_ID:  X64_0xA_CLASSPNP!TransferPktComplete+1ce

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

Yes it is not normal and not expected. Memtest should not do anything like that. It just tests the RAM modules, which should not make the computer hot.

Have you noticed any Red lines there within that time?

And what is the normal heat of the computer? Upload a snapshot Using Speccy.

• Download and install Speccy.
• File> Save snapshot.
• Save it on desktop.
• Zip it and upload it following following Screenshots and Files - Upload and Post in Seven Forums .

Have you tried Windows Defender Offline yet? Want o know the result of it, too.

A single Error line is enough to stop memtest.

The computer is tending to be hot. If possible, re-apply the thermal paste if you can.



But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

As you are having errors, you may follow the part- three: If you have errors of How to Test and Diagnose RAM Issues with Memtest86+
It will help you to discriminate between a failing RAM and a failing motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.