2.4c and 9800 pro oc issue

M3GTR

Junior Member
Nov 15, 2002
6
0
0
iv been playing with this a while and i can't seem to find anyone who has experienced the same issue.

i have a p4c800-e, 2.4c, 9800 pro, ocz 3700 gold and an audigy2. i can get the 2.4 to run at 301fsb just fine. but when i set the fsb to 302, when winxp boots one of two things will happen. 1. once xp gets to the desktop the wallpaper loads then all the icons take like 2min a piece to load. or 2. the welcome screen comes up then stays for a why then there is a error message saying there is a device failure then win continues to load in 16bit color and less than 800x600. then another one of the crash messages comes up that there was a problem with the radeon driver. the radeon is not oced at all and the agp and pci are both locked

i don't think its a cooling issue cause radeon is watercooled. i also know its the radeon cause if i pop in my gf2 i get into xp just fine up to 3.8

anyone got any suggestions or know of any issues
 

bjc112

Lifer
Dec 23, 2000
11,460
0
76
301 FSB?

That's your answer... Are you running any dividers?

Back that FSB down or run a 3:2 / 5:4 divider.
 

M3GTR

Junior Member
Nov 15, 2002
6
0
0
if the devider was the problem wouldn't it manifest itself in the cpu just refusing to load windows? especially since when i tested with my gf2 this behaviour did not manifest.

 

bjc112

Lifer
Dec 23, 2000
11,460
0
76
Originally posted by: M3GTR
if the devider was the problem wouldn't it manifest itself in the cpu just refusing to load windows? especially since when i tested with my gf2 this behaviour did not manifest.

It could be the Radeon cannot handle the 301 mhz fsb, thus throwing your PCI and AGP specs way off... does your motherboard have a AGP/PCI lock?

 

boshuter

Diamond Member
Feb 11, 2003
4,145
0
76
is this by any chance a Sapphire video card? i had the exact same problem with a Sapphire 9700pro and P4G8X motherboard. this is a big problem with a lot of the Sapphire 9XXX series cards, i rma'd mine and Newegg was out of them so i got a refund and bought an Fic 9800pro.
 

M3GTR

Junior Member
Nov 15, 2002
6
0
0
Originally posted by: bjc112
Originally posted by: M3GTR
if the devider was the problem wouldn't it manifest itself in the cpu just refusing to load windows? especially since when i tested with my gf2 this behaviour did not manifest.

It could be the Radeon cannot handle the 301 mhz fsb, thus throwing your PCI and AGP specs way off... does your motherboard have a AGP/PCI lock?


thats what i thought it was too when it started happening. even though i have agp/pci locked in the bios i though somehow the bios settiong weren't being obeyed. but i found no one who mentioned something similar happening with this board. thats why tried with my geforce 2, thought that if the agp/pci was not being truly locked it would show up there too but the gf2 worked fine.


Originally posted by: boshuter
is this by any chance a Sapphire video card? i had the exact same problem with a Sapphire 9700pro and P4G8X motherboard. this is a big problem with a lot of the Sapphire 9XXX series cards, i rma'd mine and Newegg was out of them so i got a refund and bought an Fic 9800pro.

its an ati card.

 

Slammy1

Platinum Member
Apr 8, 2003
2,112
0
76
Yet another o/c horror story. What are your temps? 301FSB, you must be running some rather intensive cooling, otherwise you're risking damage to the CPU. There are a million scenarios where you can have CPU or memory issues yet still boot into Windows, which is why you run Prime 95. These may involve temperature or minor hidden problems, but finding them you now are left to deal with them. In your case, the answer is almost certainly to back the FSB down significantly.
 

bjc112

Lifer
Dec 23, 2000
11,460
0
76
Originally posted by: M3GTR
Originally posted by: bjc112
Originally posted by: M3GTR
if the devider was the problem wouldn't it manifest itself in the cpu just refusing to load windows? especially since when i tested with my gf2 this behaviour did not manifest.

It could be the Radeon cannot handle the 301 mhz fsb, thus throwing your PCI and AGP specs way off... does your motherboard have a AGP/PCI lock?


thats what i thought it was too when it started happening. even though i have agp/pci locked in the bios i though somehow the bios settiong weren't being obeyed. but i found no one who mentioned something similar happening with this board. thats why tried with my geforce 2, thought that if the agp/pci was not being truly locked it would show up there too but the gf2 worked fine.


Originally posted by: boshuter
is this by any chance a Sapphire video card? i had the exact same problem with a Sapphire 9700pro and P4G8X motherboard. this is a big problem with a lot of the Sapphire 9XXX series cards, i rma'd mine and Newegg was out of them so i got a refund and bought an Fic 9800pro.

its an ati card.


Does the card function properly at anything under 301FSB?

Truthfully, if it's not working with the AGP/PCI lock in place you may want to return it, especially if it's working with another video card. I heard that some Ati cards had and issue with the Asus board and the serial number ending in "00" or sometihg... * sorry not too sure on that one*
 

M3GTR

Junior Member
Nov 15, 2002
6
0
0
Originally posted by: Slammy1
Yet another o/c horror story. What are your temps? 301FSB, you must be running some rather intensive cooling, otherwise you're risking damage to the CPU. There are a million scenarios where you can have CPU or memory issues yet still boot into Windows, which is why you run Prime 95. These may involve temperature or minor hidden problems, but finding them you now are left to deal with them. In your case, the answer is almost certainly to back the FSB down significantly.

temps are not a concern really cause i load at like 38c. i have no problem running prime at 301, it runs 26hours fine... had to stop cause i wanted to play bf1942 :cool:

see the thing is at 302fsb all that happens is the vid drivers get shot to hell but once winxp defaults down to the crappy setting i can actually run benchmarks that will run in the low colour settings. thats the part that sucks trying to figure this thing out.


Originally posted by: bjc112

Does the card function properly at anything under 301FSB?

Truthfully, if it's not working with the AGP/PCI lock in place you may want to return it, especially if it's working with another video card. I heard that some Ati cards had and issue with the Asus board and the serial number ending in "00" or sometihg... * sorry not too sure on that one*

thing is it functions flawlessly at 301. no crashes. benches run looped fine. and as i said above prime runs fine. games run fine.

guess 301 is the edge of what the radeon drivers can handle on this board.