BSOD, usually when playing League of Legends, 0x0000001e

Do you use any antivirus?

Please use a good stick of ram during your troubleshooting here.

Probably it's a damaged slot. Did you memtest with the good stick?

Do the following:

1. Click on User CP on the top right of this page
2. Click on Edit System Spec
3. Fill in your computer specs
   
   • System Info - See Your System Specs

All your dumps come with different bug checks.
Here's some info on they're usual causes:

Code:

STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION   
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000005, fffff80002ce2dcf, fffff88007c7e130, 0}
Probably caused by : hardware ( nt!KeWaitForSingleObject+1df )
.................................................................................
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION   
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c0000096, fffff80002cd2247, fffff880029f4de0, 0}
Probably caused by : ntkrnlmp.exe ( nt!SwapContext_PatchXSave+a7 )
.................................................................................
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION   
Usual causes:  System service, Device driver, graphics driver, ?memory
BugCheck 3B, {c000001d, fffff80002f7f68c, fffff88005ba0f80, 0}
Probably caused by : hardware ( nt!NtWaitForMultipleObjects+e3 )
.................................................................................
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Kernel mode driver, System Service, BIOS, Windows, 
Virus scanner, Backup tool, compatibility
BugCheck A, {35fe03010002, 2, 1, fffff80002c88800}
Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::NotificationDpc+168 )
.................................................................................
STOP 0x0000004E: PFN_LIST_CORRUPT   
Usual causes:  Device driver, ?memory
BugCheck 4E, {7, 4a1b0, 4a17b, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3727b )
.................................................................................
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL 
Usual causes:  Device driver
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
.................................................................................
BugCheck 50, {fffffffffffffff8, 0, fffff88001a6bad0, 0}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsReleaseFcb+190 )
.................................................................................
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED    
Usual causes:  Device driver, hardware, System service, compatibility, 
Remote control programs, memory, BIOS
BugCheck 1E, {ffffffffc0000005, fffff80002cd4ec5, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

RECOMMENDATIONS

Scan the system for viruses:

Run these tools and delete anything they may find:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Make a full scan with Malware bytes and Microsoft security essentials:

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• Good and Free system security combination.

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

Upload a screenshot of your hard disk using crystal disk info and Summary tab using Speccy:

• Speccy - System Information - Free Download
• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

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

Check for a BIOS update:

Code:

BIOS Version/Date	Insyde F.18, 7/6/2010

Update the graphics card drivers:

Code:

Driver	c:\windows\system32\drivers\atikmdag.sys (8.1.1.921, 5.76 MB (6,036,480 bytes), 7/2/2009 2:51 PM)

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to; ATI. (Reboot the system). Delete remnants of its drivers/older drivers using Driver Fusion/Sweeper.

Download link:

• AMD Driver Autodetect

Check this tutorial, it might help you:

• USB Driver - General Fix for Problems

Let us know the results.

sorry really busy week,
took me a while but i finished the scans, everything is clean no viruses, no errors, no corrupted files/sectors.
and my bios is up to date as well.

Here are the screenshots you asked for, and i will be doing the graphic drivers after posting this.

Update:
Updated graphic drivers, and i didn't have a anti virus before but im running Windows Defender now.
I just got a crash but i dont think i got a dump :S it was "something along the lines of "IRQL driver" but the BSOD seem to be all over the place :/

Upload latest reports please.

None of them are memory management here. (the dumps of 6th) anyway, time to test RAM.

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.

Errors are sometimes found after 8 passes.
Do this test overnight, before going to bed.