test content
What is the Arc Client?
Install Arc

Blue Screen of Death after game starts

hatepwehatepwe Member Posts: 252 Arc User
I just patched up with the most recent patch.

The game is literally unplayable now.

The first start up I selected my character (KDF Reman) and logged in. Immediately upon loading the Contested zone (floating over the battlezone entrance) I started seeing white squares all over my screen then it went black then a BSoD.

After restart I tried to log in again thinking it was a quirk of the initial log in after the update. Second time I didn't even make it to the character screen before the same thing happened.

However, this time even after the loading attempt and the BSoD I had squares and then white lines all over my screen obscuring parts of the computer's reboot text and then obscuring parts of windows after I restarted it in Safe Mode.

Thoughts?

Oh and I tried Neverwinter and it runs fine.
[SIGPIC][/SIGPIC]
Post edited by hatepwe on
«1

Comments

  • stoutesstoutes Member Posts: 4,219 Arc User
    edited November 2013
    Could you give the BSOD error code? This could help us looking in the correct direction.
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    Grrr this is frustrating that I paid to be a lifetime member of STOL and I cant post new threads ... wtf

    Anyways I am also getting the BSOD winsys32 ... I thought it was random then after a time or two I noticed its only when I start STOL ... it seems like it isnt ont he first start but maybe the 2nd or third.

    It only recently started happening.

    I launch from steam.

    I have windows 7 Pro 64bit
    32gig ram
    Intel i7 3820 3.6ghz
    SSD
    Radeon 7970HD Sapphire 3gig

    Edit, typically right when I press engage from launcher.
  • stoutesstoutes Member Posts: 4,219 Arc User
    edited November 2013
    Grrr this is frustrating that I paid to be a lifetime member of STOL and I cant post new threads ... wtf

    Anyways I am also getting the BSOD winsys32 ... I thought it was random then after a time or two I noticed its only when I start STOL ... it seems like it isnt ont he first start but maybe the 2nd or third.

    It only recently started happening.

    I launch from steam.

    I have windows 7 Pro 64bit
    32gig ram
    Intel i7 3820 3.6ghz
    SSD
    Radeon 7970HD Sapphire 3gig
    Error 0x0000???
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • dercheetodercheeto Member Posts: 5 Arc User
    edited November 2013
    I am also BSODing, (so says the error I get when the machine restarts) but my machine just goes black and the computer restarts. This has been since the last two patches...
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited November 2013
    @dercheeto

    run a Dxdiag and either post here or send me the results via pm
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    stoutes wrote: »
    Error 0x0000???

    I'll try to induce it later and take a picture
  • dercheetodercheeto Member Posts: 5 Arc User
    edited November 2013
    dxdiag reported no issues, crash report gave me this:

    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: 116
    BCP1: FFFFFA80033C91E0
    BCP2: FFFFF8800F99E28C
    BCP3: FFFFFFFFC000000D
    BCP4: 0000000000000003
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\112213-43493-01.dmp
    C:\Users\Dom\AppData\Local\Temp\WER-467768-0.sysdata.xml
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited November 2013
    dxdiag wasn't going to report any issues but when you save all information it would of given us a reason why the game is causing a conflict with your system so much that you get the error.

    http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-bccode-116/70bda113-799b-4b9d-ae50-ca570136e7f8

    Hi,
    Welcome to Microsoft answers.
    I would suggest you to update the drivers for your graphis card, here are the steps: FYI- the DXdiag would of told us the version of your drivers so i would know if this was right for your problem most likely is though.

    1. Open Windows Update by clicking the Start button. In the search box, type Update, and then, in the list of results, click Windows Update.
    2. In the left pane, click Check for updates, and then wait while Windows looks for the latest updates for your computer.
    3. If there are any available updates, click the link in the box under Windows Update to see more information about each update. Each type of update might include drivers.
    4. On the Select the updates you want to install page, look for updates for your hardware devices, select the check box for each driver that you want to install, and then click OK. There might not be any driver updates available.
    5. On the Windows Update page, click Install updates If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
    http://windows.microsoft.com/en-US/windows7/What-to-do-when-a-device-isnt-installed-properly
    If you cannot find the drivers, then go to manufacturer?s website download the latest drivers and install.
    For more information on the issue, refer this link:
    http://social.answers.microsoft.com/Forums/en-US/vistaperformance/thread/6940c7ff-64e7-48fd-8101-239abd5678a0
    Please respond back for the status on the issue and let us know if you have any issues.
    Thanks and Regards,
    Azam ? Microsoft Support.
  • stoutesstoutes Member Posts: 4,219 Arc User
    edited November 2013
    dercheeto wrote: »
    dxdiag reported no issues, crash report gave me this:

    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: 116
    BCP1: FFFFFA80033C91E0
    BCP2: FFFFF8800F99E28C
    BCP3: FFFFFFFFC000000D
    BCP4: 0000000000000003
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\112213-43493-01.dmp
    C:\Users\Dom\AppData\Local\Temp\WER-467768-0.sysdata.xml
    Thnx for the info.

    Do you have an Nvidia? Which driver do you have installed? Some versions introduced the 116 error, while others were causing severe memory leaks.

    Hope to hear from you soon.
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • dercheetodercheeto Member Posts: 5 Arc User
    edited November 2013
    I have nvidia, I just updated today to the most recent to see if that would solve the issue; it didn't. I tried a few other games as well and am having the same seeming crash on L4D2.
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited November 2013
    What graphics card is installed?
  • stoutesstoutes Member Posts: 4,219 Arc User
    edited November 2013
    dercheeto wrote: »
    I have nvidia, I just updated today to the most recent to see if that would solve the issue; it didn't. I tried a few other games as well and am having the same seeming crash on L4D2.
    Try downgrading to 275.xx ; the 116 error was introduced after 28x.xx.

    Anyhow, if even that doesn't help then there's an 80% chance it's your hardware breaking down.
    maxvitor wrote: »
    Nerf is OP, plz nerf
    That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.

    I call it, the Stoutes paradox.
  • dercheetodercheeto Member Posts: 5 Arc User
    edited November 2013
    Its an old card, GeForce GT 240

    I am thinking it might be a hardware issue at this point, there's no over heating in my CPU or GPU, but it seems like the fan on my power supply is not really moving air... so maybe my power supply is overheating when I start drawing more power?
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited November 2013
    dercheeto wrote: »
    Its an old card, GeForce GT 240

    I am thinking it might be a hardware issue at this point, there's no over heating in my CPU or GPU, but it seems like the fan on my power supply is not really moving air... so maybe my power supply is overheating when I start drawing more power?

    yeah just take the side of the computer and clean the dust out of the computer.

    Get some pincers and get the dust out of the fan, go buy a can of compressed air. (if ur in the US you need to be over 18 and need ID to buy.)

    make sure the fans are rotating inside. then put the side back on. you can check again if this fails then do stoutes suggestion down grade the patch version.
  • dercheetodercheeto Member Posts: 5 Arc User
    edited November 2013
    I m down to the patch solution, as I did that 3rd off before posting here... well, maybe this will give the excuse I've wanted to get a new machine... *grins*
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    heres is my BSOD

    http://imgur.com/AF9GYSA

    No issues for my in other games, I have the latest beta drivers, and they worked with STOL until the last patch or two.

    http://pastebin.com/MtwvxnN7

    here is my dxdiag?
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    again sorry to hijack your thread, but it was related and I cant post new.
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited November 2013
    maniacmagic

    I am looking into this for you. So far from what I can see you just need to update your sound card drivers. That wouldn't cause your BSOD however.


    I'll edit this post with more info, i just got into work so.

    Added: Please go to this website page and do the auto detect
    http://support.amd.com/en-us/download

    It appears you don't have the latest Beta drivers the latest according to their website is 11/22/2013, your driver date is 9/27/2013

    Then I suggest this page
    http://msdn.microsoft.com/en-us/library/ff558949(v=vs.85).aspx to check for any other bugs that would cause your BSOF
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    Ahh didnt notice they had another new set of drivers already. Either way the strange part is I had no issues, or other game issues until this patch ... and BSOD isnt exactly just some small game crash, they need to look into this.
  • legetdumarlegetdumar Member Posts: 263
    edited November 2013
    Some addtional tools to help diagnose and treat BSOD's, this will allow you to open and read the crash dump files:


    http://msdn.microsoft.com/library/windows/hardware/ff551063(v=vs.85).aspx

    And some hints on how to use it:

    http://www.sevenforums.com/crash-lockup-debug-how/277355-debugging-bsod-my-way.html

    :cool:
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • hatepwehatepwe Member Posts: 252 Arc User
    edited November 2013
    I can barely see anything due to the visual errors that have been caused by this last patch. My computer barely works now and this has only been occuring since the last STO update. No other programs have been updated and it's done damage to my OS somehow.

    http://i747.photobucket.com/albums/xx116/robertclark1981/screwedup_zps39271a5e.jpg

    My system won't even start properly this is kind of absurd. It would be nice to hear something from a dev since my system is bordering on inoperable and the only cause possible is the last update to this game...
    [SIGPIC][/SIGPIC]
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    hatepwe wrote: »
    I can barely see anything due to the visual errors that have been caused by this last patch. My computer barely works now and this has only been occuring since the last STO update. No other programs have been updated and it's done damage to my OS somehow.

    http://i747.photobucket.com/albums/xx116/robertclark1981/screwedup_zps39271a5e.jpg

    My system won't even start properly this is kind of absurd. It would be nice to hear something from a dev since my system is bordering on inoperable and the only cause possible is the last update to this game...

    Cool baby thing!

    So is there some way to raise the issue, cause just a game crash is one thing, but whats happening to multiple people isnt cool. I'm downloading the latest latest beta drivers but still this is the first game to BSOD my computer, actually my first BSODs period and I'm running a fairly expensive rig that I'd rather not be damaged from this game.
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    I've actually narrowed down exactly when I get BSOD ... I have two monitors, the left one with the launcher and STOL ... so a lot of time I click Engage and go back over to my other screen to finish stuff up while it loads. If I click on the other screen too fast right after engage I get a BSOD 5/5 times. I tested other situations with other games, it only seems to be STOL ... or at least the launcher.
  • legetdumarlegetdumar Member Posts: 263
    edited November 2013
    I was getting quite a few BSOD's from STO only as well. Mine were 124 bug checks, in which the crash logs kept pointing to the processor being faulty, even though it sited Vista drivers and the Game Client (STO) as the causes of the processor fail. This was after updating all my drivers, cleaning up my registery, stress testing my drivers, replacing a 3rd party antivirus with windows essentials, and what ever else I could think of.

    However, when I did another driver stress test ("verifier" typed into windows search menu) with my optimizing program (TuneUp Utilities) on turbo, which turns off back ground features for things like gaming, the BSOD's stopped. So, at least in my case, perhaps STO and some system background chatter were in conflict, causing my processor to throw up the white flag in the form of a BSOD? :confused:

    My OS on that machine is Windows 7 64 bit.
    Criticism, while never agreeable, is necessary. It is like pain in the body. It brings attention to an unhealthy state of things---Winston Churchill
  • hatepwehatepwe Member Posts: 252 Arc User
    edited November 2013
    Turns out STO fried my video card.

    I played SKYRIM, SimCity, etc all on max settings and the fan rarely kicked up. Every couple of updates STO would cause my fan to kick on my card almost at login. Always thought it was weird that every once in a while a patch would come along and my card fan would hardly turn on while running the same content that had made my fan blaze just weeks before.

    A few patches ago the fan starting screaming again and has been til this last patch which was apparently the straw that broke my card. Good-bye GTX 470, hello GT 610...just had a kid so can't afford to replace the card with something of equal power right now.

    Pretty frustrated that the patches to STO are what killed it (I also play Champs and NW and neither cause the fan to kick up as much as STO did just flying around the contested zones).
    [SIGPIC][/SIGPIC]
  • maniacmagicmaniacmagic Member Posts: 11 Arc User
    edited November 2013
    wow really sorry to hear that ... i hope it doesnt do the same to mine .... kinda of sad I bought this lifetime membership now ... afraid to play the game.
  • hatepwehatepwe Member Posts: 252 Arc User
    edited November 2013
    Looks like there's some actual video options under the troubleshooting tab in the Video section of the Options menu (why you'd call more advanced settings Troubleshooting I have no clue, I thought it was a lame help menu and not more settings).

    You can control your fps there so it doesn't hit your card as hard and set the limit manually. I'm guessing that FPS setting was getting messed with by the various patches I mentioned earlier and that's what killed my card and accounted for the varying fan noise over the last year or so.
    [SIGPIC][/SIGPIC]
  • desert4dessertdesert4dessert Member Posts: 6 Arc User
    edited December 2013
    I thought I was the only one who was getting hardware problems from this game.

    I have reason to suspect that STO is killing off my hard drives. In the last month, my old hard drive kept hanging and crashing whenever I'd play STO, to the point that it eventually just up and died a couple of days ago. After installing my new hard drive, I went and played STO yesterday for a couple of hours since I felt it was a fluke because the hard drive was like 2 years old and had no problems whatsoever. Today, however, just one fleet action and already my brand new hard drive hangs and gives me a BSoD.

    It's really frustrating because before S8, everything worked fine, my hard drive never crashed or hung, and I could run it on recommended graphical settings. Suddenly the S8 patch comes out and I can barely even play the game in Safe Mode without my hard drive failing.

    And before anyone asks, my previous hard drive was a Seagate Barracuda 7200.12 SATA 3Gb/s 500GB Hard Drive, while my current one is a Seagate Barracuda Barracuda? 3.5-inch SATA 1-TB Hard Drive

    I would have posted a new thread for it, but I can't do that yet and this thread seemed like the one that was the most related to my problems.
  • smokinssoulmatesmokinssoulmate Member Posts: 0 Arc User
    edited December 2013
    I know this is not going to go down well however it needs to be said.

    STO did not and can not do anything to your hardware or system. The DEMARC point for them is to make sure the game is able to be played at client locations. It can that is their job done! they will continue to improve quality of service and if there is a break in the line preventing or slowing people to connecting they will fix it.

    Everything else is User-end responsibility /ignorance. The computer will only do or not do what you tell it to do or not do. Other wise the computer would just sit there dumb and not do anything. It is most unfortunate what has happened with you hardware however as you admitted you miss-judged something which would of prevented the failure of the Graphics card.

    That is not Cryptic's fault it's your fault. If my stuff breaks, it is because something happened and I didn't prepare for it or I messed something up. Next time you know to try changing settings around instead of just leaving it. It's cause Trial and error, try something see if it fixes it if not try the next thing.

    It is not the game or cryptic that is causing it, as it were it would be effecting everyone not just you and there would be a Hot -fix and emergency maintenance because it would be doing the same thing to people at cryptic if it actually was causing conflicts and hardware failure.
Sign In or Register to comment.