P3 866 overclock @ 1001MHz is that too high for my PCI devices

[angelopatrick]

hi

im currently experimenting on my CPU its a P3 866 on an ASUS TUV4X board im just wondering if the pci devices in my system won't be fryed in the 154MHz FSB setting???

im at the 1001MHz level now and having no problems on anything i telkl you, its rock solid and it can run XP for 3 days w/o rebooting!

cooling is the stock intel FHS coupled with two electric fans blowing air side by side and three bus slot coolers and another fan in the mid part of the chasis.

my specs include:

P3 866 @ 1001MHz
154MHz FSB
ASUS TUV4X Mainboard Rev.1002
768MB PC133 SDRAM Kingston brand
64MB GeForce3 Ti based AGP card DDR
ASUS 8x DVD
ASUS 8x4x32 CDRW
60.4GB Maxtor Hard Drive
AdvanSys SCS Adapter
C-Media PCI Sound

hope you can help!!!

TY

[Lord Sech]

Angelo...


Go download Sisoft Sandra 2001 (if you doont already have it) and see what it says about your pci bus.

In my opinon, if it runs good and you dont have any problems....dont worry about it until it gives you problems.

-Lord Sech

[NDD]

154MHz FSB isn't too high for PCI devices. And if your PC133 can handle it too, then everything should be perfect. Are you running your RAM with CAS 3 at this speed ?

Best Regards ...

[angelopatrick]

yes, im running my sdram at cas3 what's about that???

is that good or bad?

TY

[arthur888]

CAS2 would be better but I guess that won't work at this speed..:( Does you PCI bus still use the FSB/4 setting that it uses for 133mhz FSB? Or did it change itself to FSB/5? You can check this with SiSoft Sandra. If it is FSB/5 everything is OK, with FSB/4 you might get some instabilities. Generally it is not recommended to go higher than 37mhz for PCI devices. Hope this helps,

Arthur

[angelopatrick]

yes my pci setting is at FSB/5 so you think it is fine to o'clock my proc at this speed no problems within the week yet, btw im running winXP pro, and sumtyms i get an error from windows saying that my pc was unable to start because something is wrong with my compontens??? is that with my overclocked CPU??? does microsoft hampering me to clock my cpu that high and wont let me in windows??? but in the 98/ME/2000 configuration it worked fine...

TY