JavaScript is required to use Bungie.net

Help - Destiny 2

Help us help you.
Edited by GWraith: 11/13/2017 10:53:41 PM
3

PC Crashes

Well, prior to the last couple hotfixes I fixed my crashes by running the blizzard launch and D2 in administrator mode. Recent hotfix made this actually crash D2 more. Anyways I have to start my game somewhere between 4-10 times before it starts and it randomly crashes within 30 min to 3 hours. Normally it crashes when things are getting intense in game, but dull moments it has happened as well. Here is the windows event viewer crash report, I have HUNDREDS like this for D2. Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 60642.0.0.0 P3: 59fbbbc6 P4: destiny2.exe P5: 60642.0.0.0 P6: 59fbbbc6 P7: c0000005 P8: 00000000070e4959 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4764.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_destiny2.exe_456b6af05016f84397ffea480e593c622affaf0_54078061_220771a5 Analysis symbol: Rechecking for solution: 0 Report Id: ef2ddec4-be4d-478e-a6b2-b7e7776cbbf7 Report Status: 4196 Hashed bucket: Cab Guid: 0 My current build: OS Name Microsoft Windows 10 Pro Insider Preview Version 10.0.17025 Build 17025 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name OMITTED System Manufacturer MSI System Model MS-7893 System Type x64-based PC System SKU To be filled by O.E.M. Processor AMD FX(tm)-9590 Eight-Core Processor, 4800 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date American Megatrends Inc. V1.4, 12/24/2015 SMBIOS Version 2.8 Embedded Controller Version 255.255 BIOS Mode Legacy BaseBoard Manufacturer MSI BaseBoard Model 990FXA GAMING (MS-7893) Ver. 1.0 BaseBoard Name 990FXA GAMING (MS-7893) Ver. 1.0 Platform Role Desktop Secure Boot State Unsupported PCR7 Configuration Binding Not Possible Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume3 Locale United States Hardware Abstraction Layer Version = "10.0.17025.1000" User Name OMITTED Time Zone Eastern Standard Time Installed Physical Memory (RAM) 16.0 GB Total Physical Memory 16.0 GB Available Physical Memory 12.5 GB Total Virtual Memory 18.8 GB Available Virtual Memory 15.0 GB Page File Space 2.88 GB Page File C:\pagefile.sys Virtualization-based security Not enabled Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware Yes Hyper-V - Data Execution Protection Yes GPU Information is in the attached link in a GPU-Z GIF as well as CPU-Z profile txt. https://drive.google.com/open?id=1CyqjShGEPovWWLjwpR8ok_KwN5jcnF1A https://drive.google.com/open?id=1scn_QaByIkXTipIDRje-GoaIVIB4h68E Motherboard BIOS is uptodate. GPU BIOS is uptodate. All drivers are uptodate. Windows is fall creators update. Happens with game bar on or off. All the hardware is relatively new and the motherboard was just replaced less than 2 months ago, son poured hand sanitizer on the CPU PWM. I have a gold rated 750W PSU that should be more than capable of handling the load. And all items were benched before reassembly a few months ago. This is the only game I have significate problems with. Any help would be appreciated!
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

  • Newest hotfix seems a ton more stable.

    Posting in language:

     

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

  • Well after a few days of testing I still do get crashes but far less frequent since I disabled the page file. This could indicate some sort of permissions error with HDD vs RAM. Bungie IS getting information on these crashes as I have witnessed that everytime the game crashes a Bungie error handler open collects then transmits data. I have tried to change the game to compatibility mode for windows 7 and the game would not start at all. I want to see if the security difference between windows 7 permissions and Windows 10 could be causing this issue more frequently. Hopefully, someone with windows 7 can chime in.

    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
    • So I decided to toy around a bit and found that if I remove my page file completely I haven't had any in-game crashes since and it only took me 2 tries to get the game started. Could be a fluke? Requires more testing.

      Posting in language:

       

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

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