need help wire trick

[peter p]

I just did the wire trick on a celeron 850/100. I increased the voltage from default 1.70 to 1.85 and raised the fsb to 133. It boots into windows but I get an error on the screen saying "explorer performed an illegal operation windows will now close if problem persists contact vendor" or something like that. When I reboot I get the same error but says "Run DLL cannot be found" or something like that. Does anybody know what the problem might be?

[The Doors]

Hi peter p,
Please, considering that anything between 1.70 and 1.85 volts requires VID2 to be disconnected from Vss (VID2 pin cutted off of the CPU!) what are the pins that you've connected with the VidPinning Mod???

[peter p]

Originally posted by The Doors
Hi peter p,
Please, considering that anything between 1.70 and 1.85 volts requires VID2 to be disconnected from Vss (VID2 pin cutted off of the CPU!) what are the pins that you've connected with the VidPinning Mod???

I attached vid 0 and vid 1 pins to vss, to get 1.85. The next increase would be vid 2 to vss to get 1.90 volts. Do you think my problem is not enough volts.

[takiwa]

doors, if he has a default 1.7, he could wrap vid1 and vid0 for 1.85. If the default is 1.75, he could wrap vid0 for 1.85.

What OS are you running, peter, and how much did you play with the FSB settings before reaching 133? If you booted at a lower FSB first (112, 124, etc.) you may have corrupted the Windows files on your HDD...or, you could have a bad stick of memory. When you mess around with voltage and overclocking, EVERYTHING in your system is affected, not just the CPU. Make a sig with your system specs, so we can help you better...and what is your default for that chip, 1.7 or 1.75?

[The Doors]

Well, I hope to be right saying that with these pins connected to the Vss, you've got 1.65v instead of 1.85! coz like just said into the other reply 'Anything between 1.70 and 1.85 volts requires VID2 to be disconnected from Vss!' so at this point I suggest you to monitor the Vcore with MotherBoardMonitor (http://mbm.livewiredev.com/) to check the truth ;)

[The Doors]

So for me you have to connect the Vid3 to the Vss to get 1.9v like explained here (http://www.hardocp.com/articles/intel_stuff/bumpvoltage.html), and take care to the Cpu temps, that never must go above 40-45 degree C @full load (100% load).

I hope it helps you ;)

[peter p]

Originally posted by takiwa
doors, if he has a default 1.7, he could wrap vid1 and vid0 for 1.85. If the default is 1.75, he could wrap vid0 for 1.85.

What OS are you running, peter, and how much did you play with the FSB settings before reaching 133? If you booted at a lower FSB first (112, 124, etc.) you may have corrupted the Windows files on your HDD...or, you could have a bad stick of memory. When you mess around with voltage and overclocking, EVERYTHING in your system is affected, not just the CPU. Make a sig with your system specs, so we can help you better...and what is your default for that chip, 1.7 or 1.75?

Okay, my operating system is win.98 S/E. My mobo is a ECS, (elitegroup) which I cannot do anything to increase voltage on it,
the only thing I can do is raise the the fsb from 100 to 133 in one jump. I have 160 megs of ram. My default voltage is 1.70. Cel. 850/100 Cco. When I attach the wires to the pins my bios shows the new voltage increase. I don't understand why vid 2 has to be disconnected?

[The Doors]

Well, the Vid2 pin is internally connected to the Vss pin, so there aren't other way to set it to 1 like required for that voltages in the range 1.7-1.85v, so at this point if your mem modules are PC133 (set the most conservative settings: Ras & Cas delay on 3 instead of 2) and you have a good HeatSink (remember never above 45 degree C @full load, the heat is you enemy!) you can go with the 1.9v mod, that are more than enough for this kind of chip, that generally works OCed @1.8-1.85v.

P.S. first of all use MotherBoardMonitor to check the Cpu temps @stock voltage & speed and if cool enough, go with the VidPinning Mod ;)

[takiwa]

peter, if you go back to 100FSB, does it still give you the same OS error?

[peter p]

Originally posted by takiwa
peter, if you go back to 100FSB, does it still give you the same OS error?

I didn't try that yet I had to leave the house. When I get back later I will try bringing it back too 100 and see if it works. If I was to leave the voltage at 1.85 and lower the bus to 100, will that cause any problems to the cpu?

[takiwa]

no, that will actually help, that's what's known as a burn-in :) If you get the same error, the you have a corrupt Windows file...which is the best indication that your o/c was NOT successful :( Check your RAM before you write this one off, though, you may have your timing set wrong, or a stick that is going bad...hope that helps...good luck!

[peter p]

Originally posted by takiwa
no, that will actually help, that's what's known as a burn-in :) If you get the same error, the you have a corrupt Windows file...which is the best indication that your o/c was NOT successful :( Check your RAM before you write this one off, though, you may have your timing set wrong, or a stick that is going bad...hope that helps...good luck!

what should the ram timing be set at? My cas. is set at 3
Also If I disconnect vid 2, would I then get the proper voltages?
My bios shows the jump from 1.07 to 1.85, is this not correct?

[The Doors]

Yes, the Ras & Cas set on 3 is the more conservative, and can helps to get stability, epsecially when using generic mem modules, obviously the performance (the badwidth) will increase if setted on 2.

About the PinWiring mod, well, is better for you & your chip if you wait untill we understand the right way ;) few minutes, I suppose.