My post ONLY applies to people who were banned but were honestly not using a bot, maphack, or other unauthorized 3rd party software that might be responsible.
Here's the quiz for you:
1) Did you disable DEP, also referred to as the NX bit?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /noexecute=AlwaysOff
B] Entering in the command line - bcdedit.exe /set {current} nx AlwaysOff
2) If you have DEP disabled, did you then add the /PAE option to enable that?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /PAE
B] Entering in the command line - bcdedit /set [{ID}] pae ForceEnable
3) Regardless of the above settings, did you enable the LargeAddressAware option?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /3GB or /userva=
B] Entering in the command line - bcdedit /set increaseuserva
If you answered Yes to any of these options, and you genuinely were not cheating at all, then that's probably what caused you to be banned. Here is a killer link showing that Steam's Anti-Cheat (VAC) also doesn't function with DEP disabled. Keep in mind this is an official support help page from Steam, and if you do some Googling you can see many forums topics about VAC issues being resolved by re-enabling DEP:https://support.steampowered.com/kb_article.php?ref=2117-ilzv-2837&l=english
Obviously all of this is VERY easy to test. It doesn't matter what version of Windows you are on. If you don't believe that this could be the culprit, then instead of replying to this thread with the expected insults, go ahead and disable DEP and PAE for a full gaming session or two. If you survive a week afterword or through the next banwave then you are truly a brave and courageous individual and I will bow down and worship you.
And finally, for anyone who is experiecing the slow loading and freezing issue while trying to open your inventory screen, you are probably using a 32-bit operating system. If you add the /3GB option it completely resolves this problem. However, it's not actually fixing the problem by allowing Diablo to use more memory, because I don't even think Diablo is LargeAddress aware, but it re-maps the memory and circumvents a bug in Diablo's engine that was introduced in Patch 2.4: https://www.reddit.com/r/Diablo/comments/4jz6qb/fix_for_those_affected_by_inventory_screens_that/
hebnebs, just because you cheated, doesn't mean we all did. For those of us genuinly affected by a false-positive, your post and others like it just come across as ignorant and immature. You're not helping anyone, and you're just trying to start an arguement. Go troll somewhere else. It's sad that people can't behave and have a decent conversation without people like you trying to jump in wherever possible to stir the pot. We don't really care what you have to say. Thanks for trying.
TLDR: Here are the possible conflicts. Please reply if something you have matches one of these.
1) Windows XP or a 32-bit Operating System
2) Nvidia Drivers, an EVGA graphics card, a GTX 950, or an overclocked GPU
3) Google Chrome or an Adblocker like UBlock Origin
4) Skype
5) HP Printer
6) TCP Optimizer from speedguide.net
Main Post:
It's sad to see even more people are being affected. I think something that is overlooked by those who weren't wrongfully banned, is that the vast majority of gamers do not visit forums, or furthermore create accounts to login and post. What i'm trying to say is that we are like ants, for every one of us you see posting here about being wrongfully banned, there are many many more beneath the surface.
There was another thread that died out which discussed what we all had running on our PC's, so we could tie it together and figure out the cause. I think my system is probably the most clean of all people affected. My gaming computer is literally just that, only used for gaming, and I usually only play/install 1 game at a time. I'm super OCD about having my system in pristine operating performance, so I reformat every 3-4 months and always use the latest official drivers and keep as much bloat and other crap off my system as possible.
I was using Windows XP, 32-Bit. Since Diablo 3 launched my PC hasn't changed. So whatever I got "detected" for last month, was also there on May 15th, 2012 when I first started playing the game. The only exception to this, is that I switched out the Graphics Card from a GTX 580 to a GTX 950 a few weeks before I was banned, because my card died. I find it very suspicious, and coincidental. I'm believing that caused my ban somehow. My new EVGA 950 comes pre-overclocked, and I wonder if the new drivers or the built-in overclock interfere with Warden.
One of the other things that came to mind, is battle.net had an update somewhere around May or June where they added "Browser Hardware Acceleration" to the interface options. Ever since then, my Battle.net flickered and had graphical anomalies whenever I would go into the options or hover over buttons. It occurred with the new acceleration feature turned on and off. I believe this is a conflict with Chrome, their version of Flash, or my adblocker.
It has to be one of those things. My PC is so bare bones compared to everyone else. Idling at the desktop, task manager shows about 178mb of Ram usage. I don't have microsoft bloat, a bunch of services running, lots of software installed, viruses/malware of any kind, etc. It's very clean.
I'm in the same boat. I don't have anything on my count that anyone here would consider as indications of botting. I don't use cheats, exploits, bots, scripts, macros, whatever. I have low playtime on my account, low rifts completed, low bounties, etc. In Season 6 which is the most I've ever played, I have a 4 hour day average over the season. Prior to the last few months, since I've had a change in my real life work schedule, and home life, I was only able to average less than 2 hours a day. I'm not some super paragon crazy guy with awesome items.
I simply got mistaken by Warden for some reason. I don't understand. Even if I got my account back right this second, I don't know what to do to keep from being flagged again. I can't change anything at all on my computer, it's already stripped barebones and optimized for gaming. It's freshly reformatted with just battle.net, Diablo, Skype, and the latest official microsoft updates, and necessary drivers for functionality.
That's it, there just isn't anything else to the story. Why is it so hard for fanboys to realize that Blizzard can make mistakes? Just last month they did a huge Diablo 2 banwave and tons of legit players were banned. Blizzard realized the mistake because of how many people were affected and issued a public apology as seen in the link below, but it's not the first time. Last year they issued another huge ban wave to Heroes of the Storm players because they had "hooks" into the game. Turns out these "cheats" were just Xonar Audio drivers and Nvidia Graphics drivers causing a conflict with Warden, as such they apologized and unbanned players. And even in Diablo 3 in 2012 they banned tons of Linux players, because the Wine operating system was conflicting with Warden.
How much more proof do you need that Warden can make mistakes? It's happening again, these latest ban waves have more "false-positive" than any other D3 ban wave.
0
My post ONLY applies to people who were banned but were honestly not using a bot, maphack, or other unauthorized 3rd party software that might be responsible.
Here's the quiz for you:
1) Did you disable DEP, also referred to as the NX bit?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /noexecute=AlwaysOff
B] Entering in the command line - bcdedit.exe /set {current} nx AlwaysOff
2) If you have DEP disabled, did you then add the /PAE option to enable that?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /PAE
B] Entering in the command line - bcdedit /set [{ID}] pae ForceEnable
3) Regardless of the above settings, did you enable the LargeAddressAware option?
(If you are unsure, do either of these things look familiar to you. If so then you should answer 'Yes')
A] Editing the boot.ini file to show - /3GB or /userva=
B] Entering in the command line - bcdedit /set increaseuserva
If you answered Yes to any of these options, and you genuinely were not cheating at all, then that's probably what caused you to be banned. Here is a killer link showing that Steam's Anti-Cheat (VAC) also doesn't function with DEP disabled. Keep in mind this is an official support help page from Steam, and if you do some Googling you can see many forums topics about VAC issues being resolved by re-enabling DEP:https://support.steampowered.com/kb_article.php?ref=2117-ilzv-2837&l=english
Obviously all of this is VERY easy to test. It doesn't matter what version of Windows you are on. If you don't believe that this could be the culprit, then instead of replying to this thread with the expected insults, go ahead and disable DEP and PAE for a full gaming session or two. If you survive a week afterword or through the next banwave then you are truly a brave and courageous individual and I will bow down and worship you.
The PAE portion is important as well. It seems to cause its own set of problems. From my research, this appears to have actually been what may have caused those WINE users to be banned in 2012. Look at the "HOWTO: Run Diablo III on a 64-bit machine" section, Diablo doesn't play nicely when PAE is disabled: (Reaper of Souls) https://appdb.winehq.org/objectManager.php?sClass=version&iId=29952 and (Diablo III) https://appdb.winehq.org/objectManager.php?sClass=version&iId=25953.
And finally, for anyone who is experiecing the slow loading and freezing issue while trying to open your inventory screen, you are probably using a 32-bit operating system. If you add the /3GB option it completely resolves this problem. However, it's not actually fixing the problem by allowing Diablo to use more memory, because I don't even think Diablo is LargeAddress aware, but it re-maps the memory and circumvents a bug in Diablo's engine that was introduced in Patch 2.4: https://www.reddit.com/r/Diablo/comments/4jz6qb/fix_for_those_affected_by_inventory_screens_that/
1
hebnebs, just because you cheated, doesn't mean we all did. For those of us genuinly affected by a false-positive, your post and others like it just come across as ignorant and immature. You're not helping anyone, and you're just trying to start an arguement. Go troll somewhere else. It's sad that people can't behave and have a decent conversation without people like you trying to jump in wherever possible to stir the pot. We don't really care what you have to say. Thanks for trying.
0
TLDR: Here are the possible conflicts. Please reply if something you have matches one of these.
1) Windows XP or a 32-bit Operating System
2) Nvidia Drivers, an EVGA graphics card, a GTX 950, or an overclocked GPU
3) Google Chrome or an Adblocker like UBlock Origin
4) Skype
5) HP Printer
6) TCP Optimizer from speedguide.net
Main Post:
It's sad to see even more people are being affected. I think something that is overlooked by those who weren't wrongfully banned, is that the vast majority of gamers do not visit forums, or furthermore create accounts to login and post. What i'm trying to say is that we are like ants, for every one of us you see posting here about being wrongfully banned, there are many many more beneath the surface.
There was another thread that died out which discussed what we all had running on our PC's, so we could tie it together and figure out the cause. I think my system is probably the most clean of all people affected. My gaming computer is literally just that, only used for gaming, and I usually only play/install 1 game at a time. I'm super OCD about having my system in pristine operating performance, so I reformat every 3-4 months and always use the latest official drivers and keep as much bloat and other crap off my system as possible.
I was using Windows XP, 32-Bit. Since Diablo 3 launched my PC hasn't changed. So whatever I got "detected" for last month, was also there on May 15th, 2012 when I first started playing the game. The only exception to this, is that I switched out the Graphics Card from a GTX 580 to a GTX 950 a few weeks before I was banned, because my card died. I find it very suspicious, and coincidental. I'm believing that caused my ban somehow. My new EVGA 950 comes pre-overclocked, and I wonder if the new drivers or the built-in overclock interfere with Warden.
One of the other things that came to mind, is battle.net had an update somewhere around May or June where they added "Browser Hardware Acceleration" to the interface options. Ever since then, my Battle.net flickered and had graphical anomalies whenever I would go into the options or hover over buttons. It occurred with the new acceleration feature turned on and off. I believe this is a conflict with Chrome, their version of Flash, or my adblocker.
It has to be one of those things. My PC is so bare bones compared to everyone else. Idling at the desktop, task manager shows about 178mb of Ram usage. I don't have microsoft bloat, a bunch of services running, lots of software installed, viruses/malware of any kind, etc. It's very clean.
3
I'm in the same boat. I don't have anything on my count that anyone here would consider as indications of botting. I don't use cheats, exploits, bots, scripts, macros, whatever. I have low playtime on my account, low rifts completed, low bounties, etc. In Season 6 which is the most I've ever played, I have a 4 hour day average over the season. Prior to the last few months, since I've had a change in my real life work schedule, and home life, I was only able to average less than 2 hours a day. I'm not some super paragon crazy guy with awesome items.
I simply got mistaken by Warden for some reason. I don't understand. Even if I got my account back right this second, I don't know what to do to keep from being flagged again. I can't change anything at all on my computer, it's already stripped barebones and optimized for gaming. It's freshly reformatted with just battle.net, Diablo, Skype, and the latest official microsoft updates, and necessary drivers for functionality.
That's it, there just isn't anything else to the story. Why is it so hard for fanboys to realize that Blizzard can make mistakes? Just last month they did a huge Diablo 2 banwave and tons of legit players were banned. Blizzard realized the mistake because of how many people were affected and issued a public apology as seen in the link below, but it's not the first time. Last year they issued another huge ban wave to Heroes of the Storm players because they had "hooks" into the game. Turns out these "cheats" were just Xonar Audio drivers and Nvidia Graphics drivers causing a conflict with Warden, as such they apologized and unbanned players. And even in Diablo 3 in 2012 they banned tons of Linux players, because the Wine operating system was conflicting with Warden.
How much more proof do you need that Warden can make mistakes? It's happening again, these latest ban waves have more "false-positive" than any other D3 ban wave.
Here's some more information at reddit: https://www.reddit.com/r/Diablo/comments/4qhqke/banwave_incomin/d4t58qz
0
https://www.reddit.com/r/Diablo/comments/4r591o/what_is_happening_at_blizzard/