aSnipingPenguin
Member
Hey all,
My Ghost Recon (w/1.4 patch) sometimes has problems with being kicked back to the desktop, either right as its starting up or when it tries to load a mission. It doesn't seem to be a full crash, either; the icon is still in the taskbar--clicking on it will blank out the screen like it's trying to switch back to the window before dropping back to desktop--and it still shows as an active application in Task Manager.
This doesn't happen, however, if I try playing it on a fresh boot. Even if I exit, it'll usually load again with no problems. What seems to be the main thing is that it'll never load after I've run Neverwinter Nights, or if I run something kludgy like Kazaa or AIM for a period of time, even if I turn it off before trying to start GR again.
Right now, AGP8x and fastwrites are turned off. I've tried upping AGP aperature to 128MB, which didn't help, so I backed it down to 64MB again.
The relevant parts of system are:
Asus A7N8X Deluxe rev2.0, BIOS 1004
Athlon XP 2100+ @ 155x13, stock voltage
1 stick 512MB Kingston HyperX PC2700, 1:1 w/ FSB @ 2-2-2-5 (no errors w/ overnight MemTest)
Radeon 9700NP 128MB w/ Catalyst 3.6 (3.4 also had same problems)
Antec TruePower 430W
Win XP SP1, DX 9.0b
Seagate 7200.7 80GB SATA (10GB system drive, ~5GB free for swap file)
Onboard sound, running drivers from Asus
I don't think it's an overheating issue (CPU runs about 38C idle/43C load, MB temp around 22-24C), or bad power rails (always within +/- 5% under load); even if GR crashes I can load up NWN immediately after and it'll run just fine. I'm suspecting something like uncleared clutter in RAM, but I've no idea how to deal with stuff like that.
Has anybody ever encountered this before and/or has heard of it elsewhere? I didn't find anything on the NWN forums, and the GR forums' response to all problems was pretty much "update all your drivers."
TIA
-asp
PS. If this has been addressed before, I apologize and would appreciate a link to the thread.. what I found from searching the forum archives seemed to all have to deal with BF1942 hard crashes.
My Ghost Recon (w/1.4 patch) sometimes has problems with being kicked back to the desktop, either right as its starting up or when it tries to load a mission. It doesn't seem to be a full crash, either; the icon is still in the taskbar--clicking on it will blank out the screen like it's trying to switch back to the window before dropping back to desktop--and it still shows as an active application in Task Manager.
This doesn't happen, however, if I try playing it on a fresh boot. Even if I exit, it'll usually load again with no problems. What seems to be the main thing is that it'll never load after I've run Neverwinter Nights, or if I run something kludgy like Kazaa or AIM for a period of time, even if I turn it off before trying to start GR again.
Right now, AGP8x and fastwrites are turned off. I've tried upping AGP aperature to 128MB, which didn't help, so I backed it down to 64MB again.
The relevant parts of system are:
Asus A7N8X Deluxe rev2.0, BIOS 1004
Athlon XP 2100+ @ 155x13, stock voltage
1 stick 512MB Kingston HyperX PC2700, 1:1 w/ FSB @ 2-2-2-5 (no errors w/ overnight MemTest)
Radeon 9700NP 128MB w/ Catalyst 3.6 (3.4 also had same problems)
Antec TruePower 430W
Win XP SP1, DX 9.0b
Seagate 7200.7 80GB SATA (10GB system drive, ~5GB free for swap file)
Onboard sound, running drivers from Asus
I don't think it's an overheating issue (CPU runs about 38C idle/43C load, MB temp around 22-24C), or bad power rails (always within +/- 5% under load); even if GR crashes I can load up NWN immediately after and it'll run just fine. I'm suspecting something like uncleared clutter in RAM, but I've no idea how to deal with stuff like that.
Has anybody ever encountered this before and/or has heard of it elsewhere? I didn't find anything on the NWN forums, and the GR forums' response to all problems was pretty much "update all your drivers."
TIA
-asp
PS. If this has been addressed before, I apologize and would appreciate a link to the thread.. what I found from searching the forum archives seemed to all have to deal with BF1942 hard crashes.
