Lake of Sorrows Cabbage error code to a constant currant error code.
Any time I queue up for the Lake of Sorrows NF adept or hero, I will load in just fine. But when we clear the adds up to the point we clear out the taken blights and are sent to to find the root cause of the blight and we enter the Broken down dam I receive the cabbage error. it doesn't happen immediately but it does happen. When in other activities before this cabbage doesn't appear. but when it rears its nasty head, I get stuck with Currant error code until I force close Destiny.
Before anyone tries to be little network majors. I'm cut you off at the knees this isn't a network issue. I have a Netgear, Nat Filter is set to open. I am on PC and YES I'm wired direct into the router. I also have a Fiber connection so its not the internet. I've actually logged into the router and processed a reboot.
This seems to be too coincidental that I'm getting network error codes each time at the same spot in the game. I believe something may be busted with match making NF and I've done this on both Adept and hero.
If someone cares to know my PC specs
R5 5600x
RTX 3070
Asus Dark hero viii
32GB of ram 3600mhz Gskill trident Z neo ram.
NVME dual 500GB Samsung Evos (one for boot one for games like destiny)
Any other specs is unnecessary and irrelevant.
Any assistance would be helpful.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.