{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Griffilicous:
11/17/2017 2:50:52 PM
39
Intel crash compilation thread (update Possible Fix Found!!!!)
Update 11/17/2017 MAY HAVE FOUND A FIX
After tons of trial and error, I was only able to prolong gameplay by a marginal span of time by reducing the overall render resolution to 75%-80%. This was a bandaid that still led to crashes and going down from 3440x1440p 21:9 aspect ration was unacceptable. I then figured there has got to be a way to squeeze out near 4K native resolution without crashes. It came to me last nite, manually capping the frame rate! With a quick search I found this video.
https://youtu.be/UmYIO7IrGiU
I followed the directions by rewriting the cvars.xml file in notebook and setting the FPS cap from “0”(which is uncapped causing to instability) and setting the value to “60”. After I was done went into the cvars.xml properties and set as read only so the game wouldn’t automatically rewrite this setting. Long story short I was able to finish the campaign and haven’t crashed since!
Use the intrusions above and set your FPS cap manually to attleast 60 and move it up in increments until you find instability at your native resolution and then back it down by 4 FPS. Also make sure V-sync is turned off in the game. Please report back to me if this fixes it for you. But with that said, Bungie still needs to implement a FPS adjustment in the setting menu tab. Good luck guys!
*Please upvote so that the game breaking crashes get addressed*
I guess it's finally time to get a refund. It's been a whole two weeks since launch and a lot of us with Intel processors on PC have not been able to play for 3+minutes without a hard crash, or crash to desktop. Cozmo has had two TWUB's to att least mention the problem, but he doesn't want to (Not even an addition the PC known issues list).Below is links just from the first 4 pages of the Help forum of other players with the same issue for those of you that want to dismiss this post.
Honestly how can you go on and talk about the next DLC, Trials, and the Raid on PC when a large portion of your player base CAN'T EVEN PLAY SINCE LAUNCH? With all of the games that have come out since October, and Call of Duty World War II today you are simply going to loose all of us. Att least WB games had the decency to pull Batman Arkham Knight off the shelves, and issue an apology when they had a similar launch. What does Bungie do? They pretend everything is fine and have the audacity to pimp out their next paid expansion with no mention of the huge player base that is getting left behind that can't even play the vanilla game without crashing!
Edit:
Just thought you would like to know, have been playing Call of Duty World War II on 3440x1440p on ultra settings and it has been playing flawlessly without a hitch for hours! Maybe Bungie should take notes from their big brother in how to do a proper PC launch.
Huge update:
Segmentnext.com has just wrote an article on our issue
Link below!
https://segmentnext.com/2017/11/03/many-still-not-able-play-destiny-since-launch-intel-nvidia-user-base-facing-issues/
Update: 11/6/2017
Still nothing on BungieHelp's Twitter, or an addition to the known issues list in the #Help Forum. But our thread and problem has been acknowledged by PCInvasion.com! Link is below
https://www.pcinvasion.com/destiny-2-pc-issues-framerate-crashes
Update: 11/8/2017
Bungie makes it a priority to fix Silver/Microtransactions on XBOX rather than fixing our hard crashes that make completing the vanilla campaign on PC impossible. This shows you where their priorities lie. BTW the micro transaction bug was found only yesterday and is fixed already. How does that make you guys feel?
Update: 11/10/2017
Issue has finally been mentioned in the TWAB! Hopefully we are able to play before the release of Curse of Osiris. Finally a ray of hope!
Update: 11/15/2017
Curse of Osiris stream goes live today, still no mention of a fix incoming from Bungiehelps Twitter account. Guess we are getting left behind, please post up if you guys are able to get refunds.
Community links:
https://www.bungie.net/en/Forums/Post/237347361?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237228130?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237349016?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237278239?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237254894?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237264784?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237359097?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237356883?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237231759?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237375666?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237230404?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237371109?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237363721?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237356473?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237349399?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237232541?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237124359?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237224682?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237205629?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237676200?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237715588?sort=0&page=0
https://www.bungie.net/en/Forums/Post/237717487?sort=0&page=0
-
Edited by Faulted: 12/1/2017 6:36:56 AMI'm having the same issue here. I just bought the game yesterday, and have had problems with the game freezing (and not generating an error report) during every play session so far. I can't tell what triggers it, but it seems like it can happen both on the title screen and while playing in the open world. When it occurs my screen freezes and all sound stops, but I'm still able to alt-tab. However, when I tab back in the screen is black. I tracked down my crash logs, and in all of them this is the only information listed: 11.30.17 16:43:14.957 [Misc][Log] Starting 'screenshot' (unknown) 11.30.17 16:43:14.957 [Misc] 0% bug_screenshot.bmp It's a shame really. I was on the hook about even purchasing the game after seeing the feedback, but figured I would still enjoy playing. *Update* Tried playing again with the suggestions listed in this post and had the game crash during a cutscene.
-
Literally tried everything and my game still freezes and has to be force closed all the time.
-
1 ReplyEdited by Notorious One: 11/21/2017 4:22:44 PMI went into cvars and set vsync to 0 and frame limiter to 60 and now the game doesn't crash but I'm getting really bad screen tearing at 60fps on a 60hz monitor with vsync off. If I turn vsync back on while playing the screen tearing goes away but game crashes shortly after. Is there anyway to stop the screen tearing using these settings or no?
-
1 Reply[quote]Update 11/17/2017 MAY HAVE FOUND A FIX [/quote] not working for me :(
-
8 RepliesAnother update and a bump. Just submitted a support ticket with Blizzard, I’ll let you guys know if I’m able to get a partial or full refund for the Deluxe edition.
-
I've been crashing all the time since launch. Windows is up to date, all drivers are up to date, my BIOS is up to date, nothing is overclocked. I've made sure both the Blizzard app and Destiny 2 are allowed to communicate through Windows Firewall. I've enabled/disabled Windows Game Mode. I've ran memory tests overnight with no errors, I've ran graphics card stress tests with no errors. I've monitored PC temperatures, nothing is overheating, I've taken my computer apart and cleaned everything very thoroughly. I've monitored CPU/Memory usage while playing, and it never spikes into high numbers. I've fiddled endlessly with in game settings. I've made sure nothing else is running in the background while trying to play. I've tried every suggestion I can find on various forums/posts. I've completely reinstalled Windows, downloaded only Blizzard/Destiny. Nothing I do matters, I keep crashing and the crash report is the exact same every time. CPU: Intel Core i5-3570k GPU: GeForce GTX 660 RAM: 8gb OS: Windows 10 v1703, forcing update to 1709 through MS website at the time of this post. dxdiag: https://pastebin.com/MJvxipSw Crash Log from Destiny 2's temp folder: https://pastebin.com/txXA74Kb Crash Report from AppCrashView: https://pastebin.com/47XG1hqJ Additional AppCrashView info: 0xc0000005 Access Violation 0x00cf2880 Some Observations: The crashes are not consistent, and seem much, much worse during some PvE activities. I can play Crucible for hours on end without crashing, but it still does crash with the same errors. I was crashing last week during the raid every 30ish minutes, then it stopped and I was able to finish the raid without crashing. I can play through the Campaign without much issue, though it will randomly crash still. Public events are the worst and crash the most frequent, with the planet Titan being infinitely worse than any other location. I can just be standing in a random location on Titan and I'll crash, but this really isn't the case anywhere else.
-
Same here. But only since 1.0.6.2 https://www.bungie.net/en/Forums/Post/238430794?sort=0&page=0
-
1 ReplyCPU: Intel Core i5-4690k GPU: Radeon RX 480 RAM: 16gb Windows 10 version 1709 I've updated, reverted, reinstalled operating system and drivers. I've run game file fixes. I've tried doing a clean boot (killing all start up programs and all non-microsoft services). I've tested (memtest) and swapped ram. I've installed fresh Windows and only installed Destiny 2. Nothing helps. It's always the same result. I can launch the game and it runs just fine, not a single hitch. Then randomly, the game will freeze. The image stays on the screen frozen, but the music keeps playing. Sometimes the game will crash itself. Other times I have to force close through the task manager. This can happen after a few minutes,. or maybe up to 10 minutes if I'm lucky. Just throwing my name in the mix
-
1 Replyhttps://www.bungie.net/en/Forums/Post/238199942 Configuration Info CPU: Intel Core i7-4770k GPU: Nvidia GeForce GTX 960 4GB RAM: 16GB DDR3 GPU Driver Version: Nvidia 388.00 Operating System: Windows 10 (Version 1703) DxDiag: https://ufile.io/yebk6 Destination/Activity: All activities in Destiny 2 Description: I've been getting Buffalo error since launch like so many others, and I've yet to see a real response other then the slim info you give in your sticky thread. And the info there seems to be completly unrelated to 99.9% of all the Buffalo errors, from what I've read on the forums here. I am using battle.net, I own one PC, I have only installed Destiny 2 on this PC. It can happen any time during the game, even during cinematics. I try to roam around mostly, doing stuff like lost sectors and public events. Getting DC all the time in PVP and Strikes is not fair to the other players. Leviathan I can only dream about. The only pattern I've seen is that when I get the first Buffalo error of the day, I tend to get 2-5 almost immediatly after trying to log back in. Then it's back to "it can happen any time". Some days are worse then others. I've spent 100$ on a game I can't enjoy, and I am given no help. I will suffice for "We are aware of the issue BUFFALO and are working to fix it", and that it's caused by something else then you describe in your sticky. I will not buy anything Bungie has their name on in the future and I'm sure I'm far from alone on this, if you don't start to talk to the community and adress the issues. You'd think that a multimillion dollar company could afford to hire a few more ppl to answer forum-posts, at the very least. 1/100 post is not good enough. /A frustrated gamer who would love to play your fantastic game. ...and don't even think of sending me to blizzard, they will send me straight back here.
-
1 ReplySpeaking from the experience I had with D1's bugs that still persist to this day: Ask for a refund and only play the game when it's fixed. Bungie has the habit of saying that "all is working as intended" and ignoring issues players have. Even if said issue still happens (D1's Crota Sword disappearing for no reason, PC players being banned "because yes"). If you trust them, they'll only do as NRS/WB did with MKX and never fix the issue.
-
7 RepliesIf you are on Win10, have you updated to version 1709? Some people have been posting that after installing this latest major update, and then deleting the CVARS, that their crashes have disappeared. Therefore seems to have been a windows issue, which doesn’t surprise me since I have had lots of software affected by various windows updates, only to be fixed in a subsequent one.
-
5 RepliesHello, Thank you for reporting this issue, as well as compiling these other player reports. This issue has been escalated to our internal teams for investigation.
-
GPU: AMD Radeon R9 290 CPU: Intel 4790k @ 4.5 GHz GPU Drivers: 17.11.1 Ram: 16GB Problem: Game will randomly crash my PC. I have not been able to establish any pattern other than I cannot complete the final boss of the raid due to it crashing during damaging phases (Or at another random time).
-
1 ReplyEdited by LastChaos: 11/19/2017 4:42:40 PMI was completely fine until this most recent update. Now I can't play the game for more than 3 minutes before it hard crashes (PC resets). I have an i5 6600K and a GTX 1070. Temperatures are all fine. The only other game that has had an issue like this for me is overwatch. So I thought it might be blizzard, but Diablo III has never crashed on me. This is making me really angry that I can't play with my clan or any of my friends. A little more about this issue, the update prior to the current one, I had no crashes. Anything prior to that, my game would crash SOMETIMES. It was very intermittent. With the recent update, I can't play the game more than 3 minutes. Edit: can someone tell me how to get the crash logs? It'd be helpful to post them here Edit2: I found a fix. I made it so both the Destiny2.exe and battle.net launcher.exe run as administrator. Once that was done I haven't had a single crash. No idea why this fixes it, but I saw it in another thread and it worked for me!
-
1 ReplyI am at the point where I am ready to give up and get a refund from Blizzard. Keep holding onto hope for some reason that they will acknowledge the issue and fix it, but at this point that does not seem to be the case.
-
Edited by DarkFury: 11/6/2017 8:31:46 PMsame here.... my spec and my error cache: Mainboard: MSI x79A-GD45 CPU: Core i7-3930K @ 3.20GHz RAM: Corsair XMS3 16GB Grafik: MSI GeForce GTX 980 Monitor: ASUS ROG Swift Curved PG348Q Netzteil: Be quiet Straight Power E9 700 SSD: Samsung 850 EVO 1TB RAM: 16GB Corsair XMS3 DDR3 Windows 10 installed all up to date my Post: https://www.bungie.net/de/Forums/Post/237660792?sort=0&page=0 crash_info: stack: 00007FF7F12BD8CF <unknown> 00007FF7F12BCC3A <unknown> 00007FF7F12B88E2 <unknown> 00007FF7F1CA2688 <unknown> 00007FF7F130E748 <unknown> 00007FF7F1314DF7 <unknown> 00007FF7F1315172 <unknown> 00007FF7F1314F8D <unknown> 00007FF7F12FC87D <unknown> 00007FF7F130B27B <unknown> 00007FF7F130B36E <unknown> 00007FF7F130A5BE <unknown> 00007FF7F12D0AE2 <unknown> 00007FF7F12D4379 <unknown> 00007FF7F130A688 <unknown> 00007FF7F130A73F <unknown> 00007FFF59172774 <unknown> 00007FFF5B660D51 <unknown> session_id: Mon_11062017_201414_011848@x64@100742383@98_21_B6_88_EC_FF_8F89 halt: RELEASE_VHALT halt information: resourcerer:load: Failed to load tag 0x80BA843E (0x01d4 1086) with error error bad handle, {{!0x00000006!}} install type {{!5!}} fatal error detected, current status was: init: init.txt version: d2_live tiger_final release pc_x64 60642.17.11.02.1732.d2_live 17.11.02 1732 session_id: Mon_11062017_201414_011848@x64@100742383@98_21_B6_88_EC_FF_8F89 GPU Device: NVIDIA GeForce GTX 980 GPU VendorId: 4318 GPU DeviceId: 5056 GPU SubSysId: 829428834 GPU Revision: 161 silo_id: 1665943536958920704 signon_server_reported_content_version: none reported authority-over-current-bubble: false - map slice set 'HASH(0xade65e0a)':41, activity slice set 328 authority-over-domain: true world_controller state: activity:in_world environment_string: D2_ProdRetail:75 install type: 5 change-world: loaded edz_freeroam game_instance: 00000000F40AB4BA game_tick: time 27708 game_is_playback: false activity_tier: e_activity_tier.one activity-slice-set-index: 328 map-slice-set-index: 41 in-public-bubble: false activity_host_fireteam_is_connected: yes activity_host_last_fireteam_session_id: Mon_11062017_061155_097724@x64@game_svc_lp$@N07SH07SRV011 activity: patrol_black_blood activity_host_group_target_is_connected: no activity_host_group_target_session_id: Mon_11062017_103232_137624@x64@game_svc_lp$@N07SH03SRV011 activity_host_group_current_is_connected: no activity_host_last_group_current_session_id: Mon_11062017_103232_137624@x64@game_svc_lp$@N07SH03SRV011 system_milliseconds: time 515292958 timezone_seconds_offset_from_UTC: -3600 is_current_bubble_authority: false crash_folder_location: C:\Users\darkf\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64\crash_folder_11848_20171106_204214\ primary_bap_server_ip_address: 205.209.21.103 primary_bap_server_port: 7500 world_controller_state_manager status: activity:in_world (goal:002:activity:in_world) player_position_x: -419.673828 player_position_y: 803.581665 player_position_z: -17.681316 to much Crashes.... https://picload.org/view/drdpiawr/crash.png.html
-
Same issue here: i7 3770 - gforce 670 - 8gb ram - win 7 - all drivers up to date
-
2 RepliesJust go windowed mode, it solves it.
-
1 ReplyI bought the game and was excited to play it, after installing it I haven't been able to even do the first mission. The game crashes at 5-15 mins of gameplay. I checked if every component was up to date and they were all. I also checked if Windows was also updated and indeed it was. I really don't know what to do, I reinstalled the game, I lowered the graphics... and still the same crash. I am starting to feel desperate, I don't even know if Bungie will fix this. All the issues only happen with this game, the game just freezes and I can't get out of it to the home page, I just have to shut down my PC. Sometimes an error pops up and says "Destiny 2 stopped working, looking for a solution" The hotfix did nothing to me, I just want to play. If by a lot of time this doesn't get fixed I'll ask for a refund even if I don't want to, but this is getting insane. CPU: Intel i5 6400 GPU: AMD RX 480 OS: Windows 10 64 bits RAM: HYPERX 8GB DDR4
-
3 RepliesEdited by Fairyland: 11/6/2017 5:33:33 AMThe problem is Destiny 2 doesn't handle overclocked cards very well. This problem is only happening for people with gtx cards, and most gtx cards come overclocked already. You'll need to download a program like msi afterburner and remove the default overclock settings. I've tested this and it hasn't crashed in days. I run a 1070 and even without the overclock the game runs 60+ fps on max settings, so you probably wont notice a drop in performance unless your card is dated.
-
Bump to the top for the latest update to original post
-
Same Boat cant play. I might have been able to get a total of 3 hours since i purchased it. Feel like i wasted my money.
-
1 ReplyThat's crazy how they considered every other bugs, but not this one. Not even on the know issues... Unprofessional.
-
GPU: AMD Radeon R9 290 CPU: Intel 4790k @ 4.5 GHz GPU Drivers: 17.11.1 Ram: 16GB Problem: Game will randomly crash my PC. I have not been able to establish any pattern other than I cannot complete the final boss of the raid due to it crashing during damaging phases (Or at another random time). I've accepted I'm not gonna get a refund for a game that's ultimately broken for myself and so many others. A free seasons pass would be nice. P.S. I have extensively stress tested my computer and have determined the problem is not on my end. P.P.S. I have noticed that the recent hotfixes have seemed to make the problem worse, I crash much more frequently recently. Link to my post: [url]https://www.bungie.net/en/Forums/Post/237753940[/url]
-
Hi there, I made my own thread aswell because I get serious hard crash (like if my power supply was in cause, but it's not). https://www.bungie.net/en/Forums/Post/237689530 Made full test with Geeks3D FurMark + CPU Burner for like 1-2 hours ==> no crash at all so it's 100% coming from Destiny 2 !
-
1 ReplyI just built a new system..... everything is f**king brand new and I am having random crashes after the first day. I've done all my checks, rebooted and monitored everything as I go and it just poof like a fart in the wind crashes randomly. i7 7700k 4.2 asus rog maximus ix code corsair vengence 16gb (2x8) @3200 mhz Evga gtx 980 ti classified 6gb vram hds are brand new and have passed every test drivers are all updated and mind you this is a fresh install from nov 3. So why the -blam!- am I still freezing enough to have to sign out of windows just close the -blam!-ing program? 2 weeks and same problem on two systems as my other one has this problem as well
