rec.autos.simulators

by JD » Sun, 30 Jan 2005 13:32:26

I have a new computer (3 days old), and I am having big time problems trying
to run N2003 (the only game I've tried, and the only one I'm really
interested in at the moment).

I would appreciate any suggestions you may have as to why this problem is
occurring, and what I might try to do to fix, and or trouble shoot the
problem.

Here is the problem and some things I've tried. Sorry for this being so
long. There is probably more here than you want or need to know, but I am
desperate for a solution, and want to let you know what I got, and what I've
tried so far.

After about 10 minutes of driving, the computer locks up. Most of the time
the screen just goes black, then the computer reboots. Less frequently, the
screen will first freeze-up and then computer will have to be rebooted
manually. Occasionally, when the latter happens, there is 5 to 10 seconds
of normal sound after the lockup and before it reboots.

The number of cars on the track does not seem to matter. Also, it does not
seem to matter if the computer is on or off line, or if there are any
programs running in the background (such as Norton AV or Zone Alarm). I've
tried shutting down all background programs with "End It All" as well as
manually, and have also tried disconnecting the computer from the modem, but
the results is always the same.... lockup and reboot. I tried a system
restore to the factory fresh condition, with only N2003 installed (without
the patch), but I still get the lockup.

I can run N2003 for hours, with 40 cars on the track, with no problems as
long as my car remains on pit road. However, as soon as I get on the track,
or if I toggle (key-v) into the***pit of another car, which is on the
track, the lockup occurs with in 5 or 10 minutes.

I don't run a screensaver, and I have all the power options in device
manager set to never, and I have hibernate turned off.

I have monitored the CPU and MB temps, and the Voltage reading, and all is
well within the normal range. Actually the temps are low (30-ish
centigrade).

The 3Dmark 2100 score is 18,595 (don't know if that is good or bad-I was
just told to check it). I ran 3Dmark sever times with never a lockup.

One other thing, whenever the computer reboots, the clock is always off by 3
or 4 hours. It reverts to an earlier time (go figure that one).

My game setting are Direct D3D, 1280x960x16. Graphics and sounds (8-max
sound) set to default.

Here are some of the computer specs (factory built, all hardware and
software except for N2003 factory installed)

OS................Windows XP, Home Version, Service Pack 2
MB...............Asus A8V Deluxe (rev.2)
Power Supply...Vantec 520 W
CPU...............Athlon 64, XP3200+ (939 pin)
Memory...........1 GB (2x512mb PC3200-DDR400)
Video Card........ATI Radeon 9800 Pro (128MB)
Video Driver......6462
Hard Drive.......Seagate SATA 160gb
Sound.............Realtek AC'97 Audio for VIA
Wheel.............MOMO Force Feedback

This motherboard has onboard audio. I am wondering if this might be the
problem. I had a sound related lockup problem with N2003 on my last
computer, an AMD Athlon 1200, on an ABIT KT7 MB. The problem there was the
Sound Blaster card, which was resolved when I swapped it out for a Turtle
Beach card. I am not sure if the onboard sound on this MB can be
disabled-or how to do it.

Well there you have it. Hope there is someone one out there who has a
similar setup as I do, and knows of a solution.

Many thanks

by **bluestringe** » Sun, 30 Jan 2005 11:48:03

If that is a VIA chipset on the Asus, do you have the lastest 4in1's. Try
going into the BIOS and disabling the onboard audio, see if that helps.

bluestringer

by **Tanstaaf** » Sun, 30 Jan 2005 13:33:28

Sure sounds like some kind of heat problem to me, maybe the temp sensors
aren't accurate. Could be the video card overheating too. Failing that,
perhaps one of the memory sticks is bad. You could try removing one of the
512 sticks to check if it does it with just the other one in. Then swap
them and do it again.

by **Michael Horto** » Sun, 30 Jan 2005 15:19:37

My suspicion is a heat problem with the video card. I occasionally see the
same problem with my system. Try pulling the cover off your system and
running it that way and see if you run into the same issues. If not then you
need to add some fans to your system or get a fan that mounts into one of
the spacer slots in the back of the computer (where your AGP/PCI card
connections would normally be) and mount it below your video card so that it
sucks the heat off of it and right out of your case.

