BSOD 0x0000007A when LoL client updates

[Skoll21]

Hello.

When my League of Legends client updates it starts out fine but when it's nearing the end, the download/install speed starts slowing down a lot until it reaches almost 0 kbps and after a few seconds my PC starts locking up and then I get a BSOD (kernel_data_inpage_error 0x0000007A).

I get stuck on the BSOD screen because Windows doesn't detect the SSD anymore, so I have no dump files. Btw, I get no message that the dump couldn't be created or anything, it just stays there and I have to manually shut off the PC. And I do have my PC set to automatically restart when I get a BSOD. So after the BSOD I need to leave my PC turned off for about a minute or two, otherwise the SSD won't be detected. It only happens when the LoL client updates but it's been happening everytime (never while playing or doing anything else).

My OCZ Vertex 4 has firmware 1.5, my BIOS firmware is up to date and so are my GPU drivers (have the latest Catalyst beta version). I've ran chkdsk through the "Error-checking" option on the Tool tab of the drive properties, and I checked the "Scan for and attempt the recovery of bad sectors". Got no errors, the only thing was some free space that was marked as allocated when it shouldn't have been (or something like that).

After this I tried reinstalling LoL and Adobe AIR (the client needs it) but when I'm updating the game (necessary to complete the install) I get the BSOD again, so now I can't even finish installing the game on my SSD. I just gave up and installed the game on my storage HDD. (Not sure if it's important or not, but the updates on the HDD also slowed down to 0 kpbs but it just completed after a while and I had no issues.)

I can't really remember if the BSOD started after I updated something or not but a few months ago it used to be fine. Although I have no dump files I have a picture of the BSOD screen if needed and I provide the zip file you ask for so hopefully someone will be able to figure out what the issue is. Thanks!

 

[Arc]

The zip you uploaded does not contain any crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

If still there is no recorded dump, take a camera snap of the next BSOD screen and upload it for us.

We need to know the arguments (some codes associated with the bugcheck code no) of the bugcheck at least; without it we cannot proceed.

 

[Skoll21]

Well, I just reinstalled LoL on the SSD once again but this time I didn't get a BSOD... My computer must be trolling me. Anyway, I'm reinstalling it again and see if I get a BSOD. In the meanwhile, here's my last BSOD screen.

EDIT: Reinstalled two more times and still no BSOD. Hmm, guess I'll have to wait until the next LoL patch to see if it BSOD's again. But it's weird, the only thing I did since the first reinstall which gave me a BSOD was reinstall it on the storage HDD and then reinstall it back on the SSD. I'll post an update when the next patch rolls.

 

[Arc]

The second argument of the stop 0x9F BSOD is 0xC000009D. Which is the ntstatus code there. That code reads as STATUS_DEVICE_NOT_CONNECTED. The explanation is .....

There is bad cabling, non-termination, or the controller is not able to obtain access to the hard disk.

So this is a storage related issue, that we can say.

You said that your SSD firmware version is 1.5 .... probably the latest one is 1.5.1 for Vartex 4. I would suggest you to update the SSD firmware at first and then see how it goes.

If the BSODs continue to occur, we have to take the further steps.

The storage controller is msahci.sys; which does not fail for sure.

 

[Skoll21]

I wanted to update to 1.5.1 some time ago but I found the following note on the OCZ forum (link here): " ***Note 3*** If you have firmware version 1.5 you cannot update to (and do not need) version 1.5.1. "

 

[Arc]

If they say you dont need, you dont need. And we have to search for the other reasons behind the issue.

• Controller, msahci.sys cannot be the issue.
• Firmware version is right.

So the remaining possibilities are .....

1. Sleep settings for the SSD
2. Bad cabling
3. The disc is failing itself.

Let us check those one by one, because the last two will involve some more actions.

Some SSDs dont like to go to sleep. It may be in your case too, so keep the SSD away from sleep. Follow http://www.sevenforums.com/tutorials/778-power-plan-settings-change.html .... when you are on step 5.B, set the turn off time of the Hard Disks to Zero (0) or Never whichever is available.

View attachment 357916
​

Now observe how it goes.

If there is any further 0x7A BSOD, we will explore the remaining alternatives.

 

[Skoll21]

Seems like I already had that option set to "Never".

 

[Arc]

Seems like I already had that option set to "Never".

You are a rare and conscious user.

The next thing that you need to do is to dismantle the computer. Make it sure that the discs are properly hold in the stand, there is no loose screw there. Clean the edges of the SATA ports of the discs with clean cotton cloth, use new SATA cables and apply those to any unused port on the motherboard.

See how it goes after doing it.

 

[Skoll21]

Well, when I got the SSD I followed a guide on how to optimize it on Windows and that must've been one of the settings the guide recommended changing

Alright, I'll be doing that. Thank you very much for your help! I'll report back after the next LoL client update and hopefully the BSODs will be gone.

 

[Skoll21]

Seems like I already had that option set to "Never".

You are a rare and conscious user.

The next thing that you need to do is to dismantle the computer. Make it sure that the discs are properly hold in the stand, there is no loose screw there. Clean the edges of the SATA ports of the discs with clean cotton cloth, use new SATA cables and apply those to any unused port on the motherboard.

See how it goes after doing it.

Hello. I'm reporting back. I changed the SSD cable and SATA slot on my mobo and I didn't have a BSOD on today's LoL patch/update Hopefully the issue is gone for good. Once again thank you for your help!

I think I'll be marking this thread as solved but if I run into this issue again can I reopen this thread?

 

[Arc]

You are welcome. You have done a good job throughout, it was a pleasure to share a thread with a very conscious user like you.

Considering this issue as solved. If the BSOD bounces back at any time, unmark the thread and post back. I will be subscribed to it.

 

[Skoll21]

You are welcome. You have done a good job throughout, it was a pleasure to share a thread with a very conscious user like you.

Considering this issue as solved. If the BSOD bounces back at any time, unmark the thread and post back. I will be subscribed to it.

Hello. Seems like the problem returned BSOD while updating the LoL client.

Once again, no dump files (BSOD screen froze and WhoCrashed software says there are no valid dump files to display). Only thing I got is a pic of the BSOD screen, which has some slightly different codes from the last time (sorry for the bad quality pic, my cellphone is crap).

 

[Arc]

Generally a stop 0x7A is a situation where the requested page of kernel data could not be read in. Mostly caused due to HDD related factors. But it is odd that it is occurring only in a particular situation. If it is a general corruption, then the BSOD must have to occur in other places and actions, too.

So it seems that it is download itself that is causing the issue.

I think you should talk with the LoL developers in their forum, they might be aware of it.

 

[Skoll21]

Yeah, it's weird that it's only happening in this particular situation. I'll try to expose this issue on their forum then. Thanks!