Celeron 566A on ABIT VH6II WOES!!!!!!

[viotrex]

My Celery 566 used to run at 117FSB on my Abit BX6r2 mobo. Then recently I changed to Abit VH6II and I still can use 117FSB, but the problem is that Network Neighbourhood would crashed whenever I clicked on other users, while all the rest of my applications and 13 games worked ABSOLUTELY FINE. The error messaged is as below:


"MPREXE crashed......"


I tried lowering 1MHz until I reached 104FSB where the Network Neighbourhood would work fine. I am very frustrated...now I am running 8.5 X 104 FSB = 882MHz at 1.6V as compared to my 8.5 X 117FSB = 994MHz at 1.7V difference.. =(

Please give me some help. I have flashed to the latest bios for my mobo and it's still the same ****.



[PREVIOUSLY]Celeron 566 o/c 994MHz @1.7V /w 117FSB (Using own cooling system)


[CURRENT]Celeron 566 o/c 882MHz @1.6V /w 104FSB (Using own cooling system)

Abit VH6-II FC-PGA Motherboard
Crucial PC-133 CL2 256MB SDRAM
Samsung 753DF 17" Flat SCreen Monitor
Inno3d KYRO II 4500 32MB SDRAM
Seagate Barracuda ATA-IV 20GB 7200RPM
Quantum 5.6GB 5400
Hercules 7.1.1.4 drivers
Mitsumi 48X CDROM
LinkySys 10/100 BaseT Ethernet Card
Creative SB Live! Gold Edition
Creative FPS 2000 Digital

[Ebola]

welcome to the forum.

its a celly 2. the celly a, i believe were the ppga 370 form factor.

i have a celly 566 cbo sitting in storage. i'm also using a abit bx6 rev 2. i think your problem is 1.7v @ 994. thats pretty good voltage getting 994. i needed about 1.85-1.9 to get 994 to run.

i think your best bet is to give it a bit more juice. be careful though and don't go ove 1.9 unless your shooting for the elusive gig. then all bets are off.

also you might have problems if your pci multiplier is set at 1/3 instead of 1/4.

[viotrex]

Ya, it's a Celery 2..FC-PGA form. It's not a matter of juice ebola. I can run it stably running 994MHz at 1.7V on my ABIT BX6r2...so it should run all applications stably on my ABIT VH6II. But I just don't get it why it causes ONLY the network neighbourhood to have problems...was thinking perhaps the VIA chipset...since BX6r2 uses INTEL BX chipset. What say you?

What's your view on this then ebola?
And for your information, anything higher then 104FSB on this VH6II mobo will give problems to the NBH (network neighbourhood)


Celeron 566 o/c 882 using 104FSB(Using own cooling system)
Abit VH6-II FC-PGA Motherboard
Crucial PC-133 CL2 256MB SDRAM
Samsung 753DF 17" Flat SCreen Monitor
Inno3d KYRO II 4500 32MB SDRAM
Seagate Barracuda ATA-IV 20GB 7200RPM
Quantum 5.6GB 5400
Hercules 7.1.1.4 drivers
Mitsumi 48X CDROM
LinkySys 10/100 BaseT Ethernet Card
Creative SB Live! Gold Edition
Creative FPS 2000 Digital

[Godfodda]

What kind of NIC are you running? And what slot is it in?

[Stealth]

I have a celly 600 cC0 and have had my FSB up to 117 without any trouble on the VH6-II, sound's like it may be your NIC can't take it, is it the same one you used on the BX board.

[Bmxpunk86pl]

yea NICs are very sensative to higher pci bus speeds

[viotrex]

My NIC is Linksys LNE100TX Fast Ethernet Adapter. It's exactly the same as what I used on my ABIT BX6r2 using 117FSB.

I have more or less come round the problems guys. If I let my windows MAP the network drive on logon, I can run 117FSB. But I can't use network neighbourhood by double clicking on it...that's really strange.

After I let it auto connect on logon, I can access it in MY COMPUTER...and it won't crash. The moment I double click on Network Neighbourhood, the same crash screen came out again. So I guess I will have to live with this until Windows XP comes my way then.

[Stealth]

Sound to me like a software problem and not hardware at all, might try a compleat re-install of windows and see if you have the same problem.

[deez]

Originally posted by viotrex
My NIC is Linksys LNE100TX Fast Ethernet Adapter. It's exactly the same as what I used on my ABIT BX6r2 using 117FSB.

I have more or less come round the problems guys. If I let my windows MAP the network drive on logon, I can run 117FSB. But I can't use network neighbourhood by double clicking on it...that's really strange.

After I let it auto connect on logon, I can access it in MY COMPUTER...and it won't crash. The moment I double click on Network Neighbourhood, the same crash screen came out again. So I guess I will have to live with this until Windows XP comes my way then.

I agree with stealth first reinstall windows. But you may have partially fried your NIC then switched boards. Voltage in PCI slots can be diferent on different boards and running at a high FSB will also freak out PCI cards sometimes. It may have run fine before the switch but now it may just be acting up.

And what is your own cooling system???????

[Godfodda]

I'm going to disagree with the other guys (re-installing sucks big time :D). I'm thinking hardware. My Kingston NIC was flakey most of the time, but occasionally it would work right (usually when I was about to buy another one). The DLink I have now has given me no problems.

Also, along the lines of hardware, you might try moving the card to another slot before anything else. This helped briefly with the Kingston. I've been reading elsewhere here that slots 1 and 5 share an interrupt. Maybe that's part of it?

[zPacKRat]

[
Whoa!
Do you have Tweak UI installed? if so if you changed the first icon on desktop under the desktop tab, change it to my documents.
I had a problem that sounds like what is goin on with your puter.

let us know how it turns out
QUOTE]Originally posted by viotrex
My NIC is Linksys LNE100TX Fast Ethernet Adapter. It's exactly the same as what I used on my ABIT BX6r2 using 117FSB.

I have more or less come round the problems guys. If I let my windows MAP the network drive on logon, I can run 117FSB. But I can't use network neighbourhood by double clicking on it...that's really strange.

After I let it auto connect on logon, I can access it in MY COMPUTER...and it won't crash. The moment I double click on Network Neighbourhood, the same crash screen came out again. So I guess I will have to live with this until Windows XP comes my way then. [/QUOTE]

[Yodums]

Your NIC maybe burnt partially... since NIC aren't that good handlin those PCI bus speeds since they are sensitive... If you have a spare one laying around you might wanna stick that in and see how it works just to get a brief idea whether its the Nic or not..

[Stealth]

sorry forgot what a pain a re-install is, I have been using norton ghost for a long time now, compleat re-instal in under 8min, including all drivers and O/S and favorite games/appz

[Godfodda]

Originally posted by Stealth
sorry forgot what a pain a re-install is, I have been using norton ghost for a long time now, compleat re-instal in under 8min, including all drivers and O/S and favorite games/appz

Cripes, man! That's damned good! I've had Ghost just sittin' on my system for a couple of months waiting for me to use it. I think it's time! :)

