Solved BSOD Playing League of Legends, Using Skype, MS Security Essentials

[Scry]

Hi Everyone,

I just recently bought a new computer-- an Acer Aspire V3. Right when I got it I manually removed a bunch of bloatware, uninstalled McAfee, and put a lot of my files from my old laptop on here, so I can't identify if my problem is caused by any new software. I did re-download certain programs like MS Security Essentials, League of Legends, a registry cleaner (CCleaner), etc. The version of Skype I'm using came with the computer.

I ran windows update a few days ago but I've been getting BSODs before and after that so I don't think that particular update was the change.

Anyway, I've attached the log files from the SF Diagnostic Tool and I would LOVE if someone could help me out on this. I am a semi-competitive LoL player and it is extremely frustrating to get BSODs every now and then. (They seem to happen roughly 1/10 games right after the loadscreen, but I believe the first BSOD I got was the day I got the computer, when I was moving files around on it, without running League of Legends at all).

If you need any more information let me know. Thank you very much! I really appreciate any help I can get.

edit2: Log file correctly attached now.

edit3: forgot to mention, the screen said "driver power state failure"

 

[Scry]

My only bump-- I would really appreciate it if someone could take a quick look at the files I posted and give me some sort of idea where the problem is coming from. Like I said, the computer is new so I don't know where to start. Thank you so much.

 

[richc46]

Sorry that there was a delay in helping you. In the Summer, we can be short handed.
Your reports are consistent they show acpi.sys as the driver causing the problem. This is rare, since it is a Microsoft Driver
It may actually be malware
Update your anti virus and make a full scan
Download malwarebytes update and make a full scan
If negative, we will try to fix the problem

 

[Scry]

I downloaded, updated and did a full scan with Malwarebytes. I also updated and scanned with MS Security Essentials afterwards (full scan). Unfortunately (fortunately?) they didn't find any problems.

How likely is it that this is a malware issue that the antivirus didn't catch? What's the best course of action for me now?
Again, thanks so much for your time and help!

 

[richc46]

OK
That driver is used often for the hard drive
Go to the website of your hard drive manufacturer and test the hard drive.
Malware was a small possiblity, I did not really think that it was malware.

 

[Scry]

Okay, so I ran a windows test of the Hard Drive under properties of C: -> Tools -> Error-checking. This required a reboot and after a few hours of checking it didn't find any problems.

Then I downloaded the HGST Align Tool (my HD is by Hitachi) (the link from Google that took me to the HGST Align Tool was labeled "Drive Fitness Test"). After installing this tool and starting the wizard, the tool would not allow me to select any disks and said there were no errors with any of them. I didn't have to restart my computer and the test didn't take any time at all.

Does this make sense? What now?

 

[richc46]

I am not satifisfed with the second test. The test that you used, the error check, is not accurate for these purposes.
Test Hard Drive
Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

 

[Scry]

I ran SeaTools and everything seemed to work-- I did the Long Generic Test, Short Drive Self Test, and Short Generic Test, and the drive passed all of them. Hmm...

 

[richc46]

Try with a clean boot
If the BSODs do not occur after a satisfactory amount of time, begin the clean boot procedure to find the software that is the cause of this conflict.
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[Scry]

Okay, got it. The problem is so intermittent (it only occurs 1 in every 2 days when I'm using the computer a lot) that this could take a while, but I guess it'll have to do.

By the way, I had to update my Microsoft .NET framework for the scan to work-- could that have been the issue?

Anyway, thanks so much for your help!

 

[richc46]

Dont think that is the issue
But with the clean boot, do not be in a rush. You can use the computer just fine in clean boot, in fact you get super fast boots. Once we are certain no BSODs in clean boot, we got it licked.

 

[richc46]

This is the second case today, with this game. It may just be too intensive for your computer.

 

[Scry]

Okay, good to know about the clean boot!

And the game is definitely not too intensive for the computer-- it's a newer model designed for gaming and has a lot more powerful CPU, GPU, and more RAM than this game needs. And just to clarify, the fact that it said "driver power state failure" doesn't help at all?

edit: I don't understand your comment, "This is the second case today, with this game. It may just be too intensive for your computer." My computer hasn't crashed in the last 2 days.

edit2: Again, just to reiterate, I am not able to reproduce this problem consistently at all-- it just seems to happen mostly when I'm playing the game, after the loadscreen. But I definitely got the first BSOD on this computer before the game was even on it.

 

[richc46]

Okay, good to know about the clean boot!

And the game is definitely not too intensive for the computer-- it's a newer model designed for gaming and has a lot more powerful CPU, GPU, and more RAM than this game needs. And just to clarify, the fact that it said "driver power state failure" doesn't help at all?

edit: I don't understand your comment, "This is the second case today, with this game. It may just be too intensive for your computer." My computer hasn't crashed in the last 2 days.

.

Another member has the same problem with the same game. hmm.

Give us the new reports

 

[Scry]

Okay, got it. I'll be sure to upload new logs as soon as the error occurs again.

Thanks.

 

[Scry]

Alright, so I just got the same BSOD on an entirely clean boot-- all non-windows services were disabled. Does this shed light onto the problem?

Thank you! (I've attached the newest log from the SF Diagnostic tool)

 

[richc46]

Driver Verifier
I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

The clean boot tells us its not any installed software. Lets try to find the cause with Verifier.

 

[Scry]

Okay, I'm not sure if I did the entire process exactly right, but I've definitely got something...

So I used the verifier exactly the way you instructed, shut down, and when I started up, Windows wouldn't boot. It ran something I think was called Startup Repair that was attempting to automatically fix whatever had prevented the boot. After a little while, it gave an error and said it was unable to fix any problems. The error message looked like this:

Problem Event Name: StartupRepairOffline
Problem Signature 01: 6.1.7600.16385
Problem Signature 02: 6.1.7600.16385
Problem Signature 03: unknown
Problem Signature 04: 15
Problem Signature 05: AutoFailover
Problem Signature 06: 1
Problem Signature 07: 0x7e
OS Version: 6.1.7601.2.1.0256
Locale ID: 1033

(copied by hand)

So then I clicked Finish, which shutdown the computer. I figured I wouldn't be able to use my computer at all at this point, because apparently there was a serious error that Windows couldn't fix. However, when I booted up the second time, I encountered no errors and am typing this to you now. When I logged on, a dialog popped up telling me that Windows had shutdown unexpectantly and given this error:

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: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF800031342D4
BCP3: FFFFF88003955948
BCP4: FFFFF880039551A0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\090412-17550-01.dmp
C:\Users\Admin\AppData\Local\Temp\WER-36348-0.sysdata.xml

I have attached the latest SF Diagnostic Tool files-- hopefully this helps.

Again, thank you so much for sticking with me on this. I would be lost otherwise.

 

[richc46]

The only real clue, without the dumps is Bcode 7E and it means the cause is possibly:
Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Make sure that you have enough disk space
Go to the website of the manufactuer of your hard drive and test hard drive
Update your Video card driver
Have you made any changes to software or hardware about the time of the problem
Test memory
I did not check to see what has already been done.

 

[richc46]

Almost forgot

Run memtest for 8 passes
Then test each individual stick in a good slot for 6 passes.
If you have dual channel, the results may be incorrect, if shows pass.
Guide to using Memtest86+ - Geeks to Go Forums