JavaScript is required to use Bungie.net

Forum

1/19/2025 11:21:34 PM
6
Hi there! Please follow the steps outlined below to provide an accurate system report. Please do not follow these steps while Destiny 2 is running. 1. Restart your machine. 2. When you log in, please click on the Windows icon, then type dxdiag. If typed correctly, only one command should appear. Please click it. (If you need to enter the credentials of an administrator of the PC, please do so). 3. Allow the tool to run. A green bar should progress on the bottom portion of the window. If you receive any dialogue boxes as it progresses, please address them accordingly. 4. Once the tool is completed, please click on the "Save All Information" button. Save the resulting text file in an easy to find location, such as your Desktop. Then, close the tool. 5. Open the text file you just created and copy all of text to your clipboard by selecting all of it (Ctrl+A) and copying it (Ctrl +C OR rightclick and click Copy). Then, close the file. 6. Go to pastebin.com 7. In the text box below, paste all of the text in the box. 8. If you would like to make your system specs hidden, you can change the Paste Exposure to Unlisted. This will hide it from the Public section of the site but still allow people to view your Paste. Then, click the Create New Paste button. 9. Copy the resulting URL and reply back to this comment with the URL.
English

Lingua:

 

Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • Mine ended up being a bad stick of RAM. Found this out through looking through the Event Viewer and noticing different apps crashing as a result of memory errors. Ran Windows Memory Diagnostic and isolated the bad stick and so far haven't had any more Marmot. Hopefully this helps someone going through the same issue.

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • Thoughts?

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • Hi there! Thank you for your patience. According to the DxDiag report, you have multiple LiveKernel and crash events, related to event 139. These error codes normally indicate an issue with a driver on your system. However, the DxDiag is not indicating as to which particular driver it is having an issue with. AMD chipsets can have issues based on the BIOS that is installed on your mainboard. I would advise that you review your system and the BIOS version installed to ensure that there are not any known issues related to that version or any potential issues with it. I would also recommend reviewing any installed applications and uninstalling any unused or unneeded applications, as I noticed in the report that there were some crashes related to some other applications.

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • I did a complete PC refresh from scratch and kept no settings or apps or data. Reinstalled Windows just fine and Windows runs without any errors whatsoever. Installed Steam and Destiny 2 clean and logged in, and within 5-10 minutes another marmot. I refuse to believe this is my system. Application Error log for destiny2.exe below: Log Name: Application Source: Application Hang Date: 1/27/2025 11:09:56 PM Event ID: 1002 Task Category: Hanging Events Level: Error Keywords: User: SYSTEM Computer: REDACTED Description: The program destiny2.exe version 34168.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Hang" Guid="{c631c3dc-c676-59e4-2db3-5c0af00f9675}" /> <EventID>1002</EventID> <Version>0</Version> <Level>2</Level> <Task>101</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2025-01-28T06:09:56.2169518Z" /> <EventRecordID>1127</EventRecordID> <Correlation /> <Execution ProcessID="14684" ThreadID="18296" /> <Channel>Application</Channel> <Computer>REDACTED</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="AppName">destiny2.exe</Data> <Data Name="AppVersion">34168.0.0.0</Data> <Data Name="ProcessId">0x34a4</Data> <Data Name="StartTime">0x1db714a5587a087</Data> <Data Name="TerminationTime">4294967295</Data> <Data Name="ExeFileName">C:\Program Files (x86)\Steam\steamapps\common\Destiny 2\destiny2.exe</Data> <Data Name="ReportId">37d14ec8-abc6-4d02-9587-807595b0d1a6</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> <Data Name="HangType">Top level window is idle</Data> </EventData> </Event>

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • https://pastebin.com/hYCMXzau

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

Non ti è permesso visualizzare questo contenuto.
;
preload icon
preload icon
preload icon