Thread: GF2MX4/Det28.3/WinXP
-
April 5th, 2002, 02:01 AM #1Retired mostly.
- Join Date
- Oct 2001
- Location
- Finland
- Posts
- 5,150
GF2MX4/Det28.3/WinXP
What's up with the card?
I used the reghack to get coolbits and know for certain the default memory bus speed.
Coolbits has a range from 0-100MHz for memory, that can't be right...
Core has a valid range from 0-300MHz. If I apply the memory speed, everything goes like in slowmotion movie...
I tried to use GTU, it says some german gibberish and doesn't recognize the card/drivers.
NVmax offers a valid range for memory speed, but when I apply the new speeds and try to start some game, it comes up with blue screen saying that I'm lame.
What's the buggle?
-M
-
April 5th, 2002, 02:59 AM #2
roll back your drivers... reupdate them, and see if you can't fix some probelms...
-
April 5th, 2002, 04:18 AM #3
Although I don't overclock my video cards normally, I always load coolbit just to see how well it overclocks. I'm running 28.32 and the coolbit seems fine...
Last edited by NDC; April 5th, 2002 at 04:33 AM.
[NDC]
-
April 5th, 2002, 04:59 AM #4Retired mostly.
- Join Date
- Oct 2001
- Location
- Finland
- Posts
- 5,150
I had the MS certified previous drivers and they stated the same, memory bus range from 1 to 100MHz. I recall the reason I updated to newer in the first place was because I was getting bsod after nvmax settings applied.
-M
-
April 5th, 2002, 06:00 AM #5
I had similiar problems with all my GF2 MX 200/400 cards. They give some strange OC options with coolbits enabled. They always seem to start at 0? The original GF2 MX cards would overclock normally?
-
April 5th, 2002, 08:38 PM #6
Latest RivaTuner should work well with latest DetXP v28.32 and your card.
-
April 5th, 2002, 10:10 PM #7
Likely the same old memory detection problem that has plagued nVidia drivers for months now. It only effects a small portion of nVidia cards, but its appears your card may not have been built according to the recommended nVidia reference format. No problem, it's just that Detonator drivers may fail to properly set the overclocking range.
ND is correct. Use RivaTuner's low-level hardware access option to overclock the card. This will bypass the software driver interface.
Good Luck,
Robert Richmond
-
April 6th, 2002, 03:32 AM #8Retired mostly.
- Join Date
- Oct 2001
- Location
- Finland
- Posts
- 5,150
Thanks ND+Rob, the rivatuner seems to work. Will have to check whether it does or not have an impact on performance with 3dmark.
My card was made by HIS, guess they didn't comply with nvidia that much
-M
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)



LinkBack URL
About LinkBacks



Reply With Quote




Site looks fine to me.
Is It Just Me? v233893843