JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
10/31/2019 4:57:10 PM
6

Hardware faults/crashing = permanent ban?

Hello Bungie, After more than a year away from Destiny 2, I purchased the expansion(s) to return to the game to play with friends only to find out that my account had been permanently banned for an unknown reason. Upon logging into the website I can see that my last game activity is in September 24, 2018 -- July 10, 2018 before that... I was not banned at this time. I read [url]https://www.bungie.net/en/Help/Article/11929[/url] and then thought about what may have led to this for a day before creating this post. After all, there’s no point in buying a new account if what led to my ban is still on my computer. TL;DR – it’s not a cheat/hack/anything that affects other players in any way. I very rarely even played PVP in this game, so there’s no reason for this. In June 2018, I had an issue with Destiny 2 crashing consistently. I don’t currently have the details of this crash, but it happened roughly every two to three hours and I had to repair the game files through the Blizzard launcher in order to get it to load again. Destiny 2 was the only game that crashed in this manner and it took me over a month to troubleshoot and correct the issue; I was certain it was hardware related. I was quite confused as to how the game files were getting corrupted. My first thought was that my SSD was failing and that was causing bits to get stuck, leading to corruption. I moved the game to another SSD and the issue persisted. My second thought was that the issue had to be RAM related, so I ran a multitude of memory diagnostics to rule that out and they all passed. Eventually, I pulled out half of my memory modules and the issue stopped occurring. I figured this was related to running four dual ranked memory modules at a high clock frequency, so I put them back in and attempted to tweak timings to resolve the crashing. This entire process took me around a month (including diagnostics time) to get the game stable. Repeated crashing, repeated corruption, for almost the entire month of June 2018. According to your policy, the only thing I could have possibly done that could have flagged my account is performing a [very brief] diagnostics/resource profile looking for memory leaks or other issues on the Destiny 2 process using Visual Studio in attempt to troubleshoot my crashing issue. I’ve done this to hundreds of games in order to analyze performance for diagnostics purposes and have never been banned before. Although I understand your policy now (after the fact) and your vigilance against cheaters, it never even occurred to me that I could be banned from simply analyzing [not modifying] performance/diagnostics data using a common debugging tool, as that has many legitimate purposes for anyone that knows how to troubleshoot real computing issues with them. I am an IT Consultant, not a programmer, so I can only assume that you cannot distinguish the difference between legitimate and malicious use for these tools so your policy is that no “normal” end-user will ever need to use them. Am I correct that this is what lead to my ban? Otherwise, the only thing I can think of is that your anti-cheat and/or review team think that I was modifying game files or memory values, when in fact it was bits getting flipped due to system memory instability. I am also aware that it is your policy to never overturn a ban, because apparently your [human] review team only bans based on overwhelming evidence with extreme competency and cannot possibly ever make a mistake. 😉 I am only bringing this to your attention to make you aware that if I was not banned for a few-minute diagnostics/resource profiling session, then I was banned for a hardware failure that caused flipped bits; which I’m sure you know, even a single one can result in a completely different hash. If this is the case, it would mean that you are indeed banning legitimate players for things outside of their control, such as hardware failures. Any insight into this matter would be greatly appreciated. Thanks for your time.
English
#Help #pcsupport

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • If cases were indeed looked at by actual people (...) then It would've shown that no foul play was had despite the presence of a 3rd party program, but from the looks of things Bungie's banbot must have a simple query: 3rd Party Program is running=ban. I'd say this should at least merit a response since this could legit happen to anyone, and If I was a betting man then I'd put my money on Bungie not really caring or having the proficiency to accurately diagnose a hardware problem on my end.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    21 Replies
    • Did you run your memory tests or other tests while the game was running?

      Posting in language:

       

      Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

      2 Replies
      • You answered your own question. Create a new account or if not, adios.

        Posting in language:

         

        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

      • [quote]Hello Bungie, After more than a year away from Destiny 2, I purchased the expansion(s) to return to the game to play with friends only to find out that my account had been permanently banned for an unknown reason. Upon logging into the website I can see that my last game activity is in September 24, 2018 -- July 10, 2018 before that... I was not banned at this time. I read [url]https://www.bungie.net/en/Help/Article/11929[/url] and then thought about what may have led to this for a day before creating this post. After all, there’s no point in buying a new account if what led to my ban is still on my computer. TL;DR – it’s not a cheat/hack/anything that affects other players in any way. I very rarely even played PVP in this game, so there’s no reason for this. In June 2018, I had an issue with Destiny 2 crashing consistently. I don’t currently have the details of this crash, but it happened roughly every two to three hours and I had to repair the game files through the Blizzard launcher in order to get it to load again. Destiny 2 was the only game that crashed in this manner and it took me over a month to troubleshoot and correct the issue; I was certain it was hardware related. I was quite confused as to how the game files were getting corrupted. My first thought was that my SSD was failing and that was causing bits to get stuck, leading to corruption. I moved the game to another SSD and the issue persisted. My second thought was that the issue had to be RAM related, so I ran a multitude of memory diagnostics to rule that out and they all passed. Eventually, I pulled out half of my memory modules and the issue stopped occurring. I figured this was related to running four dual ranked memory modules at a high clock frequency, so I put them back in and attempted to tweak timings to resolve the crashing. This entire process took me around a month (including diagnostics time) to get the game stable. Repeated crashing, repeated corruption, for almost the entire month of June 2018. According to your policy, the only thing I could have possibly done that could have flagged my account is performing a [very brief] diagnostics/resource profile looking for memory leaks or other issues on the Destiny 2 process using Visual Studio in attempt to troubleshoot my crashing issue. I’ve done this to hundreds of games in order to analyze performance for diagnostics purposes and have never been banned before. Although I understand your policy now (after the fact) and your vigilance against cheaters, it never even occurred to me that I could be banned from simply analyzing [not modifying] performance/diagnostics data using a common debugging tool, as that has many legitimate purposes for anyone that knows how to troubleshoot real computing issues with them. I am an IT Consultant, not a programmer, so I can only assume that you cannot distinguish the difference between legitimate and malicious use for these tools so your policy is that no “normal” end-user will ever need to use them. Am I correct that this is what lead to my ban? Otherwise, the only thing I can think of is that your anti-cheat and/or review team think that I was modifying game files or memory values, when in fact it was bits getting flipped due to system memory instability. I am also aware that it is your policy to never overturn a ban, because apparently your [human] review team only bans based on overwhelming evidence with extreme competency and cannot possibly ever make a mistake. 😉 I am only bringing this to your attention to make you aware that if I was not banned for a few-minute diagnostics/resource profiling session, then I was banned for a hardware failure that caused flipped bits; which I’m sure you know, even a single one can result in a completely different hash. If this is the case, it would mean that you are indeed banning legitimate players for things outside of their control, such as hardware failures. Any insight into this matter would be greatly appreciated. Thanks for your time.[/quote] Intentionally or not your account broke the rules. Ignorance of the rules doesn't exempt you from them. Your account is done. Right or wrong. There is literally nothing you can do about it. So your only two options are to buy the content again or move on. Here's some examples of other kids who "did nothing wrong". http://imgur.com/a/mdFAQ1A Pick your poison and live with it

        Posting in language:

         

        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

      • Basically answered your own question. Either create a new account to continue playing or move on to the next game.

        Posting in language:

         

        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

      • Edited by toneDef Weary: 10/31/2019 5:07:47 PM
        [quote]According to your policy, the only thing I could have possibly done that could have flagged my account is performing a [very brief] diagnostics/resource profile looking for memory leaks or other issues on the Destiny 2 process using Visual Studio in attempt to troubleshoot my crashing issue. I’ve done this to hundreds of games in order to analyze performance for diagnostics purposes and have never been banned before.[/quote] This abolutely would have gotten you flagged and banned. Other games are not Destiny. [quote]Although I understand your policy now (after the fact) and your vigilance against cheaters, it never even occurred to me that I could be banned from simply analyzing [not modifying] performance/diagnostics data using a common debugging tool, as that has many legitimate purposes for anyone that knows how to troubleshoot real computing issues with them.[/quote] Ignorance of the rules is not an out for breaking them. If you knew you were having issues, your first stop is here at the forums, not attempting to debug a live service game yourself. [quote]I am an IT Consultant, not a programmer, so I can only assume that you cannot distinguish the difference between legitimate and malicious use for these tools so your policy is that no “normal” end-user will ever need to use them.[/quote] What you do for a living and what you feel about the situation is irrelevant, they have had this hard-line stance since D1 and are not going to change it anytime soon. Bungies' rules, follow them or receive a ban.

        Posting in language:

         

        Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

        7 Replies
        You are not allowed to view this content.
        ;
        preload icon
        preload icon
        preload icon