BSoD while playing Leauge of Legends

[wanderinganon]

Hi everyone,

In the past hour I have experienced 3 BSoD while running a game client (League of Legends) and 1 more when trying to re-install it. Below is the problem details obtained from the error window when my computer restarted. Much help is appreciated. Thanks.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: FFFFFFFFFFFFFFF8
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF8000329437C
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052112-25116-01.dmp
C:\Users\Robert\AppData\Local\Temp\WER-77548-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Vir Gnarus]

Please provide us information as specified here. In addition, turn on Driver Verifier, and let the system crash one or more times with it on. Send us all resulting crashdumps. When setting up DV, do not select Force Pending I/O Requests, IRP Logging or Low Resource Sim. All other checks can be selected. Remember to restart after finishing setup.

 

[wanderinganon]

Sorry for the late reply, and I should have saw the sticky on the front page. Here the the necessary information.

 

[Vir Gnarus]

I think you may wanna look into updating all your drivers. All of them are quite old, with some - like your video drivers - going back to 2009. In addition, I see you're also using a very old version of Daemon Tools. DT is one of those items where you have to keep up to date very frequently as bugs can easily arise due to stuff like code rot. The sptd.sys module for it - which is not required for use of DT but is used to emulate security features like SecuROM - in itself is back from 2009. These all predate Windows 7 release.

Take some time to look through the HP website and start updating your drivers for everything one by one, as well as Daemon Tools. You may need to completely uninstall Daemon Tools and manually go to the /Windows/System32/Drivers/ and find and delete the sptd.sys file and then reinstall the latest version.

 

[wanderinganon]

Thank you Vir, I would like to ask how would I be able to find out the same information that you got to determine my problem so I know how to debug it later. Thanks.

 

[Vir Gnarus]

Sure. You'll first need access to a kernel debugger, most likely Debugging Tools for Windows (aka WinDBG). It's contained within the Windows WDK (google it). You can download the latest one for Windows 8, as the kit is independent of which version of Windows you have. Then when installed, you'll have to perform some initial setup, and then start doing some basic debugging like simply typing in !analyze -v (or just clicking the link it shows up) and following up with stuff like lmsm t to get a list of loaded modules (drivers) at time of crash and their timestamps (most Windows drivers have 2009 timestamp). You can get some basic tutorials on setting up Windbg and how to use it for some simple debugging here.

Understand that this all is just skimming things. You'll know just enough to get by with some crashes, but many others will still remain elusive. So if you're curious and interested in wanting to progress even further, I would like to think that the stuff I've written down available at my signature link "Crashdump Debugging Articles" is a good start. The BSOD Method & Tips thread is especially good for gathering resources on the topic. I also highly recommend the book Windows Internals, as that will give you both the foundation and the nitty gritty on how stuff goes on behind the scenes in Windows, which is what you'll need to know to learn what all that jargon is that you see printed in WinDBG and what's not working that's causing the crashes.

Anyways, if any of this resolved your problem, don't hesitate to mark the thread solved. If things still go bad after performing all the recommended updates, then I'll continue to work with you on this.

 

[wanderinganon]

Hey Vir

Updating my drivers didn't eliminate the problem, it feels like I have more problems than before. While starting up my computer crashes during the loading screen. This has happened about 8 times in the past hour or 2. I do have a backup computer so I am able to communicate with you there. Do you think it is a good idea to reformat my computer?

 

[Vir Gnarus]

Hi,

I figured as much, it was worth a shot though and needed doing. There was no conclusive analysis that could be performed with the dumps you gave previously.

If your system is all of sudden getting progressively worse and worse in stability, then it most likely is hardware we're dealing with. Unfortunately, analyzing crashdumps can only give us a general idea what hardware it is, so you'll need to use hardware tests to get a better chance of finding a culprit.

I noticed a couple more drivers you may wanna look into. You have SiS RAID drivers that predate Windows 7 (2008). You'll definitely want those taken care of. In addition, you'll want to update the HP Mobile Disk Protection software as that sucker is being blamed lately as cause and it's still fairly old (May 2011).

As for the hardware tests, run them in the following order:

RAM: Memtest86+ - 7+ passes
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)


All of these (excluding MemtestCL) are included in the UBCD if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the latest version of UBCD. Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better.

Last item to report, I noticed you haven't turned on Driver Verifier yet. That will greatly assist us in finding out if this is indeed a hardware or software issue we're tackling with. Remember, do not select the following checks: Force Pending I/O Requests, IRP Logging, and Low Resource Sim. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. Provide us any new crashdumps.