BSOD System_Service_Exception while playing League of Legends

[NuclearCherry]

As the title says, I was playing a game of League of Legends when suddenly, a while BSOD appeared. I've had several BSOD's in the past, but most have been simple updates and moving on with my life. The problem is that I just updated all of my drivers and whatnot a week or so ago, so everything is fresh and I'm not quite sure what is causing this issue, as I don't recall ever getting this error before (System_Service_Exception). Any help that can be given would be appreciated!

 

[koolkat77]

Welcome to the Forum.

Reduce items at start-up:

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

Perform a clean boot:

• How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Norton tends to cause BSOD/ please remove it for testing purpose.

Recommended antivirus software for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials Download | Free Spyware Protection
• Malwarebytes - The Free version
• Good & Free System Security

   Warning

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

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:

• How to Repair Windows 7 System Files with System File Checker

Check for heating issues using Speccy or HWmonitor

Upload a screen shot:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

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

Do this test overnight, before going to bed.

[FONT="Lucida Console"]Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Sun Jun 29 06:47:23.397 2014 (UTC + 6:00)
System Uptime: 1 days 4:56:40.942
BugCheck 3B, {c0000005, fffff800034ec079, fffff8800bd9ae10, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  League of Lege
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Sat Jun 28 00:58:35.416 2014 (UTC + 6:00)
System Uptime: 5 days 23:59:52.864
BugCheck A, {0, 2, 0, fffff800034fdb64}
Probably caused by : afd.sys ( afd+4c8b9 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  wmpnetwk.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Sat Jun 21 22:21:56.583 2014 (UTC + 6:00)
System Uptime: 0 days 21:29:27.047
BugCheck 1000007E, {ffffffffc0000005, fffff880056b816c, fffff8800bfd4448, fffff8800bfd3ca0}
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
Probably caused by : Netwsw00.sys ( Netwsw00+a016c )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Thu Jun 19 10:31:31.591 2014 (UTC + 6:00)
System Uptime: 1 days 9:52:41.152
BugCheck 1000007E, {ffffffffc0000005, fffff880056d016c, fffff8800cc81448, fffff8800cc80ca0}
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+a016c )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Wed Jun 18 00:37:31.498 2014 (UTC + 6:00)
System Uptime: 0 days 2:02:59.043
BugCheck 1E, {0, 0, 0, 0}
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+a016c )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  firefox.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Tue Jun 17 10:26:52.686 2014 (UTC + 6:00)
System Uptime: 1 days 3:15:25.231
BugCheck D1, {3f, 2, 0, fffff880058c6159}
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+a0159 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Debug session time: Mon Jun 16 06:05:42.259 2014 (UTC + 6:00)
System Uptime: 19 days 2:23:54.515
BugCheck 18, {0, fffffa8006f80aa7, 4, fff80000000fffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3f750 )
BUGCHECK_STR:  0x18
PROCESS_NAME:  NvBackend.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]