> Sure sounds like some kind of heat problem to me, maybe the temp sensors
> aren't accurate. Could be the video card overheating too. Failing that,
> perhaps one of the memory sticks is bad. You could try removing one of
> the
> 512 sticks to check if it does it with just the other one in. Then swap
> them and do it again.

>> I have a new computer (3 days old), and I am having big time problems
> trying
>> to run N2003 (the only game I've tried, and the only one I'm really
>> interested in at the moment).

>> I would appreciate any suggestions you may have as to why this problem is
>> occurring, and what I might try to do to fix, and or trouble shoot the
>> problem.

>> Here is the problem and some things I've tried. Sorry for this being so
>> long. There is probably more here than you want or need to know, but I am
>> desperate for a solution, and want to let you know what I got, and what
> I've
>> tried so far.

>> After about 10 minutes of driving, the computer locks up. Most of the
> time
>> the screen just goes black, then the computer reboots. Less frequently,
> the
>> screen will first freeze-up and then computer will have to be rebooted
>> manually. Occasionally, when the latter happens, there is 5 to 10
>> seconds
>> of normal sound after the lockup and before it reboots.

>> The number of cars on the track does not seem to matter. Also, it does
> not
>> seem to matter if the computer is on or off line, or if there are any
>> programs running in the background (such as Norton AV or Zone Alarm).
> I've
>> tried shutting down all background programs with "End It All" as well as
>> manually, and have also tried disconnecting the computer from the modem,
> but
>> the results is always the same.... lockup and reboot. I tried a system
>> restore to the factory fresh condition, with only N2003 installed
>> (without
>> the patch), but I still get the lockup.

>> I can run N2003 for hours, with 40 cars on the track, with no problems as
>> long as my car remains on pit road. However, as soon as I get on the
> track,
>> or if I toggle (key-v) into the***pit of another car, which is on the
>> track, the lockup occurs with in 5 or 10 minutes.

>> I don't run a screensaver, and I have all the power options in device
>> manager set to never, and I have hibernate turned off.

>> I have monitored the CPU and MB temps, and the Voltage reading, and all
>> is
>> well within the normal range. Actually the temps are low (30-ish
>> centigrade).

>> The 3Dmark 2100 score is 18,595 (don't know if that is good or bad-I was
>> just told to check it). I ran 3Dmark sever times with never a lockup.

>> One other thing, whenever the computer reboots, the clock is always off
>> by
> 3
>> or 4 hours. It reverts to an earlier time (go figure that one).

>> My game setting are Direct D3D, 1280x960x16. Graphics and sounds (8-max
>> sound) set to default.

>> Here are some of the computer specs (factory built, all hardware and
>> software except for N2003 factory installed)

>> OS................Windows XP, Home Version, Service Pack 2
>> MB...............Asus A8V Deluxe (rev.2)
>> Power Supply...Vantec 520 W
>> CPU...............Athlon 64, XP3200+ (939 pin)
>> Memory...........1 GB (2x512mb PC3200-DDR400)
>> Video Card........ATI Radeon 9800 Pro (128MB)
>> Video Driver......6462
>> Hard Drive.......Seagate SATA 160gb
>> Sound.............Realtek AC'97 Audio for VIA
>> Wheel.............MOMO Force Feedback

>> This motherboard has onboard audio. I am wondering if this might be the
>> problem. I had a sound related lockup problem with N2003 on my last
>> computer, an AMD Athlon 1200, on an ABIT KT7 MB. The problem there was
> the
>> Sound Blaster card, which was resolved when I swapped it out for a Turtle
>> Beach card. I am not sure if the onboard sound on this MB can be
>> disabled-or how to do it.

>> Well there you have it. Hope there is someone one out there who has a
>> similar setup as I do, and knows of a solution.

>> Many thanks

by **Uwe Sch??rkam** » Sun, 30 Jan 2005 17:07:18

> Sure sounds like some kind of heat problem to me, maybe the temp sensors
> aren't accurate. Could be the video card overheating too. Failing that,
> perhaps one of the memory sticks is bad. You could try removing one of the
> 512 sticks to check if it does it with just the other one in. Then swap
> them and do it again.

