Random crashing!


#41

I made these changes and still crashed. I don’t understand how this game eats up 60% GPU standing around doing nothing and near 100% when approaching a portal. I have Task Manager (Performance) up all the time on a separate monitor that I watch. I am standing nowhere near portals when I crash and the GPU is only at 60%. Changing the settings you said to change did not change the GPU amount being eaten up. When I crashed it spiked to 100% GPU until the monitor turned back on. But before than it was at 60%. I don’t understand what is going on. Once the game is done crashing and I try to reopen the game via STEAM, the monitor goes blank and I have to unplug and replug the monitor. This is with the GPU at 0% because the game is just being reopened.


#42

Crashed last night. Came back to this error and had to unplug and replug my monitor 3 times before it would let me play: default texture not created - failed to init D3D Texture (0x887a0005). The GPU would jump from 0% to 100% when I tried running Boundless and the monitor would say No Signal. Not sure what is going on. Any suggestions? I can have a graphic-intensive game on with 2 monitors, streaming on one screen, internet on another and a game on the main screen with no issues with any other game.


#43

The Testing version does have a fix for the specific crash you were seeing when the window resized - however its very likely it will crash elsewhere or appear blank since its really an out of vram issue.

So the issue is why are you running out. I see~3gb usage at 1080p when I run it around city a with many portals. Your card is 4gb plus you should have ‘shared ram’ of a few gb more so should be more than enough.

If you open Task Manager and click on the Performance tab and then on the GPU before starting Boundless what do you see for Dedicated GPU memory usage (should be low eg 0.2 of 4GB) and Shared GPU memory eg 0 of 8gb.

Its possible some other app is using a lot or one of the in game overlays is doing something odd. Try disabling the Steam Overlay (Steam->Settings->In Game) and Geforce Experience. If your running the Steam Beta (Steam->Account) try the non Beta Steam.


#44

Thanks for getting back to me, Michael.

0.2 out of 4 GB Dedicated GPU Memory

0.0 out of 12 GB Shared GPU Memory

Utilization 0%

I disabled the overlays and uninstalled the GeForce experience. I am going to see how it runs now. I’ll try some mining and try to get some hours in tomorrow to really test it. I haven’t played enough the past 2 days to report accurately what is happening. I’ll let you know. Thanks for staying on top of this!


#45

I just crashed again and took pictures of my frozen screen with the GPU information up. I’m not anywhere near running out of VRAM when it changes and was sitting looking at my inventory, inbetween mining when it happened. !


#46

Since the release of this new patch, I have had frequent crashes and rubberbanding. More so than anything I have experienced in the last 2 months I have been playing. It happens doing anything from mining to checking my inventory. I haven’t gotten into hunting/comets and feel like that portion of the game is impossible with the frequency I’ve been crashing. I would constantly die. I also don’t know how I could play anywhere near lava with the rubberbanding.

Is anyone else experiencing increased crashes? I made all the changes michael suggested and haven’t noticed any improvements.


I’ve crashed something like 4-5 times today.- 11/23/18 - 6:49PM EST

Just crashed again - 11/24/18 - 12:31 AM EST


#47

Please do keep sending in any crash dumps so we can see why its still crashing for you. Given you should have up to 16gb of memory available it really should not be hitting out of vram.
Whats your monitor set up? Is there anything unusual about the rest of your setup? The earlier crash was only reported by you so does not seem to be a common issue so something unusual is triggering it.

Have a look in the Windows event logs by running “Event Viewer”. They are a quite technical but may show an issue. Look in “Windows Logs->System” and “Application and Services Logs->Hardware”.


#48

I have a 32’’ monitor as my main monitor and 2 24’’ monitors (one to each side). I have not had any issues like this with any other application. I also never used Steam outside of Boundless and wonder if it relates to an issue with Steam or if it’s Boundless specifically since I have nothing to compare this to. I never come anywhere close to using all of my system’s resources. The computer is fairly new and I upgraded the ram/SSD awhile ago to speed it up even more and run games at max settings. I’ve been able to stream a video on one monitor, type notes on another or read an article and have a game up. I’ve had these crashes when I’ve had nothing else running and when I’ve been multitasking, I’ve had the performance tab up and seen that I never come close to using up system resources when it crashes. So I really do not understand what is going on. I can definitely say with certainty that I have crashed much more frequently since the patch. If I literally played all day, I would crash maybe 2 times a day. Now it is 5+ times a day. I have submitted crash dumps each time.

