ET phone help :)


(Warmaker) #1

Heyas gang!

I have been having one helluva a time trying to get ET to work. thisis the most resent error

ET 2.56 win-x86 Sep 5 2003
----- FS_Startup -----
Current search path:
D:\PROGRA~1\WOLFEN~1\etmain\pak1.pk3 (10 files)
D:\PROGRA~1\WOLFEN~1\etmain\pak0.pk3 (3725 files)
D:\PROGRA~1\WOLFEN~1\etmain\mp_bin.pk3 (4 files)
D:\PROGRA~1\WOLFEN~1\etmain\mittens6.pk3 (1 files)
D:\PROGRA~1\WOLFEN~1\etmain\ET_camp.pk3 (2 files)
D:\PROGRA~1\WOLFEN~1\etmain\etmapcycle.pk3 (3 files)
D:\PROGRA~1\WOLFEN~1\etmain\campaigns.pk3 (6 files)
D:\PROGRA~1\WOLFEN~1/etmain


3751 files in pk3 files
WARNING: profile.pid found for profile ‘Warmaker7’ - system settings will revert to defaults
execing default.cfg
couldn’t exec language.cfg
execing profiles/Warmaker7/etconfig.cfg
r_smp is unsafe. Check com_crashed.
r_mode is unsafe. Check com_crashed.
r_depthbits is unsafe. Check com_crashed.
r_stencilbits is unsafe. Check com_crashed.
r_stereo is unsafe. Check com_crashed.
r_colorbits is unsafe. Check com_crashed.
r_texturebits is unsafe. Check com_crashed.
r_clampToEdge is unsafe. Check com_crashed.
r_ext_texture_env_add is unsafe. Check com_crashed.
r_nv_fogdist_mode is unsafe. Check com_crashed.
r_ext_NV_fog_dist is unsafe. Check com_crashed.
r_ext_texture_filter_anisotropic is unsafe. Check com_crashed.
r_ati_fsaa_samples is unsafe. Check com_crashed.
r_ati_truform_pointmode is unsafe. Check com_crashed.
r_ati_truform_normalmode is unsafe. Check com_crashed.
r_ati_truform_tess is unsafe. Check com_crashed.
r_ext_ATI_pntriangles is unsafe. Check com_crashed.
r_glIgnoreWicked3D is unsafe. Check com_crashed.
r_ext_compiled_vertex_array is unsafe. Check com_crashed.
r_ext_multitexture is unsafe. Check com_crashed.
r_ext_gamma_control is unsafe. Check com_crashed.
r_ext_compressed_textures is unsafe. Check com_crashed.
r_allowExtensions is unsafe. Check com_crashed.
r_glDriver is unsafe. Check com_crashed.
couldn’t exec autoexec.cfg
Hunk_Clear: reset the hunk ok
…detecting CPU, found AMD w/ 3DNow!
Bypassing CD checks
----- Client Initialization -----
----- Initializing Renderer ----

----- Client Initialization Complete -----
----- R_Init -----
Initializing OpenGL subsystem
…initializing QGL
…calling LoadLibrary( ‘D:\WINDOWS\System32\opengl32.dll’ ): succeeded
…setting mode 4: 800 600 FS
…using desktop display depth of 32
…calling CDS: ok
…registered window class
…created window@0,0 (800x600)
Initializing OpenGL driver
…getting DC: succeeded
…GLW_ChoosePFD( 32, 24, 0 )
…35 PFDs found
…GLW_ChoosePFD failed
…GLW_ChoosePFD( 32, 24, 0 )
…35 PFDs found
…GLW_ChoosePFD failed
…failed to find an appropriate PIXELFORMAT
…restoring display settings
…WARNING: could not set the given mode (4)
…setting mode 4: 800 600 FS
…using colorsbits of 16
…calling CDS: ok
…created window@0,0 (800x600)
Initializing OpenGL driver
…getting DC: succeeded
…GLW_ChoosePFD( 16, 16, 0 )
…35 PFDs found
…GLW_ChoosePFD failed
…GLW_ChoosePFD( 16, 16, 0 )
…35 PFDs found
…GLW_ChoosePFD failed
…failed to find an appropriate PIXELFORMAT
…restoring display settings
…WARNING: could not set the given mode (3)
…shutting down QGL
…unloading OpenGL DLL
…assuming ‘3dfxvgl’ is a standalone driver
…initializing QGL
…WARNING: missing Glide installation, assuming no 3Dfx available
…shutting down QGL
----- CL_Shutdown -----
RE_Shutdown( 1 )

GLW_StartOpenGL() - could not load OpenGL subsyst

when I do get in game (wich is about 90% of the time) I crash about 2 mins in with a blue screen stating IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x00000002

I have a winxp pro
radeon 9700 latest cat drivers
soudblaster audigy gamer 5.1 with latest drivers
512 233mghz ram
amd 2200xp

any hellp would be GREAT!!


(Cyber-Knight) #2

i get that message occasionally.
i just quit and restart and everything is back to normal.


(Warmaker) #3

