Errors  Tagged Articles RSS Feed | Errors  RSS Feed on en Launch Media Network How to Fix np-34957-8 Error Code on PSN Thu, 02 Sep 2021 09:41:27 -0400 Sergey_3847

Many PS4 and PS5 owners are currently getting the np-34957-8 error on PSN, which is a code for server communication error. This bug has been officially acknowledged by Sony after the server maintenance. Before the issue gets resolved you can use our guide to try to fix the np-34957-8 error code on PSN.

This issue takes place whenever players try to link their accounts on PSN for multiplayer purposes. That's why you need to look specifically into this problem to be able to understand how to fix this error.

Re-Link Your Account

It is possible that after the PSN maintenance period some accounts haven't been linked properly. This means that you need to manually unlink your account, and then link it back again.

Follow these steps to re-link your PSN account:

  1. Go to PSN main menu
  2. Select "Settings" menu
  3. Go to "Account Management" tab
  4. Select "Link With Other Services" feature
  5. Choose the account you want to re-link
  6. Confirm the re-linking

Once this is done, check again, if you can link your accounts on PSN for co-operative gameplay.

Restart Your System

This means that you need to restart not only your console, but also your router:

  1. Press and hold the PS button on your gamepad
  2. Select "Power" option
  3. Choose "Turn Off" option
  4. Wait for five minutes and press the power button to switch it back on

You can do the same with your Wi-Fi router by turning it off and on after waiting for five minutes.

Wait for Official Resolution

If none of the above mentioned solutions helped your problem, then all you can do is wait before the PlayStation Network goes back up online on its own.

This may take some time, so be patient and see if it comes back up after a time.

That's all you need to know on how to fix np-34957-8 error code on PSN. If you found this article useful, then be sure to share it with your friends online!

PS4 8.00 Update Causing Multiple PSN Errors: Here's What They Mean Wed, 14 Oct 2020 16:10:21 -0400 Josh Broadwell

Sony pushed out the latest PS4 update (8.00) on October 14, which adds in new avatars, party options, parental controls, and enhanced two-step verification. It also removes event and private community creation and makes changes to the remote play app.

