0x2406ffe9 error

[wmhayes]

i'm getting a crash to desktop when playing half-life 2 death match.
everything was fine thursday, saturday it's dead.
the crash is occurring during loading but before viewing a map.
the last thing i see before the crash is the the VAC loading dialog with "Parsing game info" status text showing.

"The instruction at '0x2406ffe9' refrenced memory at '0x0d7bb128'. The memory could not be 'read'. Click on OK to terminate the program"

things that have changed recently :
- new steam update
- i've pre-ordered DoD and preloaded it from steam

i saw a reference that this may be video card related on a couple of boards so i updated my video card, an ati 9700 mobile, with the most recent drivers from the maufacturer, dell.

any pointers to resolution would be appreciated.

:: SYSTEM ::
Dell Inspirion 9200
Windows XP Pro ver 2002 Sp 2
Intel 1.6GHz
512MB RAM

:: HL2DM Version ::
Protocol version 7
Exe version 1.0.0.7 (hl2dm)
Exe build: 14:54:16 Sep 23 2005 (2512)


b :

 

[Ames]

http://support.steampowered.com/cgi-bin/steampowered.cfg/php/enduser/std_adp.php?p_faqid=278

 

[diluted]

Try running the memtest86 tool - I was getting those memory errors everywhere, even in Windows. Turns out I had a bad stick of RAM. Let it run for half an hour or so, and if it doesn't give you any errors by then, then you can probably rule out the memory as being the source of the problem.

 

[wmhayes]

found this too

seems to apply to the 9/23 update.

http://support.steampowered.com/cgi-bin/steampowered.cfg/php/enduser/std_adp.php?p_faqid=397&p_created=1127526153&p_sid=3yBxLtQh&p_lva=278&p_sp=cF9zcmNoPSZwX3NvcnRfYnk9JnBfZ3JpZHNvcnQ9JnBfcm93X2NudD0yNzMmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3BhZ2U9MQ**&p_li=&p_topview=1[/QUOTE]

 

[NJspeed]

Try turning the settings down.

I've only gotten that error when I try and run the Substance mod in extremely high resolutions.... However, I've seen it on my brothers computer as well (in Half Life 2) and I think it generally is caused by trying to push your PC too hard by running a too high resolution with too high settings... and not a real memory problem.