Well it has happened now for about 5 hours. I have reinstalled 4 times. I have also reinstalled OS. Still no go. :frowning: any help?


(=TAC=Chron) #4

couple of links to microsoft knowledgebase…

http://support.microsoft.com/default.aspx?scid=kb;en-us;314063

http://support.microsoft.com/default.aspx?scid=kb;en-us;818501

they are a little help. from these and your post, i would have to assume that there is a compatibility issue with the radeon opengl drivers and win xp. the only time that i have seen this exact crash is when i upgraded a linux kernel and since the linux Nvidia drivers are dependent upon kernel version at installation, the drivers don’t work with a newer kernel.

so i would also assume that a similar situation is happening here, but i need a little more info to make a guess.

a few questions…how long have you had the radeon? what was the previous vid card, if any? is your motherboard 8xAGP compliant? have you installed DX9? and last have you updated windows (critical, windows, and drivers)?


(fAAt) #5

This is most definitely a driver issue. Either you don’t have the latest video drivers, motherboard drivers, or version of directX.

Simple as that.

Oh ya! One more thing, the Catalyst 3.7 drivers are QUITE janky, and seem to cause lots of problems. You might want to roll back to Catalyst 3.6. I’m certain that those work properly.

Hope I was of help!


(Rippin Kitten) #6

I ran into the same problem, and its either one of two things:

IRQ Conflict
Get into the device manager and check to see if you have any overlapping IRQs, specificly between the Audigy card, your network card, and video card. Fixing this if you do can be a real pain in the butt. Some motherboards assign IRQs based on what slot the card resides in, others can change it with a bios setting. Either way, its pretty messy so if you don’t feel comfortable doing it yourself ask a friend who’s more knowledgeable.

Overheating your AMD CPU
Those 2200xp CPUs run pretty hot, and if you don’t have adequate cooling it’ll lead to this error and a PAGE_FAULT_IN_NON_PAGED_AREA stop error. A quick fix would be to underclock your CPU by running it at only 100MHz FSB instead of 133. You can also try dusting out the insides of your computer, paying particular attention to fans and heatsinks. Try running a motherboard utility that records heat levels to a log file. If you’re logging temps in the mid fifties, not only are you overheating your cpu and crashing your system, but you’re also doing damage to the cpu itself. Be careful with this, since we’ve had some pretty warm summer days and things have just started to cool down.

RK


(=TAC=Chron) #7

That is also a distinct possibility, some motherboards like the ethernet cards to go in the first couple of PCI slots. ia have run across this error in other applications and simply by moving the network card higher on the PCI bus, solves the IRQ.

Driver compatibility would be my first check, then shuffle the PCI cards on the bus.


(Warmaker) #8

A big thanks to all that helped. I am inclined to believe that its a driver issue. I have the newest cat drivers. Might roll back to earlier ones. As far as over heating…yea I am sue that WAS an issue awile ago but now now. I have had the radeon for about 6 months and all was well until I installed some raid drivers and a winbound memstick (sp?) well I will try and roll back drivers.


(Warmaker) #9

okies guys here it is…drum roll please…

//
// Watchdog Event Log File
//

LogType: Watchdog
Created: 2003-09-17 20:28:44
TimeZone: 480 - Pacific Standard Time
WindowsVersion: XP
EventType: 0xEA - Thread Stuck in Device Driver

//
// The driver for the display device got stuck in an infinite loop. This
// usually indicates a problem with the device itself or with the device
// driver programming the hardware incorrectly. Please check with your
// display device vendor for any driver updates.
//

ShutdownCount: 13
Shutdown: 0
EventCount: 2
BreakCount: 2
BugcheckTriggered: 1
DebuggerNotPresent: 1
DriverName: ati2dvag
EventFlag: 1
DeviceClass: Display
DeviceDescription: RADEON 9700 PRO
HardwareID: PCI\VEN_1002&DEV_4E44&SUBSYS_00021002&REV_00
Manufacturer: ATI Technologies Inc.
DriverFixedFileInfo: FEEF04BD 00010000 0006000E 000A18E0 0006000E 000A18E0 0000003F 00000008 00040004 00000003 00000004 00000000 00000000
DriverCompanyName: ATI Technologies Inc.
DriverFileDescription: ATI Radeon WindowsNT Display Driver
DriverFileVersion: 6.14.10.6368
DriverInternalName: ati2dvag.dll
DriverLegalCopyright: Copyright © 1998-2002 ATI Technologies Inc.
DriverOriginalFilename: ati2dvag.dll
DriverProductName: ATI Radeon Family
DriverProductVersion: 5.2.3763.0

ok I have rolled back my driver AND reinstalled 9x…any help woudl be GREAT!!


(=TAC=Chron) #10

i would uninstall the raid and memstick drivers as well since your problem started after you installed them. but, yeah, it has got to be some esoteric driver conflict going on there.


(Warmaker) #11

http://www.splashdamage.com/forums/viewtopic.php?t=4544

:clap: :clap:

cheers :drink: :drink: :drink: :drink: