Vega Strike crashes when I try to use Jump Drive
Posted: Mon Jul 13, 2015 10:46 pm
Why did I get a DEP error when I tried to use the Jump Drive? I went through the initial tutorial, then went to a jump point. There were a few ships firing at me, but no significant damage. When I got within range, I pressed "j" to start the jump. The game crashed immediately with these errors (from the Windows Log):
Why am I getting this error?
EDIT: How do I attach both Stderr and Stdout to the same post? I attached Stderr, but I can't attach the second file.
Code: Select all
Log Name: Application
Source: Application Error
Date: 7/13/2015 5:29:30 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Cody-PC
Description:
Faulting application name: vegastrike.exe, version: 0.5.1.13349, time stamp: 0x4f77de06
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x0006ccd5
Faulting process id: 0x12c8
Faulting application start time: 0x01d0bdb2009b1c09
Faulting application path: C:\Vega Strike\vegastrike.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 3e469e0b-29a6-11e5-8435-54bef70e43ef
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="2015-07-13T21:29:30.000000000Z" />
<EventRecordID>43551</EventRecordID>
<Channel>Application</Channel>
<Computer>Cody-PC</Computer>
<Security />
</System>
<EventData>
<Data>vegastrike.exe</Data>
<Data>0.5.1.13349</Data>
<Data>4f77de06</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000417</Data>
<Data>0006ccd5</Data>
<Data>12c8</Data>
<Data>01d0bdb2009b1c09</Data>
<Data>C:\Vega Strike\vegastrike.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>3e469e0b-29a6-11e5-8435-54bef70e43ef</Data>
</EventData>
</Event>Code: Select all
Log Name: Application
Source: Windows Error Reporting
Date: 7/13/2015 5:30:47 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Cody-PC
Description:
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: vegastrike.exe
P2: 0.5.1.13349
P3: 4f77de06
P4: MSVCR90.dll
P5: 9.0.30729.6161
P6: 4dace5b9
P7: 0006ccd5
P8: c0000417
P9: 00000000
P10:
Attached files:
These files may be available here:
C:\Users\Cody\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_vegastrike.exe_76bdedfcc9cdaad4907529eb287aa8dacf9bb3_0f414629
Analysis symbol:
Rechecking for solution: 0
Report Id: 3e469e0b-29a6-11e5-8435-54bef70e43ef
Report Status: 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>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-07-13T21:30:47.000000000Z" />
<EventRecordID>43552</EventRecordID>
<Channel>Application</Channel>
<Computer>Cody-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>BEX</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>vegastrike.exe</Data>
<Data>0.5.1.13349</Data>
<Data>4f77de06</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>0006ccd5</Data>
<Data>c0000417</Data>
<Data>00000000</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\Users\Cody\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_vegastrike.exe_76bdedfcc9cdaad4907529eb287aa8dacf9bb3_0f414629</Data>
<Data>
</Data>
<Data>0</Data>
<Data>3e469e0b-29a6-11e5-8435-54bef70e43ef</Data>
<Data>0</Data>
</EventData>
</Event>EDIT: How do I attach both Stderr and Stdout to the same post? I attached Stderr, but I can't attach the second file.
but stderr does give me a clue that it might be related to the version of GLSL that your GPU uses (graphic driver) from all the warnings on shader compilation stdout will tell what the game was doing when it crashed so please post in your next reply.