Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

Crash in Beta 10 #3478

Closed
wzdev-ci opened this issue May 14, 2012 · 5 comments
Closed

Crash in Beta 10 #3478

wzdev-ci opened this issue May 14, 2012 · 5 comments
Labels
closed component: other normal
Milestone
unspecified

Comments

@wzdev-ci
Copy link
Contributor

resolution_external type_bug | by RedShocktrooper

Right... this might actually be the same problem I had in Beta 9, and admittedly prior versions of the beta. Here's the log:

Error occured on Monday, May 14, 2012 at 00:14:31.

Program: C:\Program Files\Warzone 2100-3.1_beta10\warzone2100.exe(warzone2100)
Command line: "C:\Program Files\Warzone 2100-3.1_beta10\warzone2100.exe" 
Version: Version SDL-3.1 beta10 - Built May 13 2012
Distributor: wz2100.net
Compiled on: May 13 2012 20:16:51
Compiled by: GCC 4.7.0
Compiled mode: Release build
Executed on: Sun May 13 23:52:54 2012

Pointers: 32bit

Compiled against PhysicsFS version: 2.0.2
Running with PhysicsFS version: 2.0.2

Misc Data:
[23:52:55]Video Mode 1024 x 768 (window)
[23:52:55]OpenGL Vendor: Intel
[23:52:55]OpenGL Renderer: Mobile Intel(R) 4 Series Express Chipset Family
[23:52:55]OpenGL Version: 2.1.0 - Build 8.15.10.2555
[23:52:55]GLEW Version: 1.7.0
[23:52:55]OpenGL GLSL Version : 1.20  - Intel Build 8.15.10.2555
[23:52:55]OpenAL Device Name: DirectSound Default
[23:52:55]OpenAL Vendor: OpenAL Community
[23:52:55]OpenAL Version: 1.1 ALSOFT 1.13
[23:52:55]OpenAL Renderer: OpenAL Soft
[23:52:55]OpenAL Extensions: AL_EXT_DOUBLE AL_EXT_EXPONENT_DISTANCE AL_EXT_FLOAT32 AL_EXT_IMA4 AL_EXT_LINEAR_DISTANCE AL_EXT_MCFORMATS AL_EXT_MULAW AL_EXT_MULAW_MCFORMATS AL_EXT_OFFSET AL_EXT_source_distance_model AL_LOKI_quadriphonic AL_SOFT_buffer_sub_data AL_SOFT_loop_points
[23:52:55]Using Backend: SDL
[23:52:55]Using language: English
[23:54:33]Current Level/map is Sk-Startup


C:\Program Files\Warzone 2100-3.1_beta10\warzone2100.exe caused an Access Violation at location 1058b299 in module C:\Windows\system32\ig4icd32.dll Writing to location 0e6f1c64.


Registers:
eax=00000001 ebx=60582850 ecx=0e6f1c64 edx=0022e808 esi=00000001 edi=0e6f1c64
eip=1058b299 esp=0022e708 ebp=00000000 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210202

Call stack:

===

Mind, this time I have fully updated Intel drivers. So if you could point out if it's on my end or yours, that'd be wonderful.

Issue migrated from trac:3478 at 2022-04-16 09:49:02 -0700
@wzdev-ci
Copy link
Contributor Author

Terminator commented

still drivers issue "ig4icd32.dll" check this link http://forums.wz2100.net/viewtopic.php?f=1&t=9390#p102721

@wzdev-ci
Copy link
Contributor Author

vexed changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

vexed changed resolution from `` to external

@wzdev-ci
Copy link
Contributor Author

vexed edited the issue description

@wzdev-ci
Copy link
Contributor Author

vexed commented

Yeah, as Terminator said, it is crashing in the same system dll,


C:\Program Files\Warzone 2100-3.1_beta10\warzone2100.exe caused an Access Violation at location 1058b299 in module C:\Windows\system32\ig4icd32.dll

That still is a intel video driver issue. :(

If newer ones don't work, it is possible that older ones do.
Don't really have other suggestions besides trying to contact intel and tell them to fix their drivers.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
closed component: other normal
Projects
None yet
Milestone
unspecified
Development

No branches or pull requests
1 participant
@wzdev-ci