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

Page 2 of 9 FirstFirst 1234 ... LastLast

  1. Posts : 17,796
    Windows 10, Home Clean Install
       #11

    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.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #12

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


  3. Posts : 44
    Windows 7 Home Premium 64bit
    Thread Starter
       #13

    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.
      My Computer


  4. Posts : 17,796
    Windows 10, Home Clean Install
       #14

    Scry said:
    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
      My Computer


  5. Posts : 44
    Windows 7 Home Premium 64bit
    Thread Starter
       #15

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

    Thanks. :)
      My Computer


  6. Posts : 44
    Windows 7 Home Premium 64bit
    Thread Starter
       #16

    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)
      My Computer


  7. Posts : 17,796
    Windows 10, Home Clean Install
       #17

    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.
      My Computer


  8. Posts : 44
    Windows 7 Home Premium 64bit
    Thread Starter
       #18

    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.
      My Computer


  9. Posts : 17,796
    Windows 10, Home Clean Install
       #19

    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.
      My Computer


  10. Posts : 17,796
    Windows 10, Home Clean Install
       #20

    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
      My Computer


 
Page 2 of 9 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:54.
Find Us