- Nov 29, 2003
- 51
- 0
- 18,630
So it started at last... After countless of hours of scouring the endless tome of knowledge that is the internet, the little boy decided that he was ready to undertake the monumental task of overclocking.
Eager but nervous he pressed the delete key on his keyboard during the bootup and he was instantly transported to the glowing blue screen where the magic of overclocking happened. Shivering with anticipation, he changed the clock settings from auto to manual. At that moment, the realization of how far he had came hit him. The hours spent learning the art of PC from scratch and the preparation of his first self-assembled system, consisting of a 2.6c CPU with a SP94 and Delta 92mm, Abit IC7-Max3, Corsair twinx 4000 pro 1GB, Radeon 9800 pro 128MB, Audigy 2 ZS, Antec True480 watts, which now laid before him, a testament to the culmination of his studies and effort.
Barely able to control his excitement he keyed in the value 205 under FSB speed and saved. By now his heart was pounding so hard, that the howl of the delta fan was but the beating of wings of a butterfly. He gazed anxiously at the monitor as the system booted up with its new stats. And there it was... His first overclock... 2665Mhz. Tears of joy overwhelmed the little boy. The days spent cooped up in his tiny room pondering over the great tomes of PC hardware while his little friends played and laughed under the bright blue sky, finally, paid off.
In the midst of his crazy dance of jubilation, it suddenly struck the little boy, his job was not done. There was still much to do, tales of feats of 3.6Ghz spurred him to continue his quest for the ultimate overclock. But being a noob the boy decided he would be contented with a mere 3.4 or maybe at worst a 3.2. Happily the boy hit the delete key once more and was once again transported to the magic blue screen. Confident from the success of his previous astounding accomplishment, the little boy then proceeded to up his FSB another 5Mhz. And once again the system booted. The series of successes he had, encouraged him to up the FSB straight to 220. It booted. By now the little boy was thirsting for more and rammed the FSB to 230. Then it happened, the system did not boot. Dismayed but aware and calm, the little boy cleared the CMOS ram and pondered his next move. He decided to up the CPU voltage up a notch and the DDR voltage to 2.8v, and change the memory timings to 3-4-4-8. Still using the same FSB of 230, the little boy crossed his fingers and powered his com once more. As if heeding his wishes the system sprung into life and the little boy hopped up and down. Collecting himself the little boy again bumped the FSB up 5Mhz. This time, it failed to boot. The little boy who by now was quite confident, did not panic and repeated the process of clearing the CMOS and bumping the CPU v up another notch. He realized that an increase in a notch of CPU v bought him another 5Mhz. When he reached 1.65v the little boy decided that he would go no more for fear of melting his CPU core on his first overclock. "Maybe next time." said the little boy. His FSB was now 260 giving him a 3380Mhz CPU clock speed. A little short of his goal but the little boy was happy. Now for the first time since he started overclocking, the little boy did not pressed the magical delete button and allowed the system to boot through. As POST slowly went through the steps, the little boy awaited anxiously, wanting to benchmark his new cpu ASAP.
Then it happened. Something the little boy had not expected. POST halted. At the end of the POST screen, there wrote, cpu error, invalid cpu, change FSB in BIOS. The little boy was surprised but followed the instructions which he thanked god were in simple english not hexanumeric codes. He tuned down the FSB by 2 and prayed. And sure enough god answered his prayers once again and the system completed POST. Just when he thought all was well, again, another calamity struck. The little boy's system restarted before loading win XP. Confused as he'd never read about this in his long tutelage in the arts of OCing the boy was scared. He waited in fear as his system restarted, hoping that it would load this time. But this time god wasn't so kind, and once again the system failed to load XP. Calming himself down, the boy reasoned that the problem might be due to the high clock speed. So he entered the magic blue screen once more but this time saddly, to take away some of the magic. Lowering the FSB to 255, the little boy prayed yet once again, and left it in the hands of god.
It happened! There it was, the XP loading screen! Success! Just as the little boy leaped into the air with unbridled joy the screen warped and his system rebooted yet once more. The little boy looked up into the high heavens and shook his head, thinking to himself that god is indeed a powerful being that works in funny ways. But now, tempered by the pain of defeat and the passion of victory, the little boy is that little bit smarter and that little bit tougher. Again he teleported to the magic blue screen and brought the FSB down another 5Mhz to 250Mhz. Knowing that praying is useless by now, since he'd exhausted all his miracle tokens, the little boy just patiently waited. This time XP loaded successfully! The little boy happily clicked on his profile on the logon screen. His cursor already positioned at location of the SiSoft Sandra icon even before it loaded. Just as he was about to click it, the screen warped and the system restarted. The little boy is little boy no more, now a pissed off punk. The drudgery repeated. The FSB now at 245 and CPU clock at 3185. 15Mhz below the minimum the little boy had set. Discouraged but assured that his system at least now completed the entire boot, the little boy ran Prime95. Barely 10 seconds passed and an error he had. Sigh... Life's tough for the little boy on his first overclock. He repeated the painful task of tuning the FSB down another 5. It hurt him every single time he had to do it, now it was even more painful as he was already below his intended target. Then it went on and on, till now and 230, the little boy is too weak to continue. His heart not being able to take another blow, he called it a day. The little boy knows tommorow he would have to face painful defeat again.
And so at the end, he thought long and hard. Why? Just why is his OC so crappy. Is it the motherboard? But it's an Abit IC7-Max3 and on the abit forums he had read many a heroic stories of gallant overclocks of 3.5 with this board. Is it the memory then? How can that be? Yes sure, the OC was done at 1:1 but it's PC4000 corsair ram, and at the highest OC of 255, it's only running at 510Mhz! And it passed Memtest86! Is it the Cooling then? SP94 with AS5 and 92mm delta = lousy cooling? Presposterious! Is it the cpu then? But how can that be, 2.6c is one of the most overclockable cpus around. Then as the little boy was searching through the abit forums for an answer, he stumbled upon a thread, in which was a post which caught his attention so. And there it was a hint at the truth, another who's fate and plight similar to the little boy's. Posted in the message laid the production code and FPO/Batch No. of a 2.6c. Which bore resemblance to the little boy's 2.6c! At last some evidence that points the finger at the cpu as the culprit. Happy for a moment the little boy was, till he realized that nothing could be done even so.
And here it is the story of the little boy
Who prayed to god
For help on overclock
Now he's a muslim and eats no pork
Moral of the story? Beware 2.6c with production code: DSL6WS
Eager but nervous he pressed the delete key on his keyboard during the bootup and he was instantly transported to the glowing blue screen where the magic of overclocking happened. Shivering with anticipation, he changed the clock settings from auto to manual. At that moment, the realization of how far he had came hit him. The hours spent learning the art of PC from scratch and the preparation of his first self-assembled system, consisting of a 2.6c CPU with a SP94 and Delta 92mm, Abit IC7-Max3, Corsair twinx 4000 pro 1GB, Radeon 9800 pro 128MB, Audigy 2 ZS, Antec True480 watts, which now laid before him, a testament to the culmination of his studies and effort.
Barely able to control his excitement he keyed in the value 205 under FSB speed and saved. By now his heart was pounding so hard, that the howl of the delta fan was but the beating of wings of a butterfly. He gazed anxiously at the monitor as the system booted up with its new stats. And there it was... His first overclock... 2665Mhz. Tears of joy overwhelmed the little boy. The days spent cooped up in his tiny room pondering over the great tomes of PC hardware while his little friends played and laughed under the bright blue sky, finally, paid off.
In the midst of his crazy dance of jubilation, it suddenly struck the little boy, his job was not done. There was still much to do, tales of feats of 3.6Ghz spurred him to continue his quest for the ultimate overclock. But being a noob the boy decided he would be contented with a mere 3.4 or maybe at worst a 3.2. Happily the boy hit the delete key once more and was once again transported to the magic blue screen. Confident from the success of his previous astounding accomplishment, the little boy then proceeded to up his FSB another 5Mhz. And once again the system booted. The series of successes he had, encouraged him to up the FSB straight to 220. It booted. By now the little boy was thirsting for more and rammed the FSB to 230. Then it happened, the system did not boot. Dismayed but aware and calm, the little boy cleared the CMOS ram and pondered his next move. He decided to up the CPU voltage up a notch and the DDR voltage to 2.8v, and change the memory timings to 3-4-4-8. Still using the same FSB of 230, the little boy crossed his fingers and powered his com once more. As if heeding his wishes the system sprung into life and the little boy hopped up and down. Collecting himself the little boy again bumped the FSB up 5Mhz. This time, it failed to boot. The little boy who by now was quite confident, did not panic and repeated the process of clearing the CMOS and bumping the CPU v up another notch. He realized that an increase in a notch of CPU v bought him another 5Mhz. When he reached 1.65v the little boy decided that he would go no more for fear of melting his CPU core on his first overclock. "Maybe next time." said the little boy. His FSB was now 260 giving him a 3380Mhz CPU clock speed. A little short of his goal but the little boy was happy. Now for the first time since he started overclocking, the little boy did not pressed the magical delete button and allowed the system to boot through. As POST slowly went through the steps, the little boy awaited anxiously, wanting to benchmark his new cpu ASAP.
Then it happened. Something the little boy had not expected. POST halted. At the end of the POST screen, there wrote, cpu error, invalid cpu, change FSB in BIOS. The little boy was surprised but followed the instructions which he thanked god were in simple english not hexanumeric codes. He tuned down the FSB by 2 and prayed. And sure enough god answered his prayers once again and the system completed POST. Just when he thought all was well, again, another calamity struck. The little boy's system restarted before loading win XP. Confused as he'd never read about this in his long tutelage in the arts of OCing the boy was scared. He waited in fear as his system restarted, hoping that it would load this time. But this time god wasn't so kind, and once again the system failed to load XP. Calming himself down, the boy reasoned that the problem might be due to the high clock speed. So he entered the magic blue screen once more but this time saddly, to take away some of the magic. Lowering the FSB to 255, the little boy prayed yet once again, and left it in the hands of god.
It happened! There it was, the XP loading screen! Success! Just as the little boy leaped into the air with unbridled joy the screen warped and his system rebooted yet once more. The little boy looked up into the high heavens and shook his head, thinking to himself that god is indeed a powerful being that works in funny ways. But now, tempered by the pain of defeat and the passion of victory, the little boy is that little bit smarter and that little bit tougher. Again he teleported to the magic blue screen and brought the FSB down another 5Mhz to 250Mhz. Knowing that praying is useless by now, since he'd exhausted all his miracle tokens, the little boy just patiently waited. This time XP loaded successfully! The little boy happily clicked on his profile on the logon screen. His cursor already positioned at location of the SiSoft Sandra icon even before it loaded. Just as he was about to click it, the screen warped and the system restarted. The little boy is little boy no more, now a pissed off punk. The drudgery repeated. The FSB now at 245 and CPU clock at 3185. 15Mhz below the minimum the little boy had set. Discouraged but assured that his system at least now completed the entire boot, the little boy ran Prime95. Barely 10 seconds passed and an error he had. Sigh... Life's tough for the little boy on his first overclock. He repeated the painful task of tuning the FSB down another 5. It hurt him every single time he had to do it, now it was even more painful as he was already below his intended target. Then it went on and on, till now and 230, the little boy is too weak to continue. His heart not being able to take another blow, he called it a day. The little boy knows tommorow he would have to face painful defeat again.
And so at the end, he thought long and hard. Why? Just why is his OC so crappy. Is it the motherboard? But it's an Abit IC7-Max3 and on the abit forums he had read many a heroic stories of gallant overclocks of 3.5 with this board. Is it the memory then? How can that be? Yes sure, the OC was done at 1:1 but it's PC4000 corsair ram, and at the highest OC of 255, it's only running at 510Mhz! And it passed Memtest86! Is it the Cooling then? SP94 with AS5 and 92mm delta = lousy cooling? Presposterious! Is it the cpu then? But how can that be, 2.6c is one of the most overclockable cpus around. Then as the little boy was searching through the abit forums for an answer, he stumbled upon a thread, in which was a post which caught his attention so. And there it was a hint at the truth, another who's fate and plight similar to the little boy's. Posted in the message laid the production code and FPO/Batch No. of a 2.6c. Which bore resemblance to the little boy's 2.6c! At last some evidence that points the finger at the cpu as the culprit. Happy for a moment the little boy was, till he realized that nothing could be done even so.
And here it is the story of the little boy
Who prayed to god
For help on overclock
Now he's a muslim and eats no pork
Moral of the story? Beware 2.6c with production code: DSL6WS
Facebook
Twitter
Instagram