[Stealth]

print out the PDF manual, you will be suprised at what this program can do, I was, the PDF is 116pgs but a lot of great info on command line switches, including how to wipe you drive to the DOD standards(Department Of Defence) I love it, not that you or I will ever have any use for such a high level format, but it is nice to know you can,

(P.S, the dodwipe takes about 4hr, I won't do that again, diskwipe works just fine for me. 30min)

[viotrex]

Guys, I have solved the problem already, I tried changing it to another PCI slot and for a while it works. I can enter the NETWORK NEIGHBOURHOOD without crashing, but then after a few rebooting, the problem came back to haunt me again, thus I decided to reinstall my protocol, I was thinking that it's not relevant but what the heck...it works.

Now I am back running 117FSB...and everything works perfectly!

Thanks alot guys, for your help, you guys are much better then my local forum dudes, they are too egoictic already.

[Godfodda]

Good job, viotrex. Now you gotta be sure and hang around here to help someone else with the same problem. :)

[Yodums]

I think it was a Windows problem nothing with the FSB really ...

[LutaWicasa]

Originally posted by Ebola
welcome to the forum.

its a celly 2. the celly a, i believe were the ppga 370 form factor.

i have a celly 566 cbo sitting in storage. i'm also using a abit bx6 rev 2. i think your problem is 1.7v @ 994. thats pretty good voltage getting 994. i needed about 1.85-1.9 to get 994 to run.

i think your best bet is to give it a bit more juice. be careful though and don't go ove 1.9 unless your shooting for the elusive gig. then all bets are off.

also you might have problems if your pci multiplier is set at 1/3 instead of 1/4.

Hey Ebola, there have only been 2 times Intel used the XXXa designation. The 300a, which had L2 cache the 300 didn't... and the 533a to show the switch to a new core. The "a" had nothing to do with the packageing.