New Posts  All Forums:Forum Nav:

8890 locking/crashing during gaming/intense CPU activity

post #1 of 14
Thread Starter 
All,

I just started playing with my new 8890 and have been having some problems, unfortunately. First, I fired up Everquest. The game loads fine and starts up great. Fast as all hell. But after anywhere between 5 and 15 minutes of activity, I get a hard lockup, which requires that I press the power button to reboot. I didn't take EQ crashing as unexpected. The game is seriously flawed in the coding department and always has been.

I figured I should try and see what was happening so I fired up 3DMark03 (bulid 330) and ran the free benchmark suite. I get through the first 4 graphics tests ok and the get an immediate lock or quit to desktop when the CPU tests start. The crashes to desktop will be followed inevitably by Windows STOP error blue screens.

In both of these cases the machine is working really HARD. The fan is really spinning and a ton of hot air is blowing out of the vent on the right side, which I would assume would be normal.

I am really hoping my problems are only with these particular games and that they are not hardware related. The machine has been 100 percent stable while it is on in the normal desktop. It just seems that using the video card causes havoc.

Is anyone else having any probles like these? Could I have a bad Sodimm? Is it a heat related problem? The room I am in is not particularly hot, it is pretty cool in fact.

Anyway, thanks for any help.

Ed

-------------
8890
3.2 HT p4
1 gig ram
60 gig 7200 hd
WinXP Home
post #2 of 14
Check your video drivers. I know Adam mentioned that there are 2 sets of drivers on the cd, one of which you do not want to use. I would double check the manual for which drivers to install or perhaps PM or e-mail Adam.
post #3 of 14
Thread Starter 
Thanks for the quick reply. I am using the drivers that Sager installed, the 7.93 version. I think these are the ones that Adam said to use. I am running a MemTest right now, just to see if it is RAM related. It does look like it could be ATI driver related tho. Can anyone else get all the way through the 3DMark03 test suite?
post #4 of 14

Check out the 8890 Crash thread

Is anyone else having any probles like these? Could I have a bad Sodimm?





I was having exactly the same problem. Sager support had me remove half my ram (512/512) and the crashes went away. I am waiting to hear back from them (Tues I guess) to see where we go from here
post #5 of 14
Thread Starter 
wessam,

This is interesting. I am in the middle of doing a couple of hour run of MemTest to see what happens. I will post the results of that when I am done.

For laughs, I used PowerStrip to change the AGP settings from 8x to 4x and it actually got through another 3DMark03 test before crapping out again... hmmm...

Well, at least it's under warranty! :-)

Thanks for your input.
post #6 of 14
Thread Starter 

Memory is probably bad...

Ok, well more facts. I let MemTest run for over an hour all by it self with nothing else running and BOOM! BSOD city..

Bad SODIMM may be the culprit.

I guess I'll send Adam a note and point him to this thread.

post #7 of 14
hmm... there seems already to be 2 people with bad ram... what company made the ram again?
post #8 of 14
I've had a similar problem to this ... running Quake3. Each time I go to play, somewhere between 5-20 mins into the game .. the game crashes and I'm given a popup box trying to send an error report out to MS .. I've never gotten this before on any of my desktop pc's.
post #9 of 14
Thread Starter 

One SODIMM = Goodness

I did what they told wessam to do (I haven't talked to tech support yet, so I hope they don't slap me around too bad ;-) and removed one of the SODIMMs. I left the one on the left in and took the right one out. Voila! 3DMark03 ran to completion with no problems. Oh, BTW score was 2980 - not bad with all gfx props left at default in the ATI panel.

BTW for whoever asked: The ram is Apacer PC3200 CL2.5.

*sigh* oh well. At least I can use this beautiful thing until they figure out the next step.
post #10 of 14

Mark03

My computer crapped out the first time I did the test. The second time it got through and scored a3054. After I took out 1/2 the ram it hit 2972. Like you said, not too bad considering. Hopefully the problem is just the ram, an easy fix, and not something else.
post #11 of 14
Glad it looks like an easy fix. I hadn't seen any other cases other than the ones mentioned in this thread. Give Sager a call/email on Tuesday to possible get a quick swap on the RAM if that's what is needed. Sorry for the troubles guys, I'm sure Sager will be all over the bad RAM modules and modify their testing to identify them better so they don't send out anything that will fail.
post #12 of 14
Adam is da man
post #13 of 14
So how many people have had this problem already?
post #14 of 14
Thread Starter 

*WAAAHHH*

Well, it looks like my machine will need to go back to Sager.

I called them today and they called back and asked me an obvious question: Did you try putting the SODIMM you though was bad back in and see if it fails? *DOH* I was hoping to avoid that, but they were right. I did and guess what? It's working perfectly as far as I can tell! Ouch... maybe the actual motherboard has a flaw..

Oh well. Better to find out now instead of later on. I am going to run on the one SODIMM for the rest of the night and they are calling me tomorrow to let me know what's next.

I feel like Ralphie from the Christmas Story after he shot his eye out!!!
New Posts  All Forums:Forum Nav:
  Return Home