No error code? Read here for extended diagnositics (support the Dev team!)
by The_TibberOriginal Post
Hello!
Here i will be guiding you through how to supply our Dev's with as much info as we can give them to help resolve issue's.
This guide can be used for any other game aswell since its information supplied outside of the game.
(You can supply this information on top of ingame Error codes so Dev's have all the resources you can supply to them)
1. Dxdiag
A guide for this has already been made Here.
Dxdiag supplies the information about your PC.
Drivers and there versions.
Connected Devices and many other small details that could be significant to finding a fix or a cause to your issue.
2. Windows Event Viewer
Windows Event Viewer (W.E.V.) Is a feature in windows that logs all information good or bad.
Note: its required that you know what time and date the crash happened in order to supply the correct information.
To find this open your start search and type: eventvwr.msc
Once opened click the Event Viewer (Local) in the top left.
In the "Summary of Administrative Events" panel you can see how many events have been made in certain time periods, Last hour, 24 Hours and 7 Days.
(ProTip: you can minimise the other center panels by clicking the small arrow to the right.)
Now click the + boxes to the left of Critical, Error and Warning to expand the event list.
Events made after an hour would be in the 24 Hour section and 7 Days section but not in the Last hour section.
Some events are in the 24 Hours section but not in the Last hour section because the event is older than a hour.
When you start browsing for the events that happened at the time of the crash you can click an event and be sent to the Summary page events.
If the event did not occur on that time you can click the blue back button on the top left.
Once you find the relevent event/s (there can be more than one event log for a game crash)
Right click the event, select copy and click "Copy Details as Text".
Then go to your browser and open a topic for Technical Issues or Bug Reports.
Explain the details of your issue and click the brown spoiler icon on the top left when you wish to post the details of the events.
Like so:
Source: Application Error
Date: 16/02/2019 21:41:07
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-SE9MCTC
Description:
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process ID: 0x287c
Faulting application start time: 0x01d4c640439b78da
Faulting application path: bad_module_info
Faulting module path: unknown
Report ID: a6e88cdb-c236-4c2d-bebc-afb66fa2578d
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="2019-02-16T21:41:07.192775800Z" />
<EventRecordID>9434</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-SE9MCTC</Computer>
<Security />
</System>
<EventData>
<Data>bad_module_info</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>00000000</Data>
<Data>0000000000000000</Data>
<Data>287c</Data>
<Data>01d4c640439b78da</Data>
<Data>bad_module_info</Data>
<Data>unknown</Data>
<Data>a6e88cdb-c236-4c2d-bebc-afb66fa2578d</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
------------------------------
(next Event)
------------------------------
(next event)
In this example you can see the refrences to Bad_Moudle_Info which is a know issue, you can reply to the post with this information to organise the forums. 
and thats it! 
