Matrix Games Forums

While playing DW2 v 1.0.3.3 the morning my PC shut down 4 times. The PC just turned off...black screen. I had to push the on button to get it started again. There was no power stutter, my UPS never blinked. I checked temps and found my cores running 25-27 deg C and my Nvidea 1070 running 57 deg C.
Using the Windows Event Viewer I can open the error log and see the four events and they all have DW2 as the application involved with the problem.
I do not know where to get the error log to send to you.
I have gone back to playing TW:Warhammer III problem free, as an indication of my PC's general health.

Also, the game is early. I have four colonies and all the tech is in the first three levels, 700 stars, seven empires.

I will go ahead and send the dxdiag file and the log file out of the DW2 folder, but they don't seem to have much. The Windows 10 crash file I was looking at did record the events.

There's no way that I'm aware of that DW2 could cause a computer to shut down. This would indicate to me some kind of hardware issue or very low OS level crash. DW2 does use a lot of resources though. If I were you I would try some diagnostics to check and make sure memory, CPU, GPU, etc. are fine and without issues.

You can check the Windows Event Viewer to see if it recorded anything at the time that these shutdowns happened. If you are seeing it listing DW2 as the source of the problem, then I would like to see all the details of those logs.

Here are the Dxdiag and Session files. There is no Crashdump file. I would love to post the error file that I viewed via the Event Viewer, but I don't know what file that is or where it is located. I was kind of hoping you could tell me where/what it is. I assume it is a Windows system file but I cannot find it.

Here is all I could dig up in Windows related to the crash times:

Information - Windows Error Reporting

Log Name: Application
Source: Windows Error Reporting
Date: 4/7/2022 1:15:41 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: D2-PC
Description:
Fault bucket 1665321481984798445, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DistantWorlds2.exe
P2: 1.0.3.3
P3: 9a25637e
P4: StackHash_4ffd
P5: 0.0.0.0
P6: 00000000
P7: 00000000
P8: PCH_11_FROM_ntdll+0x000000000009D8C4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C30.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D3B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D5B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D69.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D89.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DistantWorlds2.e_20e77780c5da689ee07def69b88c4786077e12f_be741524_b7290cb4-09de-448a-8179-79e8558a8621

Analysis symbol:
Rechecking for solution: 0
Report Id: d2c1d3a2-209e-480c-a766-55d8b1a4e7c4
Report Status: 268435456
Hashed bucket: 95401a4c63b60537e71c69108a87eeed
Cab Guid: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-07T18:15:41.1226761Z" />
<EventRecordID>38951</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>D2-PC</Computer>
<Security />
</System>
<EventData>
<Data>1665321481984798445</Data>
<Data>4</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>DistantWorlds2.exe</Data>
<Data>1.0.3.3</Data>
<Data>9a25637e</Data>
<Data>StackHash_4ffd</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>00000000</Data>
<Data>PCH_11_FROM_ntdll+0x000000000009D8C4</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C30.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D3B.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D5B.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D69.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1D89.tmp.txt</Data>
<Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DistantWorlds2.e_20e77780c5da689ee07def69b88c4786077e12f_be741524_b7290cb4-09de-448a-8179-79e8558a8621</Data>
<Data>
</Data>
<Data>0</Data>
<Data>d2c1d3a2-209e-480c-a766-55d8b1a4e7c4</Data>
<Data>268435456</Data>
<Data>95401a4c63b60537e71c69108a87eeed</Data>
<Data>0</Data>
</EventData>
</Event>

And...

Error - Application Error

Log Name: Application
Source: Application Error
Date: 4/7/2022 1:15:39 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: D2-PC
Description:
Faulting application name: DistantWorlds2.exe, version: 1.0.3.3, time stamp: 0x9a25637e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x00007ffb4381c1de
Faulting process id: 0x1ff0
Faulting application start time: 0x01d84aab7b40186a
Faulting application path: E:\Matrix\Distant Worlds 2\DistantWorlds2.exe
Faulting module path: unknown
Report Id: d2c1d3a2-209e-480c-a766-55d8b1a4e7c4
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>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-07T18:15:39.4507393Z" />
<EventRecordID>38950</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>D2-PC</Computer>
<Security />
</System>
<EventData>
<Data>DistantWorlds2.exe</Data>
<Data>1.0.3.3</Data>
<Data>9a25637e</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>00000000</Data>
<Data>00007ffb4381c1de</Data>
<Data>1ff0</Data>
<Data>01d84aab7b40186a</Data>
<Data>E:\Matrix\Distant Worlds 2\DistantWorlds2.exe</Data>
<Data>unknown</Data>
<Data>d2c1d3a2-209e-480c-a766-55d8b1a4e7c4</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

The above post was about the shut-downs I had at lunch. I tried to play again and the game crash again. This time, the PC rebooted by itself. I found this error message:

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 4/7/2022 8:40:50 PM
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: D2-PC
Description:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
<EventID>3</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2022-04-08T01:40:50.7359278Z" />
<EventRecordID>610</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="176" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>D2-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Microsoft Security Client OOBE</Data>
<Data Name="FileName">C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl</Data>
<Data Name="ErrorCode">3221225485</Data>
<Data Name="LoggingMode">8388613</Data>
<Data Name="FailureReason">2</Data>
</EventData>
</Event>

If you haven't already, I would recommend cleaning and reinstalling your nvidia drivers and doing a Windows system integrity check. Sometimes a bit of corruption will affect a specific game, even when others work fine.

Another thing to try would be borderless windowed mode.

...but yeah, I doubt you are going over your RAM/VRAM pool. Only thing I'm suspicious of is that 27C load temp on your 4770, as it should be a bit warmer than that, even with a custom water loop.