View Full Version : SYStool 0.24 and my p-M735...
Moruem
10-14-2005, 03:42 PM
Hi there,
Ok, so I downloaded the SYStool0.24 to change the EIST of my p-M735 on ct-479/p4c800-dlx. Everything went fine, got multi downed from x17 to x10. Then, knowing this chip did clocked to 2.45ghz+, I setted the fsb, using the clockgen for the i875p chipset, to some 201mhz, with the multi x10, for a 2ghz action.. It froze, then nothing. No boot after that. The motherboard and everything is ok, as I slapped a 1.6a woody in it and it booted allright.
Now, what happened to my chip? The chip has run over 2.4ghz. Maybe the fsb201 wasn't good for the chip, but I would have expected some freeze, then reboot and it's straight up.. I'm really confused about this, as it's not my first chip I push, but it's the first to stop that way, in so short time, I just changed the settings, hit apply, them bam, and it's dead...
I feel I have to tell, since one click seem to have killed my chip. I wasn't thinking it even possible. Any thoughts on this are welcomed.
Urlyin
10-14-2005, 10:30 PM
Hi there,
Ok, so I downloaded the SYStool0.24 to change the EIST of my p-M735 on ct-479/p4c800-dlx. Everything went fine, got multi downed from x17 to x10. Then, knowing this chip did clocked to 2.45ghz+, I setted the fsb, using the clockgen for the i875p chipset, to some 201mhz, with the multi x10, for a 2ghz action.. It froze, then nothing. No boot after that. The motherboard and everything is ok, as I slapped a 1.6a woody in it and it booted allright.
Now, what happened to my chip? The chip has run over 2.4ghz. Maybe the fsb201 wasn't good for the chip, but I would have expected some freeze, then reboot and it's straight up.. I'm really confused about this, as it's not my first chip I push, but it's the first to stop that way, in so short time, I just changed the settings, hit apply, them bam, and it's dead...
I feel I have to tell, since one click seem to have killed my chip. I wasn't thinking it even possible. Any thoughts on this are welcomed.
Moruem... overclocking the chip itself shouldn't have killed it. Generally it's the voltage or heat that will kill the chip. What voltage was the vcore set at and are you still using the stock HSF?
My experience with the PM was it would instantly freeze at certain FSB, for instance it would run at 195FSB but as soon as you clicked 196FSB it locked. Now I did experience times when it didn't reboot and this is in the ASUS board which I would just turn it off and reset CMOS. It may be it's not the chip but the CT-479 adapter. At first it didn't like the change to lower multi and didn't scale accordingly but running tighter timings on the memory helped with that.
So at this point the adapter and PM do not boot at all? Do you have a multi meter?
Moruem
10-14-2005, 11:29 PM
As detected by SYStool, vcore 1.375v, EIST x10, fsb201, the thing froze. Multi 10 was ok, but then trying fsb201 froze it, then nothing after that. I cleared the CMOS, tried latest betabios, tried bios from p4c800e-dlx with a trick, nothing seems to take it back to work. I'll have another setup comming, ct-479 and c-M 330 with p4p800se, see what's up with that. I'm very confused about that bug/freeze that "killed" my chip. It's not the first o/c I do. Also, this chip did 2.4ghz, and "died" when I tried going for 2ghz... still with the stock ct-479 hsf, but heat seemed ok to me. Yes I have a multimeter, something to help me? I don't really see how it died, I'd expected a freeze, but it isn't working now...:(
Urlyin
10-14-2005, 11:39 PM
As detected by SYStool, vcore 1.375v, EIST x10, fsb201, the thing froze. Multi 10 was ok, but then trying fsb201 froze it, then nothing after that. I cleared the CMOS, tried latest betabios, tried bios from p4c800e-dlx with a trick, nothing seems to take it back to work. I'll have another setup comming, ct-479 and c-M 330 with p4p800se, see what's up with that. I'm very confused about that bug/freeze that "killed" my chip. It's not the first o/c I do. Also, this chip did 2.4ghz, and "died" when I tried going for 2ghz... still with the stock ct-479 hsf, but heat seemed ok to me. Yes I have a multimeter, something to help me? I don't really see how it died, I'd expected a freeze, but it isn't working now...:(
First the Systool vcore only works if you have Auto set in the BIOS for vcore. You can check the voltage on the CT-adapter by removing the CPU and measuring the voltage at the coil and on the adapter at cap c-25 I'll upload a pic and circle the two spots. Both voltages should equal the same or with in .05v of each other... Be sure to plug in the power for the adapter ...
Moruem
10-14-2005, 11:56 PM
So, I boor without the chip?
Yeah, I kept AUTO in the bios for vcore, and SYStool read 1.375v just before I clicked apply... The more I read, the p-M735 should not be able to boot at fsb201, yeah the thing froze, but ain't booting anymore... After newer bios and cleared cmos..
Keep those hints coming please.:o
Edit: Ok, this ain't the same pics as my mobo, so I tested voltage on every coil, and gave my nothing. Voltage at the c25 is 0.11v-0.12v, when power is on and no chip inserted. Should this be higher and maybe the adapter died? What's the next step? :D
Urlyin
10-15-2005, 12:25 AM
So, I boor without the chip?
Yeah, I kept AUTO in the bios for vcore, and SYStool read 1.375v just before I clicked apply... The more I read, the p-M735 should not be able to boot at fsb201, yeah the thing froze, but ain't booting anymore... After newer bios and cleared cmos..
Keep those hints coming please.:o
Yes ..without the chip because you can't get to the adapter with the HSF on ... and you don't want to boot up with the chip in and no HSF ... :eek: ... what BIOS rev did you flash? In most cases that I've read about the PM735 was able to boot to 200fsb in the BIOS and it is what most PM owners would want to do to get all the mem dividers and ASUS mem tweaks .... check the voltage and see if the adapter is at least acting right ... you've reset the BIOS since you booted with the P4 CPU correct?
edit the issue with the 200FSB that may be the same as 133FSB was no agp/pci lock
You may want to create a thread in the Hardware section so we don't go to far off topic in the Systool thread ...
Moruem
10-15-2005, 12:39 AM
Well, booted and had 0.11v-0.12v on that c-25, and I booted without the hsf, since it's not working, and had like 0.02v on that c-25 with cpu in... :confused:
From what I've read, those new fsb533 cores does fsb200 well, and older fsb400 ones stop around the fsb170-180... Has to do with core revision B1 vs C0. For that agp/pci lock, that's why I tried fsb201...
So the adapter would be fux0red? Yeah, I cleared the bios a couple of time.. I was on betabios 1021.004 when it happend, tried 1021.005, and the official bios 1023 for p4c800e-dlx, nothing better.
What should I read with cleared bios and no chip on that c-25 thing?
Thanx
Urlyin
10-15-2005, 02:33 AM
Well, booted and had 0.11v-0.12v on that c-25, and I booted without the hsf, since it's not working, and had like 0.02v on that c-25 with cpu in... :confused:
From what I've read, those new fsb533 cores does fsb200 well, and older fsb400 ones stop around the fsb170-180... Has to do with core revision B1 vs C0. For that agp/pci lock, that's why I tried fsb201...
So the adapter would be fux0red? Yeah, I cleared the bios a couple of time.. I was on betabios 1021.004 when it happend, tried 1021.005, and the official bios 1023 for p4c800e-dlx, nothing better.
What should I read with cleared bios and no chip on that c-25 thing?
Thanx
Running the CPU without the HSF isn't wise .... Did the CPU heat up? You did have the adapter power cable plugged in? When I tested the voltage I had it set to 1.6v in the BIOS and both measure points equal 1.58v, after resetting BIOS it didn't change.
So your measurement was .11v-.12v on the coil? But on the adapter it was .02v?
Moruem
10-15-2005, 02:41 AM
It was 0,12v without cpu and 0,02v with cpu, I'm wiser than you think, I just sound dumb :P And no, the cpu did not heat up, I was ready the finger on the switch to turn it off, but nothing.. Like this whole story... :P
Seems to me the adapter took a hit.. I didn't measure the coil since it wasn't the same mobo pictured, I wasn't sure which coil, but I tried the three and got no readings..
I'll have another kit in soon, I'll test further, but since you said you measured 1.58v on that c-25, I'm noway near that, so it points out to this thing. :shadedshu
Then changing the fsb killed the ct-479? :confused:
Weird thing..
Urlyin
10-15-2005, 03:09 AM
It was 0,12v without cpu and 0,02v with cpu, I'm wiser than you think, I just sound dumb :P And no, the cpu did not heat up, I was ready the finger on the switch to turn it off, but nothing.. Like this whole story... :P
Seems to me the adapter took a hit.. I didn't measure the coil since it wasn't the same mobo pictured, I wasn't sure which coil, but I tried the three and got no readings..
I'll have another kit in soon, I'll test further, but since you said you measured 1.58v on that c-25, I'm noway near that, so it points out to this thing. :shadedshu
Then changing the fsb killed the ct-479? :confused:
Weird thing..
I've read in a few forums that the adapter just rolled over and died ... I wasn't thinking that you didn't know what you were doing just that we were on the same page ... :)
But I use Systool to set multi and raise the FSB ... it also has max CPU which is nice as well ... my BIOS doesn't have the multi ... may find this interesting http://www.techpowerup.com/reviews/ASUS/CT-479/ ... lets us know how you make out and post some benchies when you get it running again :rockout:
Moruem
10-15-2005, 06:46 AM
Well, the chip clocked 17x144 for a 2.448ghz superpi/occt stable. Ram at 2.2.2.5 ratio 1:1, superpi sse2 patched ran in 30sec. Pretty sure the thing would fly with high fsb, that's why I came here and d/l'ed SYStool, changed the multi to x10, then fsb201, for easy 2ghz... Errr... We'll see next week if the chip survived after all, maybe just the ct479 that's dead. And it's under warranty I think, can't wait to rerun that chip.:rockout: :rockout: :rockout: Let's be positive!~
Moruem
10-19-2005, 05:00 PM
Ok, got this resolved.. It's my ct-479 adapter that died. With latest betabios 1021.005, I can now set multi and more vcore. Maybe it was with betabios 1021.004 that wasn't able to change the multi in the bios that the ct-479 died when I tried to change values. But again, I get many freezes when I try to change values on the i875p chipset with latest bios. Seems to me this thing doesn't like too much my p4c800-dlx/ct-479 setup.
edit: for the benchies.. tried to squeeze the highest fsb, got like 30.083sec spmod1m, at fsb177x14, fsb won't go one notch higher.. ..still not bad for a rev.B1 dothan..
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.