{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Kell of Kellogs:
10/24/2017 8:55:09 PM
221
banned for nothing
Well I'm seeing many other people saying that they are being banned simply in the first second they are entering the game as I did not even have how to create the character and I did not have the possibility to enter I believe that the program has a bug I read all the rules and I did not nothing to be banned wanted an official response to believe in a bungie transparency.
if you have also been banned without doing anything post here to know the problem!
edit1: apparently a lot of people are being banned for some random reason even without any linked overlay application.
-
Edited by Zurv: 10/25/2017 6:35:28 PMI too was banned for no reason. I was just playing thru the story (i'm around level 14) then.. *poof* banned! Bliz won't won't return my money because i "played to long".. argh! This is BS. I was playing on a fresh install of windows 10 (1709 - "fall update") i9-7980, titan Xp SLI, no geforce exp, but using the 388.00 Destiny 2 drivers. software running, Outlook 2016, skype4b 2016, Edge, Remote desktop, battle.net launcher, Afterburner 4.4.- beta 19, logitech gaming keyboard/mouse software, core temp. I was banned around 5:20PM EST (10/24/2017, day of launch) clearly I played some hours as I made it to level 14. Of note is i crashed, about what felt like 30min, before i was banned. looking thru the event logs, the only errors I see from Desinty2 are as follows: [quote] Log Name: Application Source: Application Error Date: 10/24/2017 11:11:22 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-UJTGCQS Description: Faulting application name: destiny2.exe, version: 60349.0.0.0, time stamp: 0x59e12ae8 Faulting module name: destiny2.exe, version: 60349.0.0.0, time stamp: 0x59e12ae8 Exception code: 0xc0000005 Fault offset: 0x0000000000cf0730 Faulting process id: 0x34fc Faulting application start time: 0x01d34d2466255813 Faulting application path: D:\Games\Destiny 2\destiny2.exe Faulting module path: D:\Games\Destiny 2\destiny2.exe Report Id: 9b04701e-801a-443f-940e-b0690161907e Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-10-25T03:11:22.454615700Z" /> <EventRecordID>2072</EventRecordID> <Channel>Application</Channel> <Computer>DESKTOP-UJTGCQS</Computer> <Security /> </System> <EventData> <Data>destiny2.exe</Data> <Data>60349.0.0.0</Data> <Data>59e12ae8</Data> <Data>destiny2.exe</Data> <Data>60349.0.0.0</Data> <Data>59e12ae8</Data> <Data>c0000005</Data> <Data>0000000000cf0730</Data> <Data>34fc</Data> <Data>01d34d2466255813</Data> <Data>D:\Games\Destiny 2\destiny2.exe</Data> <Data>D:\Games\Destiny 2\destiny2.exe</Data> <Data>9b04701e-801a-443f-940e-b0690161907e</Data> <Data> </Data> <Data> </Data> </EventData> </Event> [/quote] [quote]Log Name: Application Source: Windows Error Reporting Date: 10/24/2017 1:14:46 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: DESKTOP-UJTGCQS Description: Fault bucket 129590558131, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 60349.0.0.0 P3: 10.0.16299.2.0.0 P4: P5: P6: P7: P8: P9: P10: [/quote]
