Hey Unclewebb,
Ok quick progress update, i reduced down the VID a bit too far and found out what system instability is (system seems happy down to 1.0750V at 9 multi)... After the reboot however i have found that unless there is a bit of load on the CPU the Multiplier does not lock onto 9x... and Dual IDA turns on and off again, depending on load.
Not sure if this is normal behaviour or not... Will have another read of this thread and see if i can figure it out.
Take care all,
Demon
-
DemonBG: I need some more info to help you. I have no idea what CPU you are using and I don't know if Dual IDA is setup and working properly.
To keep things simple, I only use profile 1 as my Dual IDA profile. If the EIST box is clear and the C States box is clear then your multiplier should be locked on the highest value for both cores. My guess is that you have enabled C States after you enabled Dual IDA. That causes the floating multiplier when lightly loaded.
If you hold down the ALT key and press the PRINT SCREEN key on your keyboard and then go into Paint and select Paste in the menu, you can save a picture of ThrottleStop and upload it to ImageShack and post a link here so I can see what's going on without having to ask too many questions. -
Here we go, screenshots as requested:
First one is with no load (Highlighted by the low CPU usage in speedfan) and second is with very light load (I.e. - Firefox is open).
As i say, all was fine untill i went a bit too low on the voltage initially and had to restart - Then the system did not want to "Lock" into the 9x multi and would only do it when under the smallest bit of load.
personally i don't mind too much as they seem to clock up to 9x multisampling as soon as there is any load on the CPU... So surely it will help matters when the PC is idle?
All the best,
Demon -
I'm not sure if it's a bug in ThrottleStop or your CPU or motherboard works a little differently than my laptop does.
Can you try clicking on the C States box and cycling that on and then off and see if that makes any difference? It looks like one of the C States is being left on.
If clicking the C States box on and off gets your CPU multi steady at 9.00 when idle then that's a bug in ThrottleStop that I'll try to fix. If doing this doesn't make any difference then I probably won't be able to fix it because I don't have access to the full Intel documentation about the C States register. I've been doing a lot of winging it.
If this doesn't work, can you send me a CPU-Z TXT report for your CPU? I might be able to find a C State bit in your P8400 that is different than my T8100 uses. Run the CPU-Z TXT report with ThrottleStop running and the C States box cleared. Thanks.
You can upload this report to www.mediafire.com or do a Copy/Paste and send it to me in a PM message. -
Hi Uncle,
Its a little difficult to monitor exactly when the cores are not running at 9x multi as its difficult to get low enough load that it stops working. I can confirm however that with C-states enabled, even under load the Multi no longer locks at 9x (I.e it fluctuates and gets as high as 9X for both cores under load).
Will get you the CPU-Z report sent in a few minutes.
Thanks for all the effort bud,
-Demon -
While Uncle i reading through my CPU-Z report, i have another Noggin scratcher for you all:
The tool in TS that allows for temperature monitoring (found through the options menu) doesnt seem to stay activated after a reset? Does anyone know how to set it up so that it turns on with throttlestop?
Take care all,
Demon -
ThrottleStop needs to be run each time you boot up if you want to use any of its features. Have a look at the second post in the ThrottleStop Guide thread for more info.
Hopefully I have some time this weekend to write some code to see if I can turn off the C State that you might have found. -
-
Hi mbarry,
It's possible that you may be able to tie the TME pin directly to ground without problems, however keep in mind that once the pin is checked for the overclocking status, it becomes a 3.3v output pin.
The resistor is just there so that pin doesn't draw unneccessary power when it becomes an output pin. -
Great to see you still active around here, kravis. And thanks for the straightforward answer. Also, do you know where I can find your modified SetFSB program? Someone put it up as an attachment but it was corrupted.
-
Actually, I found it after digging through the thread, thanks a ton! What timings did you relax the RAM to to achieve your 3.6GHz overclock?
-
I think I used something like cas 8 ram settings using Memset to overclock to 3.6GHz but at that point, it's not fully stable, not because the CPU couldn't handle it or the ram but something else that I can't determine (could be FSB too high for PLL, intel chipset needs more voltage etc) as it just randomly resets itself when idle.
I've got an updated version of the modified SetFSB program if you want it that is more stable and combines overclocking with dual IDA at the same time. -
I believe at 3.6 you are running into an unstable NB, which I don't think you can voltmod easily (probably requires soldering/hardmod). The updated SetFSB would be great. I also tried to unpack your previously uploaded SetFSB program, but it said it was corrupt? I also wasn't able to run Thaiphoon because of the driver signing issues. Does Memset not have this issue?
-
Hi mbarry, you are probably right about the unstable NB. Well anyway at lower settings it's stable enough so that's fine with me.
Memset doesn't have driver signing issues as it uses a signed driver for low level access.
I've updated my signature to include an updated version of the SetFSB .Net 4.0 program that I use.
You can run it in Windows and specify an fsb value to set (it can include decimals) after clicking Read to get the current fsb. It will automatically increment or decrement the fsb in 5MHz steps until it reaches the fsb closest to your fsb value and then apply the Dual IDA setting. Reset will set the fsb to 267MHz and revert the Dual IDA setting.
This is what I've done to use it at Windows Startup and Shutdown:
1. Launch gpedit.msc
2. Go to Local Computer Policy > Windows Settings > Scripts (Startup/Shutdown)
3. Double click on Startup, add the following script and click OK twice:
Script Name: [full path to SetFSB.exe]
Script Parameters: -s [fsb to set]
4. Double click on Shutdown, add the following script and click OK twice:
Script Name: [full path to SetFSB.exe]
Script Parameters: -r
What this does is it sets the fsb you specify at Windows startup and resets the fsb to 267MHz on shutdown or restart.
In the SetFSB.exe.config file, you can change the voltage to set in Dual IDA mode e.g. 0x22 for 1.1375v or 0x27 for 1.2000v (corresponding to the default 8.5x and 9x multipler voltage IDs on my P8400).
If you find that your settings prevent you from entering Windows, then you can just start Windows in safe mode and remove the settings using gpedit.msc. -
Perfect. Although I don't see why you would need to reset the clocks at shutdown, as the system should reset to default clocks at startup anyways.
I also noticed that changing the memory timings doesn't accomplish much, I'm still resetting at around 305 FSB. It shouldn't be the processor as it is perfectly stable at 302 FSB. I get the same results when setting the memory to 7-8-8-24 (for some odd reason, MemSet can't change the first timing, so I had to leave it at 7). I will be getting some faster RAM to test with soon, so I'll post back with an update. Thanks again for all your help!
EDIT: Somehow using your modified SetFSB rather than the original SetFSB was able to get me to 330FSB. I wonder why... -
mbarry, another thing that you can try is to change the speed reported by one of your ram sticks using Thaiphoonburner (I used 32 bit Windows from dual boot to run it) e.g. from 533MHz to 400MHz. The effect of this is that for the same fsb, your memory will run at a lower frequency (bios uses the lowest memory speed of the two sticks) but this gives you more legroom to increase your fsb, while keeping your ram at speeds that it can handle.
-
I tried Thaiphoon burner, but since it has unsigned drivers, I am unable to change the settings. Are the RAM settings kept constant even after a restart?
-
The ram timings in Memset can be set to run at startup using save button, otherwise they'll only apply during the current Windows session.
-
Hi all,
This is a question mroe directed to Unclewebb but if anyone has any input - it is as always appreciated.
I have just replaced my CPU for a T9550 and have used throttlestop to unlock the 10.5 multiplier to gain 2.8Ghz on both cores... happy days!
Now here is the odd part. I have always used Speedfan to monitore my temps and with the P8400, both Speedfan and throttlestop stated the same core temps, now that i have the T9550 Throttlestop is stating my cores are 5 degrees higher than that stated by Speedfan. My question is, which is correct?
Kind regards,
Demon -
For software to report the correct core temperature, it needs to know what the correct TJMax value is for the CPU. A difference of 5C is usually a good sign that two programs are using different values.
The correct value for a T9550 is 105C according to the Intel specs.
http://ark.intel.com/products/37130/Intel-Core2-Duo-Processor-T9550-(6M-Cache-2_66-GHz-1066-MHz-FSB)
If ThrottleStop is reporting the higher temperature then it is likely using the correct value and SpeedFan is using a TJMax value of 100C. You can open up the ThrottleStop.ini configuration file to make sure it shows TJMax=105.
If this is correct then you need to add a +5C offset to SpeedFan.
If you play musical processors then its possible that either program is using a TJMax value based on a previous CPU. -
hi Unclewebb,
Thanks for the help bud. Before you replied i downloaded HWmonitor and that is giving me the same as speedfan... i have taken a look at the TJmax value in TS and it is indeed at 105C so have changed Speedfan accordingly.
What is strange however is that apparently the TJmax value of old P8400 is also 105... So i dont see why TS and SF are now giving me different readings?
All the best and thanks once again,
Demon -
If SpeedFan and ThrottleStop were both using a TJMax value of 105C for your previous P8400 then they would report the same core temperature. When you swap CPUs, you need to make sure that temperature monitoring software is using the correct TJMax for your new CPU.
-
Hi Unclewebb,
Sounds good - i didnt realise some software automatically recalibrate based on CPU. Clearly throttlestop does so good on you for making such an awesome bit of kit!.
And FYI all - If anyone is wanting to upgrade their P7805U: The T9550 is absolutely faultless in it! Undervolted and with EIST unlocked it is a powerhouse and never gets above 45 degrees (UV'd to 1v at 10.5 multi).
Take care all,
Demon -
Another question @kravis, I recently "upgraded" to a p8600, which has a IDA multiplier of 9.5 instead of 9. I dug through the config file for your modified SetFSB and found that the value for a 9x multiplier is 0x9. Do you happen to know what the value for 9.5 would be? Thanks!
-
mbarry: I'm not sure if this is the info you are looking for but the CPU uses the code 0x49 for the 9.5 multiplier. The leading 4 sets the half multiplier bit within the CPU.
-
Hi Mbarry. Yes, just as unclewebb mentioned, to lock the CPU at the 9.5 multiplier, try and use 0x49 for the IDA_FID setting in the SetFSB config file.
I've tested mine with 0x47 on my P8400 and it locks the multiplier at 7.5. -
Thanks! I was able to get up to 320FSB with the stock RAM, so I got a 2x4GB set of 1600MHz RAM. However, the new RAM defaults to 6-6-6-19 when running at 1066MHz, and with those timings, the RAM fails at 1120MHz. MemSet is unable to change the timings.
Are the settings made in Thaiphoon Burner permanent? If so, I will install a 32-bit just to change the timings. -
Mbarry, that's a great result! The settings made by Thaiphoon burner is semi-permanent in that it will keep it's settings on startup or reboot. You can always reflash again with Thaiphoon burner with new settings later.
There is a setting to be careful with in ThaiphoonBurner that makes the settings permanent though, which means you can't change the settings ever again in the stick of ram even if you force it. -
Well I am using Windows 7 64-bit, so Thaiphoon Burner doesn't work. So if I flash with Thaiphoon the normal way using a 32-bit operating system, it only saves the settings for that particular system and when I move back to my 64-bit, it will revert back to stock 6-6-6-19 right? But if I use the permanent method, I should be able to flash 9-9-9-28 and move back to the 64-bit with the 9-9-9-28 settings kept right? Thanks!
-
Hi Mbarry, what I meant is that when you flash settings with Thaiphoon Burner, it will save it to non-volatile memory on each ram stick. This means that the settings will be applied to any operating system that you run and the settings will be kept. So you just need to flash your settings with Thaiphoon burner in Windows 32bit and it will be applied even when you move back to Windows 64bit
The permanance I was talking about was not being able to use Thaiphoon Burner to ever change the settings on the ram sticks, which you should avoid. -
Oh, great. I'll get to it and post back with results.
-
Ok, so I installed 32-bit and Thaiphoon burner works as expected. Only issue is I wasn't too sure about how to use it. I made a save of the original flash. I then used the editor and made it so that when the FSB displayed 533MHz, it would use the 9-9-9-28 settings. I made sure protection was off, and I wrote it to the RAM. I rebooted and realized the other stick was still at factory settings, so I booted back to 32-bit and noticed that I no longer could see the first stick that I flashed in Thaiphoon Burner. I didn't think much of it and continued to flash the other stick. When I tried to boot again, the computer wouldn't go. However, when I use 1 stick of the Samsung memory that came with the computer and 1 stick of the new G.Skill RAM, it still works and detects fine in the BIOS and Windows. Any ideas?
-
Hi Mbarry, it's best to use no higher than cas 8 settings for the ram as cas 9 didn't work for me either. It's good that you've still got another stick that works.
What you need to do now is to do a hot flash.
To do this, place the single memory stick that works in the bottom slot and boot into Windows 32bit.
When Windows is fully loaded, insert the memory stick that doesn't work into the top slot without turning off the computer.
Start up Thaiphoon Burner and select the memory stick that doesn't work (you can check the settings for that stick).
Load the saved settings (original settings) and write the selected memory stick with the loaded settings.
You can reload the settings again to check that the new settings were applied successfully.
The next time you reboot, hopefully it will start fine with both sticks installed. -
I'm not too sure how that would work. How would it be able to detect the stick that doesn't work? Regardless, you know more than I do and I'll post back with results. Also, the G.Skill RAM that I bought is supposed to run at CAS9. It says right on the stick that it's supposed to run at 9-9-9-28 @ 1600MHz. The only issue is at 1066, it defaults to 6-6-6-19.
-
Update: Tried that and it did not work. The "broken" stick is not detected in Thaiphoon Burner.
-
hmm, maybe the stick got physically damaged then. Usually the system should still be able to recognise the ram as it's just the settings that are wrong (only used at bootup) and not the functionality of the memory or SPD chips.
-
It almost seems as if it's locked. The system detects the RAM fine. (6GB when booting with the working 2GB stick and broken 4GB stick). It's just that thaiphoon burner doesn't see it.
-
anyone has a modded bios with fan control option?
-
I know I'm coming in out of the blue. Been reading all this stuff intently. Got setfsb, flashed the unlocked bios. I'm down to the pinmod thing. I see diagrams pointing to parts of the clock generator. Do you dismantle those connections, or put a blob of solder to bridge them to the adjacent? This is where my confidence in doing it correctly is really waning. Wondering if someone could show a photo step by step or at least explain in terms of physical proximity. IE 5th from the left top...instead of the BIEI OU49 bridge to the 328QCP-4T8(I made up those specifics but you get my drift?) Any help is greatly appreciated.
-
BTW I got throttlestop too. Disabled the EI somethingorother messed oaround with the multiplier. It did stuff but my cpu because of the (i haven't done it yet pin mod) is still capped at 2.8 ghz. So is it doing something worth while? Or am I just multiplying at a brick wall?
-
thanks -
Anyway thanks in advance! -
Can someone post up a video on the Pin Mod? I'm willing to try it but, even with some [READ: not a lot] of soldering experience, I'd rather not risk it without seeing someone else do it or demonstrate where it is.
-
Heh I love how far this thread of mine went from a simple question to GREAT advancements in achieving the most out of our Laptops.
I hadn't read most of the discussion on Dual IDA vs and OC'd Extreme dual until now.
I am currently OC'ing my X9100 to 3.2 Ghz, which is the best stable clock I can get.
I still have my T9900 (I would have to make my dad ship it to me) and I wonder if I could achieve better clocks and temps than on my current X9100 by using the Dual IDA function. -
Thank you to everyone for their support in this forum - Just finished removing the resistor on my system (Did not ground it though, my soldering iron was just too large...). I will be honest, those things are TINY so unless you are confident with a soldering iron... just say no! (i regretted it as soon as my soldering iron hit the board...)
Anywho, it worked an absolute treat luckily. Increase the VID from 1.025 to 1.0625 to make the system stable but other than that its all great! Ambient temps are about 1 or 2 degrees higher than previously on the CPU which is a 3Ghz T9550! (I dont know why, but it runs cooler... (Even now) than the original P8400 ...)
Huge thank you to Kravis for creating the SetFSB and to Tanware for Throttlestop! This simply would not have been possible without you guys.
All the best,
Demon
-
That is Uncle Web's program not mine....................
-
Then i thank him too!
On another rather odd note... I no longer have my Overclock
System was running happily all of yesterday including a bunch of restarts etc and shutdowns but this morning when i turned my laptop back on i no longer have the ability to change the FSB...
I have tried removing the battery and power cable etc but no avail, when i click write in SetFSB it simply sets back to 266...
Any suggestions would be appreciated.
Warm regards,
Demon -
Anyone out there have any ideas?
All the best,
Demon -
sorry, I've never done the mod so I'm not familiar...................
-
No worries TANWare - a quick update to say that for whatever reason i have yet to identify, i can once again set my FSB... I do not know why but for the moment my P7805U is running again at 3Ghz!
Will let you know if anything changes again.
Has anyone successfully overclocked p7805u CPU?
Discussion in 'Gateway and eMachines' started by andros_forever, Aug 21, 2009.