I went to Hardware Events. There are 0 logs.

I also noticed under Windows Logs --> Applications - there were Steam.exe errors:

Log Name: Application
Source: Application Hang
Date: 11/24/2018 12:30:11 AM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
The program Steam.exe version 4.80.58.24 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.
Process ID: 3ab4
Start Time: 01d482edb27a15d5
Termination Time: 4294967295
Application Path: C:\Program Files (x86)\Steam\Steam.exe
Report Id: 1bd3aad4-88f7-4c73-b27b-27a709c09032
Faulting package full name:
Faulting package-relative application ID:

Event Xml:



1002
2
101
0x80000000000000

22645
Application
DESKTOP-L53IF4M



Steam.exe
4.80.58.24
3ab4
01d482edb27a15d5
4294967295
C:\Program Files (x86)\Steam\Steam.exe
1bd3aad4-88f7-4c73-b27b-27a709c09032




54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000

Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:30:12 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket 1224589524137106911, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Steam.exe
P2: 4.80.58.24
P3: 5be646d1
P4: def5
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERACF4.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_Steam.exe_1dab4c573624a86fcb769379adef33bc5f93c89_3b891d34_59aeafc3

Analysis symbol:
Rechecking for solution: 0
Report Id: 1bd3aad4-88f7-4c73-b27b-27a709c09032
Report Status: 268435456
Hashed bucket: d8dc42efad80942db0fe9daf1ddb5ddf
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22646
Application
DESKTOP-L53IF4M



1224589524137106911
5
AppHangB1
Not available
0
Steam.exe
4.80.58.24
5be646d1
def5
67246080











\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERACF4.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_Steam.exe_1dab4c573624a86fcb769379adef33bc5f93c89_3b891d34_59aeafc3


0
1bd3aad4-88f7-4c73-b27b-27a709c09032
268435456
d8dc42efad80942db0fe9daf1ddb5ddf
0

Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:30:11 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Steam.exe
P2: 4.80.58.24
P3: 5be646d1
P4: def5
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Steam.exe_1dab4c573624a86fcb769379adef33bc5f93c89_3b891d34_090aacc6

Analysis symbol:
Rechecking for solution: 0
Report Id: 1bd3aad4-88f7-4c73-b27b-27a709c09032
Report Status: 4
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22644
Application
DESKTOP-L53IF4M





0
AppHangB1
Not available
0
Steam.exe
4.80.58.24
5be646d1
def5
67246080












C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_Steam.exe_1dab4c573624a86fcb769379adef33bc5f93c89_3b891d34_090aacc6


0
1bd3aad4-88f7-4c73-b27b-27a709c09032
4


0

Log Name: Application
Source: Windows Error Reporting
Date: 11/23/2018 6:26:19 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket 1666172085852154807, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: boundless.exe
P2: 1.0.6.3
P3: 5bf6bdf7
P4: boundless.exe
P5: 1.0.6.3
P6: 5bf6bdf7
P7: c0000005
P8: 0000000000b286fd
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F7D.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9049.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER905A.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER905A.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER908A.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_boundless.exe_451de7e91850bbc65aaa7f473b84b0f66d8a1a37_0ce8c3fc_146d9644

Analysis symbol:
Rechecking for solution: 0
Report Id: 1e2713ab-0518-4f97-ad64-0325a1fff3fc
Report Status: 268435456
Hashed bucket: 3289a0565889abd2371f6eaf2fe3abb7
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22600
Application
DESKTOP-L53IF4M



1666172085852154807
4
APPCRASH
Not available
0
boundless.exe
1.0.6.3
5bf6bdf7
boundless.exe
1.0.6.3
5bf6bdf7
c0000005
0000000000b286fd





