• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

***G3258 Owners*** - Windows 10 will not install/boot when overclocked

I think this just happened on Windows 7 as well, my MSI B85-G43 Gaming and 4GHz G3258 I picked up for $100 total last year "bricked" itself after installing updates this week (gets to Starting Windows for a few seconds and reboots), and changing the multipliers to Auto immediately fixed it. I doubt I will see any BIOS updates for my board, but it was a fun combo while it lasted...
 
I don't see why it shouldn't last a bit more: remove the offending dll file. I didn't try it in w10 but w8.1 seems OK with it. No reason why w7 should be any different.
Have more fun if you can :)
 
this will suck if i can't OC on my B85. i bought the G3258 specifically for OCing and luckily my board initially supported it. er, still does, except for the fact i can't install Win10 regardless of OC or not. and i'm not about to buy a Z97 due to current income situation.
 
And I was recently schooled (here) on the FACT that "The days of software being screwed over by an OC are all over" Right on!
 
meh devils advocate in a way i guess you could say they solved the problem? What is more interesting to me is how they are doing it? Im curious as to why modifying or deleting the authentic intel dll allows the use of the chip overclocked on some systems. but only in single core mode? That doesnt make much sense. I can only imagine its a break in the chain if you will. There has to be more too it. They have to be pulling motherboard information and making the distinction. If thats the case all taking the dll out of the equation does is confuse the OS as to what intel CPU is used on the mobo. The actual problem isnt fixed. That also probably explains why only one core works since it cant use the advanced sync or call functions to the CPU itself. meaning that HT encryption entire cores etc are probably unavailable. though im sure WMI pulls the information fine.
I'm still trying to work out how a CPU microcode update was done using a .dll via Windows. The only microcodes I know of are in the CPU MSR's and updated by a BIOS flash.

Sounds like maybe someone is telling porkies? :D I suspect it has to do with Windows Power Management ACPI, not microcode.
 
Microcode is a bad choice of file name from MS. What actually happened has probably more to do with their invasion of the motherboard BIOS with UEFI, so gaining even more access to more unique and reliable information about their customers and control over the harware.
They use this information for some nasty purpose, obviously now. Little by little they come to make this nightmare we had about "palladium" come true. I remember clearly how grim the future sound when Xp was but news articles and Intel CPU unique ID project seemed far fetched.
Last month the two of them collude together to prevent cheap overclocking (like "cheap" wasn't the point to begin with). Last week MS released a revised EULA for so called "Windows Services" that you have to sit down to fathom. Tomorrow... seems grimmer than ever.
We are being lazy and the evil geek has no shame; let's just avoid complaining like we're not responsible for it and start doing what's right : free software....
 
No luck.

Will try this. I know it goes against proper troubleshooting, but I am going to disable one core while I do this. I just want windows 10 installed. I can fix it later. It takes almost 24 hours to get windows 10 to upgrade on this pc, while it took 3 hours on my slower laptop.

edit: This worked. I deleted that file and ran with one core while installing. After install I tried running it with both cores installed, and it failed to boot. I eagerly await a bios that will allow me to enable both cores. For now I am happy that I have the install out of the way. The computer is not being used much right now, so a single core is not a concern.

So I checked if there was an update for my bios. There was from 8/6 with cpu microcode updates.

So instead of only being able to have windows 10 running with a single core, I now have both cores unlocked. Overclocking options are gone from the bios. I can adjust voltage, but I can not increase core clock.
 
Last edited:
I have installed/updated to Windows 10 and I am running a G3258 with Gigabyte Z97X-SLI motherboard @4.4Ghz, both cores, no problem.
W10 is uptaded and is showing two cores!
 
Found this windows forum for those that still have a problem for their G3258. The user by the name ThinkingMonkey have a solution

Hi McD,

I've found a 'solution' (until Intel and Microsoft get off their a** and fix it) and it's amazingly simple, no registry editing, changing Windows settings to try to disable the core for a second then re-enable it, or anything.

It's simply changing the name of a single file. Hard to believe but true.

I not only re-enabled the 2nd CPU core (now I have both, as it should be) but I re-applied my overclock and have experienced no problems whatsoever. It appeared that the only way G3258 CPU owners were getting Windows 10 to install were either disabling 1 core in the BIOS or removing all overclocking settings (using 3.20GHz with Adaptive voltage (all stock, in other words))

Here's how to fix the problem for now:

1) Either disable one core of the CPU in the BIOS or remove all OC and return to stock settings or both. Whatever it takes to install Windows 10 successfully.

2) Once booted into Windows 10, navigate to C:\Windows\System32 and find the file named 'mcupdate_GenuineIntel.dll'.

3) All you have to do is rename it (most posts I've read say it's safe to just delete it but I prefer renaming it), such as adding .old or .bak to the end of the filename. So it would look like 'mcupdate_GenuineIntel.dll.OLD' or 'mcupdate_GenuineIntel.dll.BAK' (or 'mcupdate_GenuineIntel.dll.MyStupidCat' will also work
001.png
)

4) You will have to temporarily change permissions on the file to change the name since it's a system file and will say 'File Access Denied' when you try to rename it (or do anything with it, really)

Change the permissions:
(Credit: © 2015 Sergey Tkachenko at WinAero.com)

There are pictures on that site if you prefer to go there and do it that way, but I'll just describe it with steps.

This may seem like a lot of steps but it's all the steps necessary for someone who has no previous experience working with file permissions. For those who are, just set permissions as usual to allow renaming of the specified file.

1) Right-click on the file whose permissions you wish to change ('mcupdate_GenuineIntel.dll', in this case)

2) Select Properties then click on the Security tab.

