🚀 go-pugleaf

Hi,

I too was having the same problems, however, I seemed to have solved them
(well, I've had no crashes today), with a great deal of help from people
from various newsgroups.

Firstly, install the reference drivers from http://www.reactorcritical.com
the latest version in 5.14.  But, before installing, go over the
www.3dtweak.com and read the section on 'tweaking' your machine for GeForce.
It involves a number of changes to your Bios and clearing out all old
drivers from your system before installing the new ones.

The Asus drivers might just as well go in the bin, until they release
correct drivers themselves.  Which is slightly annoying as I can't use all
the fancy features on the card at present.

Hope this helps

Pete

"AxMan" <AxMan@NOSPAMdial.pipex.com> wrote in message
news:8dk5on$8g8$1@news6.svr.pol.co.uk...
> Hi I have recently built a new machine to run Max at work and have
purchased
> a Geforce card after reading several glowing reports about its OpenGL
> performance.
>
> Plus I get to play Quake3 at lunchtimes... (LOL)
>
> However I am having some problems with the card with more "serious
apps"...
>
> The main problem is under 3d Max 3.1.
> In the openGL window when rotating the view the machine will hang
completely
> after a while
> sometimes almost immediately and sometimes after 10 mins or so...
> (not just Max but the whole machine) CTRL/ALT/DEL etc. does nothing.
>
> What settings should I be using under Max for my card?
>
> System Spec.
>
> Creative Annihilator Pro DDR <NVidia 5.14 drivers>
> Abit BP6 mobo QQ.b01 Bios (ACPI multiprocessor system)
> Creative sound blaster live 1024 (Win2k retail drivers>
> 2 X Celeron (366@550) <100 FSB>
> 384MB PC100 RAM
> Windows 2000 Pro <Retail>
>
>
> The processors are fully stable at 550 and render under Max at full load
> with no problems at all,
> both processor bars at 100% for 4 hours without a glitch.
>
> Quake3 runs fine BTW :)
>
> Another error that I occasionally get is a "...tried to reference memory
at
> <hex code> address, the memory
> couldn't be read..." dialog in windows (not BSOD screen)
>
> The application is then terminated, but the system stays up.
>
> Anyone had any similar error messages?
>
> Any help will be much appreciated
>
> TIA
>
> Ax
>
>
>
>
>
>
>
>
>
>
>
>
>