\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F7D.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9049.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER905A.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER905A.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER908A.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_boundless.exe_451de7e91850bbc65aaa7f473b84b0f66d8a1a37_0ce8c3fc_146d9644


0
1e2713ab-0518-4f97-ad64-0325a1fff3fc
268435456
3289a0565889abd2371f6eaf2fe3abb7
0

Log Name: Application
Source: Application Error
Date: 11/23/2018 6:26:17 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Faulting application name: boundless.exe, version: 1.0.6.3, time stamp: 0x5bf6bdf7
Faulting module name: boundless.exe, version: 1.0.6.3, time stamp: 0x5bf6bdf7
Exception code: 0xc0000005
Fault offset: 0x0000000000b286fd
Faulting process id: 0x223c
Faulting application start time: 0x01d48359adffe0e5
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
Report Id: 1e2713ab-0518-4f97-ad64-0325a1fff3fc
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
2
100
0x80000000000000

22599
Application
DESKTOP-L53IF4M



boundless.exe
1.0.6.3
5bf6bdf7
boundless.exe
1.0.6.3
5bf6bdf7
c0000005
0000000000b286fd
223c
01d48359adffe0e5
C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
1e2713ab-0518-4f97-ad64-0325a1fff3fc





Log Name: Application
Source: Windows Error Reporting
Date: 11/23/2018 6:26:02 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8846ec34a0
P3: fffff80f0736bc60
P4: 0
P5: 51c0
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181123-1825.dmp
\?\C:\WINDOWS\TEMP\WER-244926390-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50EE.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50FE.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50FD.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER511D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_6df6568c8facf945be64bba2f3b744d37da8e_00000000_cab_5afd517a

Analysis symbol:
Rechecking for solution: 0
Report Id: 80a9ff9b-4841-4171-9612-99216b6ac5bb
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22597
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8846ec34a0
fffff80f0736bc60
0
51c0
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181123-1825.dmp
\?\C:\WINDOWS\TEMP\WER-244926390-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50EE.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50FE.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER50FD.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER511D.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_6df6568c8facf945be64bba2f3b744d37da8e_00000000_cab_5afd517a


0
80a9ff9b-4841-4171-9612-99216b6ac5bb
2049


0

Log Name: Application
Source: Windows Error Reporting
Date: 11/23/2018 12:27:11 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket 1330412569701840589, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: boundless.exe
P2: 1.0.6.3
P3: 5bf6bdf7
P4: 9343
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC217.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_boundless.exe_486284a3486290d77b6e161965f548b225f76a3_0ce8c3fc_363cc870

Analysis symbol:
Rechecking for solution: 0
Report Id: 5783ec91-e8bc-4b45-8c51-a6cd04479899
Report Status: 268435456
Hashed bucket: 964e2467a762baca8276932eedcaf6cd
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22583
Application
DESKTOP-L53IF4M



1330412569701840589
5
AppHangB1
Not available
0
boundless.exe
1.0.6.3
5bf6bdf7
9343
67246080











\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC217.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_boundless.exe_486284a3486290d77b6e161965f548b225f76a3_0ce8c3fc_363cc870


0
5783ec91-e8bc-4b45-8c51-a6cd04479899
268435456
964e2467a762baca8276932eedcaf6cd
0

Log Name: Application
Source: Application Hang
Date: 11/23/2018 12:27:09 PM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
The program boundless.exe version 1.0.6.3 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.
Process ID: 2ccc
Start Time: 01d483457bfd7721
Termination Time: 4294967295
Application Path: C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
Report Id: 5783ec91-e8bc-4b45-8c51-a6cd04479899
Faulting package full name:
Faulting package-relative application ID:

Event Xml:



1002
2
101
0x80000000000000

22582
Application
DESKTOP-L53IF4M



boundless.exe
1.0.6.3
2ccc
01d483457bfd7721
4294967295
C:\Program Files (x86)\Steam\steamapps\common\Boundless\boundless.exe
5783ec91-e8bc-4b45-8c51-a6cd04479899




54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000

