Search the Community
Showing results for tags 'microcode'.
-
What's Intel Microcode? How does it affect me? It my first time on Linux and I don't know almost anything about it, but I want to learn.
-
So people considering buying Ryzen CPUs, rejoice! It looks like the info was leaked by Gigabyte's rep: For comparison, here are fixes & improvements from their previous Ryzen AGESA code update: So pretty much TL;DR: In my opinion it's great that the update came, but it should have been here since Ryzen R7-lineup launched. It's good though that most of the RAM kits out there should be working properly after the microcode update, even the "Intel-friendly" ones. Sources: http://www.tweaktown.com/news/57410/amd-ryzen-microcode-update-improved-ddr4-support/index.html https://www.techpowerup.com/233106/amd-readies-ryzen-agesa-update-to-improve-ddr4-memory-support http://hothardware.com/news/incoming-amd-ryzen-update-expands-ddr4-memory-support I will update the post when AMD releases their official community update with the news and release notes, here's a link to the previous one that was released almost exactly one month ago: https://community.amd.com/community/gaming/blog/2017/04/06/amd-ryzen-community-update-3 ----------------------------------------------------------------------------------------------------------------------------------- ###[UPDATE 19.05.2017]### https://www.forbes.com/sites/antonyleather/2017/05/18/an-interview-with-amd-the-latest-on-ryzen-memory-support-game-performance-and-ryzen-3s-launch/#695a3e555ff4 The update is coming "in late May" according to Robert Hallock - AMD's head of global technical marketing: More interesting info from James Prior (product manager for Ryzen):
-
So I am trying to install the latest version of tails on my computer through a cd. When i boot into it I can the menu screen where it gives you the option to install it. While installing (3 minutes in) I get a error code saying "Modprobe module microcode not found in modules.dep" please somebody teach me how to fix this. Im very new to linux and dont know how it works. Thanks for your time!
-
Fudzilla wrote an article about how intel's Skylake and Kabylake CPUs have a broken Hyperthreading and users must disable it for the meantime. Originally from debian.org - Fudzilla - This doesn't only affect Linux systems but other systems as well. ...i5 users rejoice! ...perhaps
-
Hi....I have a Gigabyte motherboard GA-EP35-DS3R. Thing is, I have a Xeon X5270 on its way to be installed on this board. However, I have to add new microcode to the BIOS in order to get the full performance of the processor. Here where the problem came, I tried to use MMtool to insert new microcode to my bios file, EP35DS3R.F4, but it won't load the file. Someone on the internet said to just change the ".F4" to ".ROM" instead, when I did that, MMtool gave me error "Error loading ROM image (100003h)". Please help me... or if will it affects the performancec if I don't insert new microcode? EP35DS3R.F4
-
Has anyone ever encountered that error? It prevents my PC from booting, it works, but there is nothing going on besides components visually doing their thing inside the PC case.
-
Hello guys, I bought from ebay a gpu that was describded as a gtx 750 ti, but in fact was a gtx 550 ti. Now, I tried to flash to the proper bios using the CH341A programmer and this stuff. The bios chip was the one below. (MX25L512) My problem is, that after I reflashed the bios when I try to install the driver, when I go to device manager and scan for changes my screen goes black and I cannot do anything but shutting down/restarting the computer so my gpu is unusable. What I need to mention is that before finding the proper bios chip on the cpu, I connected that programmer clip to the below chip (EM 5103) and I did some modifications there, so that could be the problem. So what do you think? Is that the issue? If yes, what can I do about it? If not, what else could be the problem? Thank you very much in advance.
- 17 replies
-
- gtx 550 ti
- microcode
-
(and 3 more)
Tagged with:
-
Does anyone know a website called "<link removed>" ? I found it accidentally before when I was searching for some CPU information, and it just caught my attention. In this website's "about" tag, there are some explanation of how it worked. It seemed to make sense to me, but well, is it really that simple? If so, then why the hell are Intel engineers working hard on getting more performances on their CPUs by increasing their architecture? I searched on youtube, and it turn out to be a fxxking joke haha. It even don't require a restart, still it claims to have flashed CPU microcodes.... There are also some other websites claiming more RAM or more internet speed. Fuck those bro.
-
https://www.techpowerup.com/247028/intel-gags-customers-from-publishing-performance-impact-of-microcode-updates "The company has hence updated the license terms governing the microcode update distribution to explicitly forbid its users from publishing comparative "before/after" performance numbers of patched processors."
-
As title says, Intel has given up on mitigating spectre variant 2 after having multiple issues making a functional microcode updates, as well as seeing low customers demand for such patches. Note spectre variant 2 only affects older chips: The newest chips that are on the list that I can make out are the 1000 series core series. If you have a sandy bridge processor or newer, this vulnerability does not affect you. This leaves the "Intel core", "Penryn", and "Nehalem" architectures vulnerable. These architectures are all 10+ years old but nonetheless I still think it's reckless to not even try to secure them. Im sure there are plenty of ATM's, School PC's, and other critical systems running these chips. That being said, anybody still running these chips likely are running Windows XP or Windows 7, so it's not like they were secure anyways. I still believe these should be patched, and even if not for practical reasons. It's important to foster an environment of zero tolerance for security flaws in a company, as well as proving to your customers you stand behind your products. Source: http://www.zdnet.com/article/intel-we-now-wont-ever-patch-spectre-variant-2-flaw-in-these-chips/ this was written on mobile when extremely sleep deprived so if I missed anything let me know
-
What up guys? Hope you having a good Sunday. Of with the maners and into the matters... So, for last few days I've been dealing with a butt load of BSOD's on my desktop. It all starded Monday or Tuesday when I was starting to play The Talos Principle. A couple of minutes into it the game crashes and I get a message box saying "File signature verification failed (Content/Talos/All_02.gro).". I proceed to press OK and boom, the saga begins. BSOD, stop code: MEMORY MANAGEMENT. *Computer restarts* *BSOD's while logging in* This time I wasn't able to catch the stop code but it just self restart again and I let it do it's thing. Fine. Sh*t happens... Let's just reboot and proceed with life. Computer turns back on like usuall, I hop onto the game and 5 minutes latter the game crashes again and the same message pops up. This time though some particle of the universe must have hit me and I decide to record the thing in case it does it again: BSOD after game crash Alrighty then... Probably just a bad game install and some corrupted files. I've been wanting to format the sucker for a while now due to the OS install being 2 years old and Windows being Windows (stuff like the start menu not opening and stuff being really slow to respond. The explorer would sometimes take over 10 seconds to open from the mouse click. This was totally random and happened in some OS boots and not in others. I checked the drive performance at this time and it was pretty good.). But before I wipped out everything I decided to grab BlueScreenView and have a look at the dump files. The culprit was pointed out as being ntoskrnl.exe (the system kernel). I was about to look it up on the webz when it blue screened again when opening Chrome with the same code (wow, such hard, much demand). Decided then to do some stress testing. Left AIDA64 to run with the CPU, FPU, Cache and memory boxes ticked for about an hour and all was good until I stopped the test and 10 to 15 seconds latter it crashed again. Same thing. I repeated the stress test for 5 minutes and stopped it trying to replicate the issue. Nothing happened this time arround until I opened Chrome back again and started typing away. Fast foward to the next day I go about formating the machine. All goes fine except for me wanting to do a secure erase on my SSD and ended up giving up because Samsung's tool refused to recognize I had a compatible drive (maybe it wasn't after all). Thanks anyway uncle Sammy. I get the OS and all the most up to date drivers rolling. All is going nice and smooth up until this point. But midway through installing my programs I start to get random BSOD's again. No significant load was being applied or anything. Stuff just went down completely out of the blue. (pun intended) It go to the point where it would BSOD many times while rebooting and the BSOD's themselves looked like they wanted to blue screen too! Here the stop codes started to get more diverse. A few examples are: MEMORY MANAGEMENT; PAGE FAULT IN NONPAGED AREA; QUOTA UNDERFLOW; BAD POOL HEADER. Because at the time and still up to this day I couldn't really link any programs that could have been causing this (I didn't install any anitvirus nor hardware tweaking software that ran at startup or anything like that aside from AI Suite 3, but that was done long before the issues started to occur) I decided to keep installing and just punch through it so I could create a system image with everything configured before dealing with the issue. That done I finally began with the serious troubleshooting. Ran the AIDA64 stress test with the CPU, FPU, Cache and memory loads selected all at the same time and individually, the cache and memory benchmark and even Cinebench. I could not get it to crash while under load. Now the interesting part is it would crash seconds after I stopped the memory load on AIDA stopped the test, let the RAM usage come back down and start it again, navigate on the web or the OS or almost every single time I ran Basemark Web 3.0 and it got to the draw call test. This is the only pattern I have been able to find so far. That said, I decided to scrap my overclock and test at bone stock settings. Same thing. Next, I bumped up the IMC and RAM voltages a tad with everything else untouched to see if it could really be a fault related to that since the stop codes have been indicating so. Surprise surprise... No changes. Still BSOD'ing. Booted up again now with the OC applied back again and the voltage adjustments to the IMC and RAM applied to test (the added voltage weren't necessary to the day. the system was rock stable at those OC settings). Still no changes. Next up on the list: different RAM configs. Tried every. single. thing. Swapping the sticks arround, using only one at the time, cleaning them with alcohol and blowing the dust off the slots. Nothing helped a single bit. Onto taking the OS out of the equation. Enter MemTest86. Ran it for hours with both sticks. Flawless. At least I think I saffely assume my hardware is in good working order. Me and the wallet are relieved. The other thing it popped into mind was the meltdown and spectre patches that have been known for not being the nicest pieces of software of the moment in regards to leaving your computer running well. They are kinda resemblant of chemotherapy in the way they bring many side effects. With the InSpectre tool I disabled both protections but it didn't help. I'm not able to uninstall the updates themselves because they seem to be embeded into the current Windows 10 image already and don't show up on the Windows Update history so that's the best I can do reagrding that. I also uninstalled the Nvidia drivers I had (the most recent ones at the time of writting, 390.77) and swapped them for the 388.13 but it was worthless. The last thing I've done was to go on msconfig and switch the startup mode to diagnsotics but that didn't help either. *Phew... Done. That was a lot of text* System Specs: Windows 10 Pro 64 bits; Intel Core i7 6700K; Kingston HyperX Fury 16GB (2x 8GB 2133MHz CL14); Asus ROG Maximus VIII Hero; Asus Strix GTX 1080; Samsung 950 Pro 512GB; Western Digital Red 2TB; Corsair RM650; Corsair H110i GT; Original build date: over 2 years ago (HDD added 6 months latter and GPU 1 year latter) All drivers and BIOS were up to date at the same time at some point during the diagnostics process. Link to the public Google Drive folder containing the available dump files (a bunch didn't end up being available god knows why), a SysPerf report and a few pictures I took of some of the BSOD's: BSOD Troubleshooting Files And that is all for now from me for now guys. I'm counting on you little geniuses to help out this desperating chap that wants to play something before the next semester begins . Not that I help much if anything arround here... I don't P.S.: Sorry for the long and over detailed explanation but I felt like detailing as much as possible. This crap has been driving me nuts. I've lost a few hours of sleep already trying to figure out what the heck is wrong. P.S.2.: The system has now been runing fine for just over 2 and a half hours while I've been looking arround and writing this post. Let's hope I don't jinx myself... EDIT: Recap of what I've done so far: Shuffling the RAM arround, using only 1 stick and cleaning it; Running at bone stock settings and messed with the IMC and RAM voltages to try to improve stability; AIDA64 stress test comes out clean if I don't do the above mentioned; Cinebench comes clean after multiple runs; Basemark Web 3.0 makes it BSOD almost everytime during the draw call test; MemTest86 comes out clean; Disabled Meltdown and Spectre patches; Tried older Nvidia drivers; Diagnostics mode through msconfig; Running Chkdsk on the OS drive says everything is fine and the same for SMART data. One thing I forgot to mention is that the system also crashed while running Unigine Superposition (BSOD).
- 20 replies
-
- bsod
- windows 10
-
(and 4 more)
Tagged with:
-
I recently found a page on github where one can find the microcode of various Intel, AMD and VIA cpus going back to 1997. I opened one of those files in a hex editor and dissassembled the contents to find that it contains valid x86/x64 assembler . My experience with microcode is mainly limited to pre-90's CISC machines, but i was always told that microcode is what the operation of the microsequencer/FSM for decoding and control signals , and isn't really "code" in itself, let alone coherent machine instructions of the target ISA. I see people refer to microcode as something that seems more powerful than i originally though it to be , as in something that can fix logic flaws .I am under the impression that updating/patching it can ONLY solve control signal-related problems. Is my original view of microcode wrong, or simply not applicable to current generations? Am i mistaken?
-
As spotted by grsecurity on Twitter: Intel seems to have released a Microcode update yesterday (8th) that covers almost all of their range of processors, including a range of server processors like 64-bit Intel® Xeon(s). It's still unclear as to what this update addresses exactly (confirmed via multiple news sources) but one can speculate, based on TechCrunch's citation of Intel's CEO, Brian Krzanich (quoted below), that these updates will be addressing the previously disclosed CVE-2017-5753, CVE-2017-5715 (Spectre 1, 2) and CVE-2017-5754 (Meltdown). This microcode update comes as a "handy tool" for system administrators managing the Linux platform as it features an after-boot update mechanism: Update (11th): Several performance impact reports have been made so far about this and other kernel/bios updates released across the board, most of them show a decrease of up to 6% in performance on (new) Intel Hardware (6th Gen+) and some bigger impacts on older platforms (5th Gen and Below).
-
I'm getting ready to build my first major PC from scratch. I'm a little inexperienced in the building process itself but I do have a good bit of experience and general PC knowledge. My questions are in regards to what bios I should flash on to my motherboard. I am planning on overclocking a non-k processor with a bios and guide that I've found on a website called overclocking.guide - I only recently found out that when I decide flash my bios to the one downloaded it will disable the IGPU. I'm fine with this, but I can't have it disabled immediately. I don't have enough for a good discrete GPU yet and I have to have this computer for college work too. I have several concerns I'm going to address and I'm not sure how many or if any are valid, so please bear with me on this long list. 1) Gigabytes website shows several bios versions, one of which states it "updates microcode" but shows the release date of October of 2015. Surely this is a different microcode update than the one I've read about that will disable bclck overclocking right? 2) If it does update the microcode does that mean that version and any of the later versions likely do the same? 3) What are the chances that the microcode was also already installed on the board and will update the CPU microcode on the initial boot regardless of what I flash it to? And would it matter if I temporarily installed say a 1151 Pentium and then flashed it and used my main CPU afterwards? 4) Do Ice cubes really melt in the winter? I realize that this is all extremely situation specific and complex but I'm hoping that someone with more experience and knowledge into this sort of thing will be able to offer some kind of suggestions to a possible solution.