Yen,i followed your advice and went to a serious OC related forum!! i was able to increase my q6600 from 2.4ghz to 3.6ghz thank you for the suggestion!!
Out of interest Jay, which forum did you visit ? I my last rig had a Q6600 and i was never able to get past 3.06 ghz. As Yen has correctly pointed out, it does depend on the batch it came from. I know some engineering samples were pushed very hard indeed !
Congrats. Yes it isn't that simple just to alter the clock. You need to know how the CPU works. There is the multiplier, which can be locked. There is the FSB (front side bus clock). There is a clock quotient (RAM divisor and dividend) There is the CPU voltage. To remain stable when OC'ed it needs to be slightly increased. Best is as little as possible. (Overheat) You need to know how they are related and what changes affect the others (CPU clock / FSB / RAM clock / bus clock) Also the core I's have no more the FSB. There are some useful tools to check it after OCing. Coretemp / coretemp64 to monitor the core temps. Prime95 to stress the CPU / system CPU-Z / CPU-Z64 to monitor the clock (EIST might lower the clock / voltage to safe energy, should be disabled when OC'ed) Prime95 makes the CPU very busy and it will be a stress situation. As result the CPU temp increases very quickly. You need to monitor the temps at the same time, best to start it already before prime starts The OC freaks say the system is stable if it runs prime95 without to overheat much and without to crash. You can have the situation that an OC'ed CPU boots up very well, but as soon as it get busy it crashes. So they use the hardcore prime tool to stress the CPU. If it survives prime95, it survives anything else. The only risk besides a crash of the system is overheating. Also the ambient temperature of your working room plays a role. At summer time when it's 30 degrees Celsius, your CPU might overheat even more. The BIOS usually shuts down if the CPU gets too hot. Some boards have a temp. monitor and a adjustable shut down temp. Prime is very hardcore. As soon as started the temp increases at once. As soon as stopped it drops down immediately. IMHO the cores of the CPU should not be more than 65 degrees Celsius when prime stressing. A high temp a long time might shorten the lifetime of the CPU.
Id be way out of my depth attempting to remove whitelists as im not at all familiar with the dissembly techniques,tools etc so in this case id rather pay someone who knows what they're doing. I have been trying the method of replacing the existing card ID, Only my WLAN card "which I want to keep using" is a half size PCI-E card My new WWAN card I want to use in conjuction with the WLAN card is full size & fits snug into a secondary (un-used) PCI-E socket, but in my case the below procedure does not work when using the secondary PCI-E socket dispite getting the BIOS incompatible warning on bootup. I followed your instructions on How to obtain the IDs: 1. Remove existing wireless card from laptop, leave the access cover off. 2. Boot laptop and enter boot selection screen. Press F8 therefore. 3. Install new card (whilst laptop is running), no need connect antenna wires. 4. Boot into windows and new card will appear as unknown device. 5. Now you can obtain exact ven, dev & subsys id's from device properties Now thinking i've just wasted money on a new 2XGNJ Ericsson WWAN card
No, it is the HP EFI module that triggers the 105-Unsupported wireless broadband device detected. message. I had the disassembled module right in front of my eyes, too. It checks the card's IDs and if not located at the whitelist it triggers the message and halts the system. Is your card Ericsson F5521gw? You have already flashed a mod from bios-mods. And your notebook still boots. This was IMHO the most dangerous part. This proves that an RSA encypted BIOS is properly decrypted by andy's tool /decomposed/ re-compiled and can be flashed back! So the only thing that can brick your notebook then is a wrong patch. camiloml from BIOS-Mods did not find the right code to patch. He has to be very careful with it. So better the patch doesn't work than to get a brick. I will have a look what he did. I can disassemble the code that's not the problem, to understand it and to find the right place to patch is it..... I'd replace an existing ID This means no change of any code. But it only works if I got the right IDs of it! Edit: Can you upload his mod you have tried already to sendspace? It seems bios-mods is down atm..thanks.
There are two modules responsible for the error message. The module that triggers error 104: E62F9F2F-4895-4AB5-8F1A-399D0D9C6B90_2_632.ROM Here is the whitelist and it allows your card to run which you have posted above, otherwise it would trigger error 104 Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 00000EB0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000EC0 8C 16 2B 00 3C 10 3F 30 8C 16 2B 00 3C 10 40 30 Œ.+.<.?0Œ.+.<.@0 00000ED0 E4 14 27 47 3C 10 5C 14 14 18 90 30 3C 10 53 14 ä.'G<.\....0<.S. 00000EE0 E4 14 27 47 3C 10 83 14 00 00 05 00 00 00 05 00 ä.'G<.ƒ......... Here his the module that triggers code 105: 7FA4AE0A-1404-4DCC-BE28-CE58029CF5D1_2_637.ROM Code: Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 00000F30 1C 54 07 00 1C 34 06 00 1C 32 18 70 01 15 03 00 .T...4...2.p.... 00000F40 15 42 11 70 10 30 00 00 00 00 00 00 00 00 00 00 .B.p.0.......... 00000F50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000F60 F0 03 1D 20 F0 03 1D 1F F0 03 1D 24 F0 03 1D 25 ð.. ð...ð..$ð..% This is a part of the whitelist. Here your card's IDs need to be added / replaced. It seems there is even some space left (zero bytes) So all we need to make a working mod are the complete Ids of it. No chance to get the IDs by inserting it into a machine where it runs? Another way would be to have a look at its drivers and to obtain the Ids from the driver setup!
Yes I know. Anyway can you provide his mod? Btw: I am always careful when I mod... I only would provide one if I am absolutely sure. Hence I hesitated to develop my own patch so far.
That would mean going through all his mods one by one & re-uploading, he probably has hundreds. Do you think he would bother going to that extreme?
I think the best is to ask what he has done. I don't know why he has encrypted it again and how he did it. Fact is that he did it well, because it flashed and worked. The only thing he missed is to patch the whitelist properly. I don't know if he is willing to share it. Or if the how-to is found at bios-mods. I am not a member over there. But IMHO he could tell us about his idea since he uses all the tools developed at MDL. Without andy's tool he couldn't mod anything. What is strange is that his mod can't be opened again. All the original HP encrypted EFIs can be opened and decrypted with andy's tool. Either he has completely understood how it works and is a sort of genius, or he did a mistake, lol. He hasn't replied to your report that it didn't work the first time. I am curious what he will do next. I guess I register there and ask him. Maybe I can learn something new.....
No, he's still using a beta of phoenixtool which assigns a bad signature to the modded bios. That's why he has to patch the flashprogram as well. Note: It's probably the best to us HP's EFI Flash, since it looks like the windows program only flashes the DxE image and not also the PEI image [which is needed to get rid of the black screen after updating the bios setting on a modded bios]. BTW: I would highly recommend to make AND !TEST! a bios recovery usb stick BEFORE flashing any mod.
I see! The man with the RSA decryption knowledge that made it possible. Thanks for the update. I had noticed at a EFI history that HP firstly provided their EFI unencrypted and at later revisions encrypted. My idea would have been simply to use the Insydeflash.exe of a previous revision then. Can you point us to HP's EFI flash and have you tried to flash a mod with it already? For recovery you need the decrypted image then, right? Thanks. @netwave Did the BIOS flash at all? If yes I guess you had good luck then...