Log Name: Application
Source: Windows Error Reporting
Date: 11/23/2018 12:27:09 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: boundless.exe
P2: 1.0.6.3
P3: 5bf6bdf7
P4: 9343
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_boundless.exe_486284a3486290d77b6e161965f548b225f76a3_0ce8c3fc_328cc1e8

Analysis symbol:
Rechecking for solution: 0
Report Id: 5783ec91-e8bc-4b45-8c51-a6cd04479899
Report Status: 4
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22581
Application
DESKTOP-L53IF4M





0
AppHangB1
Not available
0
boundless.exe
1.0.6.3
5bf6bdf7
9343
67246080












C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_boundless.exe_486284a3486290d77b6e161965f548b225f76a3_0ce8c3fc_328cc1e8


0
5783ec91-e8bc-4b45-8c51-a6cd04479899
4


0

Log Name: Application
Source: Desktop Window Manager
Date: 11/23/2018 12:26:43 PM
Event ID: 9027
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
The Desktop Window Manager has registered the session port.
Event Xml:



9027
4
0
0x80000000000000

22580
Application
DESKTOP-L53IF4M




Log Name: Application
Source: Windows Error Reporting
Date: 11/23/2018 12:26:23 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8842eaf4a0
P3: fffff80f0736bc60
P4: 0
P5: 2c84
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181123-1225.dmp
\?\C:\WINDOWS\TEMP\WER-223347859-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBB.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCB.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCA.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEB.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_75d3b03f28426c73b9d5f95c979a5326d1828b_00000000_cab_2dc40e47

Analysis symbol:
Rechecking for solution: 0
Report Id: 1ad2623a-d4eb-4e6e-82bc-1f1f4dc1b45a
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22579
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8842eaf4a0
fffff80f0736bc60
0
2c84
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181123-1225.dmp
\?\C:\WINDOWS\TEMP\WER-223347859-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDBB.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCB.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDCA.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDEB.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_75d3b03f28426c73b9d5f95c979a5326d1828b_00000000_cab_2dc40e47


0
1ad2623a-d4eb-4e6e-82bc-1f1f4dc1b45a
2049


0

Those are Windows event logs from the last 3 crashes yesterday. I really appreciate you looking into this. The game may have bugs. But, to have this much community engagement to iron things out from developers is really incredible. I am loving the game when I am not crashing! Thanks Michael!


#49

I just crashed.

Below are the Windows Crash Logs:

Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:26:22 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8846f014a0
P3: fffff80f0736bc60
P4: 0
P5: 5dac
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1225.dmp
\?\C:\WINDOWS\TEMP\WER-309744015-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C10.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_18aeabc378e198e9369fe2309a4ca2e8b6b47850_00000000_5fb25c0f

Analysis symbol:
Rechecking for solution: 0
Report Id: da0b3beb-de6f-4ece-b425-b3a13ac21f94
Report Status: 4
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22678
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8846f014a0
fffff80f0736bc60
0
5dac
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1225.dmp
\?\C:\WINDOWS\TEMP\WER-309744015-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C10.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_18aeabc378e198e9369fe2309a4ca2e8b6b47850_00000000_5fb25c0f


0
da0b3beb-de6f-4ece-b425-b3a13ac21f94
4


0


Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:26:22 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8846f014a0
P3: fffff80f0736bc60
P4: 0
P5: 5dac
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1225.dmp
\?\C:\WINDOWS\TEMP\WER-309744015-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C10.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_18aeabc378e198e9369fe2309a4ca2e8b6b47850_00000000_cab_38de5c8c

Analysis symbol:
Rechecking for solution: 0
Report Id: da0b3beb-de6f-4ece-b425-b3a13ac21f94
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22679
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8846f014a0
fffff80f0736bc60
0
5dac
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1225.dmp
\?\C:\WINDOWS\TEMP\WER-309744015-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD0.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BF0.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BEF.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5C10.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_18aeabc378e198e9369fe2309a4ca2e8b6b47850_00000000_cab_38de5c8c


0
da0b3beb-de6f-4ece-b425-b3a13ac21f94
2049


0


