Jump to content

tmash

Registered User (Promoted)
  • Content Count

    45
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by tmash

  1. Hi all, After I saw this result: http://hwbot.org/submission/2830783_0.0_cpu_frequency_core_i7_4700mq_4550_mhz , I got interested to replicate it with a similar method and decided to share my steps to score higher than a desktop 4.4ghz 4770k (according to cinebench ;)) Intel Stock microcode has a Turbo multiplier bin glitch that allows unlimited multiplier increase, I used prema's bios and removed a cpu microcode update to let the cpu run the stock glitched microcode. I will share the bios file, use it at your own responsibility and if you know what you are doing. 1) Download or dump your BIOS, if your bios is ami (my case) then use AFUWINx64 2) Get AMI Aptio UEFI MMTool v5.0.0.7 and UEFITool, HxD (or your fav hex editor) 3) Open your BIOS image with UEFITool, then File>Search, in our case Haswell has the following ID: , enter C3 06 03 in Hex pattern dialog click OK 4) You can see the last four Hex pattern result, double click the first result and a structure item in the main dialog will be highlighted, right click>Extract as-is to a folder (be sure to be neat and organized or you will mess things up) 5) Do the same with the third result and save it as a diff name other than the first one 6) Now in the folder you have saved the 2 files from step 4&5, open the first one with HxD(any hex editor) and look for be sure to choose Datatype:Hex-values then hit search 7) Press F3 to find again till you reach this pattern(highlighted): 8) (1) Indicates the microcode version, 17 in this case, we want 00 (cpu stock), (2) the platform ID (the search context we reached at) (3) the microcode length = 5000 (in my case) in reverse (important to know when the microcode ends in order to remove). 9) Adjust the cursor on the beginning of the highlight text/microcode (01) right click>Select Block>Length>5000 or whatever in your case 10) Delete the highlighted blocks (after step 9) then save the file 11) Do the same with the second result from step 3 to 10 then save 12) go back to UEFITool, double click the first result like you did in step 4, right click the highlighted structure in the main dialogue > Replace as-is then choose the FIRST file you edited in HxD 13) Double click the third result and follow step 12 with the SECOND file you edited in HxD 14) You will see "Rebuild" in action row, File>Save image as> P15SM04.PM2 in my case (can be any name as long as your flashing tool recognize it) 15) Open AMI Aptio MMTool > Load Image > your modified rom > CPU Patch Tab and verify there is no 06C3 in CPU ID 16) Be brave and flash your BIOS Windows Mod to remove auto update microcode on boot: Click on Start Type CMD in the Search box Right-click on CMD and choose Run as Administrator In the Command Prompt window and change to the directory where the file is located. To do this, use the CD command. You can follow the example below. to change to the Windows\System32 directory you would enter the following command and Press Enter cd \windows\system32 Now use the DEL command to delete the offending file. Type DEL mcupdate_GenuineIntel (and backup) Done! Overclocking: 1) Check CPU MCID:Download AIDA64 , open AIDA64>Motherboard>CPUID and look at IA Brand ID, it should be 00h 2) Download the latest beta Throttlestop (not stable) in my case 810b2 3) Make sure you don't have XTU installed or running (especially at startup) or it will reset any changes in Throttlestop 4) Open throttlestop, click FIVR and look at "[checkbox] Overclock [DIALOG] Max" and note it down 5) Now here is the magic! close FIVR and open it again, [DIALOG] Max value should increase by 2 (up to 80x max ~ 8ghz) everytime you open and close FIVR aslong as long as you increase one of the cores, LOL 6) Increase "Set multiplier" to maximum after your final changes in FVIR (Iv set mine to 42x all cores, so I increased set multiplier to 42 aswell - note voltage ID is messed up ignore it) 7) Increase voltage in FVIR for stability by using cinebench run 3 times instead of prime95, as it stresses FPU which increases heat and tdp instead... 8) Unlock maximum TDP and turbo wattage in TPL, in my case: 9) Done! Changes should be persistent as long as you dont save and exit from BIOS, here is my result in Cinebench with temp throttling (from 4.3 to 3.9 ghz), room temp 25-27 XD: (no.1 at 4.2ghz, no.7 stock latest microcode) UPDATE: OCed RAM from 1600 to 1866, cpu@4.3Ghz, +200mV adaptive vcore: I'm also getting 852 with 4.5ghz with this adaptive voltage-like method: Note: You can maintain maximum turbo multiplier bin with latest microcode after setting it in throttlestop (imp: no crash when testing; make sure its stable) then flash the latest microcode for bug fixes (more stable on my side at x45 with only +230mv, depends on your CPU, i7-4800+ will require less voltage), and you will still be able to set the bin high (up to 80x) as long as you don't crash... Post your results and I'll copy it here. Tips: I highly recommend lapping heatsink and use liquid metal thermal paste or any decent tp ( I used collaboratory liquid ultra) before doing this -If your cpu throttles no matter what, try decreasing dynamic voltage in FVIR and look at maximum value the package power indicate while stressing, decrease the value by 10% in order to avoid rapid throttling (happens with bad TP) -Do not attempt the OC if you are looking after long service life wear&tear (I expect 2 years from now if I stress the cpu everyday for an hour, which i never do :P) Happy overclocking, and don't melt your laptop Thanks to Intel if they leaked this on purpose, kinda futureproofed my machine XD P150SM 1.03.05 modded bios (at your own risk): MOD EDIT: link removed, please use a clean BIOS base because of legal implications with Intel :
  2. Hello earth, WARNING: although this is a semi-guide, what you're about to read isn't for the faint hearted XD, I'm not responsible for any damage, fire, death to your pet etcetera if you attempt to do it... As you may already know, you cannot force custom timings on intel igps, unlike dGPU system only, since Intel IGP cannot do EDID overrides. More about EDID: https://en.wikipedia.org/wiki/Extended_Display_Identification_Data The solution was to dump the EDID which can be done using modeline in windows registry, linux modeline, or dumping directly from the EEPROM (electrically erasable read only memory found physically in most screen logic) which should be straightforward as we need to actually reflash it with our modification simply over i2c interface using arduino (simple 328 with serial-to-usb, can be from 8$ to 25$ max) you can also buy an EEPROM programmer which can be slightly expensive. The screen I have is a CMN1B, Chi . Should also work with AOU 95% gamut screen, any screen with i2c interface to eeprom, you can actually trace it along the 18th and 19th pin from the LVDS cable, however it should be pretty visible. So I ended up (easily), disassembling the screen as per this guide: [GUIDE] How to replace an LCD panel on a Clevo shell (pictures included) | NotebookReview I've then cut the film from both sides then taped for making it easier to work (i.e: instead of cutting EEPROM's pin location): There are 2 EEPROMS in my case, identified it simply by looking at the test point tagging, EE_SC SD etc, should be similar in any other displays: Tip size reference, basically any 15 to 30 watts soldering iron should work, unless the testpoints are tiny on other displays like AUO, though it is least likely you will ever have to desolder the EEPROM chip: Sold'er! Roger that(You can see the EE_* tags, SC for clock, and D for data etc): Connect to my Duino(wire it as you normal i2c): My EDID dumped in Linux before proceding to flash: EDID: 00ffffffffffff000daeb11500000000 01160104902213780231d59f56589527 15505400000001010101010101010101 010101010101963b803271383e405a3c 690058c21000001a9b2580ee70382340 3523350058c21000001a000000fe0056 434d3858024e31353648470a00000000 000041319e0000000002010a20200005 BACKLIGHT: 133 range: (0, 976) Backlight: 133 range: (0, 976) scaling mode: Full aspect supported: None, Full, Center, Full aspect Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 (0x4c) 152.5MHz +HSync -VSync *current +preferred h: width 1920 start 2010 end 2070 total 2226 skew 0 clock 68.5KHz v: height 1080 start 1086 end 1095 total 1142 clock 60.0Hz Pasted in Deltacast EDID editor then modified Pixel clock from 152 mhz (60hz calculated in DTD calculator) to 209 mhz, you have to calculate by entering these from the upper code repecitevly from top to bottom 920x1080 (0x4c) 152.5MHz +HSync -VSync *current +preferred h: width 1920 start 2010 end 2070 total 2226 skew 0 clock 68.5KHz v: height 1080 start 1086 end 1095 total 1142 Export the modifications in EDID editor as hex, make sure you add 60hz(original mod) in block 3 so you can switch between 40 60 120, then using find&replace method modify the format according to the next step Then modify the array in the code (acc to format, 0x and ,) upload to arduino: https://learn.adafruit.com/adafruit-tfp401-hdmi-slash-dvi-decoder-to-40-pin-ttl-display/editing-the-edid I'v managed to go up to 120hz stable, yours may be different although the same model number... xrandr output at 85hz: Had to reboot twice on Windows under UEFI boot manager in order to recognize the 120hz option, weird Again, this is not a thorough guide, just sharing my experience. It went pretty straightforward, and simple as a typical EDID modding over VGA cable or DVI.
  3. tmash

    Nvidia surround on pascal gpus?

    Hello, It seems that new Pascal gpus in mxm form factor no longer support Surround? Any insight on why it has been disabled, or how to enable it? 980 desktop mxm supports mxm according to notebookcheck. Thanks!
  4. You should avoid Optimus as it adds noticeable latency. Use kyran 30awg wire or PATA/SCSI (preferred) solder the wires, then tape the entire wire (shield) with copper tape, and connect ground to the copper tape. Don't do twists, single flat 90 degrees is ok, helix like twists are bad. Keep no-dry flux over the soldered pins/contact with wire. Then cover the copper tape with kapton tape to avoid shorts. I was able to do pcie 3.0 gen x8 with my mxm laptop, should be easier with mpcie @gen2.0 Sent from my LG-D855 using Tapatalk
  5. @Derlep Yeah liquid metal fixed my temp jumping, though not max temp as significant. Example: IC diamond stayed consistently at 90 for 50 seconds before it started to increase which is okay I guess. Took long to rise to 90 with gallium on the other hand with -5c difference max temp at 26c room temp. Thats 96c at 4.4ghz@1.28v, and 86c at 20c room temp which is significant due to airflow (active cooling effectiveness is not linear with room temp) v0 and v1 only gives wrong voltage reading, just square the value to get the real one. Power delivery differs between brands and laptops, e.g my p150sm/p170sm supports i7 4940mx which is 65watts, my 4700mq running at 1.20v pulls 78watts at 4.2ghz (stock 48w) which is close. I don't think your model is designed to handle the extreme or high tdp CPUs so you might be putting too much stress on mobo since it's way far from the designed tdp, would explain why Dynamic voltage mode is unstable (my speculation tho). You can also try cooling the VRMs if they're not being cooled, you can post your laptop model.
  6. @Derlep Try MC v1, it works fine on a y510p which had the same issue
  7. yes its totally fine, there is no risk at all playing with microcodes, the important part is bios size and padding insertion, UBUtool does that properly (checked aswell), you can go ahead and do it with confidence. (Note: I don't have access to my PC for the next month)
  8. If your bios is AMI Aptio 4 or 5 ,use Ubutool: https://cloud.mail.ru/public/9SSs/YJbsWyC2V, extract, put the bios in the extract folder, run UBU.bat then change microcode to v1 or v3. I avoided this as I'm not aware of how it inserts padding. I'll update this reply soon once I have access to my laptop.
  9. I don't remember what I did in 6, has to do with MSR199 198 and 150, I'll flash 6 tonight and check again
  10. First, remove the microcode, or do 00h, then open R/w everything select CPU MSR register, do and post a screenshot of it before throttlestop and after throttlestop bin increase (in your case 37x all cores). What throttlestop version are you using? I had similar issue locking at 38x unless I shutdown completely. Also, make sure you aren't using Windows uefi mode, standard uefi is ok as it works here, bios works aswell. Disable fast boot when shutting down.
  11. tmash

    How to overvolt 680m memory

    hey thanks to your quick guide, it gave me an idea where to start with memory OC/OV on my ancient 770m lol I was able to go from ~2000 mhz memory to ~3200 with samsung memory @ 1.51v (stock 1.35v), used 4B pencil as i noticed its less grainy and thus dust and airflow doesnt wipe it out easily i guess, though still havent tested it >1mo. I also had to raise vbios tdp limit since the core started to throttle after memory overvoltage, and now its perfectly stable. http://i.imgur.com/3iRJwed.jpg http://i.imgur.com/eA3MHcc.jpg http://i.imgur.com/V7T8MoL.jpg offtopic, did you actually remove the backside memory from your 980m? " MSI 980m 4GB (no pointless backside memory wasting power) " thats awesome for OCing...
  12. tmash

    [HARDWARE MOD] P157SM cooling overhaul

    Would be nice to see temps with CPU OC, I need more fins for increased "virtual" cooling capacity
  13. I don't mind throttling as long as long as it doesnt stay at tjmax temp, see this video i made for a fix (a.k.a adaptive voltage): switches 4ghz to 4.5 back and forth, 4800 can run at lower voltages, so yours should run much cooler, 180mv at 4ghz, and 270 at 4.5 ghz, insane 360 at 4.6 pulling 110 watts which worries me about mobo components and warping XD
  14. Btw, you can always flash the latest uC after opening the FVIR (bin recursion bug) multiple times till u reach 80x with the old uC Right now i'm on the latest, will add note...
  15. Your uC is stock, not undetected, I'm on 06 right now since I no longer need to do overvolting over 250mv Disable C1E for stability(as it introduces scaling issue), and BD PROCHOT for throttling (down to non turbo clock speeds instead of decreasing frequency by 1 step). Ofc, P157 and P150 has the worst airflow design, try removing the back-plate and see the temp drop down, 10 in my case(punched holes), this is what i have done to both gpu/cpu and decreased around 5c: Check this awesome blog: http://null-bin.blogspot.com/2015/04/extensive-clevo-p150sm-cooling-and.html Glad it worked for you!
  16. Thankfully, my system up time has been 3 days on OC, though I also think MC can improve performance, stock frequency bench on stock MC < latest, I also noticed that in newer MC , CPU voltage has been decreased, 45w mc17 cinebench vs 48 with 1% power throttle current (00) without modifying anything
  17. Done: EDIT: oops, thought you quoted me, sorry... But why would you want to do it when stock (clean) bios has the update anyway? Would be useless without posting how to remove mc from bios first XD
  18. Yeah, i think the microcode in volume 4 (in my case, see scr) gets uploaded when using UEFI
  19. And btw, do you have any idea about the manufacturing date of a new battery? Having a model number P150HM sounds suspicious, that over 4 years old (-30% of capacity due to shelf life XD) Guess its going to cost me to get a new one, should fail soon in case it is over 4 years old :/ , properly disassemble , rip out the cells and replace, or end up getting unofficial batt: http://www.replacement-laptop-battery.co.uk/clevo-p150sm-battery-36615.html (still not cheap, yet cheapest i could find) I was able to get ~6 hours on batt too with cpu undervolting and under Linux first month, and it degraded fast till mid 2015 (since Feb 2014)
  20. I'm having the same problem with the battery case, except that i kinda bent the case, your post is also useful for knowing the boundaries to cut without making fire party XD Why didn't you use Samsung cells instead of Panasonic? I think they have longer service life
  21. tmash

    Post Your System

    Clevo P150SM i7 4700MQ @ 4.6GHz, 1.2 vcore (stock microcode glitch), Cinebench ~830-840 > DT 4770k@4.4ghz RAM 16GB @ 1866mhz GTX770M , core @1154MHz, Mem@2554MHz (samsung), core voltage offeset: +137.5mV (working on external PCIe MXM adapter for Titan X) Collaboratory Liquid Ultra TP on CPU/GPU, arctic thermal pads on cpu vrms and gpu memory 85/120 hz Chemei modded display 128gb crucial m4 msata (SSD) + 1tb toshiba HDD 240w power supply SED SSD Encryption (+password) BIOS mod Optimus GPU mod to use jpeg compression instead of mux for latency (useful for demanding fps game) Punched some d**n holes on cpu&gpu bottom cover vents, decreased -5c(-12c without cover) (highly blame Clevo on that) Modded 8-cell battery pack with Samsung 18650 cells (old: panasonic), achieving ~6 hours of web browsing on battery and -100mv on cpu(@1.5ghz max with dGPU off)
  22. Hey thank you for mentioning this, sorry to be dumm about legal issues this might introduce and any wrong attempt I have done.
  23. Haha, though I would be careful modding these if I dont have SPI flash programmer and soldered header :p, screwing up microcode part will change file size and UEFITool wont be able to rebuild which makes it kinda safe...
  24. It would be really nice to try this on other Haswell CPUs, results would be interesting, guess 4900mq can go 4.8ghz stable due to having high quality ASIC compared to 4700mq, 200+mV to reach 4.6 should be less with better cpus
  25. 07 is for 36x on all cores, not +2 bin everytime you read ME settings, anything below 07 works, 07 just for locking all cores to 36x, and yes they are universal, what do you mean one of the microcode is actually important? EDIT: forgot to mention that, 06 to 01 does not allow adaptive vcore increase over 250mV, 00 does
×

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.