Jump to content

Mr. Fox

Retired Staff
  • Content Count

    1456
  • Joined

  • Last visited

  • Days Won

    167

Everything posted by Mr. Fox

  1. Special thanks to @StamatisX and @imsolidstate for great technical advice! 330W AC adapters were purchased new for $30 USD each on Amazon. Required tools and components: 40A 200V bridge rectifier (Mouser - Part #: 821-GBPC4002) Electronics project box (Radio Shack - Model: 270-1809 | Catalog #: 270-1809) Female Spade Terminals (Radio Shack - Model: 76-FT12L | Catalog #: 55048637) Block Terminal (Radio Shack - Model: 274-680 | Catalog #: 274-680) Wire nuts or push connectors (I used what I already had on hand) Heat sink (an old CPU heat sink is what I used and it was perfect) Thermal paste (brand does not matter - I used what I had on hand) Wire grommets or electrical outlet box clamps (I used this type) Self-adhesive rubber bumpers (used as feet for project box) Miscellaneous screws (see photos - I used what I had on hand) Simple hand tools (screwdriver, wire cutter/stripper, etc.) Soldering iron and rosin core solder Drill and appropriate bits Link: Downloadable PDF Instructions Another 4.7GHz run without toggling CPU clock speeds during 3DMark11 tests...
  2. Woman Wins $10,000 From Microsoft After Unwanted Windows 10 Upgrade Good for her! She deserves it based on their bad behavior. Too bad the award doesn't have 5 or 6 more zeroes to the left of the decimal point. The Redmond Mafia needs to learn a lesson for their bad behavior, and that tiny little slap on the wrist will only represent a minor inconvenience to them. They deserve to draw back a bloody stump. Unfortunately, the wickedness of Micro$loth knows no boundaries. They think they own us and our computers. This is what I use to kill all of the spyware and telemetry trash in Windows 10, block all updates and permanently expunge all of the bloatware apps and Windows Store garbage. It also kills and deletes OneDrive and disables (rather than only muting) UAC. Works great... very nice tool IMHO. Destroy Windows Spying I have also found third-party tweaks to replace the hideous giant calculator with the older version, completely kill the obnoxious Security Center nag-o-rama and exterminate Cortana. Notwithstanding the tacky-looking aesthetics that remain (nasty abuse of white and pastel colors akin to the Windows 8.X abortion) it's fairly decent if you go to enough trouble to correct all of their mistakes. Performance in some things is still inferior to Windows 7, unfortunately. I pointed that out as an 'Insider' quite some time ago, but they apparently do not plan to fix it. They started hindering CPU performance in Windows 8.X and they must think it's OK since they are leaving it messed up from then until now.
  3. For those that are not already aware of the issue, the folks at Futuremark seem to be struggling to keep a consistent product in the latest 3DMark benchmark. In particular, Fire Strike. Sometime around the release of Time Spy things started getting screwy with Fire Strike and now it seems with every Fire Strike GUI update the effect is lowered benchmark scores, and specifically the physics portion of the benchmark. Kudos to @Papusan for noticing this months ago. He been going back and forth with Futuremark about the problem and it seems they are either ignoring him or don't care. Maybe because most people are not observant enough to notice or care. Some people might say you cannot compare results across benchmark software versions, but that shouldn't hold water here. There is a leaderboard and searchable database of results and if there is not a high degree of consistency between GUI versions the results in their database will become irreleant, as will their leaderboard. The search filter does not have a field to filter by GUI version, so we can expect the results from the database and leaderboard to be misleading, inaccurate and unreliable. You will notice from the examples posted below that with each new version of Fire Strike the scores get lower and lower. These examples are consecutive runs on the same day, same machine, and identical CPU and GPU settings. The only thing that changes is Fire Strike benchmark results. We need Futuremark to understand and correct this. http://www.3dmark.com/compare/fs/11047304/fs/11047179/fs/11047154 Here is a similar example from @Papusan: http://www.3dmark.com/compare/fs/11036017/fs/11035883 If you agree this is a problem and want it to be fixed, please complain to Futuremark and let them know they need to put the brakes on and not do anything else with 3DMark until they have this mess under control. Gimmicky features are one thing, but inconsistent benchmark results makes 3DMark unreliable. This post has been promoted to an article
  4. I already knew (or so I thought) that gains or losses from different memory speeds and timings made only a small difference in real-world performance, but the allure of something faster is a hard bug to shake. I grabbed some G.SKILL Ripjaws 2133 CL11 memory to replace my Kingston PnP 2133 CL12 fully expecting to see a very modest improvement in performance for my already insanely powerful M18xR2. Unfortunately, the opposite was true. There was a substantial decrease in performance... enough to be seen and felt. I have used G.SKILL memory many times in the past and it has always been great. The Ripjaws was 100% compatible and rock-solid stable. It booted with no BIOS adjustments (all "auto" settings) and ran at advertised speed without any drama. The decline in performance was a disappointment, but NewEgg issued an RMA promptly. I am sharing the results so nobody else makes the same mistake. The images in the album below speak louder than words. Tests were run repeatedly to confirm there was no anomaly. All BIOS settings were identical between the different brands. I alternated HyperX > Ripjaws > HyperX > Ripjaws and the differences were consistent in all tests.
  5. Mr. Fox

    Alienware 17 8 beeps EVGA X Precision

    Hi. Yes, what you do is temporarily install a known good panel, boot Linux. Disconnect the good one and connect the corrupted panel while on the Linux desktop. It will work flawlessly once POST has cleared, but Dell/Alienware made the BIOS in a stupid way to halt if no valid EDID is found during POST. With the corrupted display connected, follow the instructions provided by @t456 using his Linux EDID flashing tools.
  6. Just use compressed air to blow out dust. That should generally be sufficient. If it is really extraordinarily filthy you can use electronics contact cleaner (spray can). I've never needed to use electronics cleaning spray on a computer.
  7. For those that are not already aware of the issue, the folks at Futuremark seem to be struggling to keep a consistent product in the latest 3DMark benchmark. In particular, Fire Strike. Sometime around the release of Time Spy things started getting screwy with Fire Strike and now it seems with every Fire Strike GUI version update the effect is progressively decreasing benchmark scores, and specifically the physics portion of the benchmark. Kudos to @Papusan for noticing this months ago and asking me to have a look at it. He has been going back and forth with Futuremark about the problem and it seems they are either ignoring him or perhaps they do not view it as a high priority issue. Or, maybe because most people running Fire Strike are not observant enough to notice, care, or ask questions they feel they don't need to fix it. Some people might say you cannot compare results across benchmark software versions, but that shouldn't hold water here. There is a leaderboard and searchable database of results that basically every benching enthusiast and PC reviewer relies on, and if there is not a very high degree of consistency between GUI versions the results in their database will become irrelevant, as will their leaderboard. The search filter does not have a field to filter by GUI version, so we can expect the results from the database and leaderboard to be increasingly misleading, inaccurate and unreliable over time. This certainly is not a desirable thing for what is supposedly the current defacto standard in PC benchmarks. You will notice from the examples posted below that with each new version of Fire Strike the scores get lower and lower. These examples are consecutive runs on the same day, same machine, and identical CPU and GPU settings. The only thing that changes is Fire Strike benchmark results degrade with newer versions. We need Futuremark to understand and correct this. http://www.3dmark.com/compare/fs/11047304/fs/11047179/fs/11047154 Here is a similar example from @Papusan: http://www.3dmark.com/compare/fs/11036017/fs/11035883 If you agree this is a problem and want it to be fixed, please complain to Futuremark and let them know they need to put the brakes on and not do anything else with 3DMark until they have this mess under control. Gimmicky features are one thing, but inconsistent benchmark results makes 3DMark unreliable. If you would like to do your own testing to validate the issue before contacting Futuremark, older versions of 3DMark are available for download from the TechPowerUp.com web site. In case you're not good at simple math, here is a visual aid to show what the fuss is about. Update 12/13/2016: We would like to acknowledge that a representative of Futuremark has responded promptly to this article and provided an email address for those interested in communicating with them about the issue. We appreciate the accountability and responsiveness. Update 12/15/2016: We sincerely are grateful for Futuremark's responsiveness. I provided additional test results to Mr. Kokko to corroborate the findings of @Papusan and they have released an update that is expected to resolve the issue. See the message from James below for more details. View full article
  8. Yes, that is a good possibility. If it only began happening after repaste, try taking the GPU out of the socket, blow out any dust or lint in the MXM slot and reseat the GPU. If you're lucky it may just be a bad connection in the MXM slot.
  9. 3DMark Update to Offer Improved Scores by up to 2.5% | HWBOT.org
  10. Hi there. Maybe if you can dump your vBIOS, zip it up and post it here as an attachment, someone with the know how can unlock it for you. The control freaks at Dell/Alienware have been making it more difficult to dump or flash their soldered GPUs, so you should confirm that you are actually able to do both of those things first. You should also have a backup copy of the original vBIOS for your own purposes. If you can dump the original, turn around a flash the original just to verify all that functionality is working as intended. If you push it right now to the maximum possible overclock on the GPU core and memory are the GPU temps still OK? That would be another point to consider. If the limits you have now are already more than the cooling system can handle properly, there may not be much, if anything, to be gained. Maybe max out your overclock with the stock vBIOS and make about a half dozen loops of Unigine Heaven to see if the temps are still OK.
  11. Mr. Fox

    M14x R1 - BIOS A08 with SATA fix

    Hi folks. Maybe this will help. User Account Promotion Rules - READ BEFORE POSTING!
  12. They're too busy working on insanely important junk like NVIDIA Drive, Shield and GeForce Experience to be bothered by something as trivial as device drivers or post-sale product support.
  13. That's really nuts. Now that 1080 is on the loose those dirty rats must be treating 980M owners like the wicked stepchildren now, just as they did all of us 780M owners when 980M was released.
  14. Hmm, that's odd. I don't know what the problem would be if all of those things are correct. Disabling DSE should not be required with W7. I don't have any suggestion at this point since your hardware ID is in the INF. The @J95 mod should work fine. Maybe there is something wrong with your GPU.
  15. Mr. Fox

    M17x-R3 780M Upgrade Difficulty

    I hope you can figure it out. Maybe @J95 knows a trick or two that he can suggest.
  16. You did a nice job of explaining it. And, I agree with you. I prefer using 3DMark 11 instead. One reason is that it is a better benchmark tool, but also because it does remember my custom settings. This is useful for testing purposes and having to manually change everything each time I open the benchmark because it does not remember my last used settings is inconvenient.
  17. @Futuremark_James - preliminary testing seems to show an improvement as expected, and in line the percentage of improvement predicted. Thank you. Any input on why the CPU power monitoring feature was removed? Was it necessary, or something Futuremark thought nobody cared about. See below: Previous GUI versus new GUI released today: http://www.3dmark.com/compare/fs/11094602/fs/11085019 New GUI today using previous driver versus new GUI today using new @J95 driver mod: http://www.3dmark.com/compare/fs/11094778/fs/11094602
  18. Thank you so much, James. I am looking forward to testing the new release and confirming the fix. I trust @Papusan is equally appreciative. Thanks as well to Jarno Kokko (Futuremark) for his assistance. I have updated the article with your response.
  19. @Papusan - Maybe @Futuremark_James can enlighten us on why they disabled the CPU power monitor. I would be interested in knowing why they did that.
  20. Mr. Fox

    [BENCHMARKS] The OFFICIAL Thread

    http://www.3dmark.com/fs/11085948 http://www.3dmark.com/fs/11086024
  21. Mr. Fox

    [BENCHMARKS] The OFFICIAL Thread

    http://www.3dmark.com/3dm/16685920
  22. Have you checked to confirm that your hardware ID is in the INF file? What OS version are you running? By disabling DSE, are you doing that using F8 and choosing "Disable Driver Signature Enforcement" or simply using the bcdedit from command prompt? (Using F8 will still be necessary unless you also use additional "bcdedit.exe /set nointegritychecks on" command to make it complete.) Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 10 locale en-US loadoptions DISABLE_INTEGRITY_CHECKS inherit {bootloadersettings} recoverysequence {b0e9c08e-b894-11e6-83ae-a975ab43e2a0} recoveryenabled Yes nointegritychecks Yes testsigning Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {b0e9c08c-b894-11e6-83ae-a975ab43e2a0} nx OptIn bootmenupolicy Legacy
×

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.