Log Name: Application
Source: Desktop Window Manager
Date: 11/24/2018 12:26:28 PM
Event ID: 9027
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
The Desktop Window Manager has registered the session port.
Event Xml:



9027
4
0
0x80000000000000

22680
Application
DESKTOP-L53IF4M





Log Name: Application
Source: Desktop Window Manager
Date: 11/24/2018 12:26:51 PM
Event ID: 9027
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
The Desktop Window Manager has registered the session port.
Event Xml:



9027
4
0
0x80000000000000

22681
Application
DESKTOP-L53IF4M





Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:26:52 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8838baa4a0
P3: fffff80f0736bc60
P4: 0
P5: 21e8
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1226.dmp
\?\C:\WINDOWS\TEMP\WER-309774250-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD333.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD343.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD344.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD374.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_c94c7e757e5faee724377149f43669919ee5fb2_00000000_219ad381

Analysis symbol:
Rechecking for solution: 0
Report Id: f7242b0f-c367-4d40-befb-efd82f3f6fdb
Report Status: 4
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22682
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8838baa4a0
fffff80f0736bc60
0
21e8
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1226.dmp
\?\C:\WINDOWS\TEMP\WER-309774250-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD333.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD343.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD344.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD374.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_117_c94c7e757e5faee724377149f43669919ee5fb2_00000000_219ad381


0
f7242b0f-c367-4d40-befb-efd82f3f6fdb
4


0


Log Name: Application
Source: Windows Error Reporting
Date: 11/24/2018 12:26:53 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: DESKTOP-L53IF4M
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 117
P2: ffff8c8838baa4a0
P3: fffff80f0736bc60
P4: 0
P5: 21e8
P6: 10_0_17134
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1226.dmp
\?\C:\WINDOWS\TEMP\WER-309774250-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD333.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD343.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD344.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD374.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c94c7e757e5faee724377149f43669919ee5fb2_00000000_cab_495ed45c

Analysis symbol:
Rechecking for solution: 0
Report Id: f7242b0f-c367-4d40-befb-efd82f3f6fdb
Report Status: 2049
Hashed bucket:
Cab Guid: 0
Event Xml:



1001
4
0
0x80000000000000

22683
Application
DESKTOP-L53IF4M





0
LiveKernelEvent
Not available
0
117
ffff8c8838baa4a0
fffff80f0736bc60
0
21e8
10_0_17134
0_0
768_1





\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20181124-1226.dmp
\?\C:\WINDOWS\TEMP\WER-309774250-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD333.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD343.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD344.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD374.tmp.txt
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_c94c7e757e5faee724377149f43669919ee5fb2_00000000_cab_495ed45c


0
f7242b0f-c367-4d40-befb-efd82f3f6fdb
2049


0



#50

The watchdog crashes are when Windows detects the GPU is not responding so stops it and reboots it - that could well crash anything running at the time (Steam or/and Boundless) and would also explain the window resize crash issue even when you didnt resize it.

It does feel like there could lower level issue here. You seem to have the latest drivers so might be worth trying to roll back to an older one to see if that helps. Perhaps the multi monitors but we use them at work (only 2 though) and some people have 960s.

Might be worth trying some of the stress benchmarks like furmark or heaven to see if they replicate the issue.


#51

I had this issue before I updated my drivers. I updated my drivers before posting in the forum because I thought it was just an outdated driver issue. I’m really not sure what to do. I just crashed again while shoveling dirt to clear my base. Is there any other information I can give you to help resolve the issue? Should I keep sending those Windows crash logs? How do furmark or heaven work? Thanks Michael!


Crashed again - 11/24/18 11:53 PM EST while doing basic digging. Nothing fancy and nowhere near portals.


Crashed again - 11/25/18 12:27 AM EST while doing more basic digging. Nothing fancy and nowhere near portals. I kept getting “Unstable Connection” frequently the past 30 minutes and crashed again.


Crashed again - 11/25/18 12:26 PM EST while mining gleam on Kada I nowhere near portals.


I am crashing much more frequently since the new patch…


Crashed again - 11/25/18 6:16 PM EST while in my inventory


