• Announcements

    • Brian

      Introducing T|I Marketplace/Classifieds!   11/24/16

      After a long wait, Tech|Inferno now has a Marketplace/Classifieds section where all registered (promoted and above) members can participate in selling, trading and seeking out items. This service is free to all members to use as they wish. Currently all ads last for a period of 14 days before they expire for promoted users. Those users belonging to T|I Elite, Contributor, Developer and Moderator have access to 30 day ad periods that are featured   Some easy rules to remember: Do not post multiple ads of the same product. Do not advertise here if you are a retailer or business. You must contact Tech|Inferno for advertising space. Keep ads civil, do not try to lowball members. You may contact them in private via PM if you feel their price is not to your liking. Harassing members will result in an infraction. It is recommended you have Heatware/eBay feedback to establish trading credibility.    Tech|Inferno assumes no liability for any sales posted in the Classified section. Always use common sense when buying/selling with traders and ask for their heatware/ebay feedback!   Enjoy!


Scientia Potentia Est
  • Content count

  • Joined

  • Last visited

  • Days Won


Khenglish last won the day on March 18

Khenglish had the most liked content!

Community Reputation

1130 A Truly Elite Reputation

About Khenglish

  • Rank
    1st Base is Overclocking
  • Birthday 04/11/89

Profile Information

  • Occupation
    student at RPI
  1. Other than being slightly larger the E6530 is identical and can be modded in the same way, but that's it.
  2. Mouser is your best choice. Search for 40k SMD resistors. Case code is what determines the size of the resistor. Get one with a case code that looks correct. I'm thinking 1005 is correct (1.0mm long, 0.5 mm wide). http://www.mouser.com/Passive-Components/Resistors/_/N-5g9n?P=1yzekikZ1yzmoub
  3. If the modified vBIOS did not fix installing the driver then I am out of ideas, sorry.
  4. I explained why the hardware reported ID and the vBIOS reported ID must be the same in my previous post, but this may have been lost in the translator. To repeat, other laptops will refuse to even boot if the two IDs do not match, so having them match is critical.
  5. Both of those images are identical. Attached is the device ID changed to match the 560 SE. I think this will work, but be warned. Clevo systems freeze on boot if the vBIOS and hardware reported device ID do not match. I'm thinking MSI systems just have driver issues like you are seeing, but if you card is by some unseen means reporting its ID correctly on boot and now it's running this modified vBIOS, it may brick with this vBIOS. In this case you will not be able to flash back if your system behaves like a Clevo and freezes on boot. 560SE_ID.rom
  6. What's interesting is that the card is running. It puts an image on the screen. It does work. Clevo systems flip out when the device ID in vBIOS does not match the device ID reported by the hardware. MSI systems probably don't like it either, which could explain your problems when installing a driver. We could modify the vBIOS to have the same 560 SE device ID that the card reports, and then your card may run perfectly fine thinking it is a 560 SE. Trying the above is just a guess though. It may completely brick the card, as it shouldn't be saying it's a 560 SE in the first place. If you want to try it though link your vBIOS here and I will change the device ID.
  7. Unfortunately I don't know what could be going on with the BCLK slider in the latest version. The only problem I ever had was the slider completely disappearing, Intel has a description of all MSRs in the 64-ia-32-architectures-software-developer-manual which you can find on their website. I see no specific mention of MSR 0x194.
  8. The i7-3520M is definitely not turbo overclockable. I'm not sure if Lenovo systems have the proper BIOS entries for XTU to work, or to set the turbo multipliers by any means. If you can lower the multipliers on the i7-3520M in XTU, then an unlocked CPU will let you raise them.
  9. 3x TI 87350d. This increases the current rating on the core from 120A to 240A. A 980m at 1.2V can pull up to around 240W.
  10. It was plug and play on the EM with a system BIOS mod. I don't know if he tried the HM.
  11. The P170EM does not require a GPU to be installed to have video because of the integrated graphics. You can run the 680m in the P170HM if you flash an older vBIOS.
  12. Something that old is likely mxm v2.1, which won't even fit into the mxm slot. An older MXM 3 card will probably work, but is not guaranteed. The HM laptops had a lot of GPU compatibility quirks.
  13. The P170EM should be able to run the 6970m to see if it works. The P170HM can only run the 7970m if it is the exact v1.2 version. The GPU will also need a proper vBIOS flashed on for HM systems.
  14. It sounds like you blew the fuse. Replace or bypass it. You'll also have to flash the eeprom to any backup that you may have because the controller will have set a flag that the battery is dead.
  15. @Prema modified me another vBIOS for the 980 and now P0 and display on boot work with the 980 core switched over to an MSI 980m board (I damaged the clevo 980m board when switching memory chips). There seems to be something wrong with the P150EM system BIOS that is compensated for by a modified vBIOS. An added bonus is the memory now clocks higher than ever with 7.8 GHz usable in benchmarks. I got a 3K display, but am having problems getting a 40-pin eDP cable that's close enough to modify. Here's an interesting picture from September where I was running both LVDS and eDP at the same time. Unfortunately the picture quality was poor.