BIG Radeon ISSUE && Just-in-time debugging error

[mod]

The matter is not simply to be described, I'll try to be as clear as possible.

An year ago I installed AA: Special Forces on this system:

CPU: Athlon XP 1800 Palomino
MB: Gigabyte 7vkml
RAM: 512 mb PC2100 (don't remember the brand)
VCARD: Sapphire Ati 9000 Pro Vivo 64 mb
ACARD: SoundBlaster Audigy LS
OS: WinXP Pro Sp2

With this hw sometimes I got general protection errors, but AASF is known for this kind of issues, so I thought it was ok; moreover, the latest version 2.5.0 worked fine till a few months ago.

About 3 moths ago I upgraded:

MB -> Asus a7v880
VCARD -> Asus 9600 XT Vivo 128 mb

And AASF worked fine as before.

Recently I've changed:

CPU: Athlon Xp 2700+ Thoughbred
RAM: 1024 mb PC3200 (brand tested as compatible with Asus mobo)

So the DUT is now:

CPU: Athlon XP 2700 Thoughbred
MB: Asus a7v880
RAM: 1024 mb PC3200
VCARD: Asus Ati 9600 XT Vivo 128 mb
ACARD: SoundBlaster Audigy LS
OS: WinXP Pro Sp2

Recently I installed Visual Studio 6.0, but I unistalled after a couple of days, moved to other machine.

Ok now the real problem:

AASF always stops for general protection errors.
EVERY application that uses 3D generates errors.

I made some search and:

1) Relating to the "system.dll" issue in the DirtectX files:

Tried uninstalling .NET 1.1
Tried uninstalling .NET 2.0
Tried using no .NET
Tried using only 1 on 2 versions

2) Relating to the "VPU Recovery" issue:

Tried both with and without (definitly better with, so I don't have to manually reset the system)

3) relating to the "AGP Fast Write" issue:

Tried with and without, no changes

4) Relating to the "Driver conflict" issue:

Tried ATI Catalyst from 5.10 to 6.1 (availables from today)
Tried latest ASUS Catalyst + Enhanced Drivers
Tried latest Omega Drivers based on Catalyst 5.12 (woah!)

5) I checked the integrity of new ram modules with Windows Memory Diagnostic Tool:

RAM is ok

6) I checked CPU temp: 55 °C , but Asus bios (latest .004 beta) is known to overestimate of about 10 °C, so I consider it's about 48 °C (hey, it's a standard fan!)

7) I checked VCARD with tool provided by ASUS (Smartdoctor):

Temperatures, voltage and frequencies in the admitted ranges.

8) I checked VCARD with 3DMARK03

- the test stops at f 748 of 1st test
- I get an error related to Just-in-Time Debugging (related to Visual Studio)


9) VIA HyperionPro Driver Package already installed

10) Maybe I've forgotten something.

EDIT: 3DMark works perfectly the 1st time I use it after reeboting.
When I exit the program, the vcard works SLOOOOOWLY, and if I use 3DMark again, this is the result:

http://img63.imageshack.us/img63/9012/screenhunter0013cg.png
http://img63.imageshack.us/img63/9012/screenhunter0013cg.png
http://img59.imageshack.us/img59/8602/screenhunter0023qe.png
http://img59.imageshack.us/img59/9656/screenhunter0034nz.png
http://img59.imageshack.us/img59/3591/screenhunter0042lf.png
http://img63.imageshack.us/img63/8194/screenhunter0063dn.png
http://img63.imageshack.us/img63/3185/screenhunter0076zs.png
http://img63.imageshack.us/img63/1489/screenhunter0085nf.png

I wonder if anyone has any helpful idea, because I'm getting out of mines, and I want to leave the full system reinstalling as the last chance..

Thanks

[DVD_GR]

well as I can see you pretty made a large amount of tests..
I could recomend disabling fast writes from bios and check..
potentially your video card overheats ;)
hope it isnt dying :(

[mod]

1st of all thanks for the answer.
Yes, I made a lot of tests, because asking for help without having tried isn't really like me :)

3) relating to the "AGP Fast Write" issue:

Tried with and without, no changes

7) I checked VCARD with tool provided by ASUS (Smartdoctor):

Temperatures, voltage and frequencies in the admitted ranges.

I've always used Fast Write OFF, the check was just for a complete report of the problem. Now it's OFF of course.
The card is perfect, and has always worked fine. I think there may be an hw conflict (= not tested compatibility), but I doubt, because both the motherboard and the vcard are from ASUS (= hey, I expect a little testing with their own products..). [ NOTE: The vcard was of a friend of mine who had the same mobo brand, and worked perfectly. ]
There could be a problem between RAM and VCARD, but without Fast Write, the conflict "may" interest only MOBO and RAM, and the modules I installed are reported as TESTED on the mobo manual.
I'm going out for 3 days, I'll try to solve the issue when back on Sunday night.
If anyone knows (if theres') some tool to DEEPLY check the hw (not simple as Sisoftware Sandra or similar of course) I would really appreciate it, because I have a lot of suspended jobs on this machine and a total reinstall would really slow my work a lot..

Thanks

[DVD_GR]

Well for hardware colflicts I think sandra will not help.Check also removing your sound card...try this also ;)
Hardware Info (http://octech.gr/forum/viewtopic.php?t=1130)
and the last step is to remove your card and test it on a friends systems to see if there is something going wrong!

[mod]

Thanks for the tool, I installed it but it gave me no additional infos (not the ones I needed :) )
I'll try reinstalling audio drivers (I have an integrated audio card, but the quality is terrible if compared to my Audigy..), then reinstalling the old 2 PC2100 256 mb modules (checking for REAL hw issues). If the problem remains, I think the only solution will be a full reinstall. The only idea I have is that there's a conflict between drivers, but it seems REALLY hard to find.. I'll post the results of this time-loss..
Thanks for the support :)

[mod]

It seems that reinstalling latest drivers for the audio card (the same as before but with win 64 support...) and setting agp speed to 4x has made the miracle.
Simply setting agp 4x hadn't worked before..
Ive run 3DMark tests 2 times, and played AASF 5 times, and it seems stable..
I hope I won't post here again.
Thanks again for the help.

[DVD_GR]

well keep your pc out of humidity,together with dust they can short circuit something :(

[mod]

I had no problem since the last post, so I think the system is quite stable now..
I know that some hw configurations can produce this kind of issues, which of course are difficult to be tested.. so I'm just happy I was able to solve the problem, because I've saved a lot of time :)
Again, thanks for the help.