But not everything's going so smoothly. The PS4 8.00 update seems to be causing a number of PSN errors. Here's what they mean and how some users are getting around them until Sony releases an official fix (which they say they're currently working on). 

PSN Error WS-44369-6

Error WS-44369-6 relates to online interactions with friends and is keeping folks from forming parties. Some of the users that have run into this error have reported it just resolved itself after a few hours.

Others found you can work around error WS-44369-6 by:

  • viewing a friend's profile
  • creating a party
  • playing as usual

You may also be able to search for a friend's PSN ID and add them manually to a party. The system still throws up the error code, but apparently still allows online play. Again, note these solutions aren't working for everyone.

PSN Error WS-36770-3

Error WS-36770-3 shows your profile status as offline, even when you aren't offline, and it accompanied the PS4 7.5 update as well.

A few Redditors found success by rebuilding the PS4's database, while others resolved the issue by going to "account management" and choosing "restore licenses."

While the best bet is likely waiting for Sony to fix the problems, these are worth trying if you're impatient.

PSN Error WS-37505-0

Error WS-37505-0 is a network connection error that pops up when your network connection is faulty or a game's server is experiencing issues. With the PS4 8.00 update issues, though, it's not clear what the problem is.

There's no workaround for this one, so you'll have to wait or just keep trying.

Hopefully, Sony fixes these issues soon. We'll revise this article with more information as it becomes available, so stay tuned to GameSkinny for more PS4 update news as it develops.

Dawn Of War III Troubleshooting Errors and Bug Fixes Sat, 29 Apr 2017 16:17:56 -0400 Ty Arthur

We've had a relative glut of AAreal-time me strategy games lately, but all that changes now that Relic has returned for a third main entry in the Warhammer 40,000 Dawn Of War series (see our full review here).

But surprise, surprise, there's more than a few Dawn Of War III bugs, crashes, and errors to deal with on release day. That's just life for PC gamers -- so much for the master race!

Below we cover workarounds and fixes for a variety of multiplayer connection and single player crashing problems most frequently reported by players.

Steam Hotfix

Several of the most pressing issues were already resolved in a Day-One hotfix, but unfortunately, the fix doesn't seem to apply itself properly unless you completely shut down and then restart the Steam client.

This was causing more than a little grief for those who leave Steam running 24/7. Shutting down and restarting Steam also fixes issues where you can't connect to a new game after being booted.

Basic DoW III Troubleshooting

Before attempting anything else, there's the basic Steam troubleshooting to get out of the way.

Right-click the Warhammer 40,000 Dawn Of War III entry in your Steam library and select "Properties." Head to the "Local Files" tab and then click "Verify Integrity Of Game Files."

In most cases, if you can't load at all or are constantly crashing, this process will fix your issue, although you will have to go the pain of un- and re-installing.

 Verifying File Integrity

Multiplayer Connection Problems in Dawn of War III

If you are getting frequently booted from matches or can't connect to a lobby at all to find a multiplayer match, Relic issued these firewall tips on a workaround until a new patch arrives:

  • Make sure your firewall or antivirus program isn’t blocking RelicDoW3.exe
  • Make sure the IP address is whitelisted
  • Make sure the TCP ports 443, 27017-27030 and 50000-50010 are open

Fixing Crashes

It's always frustrating to make it through massively long campaign missions just to crash and have to start over -- and that's been happening for a number of players already, with two main problems currently prevalent.

Fatal Error

There's some sort of unidentified issue causing a crash right at the end of certain missions as you are finishing up the last objective, and it occurs most on the third Eldar mission and fifth Ork mission.

Just as you are on the cusp of victory, you'll get a box displaying the message "Fatal Scar Error - Execution Paused," followed by a freeze or crash. There's no permanent fix for this -- yet -- other than to restart the mission.

Doing this from the in-game prompt seems to always result in the same crash again, however. To increase your chances of getting to the victory screen, you have to entirely exit back to the main menu screen and then select the mission again. Just restarting the mission won't do it, as whatever problem in the code that's causing the error will still be running.

Video Card Selection

Of course you should make sure you are updated to the latest driver for your graphics card, but that doesn't seem to be a big driving force of crashes at the moment.

An unexpected issue can be the cause of your crash or slow performance for dual video card users. Apparently, there's a bug causing the wrong card to be utilized, which might be giving you graphical glitches, lag, or system freezes.

To fix this issue, pull up your video card control panel and select the option to force the file named RelicDOW3.exe to use your main, dedicated GPU.

Forward To Victory For The Emperor

Those are all the major bugs we've come across so far -- let us know if you're experiencing any others and we'll look for a solution.

Now that you've got the game up and running, be sure to also check out our Dawn Of War III Eldar tips and strategies for both single player campaign missions and online multiplayer!

How to fix common issues, errors, and bugs in Fallout 4 (stuttering, frame rate, broken quests, etc.) Sat, 02 Jan 2016 02:51:16 -0500 Ty Arthur

It's par for the course with both AAA games in general these days and Bethesda's open world titles in particular: there's going to be bugs galore at the launch date and for months to come while we wait for a string of major patches.

While some of Fallout 4's bugs are hilarious, others will make you want to burn Bethesda's development studios to the ground.

From broken quests to major frame rate and stuttering issues, there's a host of common problems still occurring if you jumped into the game early (so many that some are declaring New Vegas and Fallout 3 to be superior games). Here's how to overcome some of the most frustrating Fallout 4 bugs and broken quests.

When Freedom Calls Broken Quest

It's a sad state of affairs when literally the very first main story quest can't be finished due to a game-breaking bug, but here we are.

This quest to help out the Minutemen and get your suit of power armor works just fine... until you reach the quest objective “Clear Concord Of Hostiles.” Many people are experiencing problems where this objective won't get checked off, or it does get checked off and then reverts back to being an active part of the quest for no apparent reason.

They seriously nerfed the very first story quest...

Before going into troubleshooting on this, make sure you've actually killed the deathclaw that pops out of the ground, and check around the town to ensure there aren't any raiders hiding in corners from the awesome might of your power armor. If you are certain all the hostiles are actually dead, here's what you need to do next:

  • Find the body of the raider leader named Gristle and click on his corpse (make sure he's actually been selected and not just highlighted with your pointer).

  • Tap the ~ key (usually next to the 1 on most keyboards) to bring up the developer console.

  • Type “resurrect” (without the quotes) and tap Enter to bring Gristle back to life.

  • Immediately gun him down to finish the “Clear Concord Of Hostiles” objective.

  • RUN to the museum to talk to Preston Garvley to finish the quest before it bugs out again!

You may be worrying about using the developer console (which is typically used for cheating by granting immediate levels or creating items), but there's no cause for concern here, as it won't actually affect your Steam achievements or prevent you from unlocking new achievements.

Hunter/Hunted Broken Quest

This quest is known to cause crashes and display all sorts of odd behavior, so if you are having problems with it, first revert to a save game before entering Greenetech Genetics. Here's how to complete the quest without crashes or bugs from there:

  • Travel to the C.I.T. Ruins, but don't bother using the Courser signal to find and enter Greenetech.

  • Use the ~ key to open up the developer console (yeah, we're going to cheat a bit to make this one work).

  • Travel instantly to Greenetech Genetics by typing in the phrase “coc GreenetechGenetics01” (without the quotes) and hit Enter.

  • Kill your target Z2-47 as normal, but do NOT open any doors or leave the area, as this will frequently make his body un-lootable.

  • Take the Courser chip from his body but DON'T leave the building normally.

  • Open the developer console again and instantly teleport out of there by typing “coc sanctuaryExt” (without the quotes) and hit Enter.

Completing the hunter/hunted quest may take a little cheating...

Vision Stuck In Hazy Colors

Echoing that weird glitch from New Vegas where your pip boy would suddenly become incredibly bright and blurry for no apparent reason, there's a vision issue occurring intermittently in Fallout 4.

This issue causes your screen to become stuck in a blurry mode that most frequently seems to happen after using the night vision or recon scopes. To fix this issue, you'll again have to bring up the developer console by typing the ~ key and entering a specific command:

  • Type “rimod 00094636” (without the quotes) and hit enter to fix the night-vision scope/green color blur issue.

  • Type “rimod 002041B6” (without the quotes) and hit enter to fix the recon scope/white color blur issue.

Bad Frame Rate/Stuttering

Even when turning the graphics all the way down, some users with decent rigs that should be running Fallout 4 smoothly are still experiencing bad frame rates, stuttering, and slow downs during regular gameplay. I unfortunately experienced this one firsthand, as I recently bought a whole new gaming rig and was annoyed to discover the game ran terribly even at medium or low settings.

Turns out the culprit is a new tool downloaded with your latest GeForce driver if you have the NVIDIA GeForce Experience program installed. You only need this tool if you are actually streaming games from your PC to a SHIELD device, so if you aren't using that feature, you might as well turn it off and get better game performance. Here's how to turn this feature off:

  • Type the phrase “Services” (without the quotes) in the Windows search box

  • Right-click the Services icon and select “Run As Administrator.”

  • Scroll down to the “NVIDIA Streamer Service” entry and right-click it.

  • Choose “Stop” and then “Yes” to turn this service off

  • Right-click it again and select “Properties” and navigate to the “General” tab.

  • Choose “Disabled” in the “Startup Type” drop-down box to prevent the service from turning on automatically when you restart your computer.                           

             Turning off the streamer service

If you aren't using the GeForce Experience, there are still ways to manually tweak settings to resolve stuttering, frame rate problems, and screen tearing. This requires changing the game's “.ini” file, which is found in a different location than you might expect.

  • Navigate in an explorer window to This PC>Documents>My Games>Fallout 4.

  • Right-click the configuration file simply named “Fallout 4” and choose “Open With” and then “Notepad.”

  • Scroll to the [Display] heading and change the iPresentInterval setting from “=1” to “=0” (without the quotes).

Opening the .ini file

Directly underneath the “iPresentInterval=0” line, manually type in these commands, entering one per line:

  • bTopMostWindow=0

  • bMaximizeWindow=0

  • bBorderless=0

  • bFull Screen=1

Save and close the file to turn off the game's internal v-sync options and get better Fallout 4 performance in full screen mode.

Fan Mods For Fixing Fallout 4 Bugs

There are already some users stepping up and resolving issues faster than the developer, and those fabulous modders have my eternal gratitude!

The Mo Betta Scrap mod, for instance, fixes issues with what sort of items you get when scrapping junk, while the Simple Bug Fixes mod does exactly what it sounds like: fixes some known issues with perks and damage percentages that can result in a less than satisfying game experience.

Although it doesn't actually fix a bug, any PC user should do themselves a favor and download the Full Dialog mod so you can actually see what is going to be said and not just get a general two or three word idea from the dialog tree.

Raiders and super mutants will tremble - if you can get past the bugs!

How to fix common issues, errors, and bugs in Just Cause 3 (crashing, stuttering, driver problems, etc.) Fri, 04 Dec 2015 15:12:23 -0500 Ty Arthur

As is unfortunately becoming expected with major PC game launches these days, Just Cause 3 is plagued with a host of bugs, errors, and glitches in what should be its triumphant first week of release. It's a shame too, because there's a whole lot of fun to be had as you blow up everything in sight and fly around Medici – if you can get the game to work, that is.

Developer Avalanche Studios has already released a statement through Steam that a major patch is in the works to fix the glitches and launch issues being experienced by many PC users.

No specific date was announced for that patch however, so in the meantime, Just Cause 3 fans are going to have to come up with some workarounds if they want a playable game. Here's a rundown of some common Just Cause 3 errors and how to resolve them.

Basic Steam Troubleshooting

There's one basic troubleshooting step you should always go through for any PC game through Steam – whether Just Cause 3 or anything else. Be sure to verify the files before making any changes to settings, as this can resolve a lot of issues.

  • Right-click on Just Cause 3 in your Steam library and select “Properties”.

  • Navigate to the “Local Files” tab.

  • Click “Verify Integrity of Game Cache” and Steam will check to see if you have any missing or corrupted files that are causing a problem.

Verifying Steam Files

Crashing After Intro Video

One of the most prevalent issues is a crash to the desktop, especially right after the intro video just as the game is actually starting. It seems like the issue here is caused by a graphics issue not getting along with certain cards and drivers.

First off, update your graphics card driver and make sure you've got the latest one available. If that's not solving the issue, you can usually get the game to work past the opening animation by turning off a specific advanced graphics feature:

  • Head to the “Graphics” tab in the options menu.

  • Set the “Screen Space Reflections” option to “Off”.

Stuttering Graphics

As with the crashing problem, make sure to update your graphics card driver before attempting any other troubleshooting here.

Some players have also reported success in fixing the issue just by running the game in administrator mode. Simply right-click the game's launch icon and select “Run As Administrator.” If that's not helping, you can get some relief again by turning off a graphical feature:

  • Head to “Graphics” tab of the options menu

  • Set the “Motion Blur” option to “Off.”

AMD Video Driver Problems

A known issue exists that is causing crashes and graphical glitches with AMD/ATi graphics drivers. An update from AMD is in the works and will be out shortly, but for now you can resolve most of the issues by switching to this driver version here.

After you've got the game working, be sure to check out our guides on how to pick up all the collectibles:

Rebel shrines location guide
Ancient tombs location guide
Stunt jumps location guide
Di Ravello audio tapes location guide
U-24 Zabijak shotgun parts guide

You too can cause mayhem like this - if you get Just Cause 3 working!

Fallout 4 has "game breaking bugs" according to some reviewers Mon, 09 Nov 2015 11:21:11 -0500 David Fisher

Don't worry, Piper's not dead. She's just planking, and not because she wants to. Fallout 4 has simply decided that her time would be best spent face-down on the floor.

While Fallout 4 doesn't technically come out until November 10th, the game has already been launched in the eastern world for several hours already. As such, the Fallout 4 review embargo has ended, and that means reviews are already starting to come out. However, while the game has been getting some great praise, some reviewers are finding some terrible flaws that might ruin the game for many players.

Glitches have always been part of Bethesda games. In fact, the developer is notorious for them. Many of these bugs come in the form of quirky physics glitches, repetitive conversations, character "pops", and even the occasional instant-death. Sometimes these are funny (like this one from Skyrim seen above) while other times it can be downright frustrating. Unfortunately, Fallout 4 is reported as having all of these classic bugs and more, as well as some potentially game-breaking ones that fall into the latter category.

According to Chris Carter of Destructoid:

At this point, you [the player] are probably aware of Bethesda's history with shipping buggy open-world games by now. If you were hoping that somehow a generational leap would magically buck that trend, prepare to be disappointed. Nearly every classic glitch is accounted for, including occasional save data issues, repeated dialogue, frameskipping, severe frame-rate drops, pop-in, falling through the floor, and so on.

For those of you who are used to this with the past work, it's par for the course -- for everyone else who doesn't put up with it, nothing has changed. I should also note that while visual issues were persistently present in the Xbox One edition (reviewed here), I only ran into full-on game crashing twice during my travels. Given how glitchy it is, I can only speculate as to whether or not there will be any game-breaking bugs that completely halt progress, but it seems very likely.

- Chris Carter - Review: Fallout 4

Carter's testimony lies with what many players have come to expect from Bethesda. Whether it is the Elder Scrolls series, or Fallout, players know that they should save often if they hope to make it through the game in one piece. However, not everyone is so lucky. 

As Chris Plante of The Verge has come to understand, Carter's hypothesis on game-breaking bugs is rather accurate.

In a rather eloquent role-played article, Plante states that he has become stuck in an elevator after 9 hours of gameplay. In an attempt to progress further into the game he reloaded a previous save file that was set several minutes prior to his beginning of the mission. However, after reaching the elevator again the elevator froze once more. In fact, none of the elevators in the game worked ever again. No matter which save file he loaded, the game would not let him use an elevator ever again.

The game was broken, as was his heart. Since then, Plante has been reconsidering whether or not he should start a new save, or simply not invest any more time into the game.

While it should be expected from Bethesda at this point, these glitches are simply inexcusable. Whether the games are fun or not, is it not an insult to us - the consumer - to pay good money towards these games, and yet be unable to play them properly as a result of glitches? 

I for one cannot see why we hold a game like Tony Hawk's Pro Skater 5 to such high standards while Bethesda simply gets a slug in the shoulder and a good ol' "Oh you!" from consumers. Maybe their games are just that good. But on the other hand, maybe we - as gamers - have simply grown accustomed to just accepting what is handed to us.

For those who want to see some more glitches in action, here's a compilation of videos I've found online:

Forget The Phantom Pain, Here's The Phantom Limb!

- via David Wilcox (Youtube)

An Air-Swimming Dogmeat

- via David Wilcox (Youtube)

Collision Error Breakdancing

- via NowGamerTube (Youtube)

Raiders "pop" in for a Surprise Party

- via David Wilcox (Youtube)

[Header Image] Piper Decides Planking is Useful

- via FPetts (Youtube)

What do you guys think about the glitches in Fallout 4? Do you think that Bethesda should be allowed to get away with this? How long do you think it will be before Bethesda or modders find a way to clean up this mess? Leave your thoughts in the comments section below!