Another thing to try is to run memtest86 for at least 12 hours or
so. It's available on most Linux Knoppix boot cd's.

Regarding onboard sound: Check the BIOS setup for "onboard features"
or "feature setup", there should be an entry called "onboard ac97
sound" or something.

The fact that you can sit in the pit lane for hours without anything
crashing sounds a bit like a heat problem though; try running with an
open case or with a fan or something (not a hair dryer, obviously)
blowing into / through the machine.

good luck,

uwe

--
GPG Fingerprint: 2E 13 20 22 9A 3F 63 7F 67 6F E9 B1 A8 36 A4 61

by **tarage..** » Sun, 30 Jan 2005 18:43:57

> I have a new computer (3 days old), and I am having big time problems
trying
> to run N2003 (the only game I've tried, and the only one I'm really
> interested in at the moment).

I wonder if N2003 has a problem with the 64-bit processor? Though it
does sound like a video problem. Do you get the BSOD, and if so, what
does MS say about the error code?
.
/t/a/r/a/

<google's beta software is mangling quotes>

by **John Simmon** » Sun, 30 Jan 2005 21:05:58

Most of the time, it's the onboard sound that makes this happen (pewople
using add-in sound cards almost never see this problem). Also, it's a
via chipset motherboard and I bet you installed the "4-in-1" drivers
that came with the motherboard.

1) If you have 3d sound turned on, turn it off.

2) Try decreasing the number of sounds.