Logged back in and crashed within a minute. The game is getting to be unplayable. Nothing about my setup has changed and I am crashing all the time since this new patch :frowning: - 11/25/18 6:25 PM EST while standing in a shop.


Crashed again - 11/25/18 10:26 PM EST ironically while hitting ESC and then shop to purchase a Gleam Club membership. Even with the constant crashing, I love this game and hope I can figure this out!


Crashed again - 11/26/18 12:25 AM EST while smacking crafting tables with my shovel in my base.

That’s 6 times in a 24 hour period (and I’m not playing 24/7. This seems a bit excessive. I haven’t changed any settings except for the settings you said to change. The results have been the same until the patch, where I noticed I have been crashing much more frequently.



#52

As Michael says, I’d try running furmark (https://geeks3d.com/furmark/) it’s a really simple gpu stress test and just lets us rule out the possibility of it being a gpu hardware issue. Leave it running for 20-30 mins or something and see if it causes any similar problems.


#53

I left Furmark running about 8 hours and monitored it while using a spare laptop and it did not cause any problems. Also, I finally hit level 50 yesterday, finished my hunter build and ran meteors with my neighbor. Then I tried soloing some without any issues - until I crashed during a solo meteor. I logged back in to find I was dead doing a level 1 meteor. I’m level 50 with max resists/armor. Until this issue is resolved, anything that makes this game fun outside of building on a level 1 world is a risk with the huge death penalty. I haven’t died since much lower levels. So, this is very frustrating. I just think it would be ridiculous if I had to unplug my monitors when I want to play or something like that when I have never had an issue like this with any other game or application. There must be a solution to this problem.

Also, I have continued to crash all the time. I stopped listing the times because I think I’ve made my point about the frequency of crashes. It’s a good 5-6 times a day at this point with no rhyme or reason.


#54

Have you ever had it crash with only 1 or 2 monitors connected? Just trying to establish if it’s isolated to when you have all 3 monitors connected.

What resolution are the 3 monitors? 1080p, 1440p or a mixture, also are they all 60hz or 144hz or a mixture?

When playing which monitor do you have the game on, presumably always the bigger central monitor? have you tried running it on one of the others and if so did that also crash.

Also how is the monitor setup managed, through the windows management/layout functions or are you using the nvidia control panel multiple display management stuff? can you show us how either are setup.

Ideally if we can reproduce the same problem we can work out either what’s wrong or at least some sort of workaround but at the moment we’ve not managed to reproduce anything like this except in a case where a lower spec gpu was running out of vram (which it appears isn’t your situation)


#55

I’m trying to play with just 2 monitors. I am going to try when I get home from work tomorrow doing this too. I log in during my lunch break at work with an inferior laptop (compared to my gaming desktop) connected to 3 monitors and don’t crash. So, I’m not sure what the issue is. But I’m also not logged in and playing for many hours at work - haha.

I have the 32’’ monitor in the center and 2 - 24’’ monitors(1 to each side). The center is a Sceptre curved monitor and the 2 side monitors are Samsungs.

The 32’’ is 1920 x 1080 (1080p) 60Hz (Sceptre C325W-1920R Curved 32-Inch Screen LED-lit Monitor Metal Black)

The 24’’ are also 1920 x 1080 (1080p) 60Hz (Samsung S24F350FHN Series - 24" LED FHD FreeSync Monitor - High Glossy Black)

I use the NVIDIA Control Panel to set them up.

The desktop is a Predator G6-710 with an upgraded 24GB of ram.

The work laptop is an Acer Aspire E 15 E5-575G with an upgraded 16GB of ram.

Thanks for getting back to me. I really appreciate it!


#56

Ok, so after playing with just 2 monitors, there are no crashes. Now the questions is: why when I play Boundless can’t I used 3 monitors? But, with any other application/game I have no issues?

I need to unplug the third monitor whenever I want to play which is kind of annoying. But at least I have a workaround so I can enjoy meteors.

I will say without the crashes the game has been so much more enjoyable and I have been playing a lot more!

Hope we are able to figure out a fix. I wanted to test it a lot before trying to pinpoint the problem.