3) Click on the Advanced button. A window named 'Advanced Security Settings for Data' will open.

4) Here you need to change the Owner of the file. Initially it should say the Owner is 'TrustedInstaller'.

5) Click the blue letters just to the right of that that says 'Change'.

6) A small window named 'Select User or Group' will open.

7) You will need to select a User or Group. There are a couple of ways to do this and this step may cause some confusion but here's how I do it:
a) Type your name or whatever the name is of the current user (click the Start button at the very lower left of the Desktop and the name is at the very top of the left column) into the box that is named 'Enter the object name to select'. The spelling must be exact.
b) Click on the Check Names button. It should then show the name of your computer plus the name you just entered.
c) Click OK.

8) Now you will provide yourself full access to the file. (which will allow the renaming of the file without the Access Denied message)

9) Close all open dialog boxes by clicking OK on each of them.

10) Right-click the file (mcupdate_GenuineIntel.dll) once more. Select Properties then click on the Security tab.

11) Click the Add button and the box from before named 'Permission Entry for Data' will open.

12) Click on the blue letters that say 'Select a Principal'. Once again the small Select User or Group box will open.

13) Again type in your name or the name of the current user (same as before) and click Check Names then OK.

14) This will take you back to the box named 'Permission Entry for Data'.

15) Make sure there is a check mark in Full Control then click OK and OK again to close all open dialog boxes.

You can now rename the file.

After renaming it, reboot the computer and enter the BIOS to re-enable the CPU core that was disabled which allowed the installation of Windows 10.

You can now also re-apply any overclocking settings that you wish if you do so inside the BIOS. I prefer this method but it's not necessary at this time if you use a utility such as Intel XTU (Intel Extreme Overclocking Utility) to set overclock settings from within Windows.

That's it.

Windows 10 will now boot normally with both cores of the G3258 CPU enabled and any overclocking you wish to add.
 
Found this windows forum for those that still have a problem for their G3258. The user by the name ThinkingMonkey have a solution
That has been listed. I tried it and it did not work for me at least.
 
has this gotten anywhere I really wanted to build a pc with this chip to do some gaming
 
has this gotten anywhere I really wanted to build a pc with this chip to do some gaming
Most motherboards have updated their bios so you can use both cores. If you want to overclock use z97 because overclocking does not work on anything else anymore.
 
I'm looking at this board
Gigabyte GA-Z97X-SLI
or
GIGABYTE GA-G1.Sniper Z97
 
Pentium G3258 is a total crap, I had it for a 3 months and sold it. Now I'm going to buy an FX6300.
 
Pentium G3258 is a total crap, I had it for a 3 months and sold it. Now I'm going to buy an FX6300.
Funnily I felt different, had mine for 6 months, ran it at 4.5gig and it flew at everything, never had any issues. There are a lot of them that hardly overclock at all though, the one I had before would not do more than 4gig but I got rid of that one quick.
 
Makes you wonder how many different Intel CPU's Intel are going to cripple for overclocking by secret micro code updates via secret undocumented win 10 updates
tin hat time

Ps don't say it wont happen it has already started with this pentium CPU
 
Makes you wonder how many different Intel CPU's Intel are going to cripple for overclocking by secret micro code updates via secret undocumented win 10 updates
tin hat time

Ps don't say it wont happen it has already started with this pentium CPU
Well, if it stops a "K" series Cpu being a K series CPU then ask Microsoft for a refund of the difference between the K and non K version :D
 
I am still using my G3258, it is the only cpu I have unless anybody here is willing to sell me a 4790k at a low price. A duo core is to lacking for heavy usage nowadays. The minimum should be a quad core.

My G3258 is still a survivor at high voltage funnily enough.

Intel have been clamping down hard on "free" or cheap overclock for years already starting with sandy bridge where we cannot clock the fsb like the old days. Their doing a good job at it to segment the markets. I miss the cheap overclock days. Nowadays overclock is no longer cheap.
 
starting with sandy bridge
they started way earlier than "dear Sandy" as far as i know or remember the P111 was the first that had locked multipliers
My first serious overclock was with a P2 300 ( 300Mhz to 550Mhz ) and that was achieved by setting Jumpers/dip switches on the motherboard. (unlocked multiplier )
 
they started way earlier than "dear Sandy" as far as i know or remember the P111 was the first that had locked multipliers
My first serious overclock was with a P2 300 ( 300Mhz to 550Mhz ) and that was achieved by setting Jumpers/dip switches on the motherboard. (unlocked multiplier )

Got to love your ingenuity. That is so much harder to do! I am not that far back. I guess overclocking was not an intended feature.
 
Overclocking was not an intended feature until Intel realized that the market they created ( the overclocking community and subsequent industry ) Could be EXPLOITED !!!!
and So Intel Released the Extreme CPU with UNLOCKED MULTIPLIER
ONLY $999.99 (Regular CPU $200 ) P4EE socket 478
Ps the prices are only a piss take example but you get the Exploited idea
 
Pentium G3258 is a total crap, I had it for a 3 months and sold it. Now I'm going to buy an FX6300.
That is an offily strong statement. It really depends on your task you are using it for. Is it bad in all scenarios? No. Is it not as good as other cpu's in other? yes.
 
Instead of changing boards why not just buy an i5?. I would rather have any 1150 than a FX6300
 
Last edited:
The CPU is indeed crap. But well it is not Microsoft at fault. Intel provides those binary blobs and microsoft just bakes them in.

Just as the late squeak that bios update brakes windows activation. M$ burn at stake... The fact that obviously the updated bios lacks needed id strings remains silent, just a borked build by oem.

Sell this cpu and mobo is the best suggestion... Especially if you seek more power and OC is vital for you.
 
Back
Top