3) Make sure you have the latest drivers for your motherboard (the ones
on the CD have probably been superceded by now.

by **Dave Henri** » Sun, 30 Jan 2005 22:21:33

run dxdiag.exe and choose the sound tab. Try turning down the sound
acceleration one or two notches. BTW...are you using directX video or
opengl?

by **Larr** » Sun, 30 Jan 2005 23:46:06

Your system is very close to mine, and this off-season I have been
experiencing the same thing.

I _think_ I fixed mine by doing the following:

1. In the BIOS, lock the AGP down to 4X.
2. In the BIOS, disable Fast-Writes.

You won't notice any performance drop.

I've gotten through the last 2 races without any crashes.

The only differences between my system and yours are the processor (I have
the 3500), the RAM (I have PNY PC3200) and the Sound Card (I have the
SoundBlaster Audigy ZS Platinum Pro).

Same board, same drives, same OS, same crashes.

I think the above two changes will help.

-Larry

by **Pete** » Sun, 30 Jan 2005 23:41:35

I'm sure this was always a symptom of graphics card problems. Screen
goes blank, but sound keeps playing. Sure that used to happen with GPL,
another Papy sim.

--
Pete Ives
Remove All_stRESS before sending me an email

by JD » Mon, 31 Jan 2005 10:39:06

I want to thank everyone who took the time to respond to my request for
help. All the advice is greatly appreciated---some of which I'll continue
to follow up on, such as updating the various drivers.

I worked through several of the suggestions, and spent the better part of
the last three days dealing with this frustration problem and was just about
ready to box this baby up and ship it back, but thanks to Larry (THANKS
LARRY!!!) I believe I have the solution.

Larry's suggestion to go into the BIOS and lock the AGP down to 4X and
disable Fast-Write has enabled me to get in over two hours of track time
without a single glitch (knock on wood). This was after hours and hours of
trying different combinations only to have the computer repeatedly lock up
after ten to twenty minutes.

Again, thanks to all!!!!!!!!!!!! And now, I am ready for a nap.

> Your system is very close to mine, and this off-season I have been
> experiencing the same thing.

> I _think_ I fixed mine by doing the following:

> 1. In the BIOS, lock the AGP down to 4X.
> 2. In the BIOS, disable Fast-Writes.

> You won't notice any performance drop.

> I've gotten through the last 2 races without any crashes.

> The only differences between my system and yours are the processor (I have
> the 3500), the RAM (I have PNY PC3200) and the Sound Card (I have the
> SoundBlaster Audigy ZS Platinum Pro).

> Same board, same drives, same OS, same crashes.

> I think the above two changes will help.

> -Larry

>>I have a new computer (3 days old), and I am having big time problems
>>trying to run N2003 (the only game I've tried, and the only one I'm really
>>interested in at the moment).

>> I would appreciate any suggestions you may have as to why this problem is
>> occurring, and what I might try to do to fix, and or trouble shoot the
>> problem.

>> Here is the problem and some things I've tried. Sorry for this being so
>> long. There is probably more here than you want or need to know, but I am
>> desperate for a solution, and want to let you know what I got, and what
>> I've tried so far.

>> After about 10 minutes of driving, the computer locks up. Most of the
>> time the screen just goes black, then the computer reboots. Less
>> frequently, the screen will first freeze-up and then computer will have
>> to be rebooted manually. Occasionally, when the latter happens, there is
>> 5 to 10 seconds of normal sound after the lockup and before it reboots.

>> The number of cars on the track does not seem to matter. Also, it does
>> not seem to matter if the computer is on or off line, or if there are any
>> programs running in the background (such as Norton AV or Zone Alarm).
>> I've tried shutting down all background programs with "End It All" as
>> well as manually, and have also tried disconnecting the computer from the
>> modem, but the results is always the same.... lockup and reboot. I tried
>> a system restore to the factory fresh condition, with only N2003
>> installed (without the patch), but I still get the lockup.

>> I can run N2003 for hours, with 40 cars on the track, with no problems as
>> long as my car remains on pit road. However, as soon as I get on the
>> track, or if I toggle (key-v) into the***pit of another car, which is
>> on the track, the lockup occurs with in 5 or 10 minutes.

>> I don't run a screensaver, and I have all the power options in device
>> manager set to never, and I have hibernate turned off.

>> I have monitored the CPU and MB temps, and the Voltage reading, and all
>> is well within the normal range. Actually the temps are low (30-ish
>> centigrade).

>> The 3Dmark 2100 score is 18,595 (don't know if that is good or bad-I was
>> just told to check it). I ran 3Dmark sever times with never a lockup.

>> One other thing, whenever the computer reboots, the clock is always off
>> by 3 or 4 hours. It reverts to an earlier time (go figure that one).

>> My game setting are Direct D3D, 1280x960x16. Graphics and sounds (8-max
>> sound) set to default.

>> Here are some of the computer specs (factory built, all hardware and
>> software except for N2003 factory installed)

>> OS................Windows XP, Home Version, Service Pack 2
>> MB...............Asus A8V Deluxe (rev.2)
>> Power Supply...Vantec 520 W
>> CPU...............Athlon 64, XP3200+ (939 pin)
>> Memory...........1 GB (2x512mb PC3200-DDR400)
>> Video Card........ATI Radeon 9800 Pro (128MB)
>> Video Driver......6462
>> Hard Drive.......Seagate SATA 160gb
>> Sound.............Realtek AC'97 Audio for VIA
>> Wheel.............MOMO Force Feedback

>> This motherboard has onboard audio. I am wondering if this might be the
>> problem. I had a sound related lockup problem with N2003 on my last
>> computer, an AMD Athlon 1200, on an ABIT KT7 MB. The problem there was
>> the Sound Blaster card, which was resolved when I swapped it out for a
>> Turtle Beach card. I am not sure if the onboard sound on this MB can be
>> disabled-or how to do it.

>> Well there you have it. Hope there is someone one out there who has a
>> similar setup as I do, and knows of a solution.

>> Many thanks

by JD » Mon, 31 Jan 2005 10:42:09

That should have been "solution" in the title...but you get the idea (grin).
It's been a long couple days.

JD

--SNIP--

by **Ed Whit** » Mon, 31 Jan 2005 09:11:46

> That should have been "solution" in the title...but you get the idea
> (grin). It's been a long couple days.

> JD

> --SNIP--

>>I want to thank everyone who took the time to respond to my request for
>>help. All the advice is greatly appreciated---some of which I'll continue
>>to follow up on, such as updating the various drivers.

Proving yet AGAIN why this is probably one of the best newsgroups in all of
Usenet......I've gotten more (free) help here than any other place ever,
period, virtual or otherwise.

Ed

rec.autos.simulators

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please

New Computer + N2003=Problems for me....help please