Question Windows 11 fried my pc

[econcepts]

well, this is odd - I have several older PC's with GA-78LMT-USB3 main boards in them. one had a FX-4100 (4 core) and the other had an FX-6100 (six core). I installed windows 11 on my main PC (just vanilla) and imaged it. I loaded the image on the first PC and it seemed to work fine. Played with it all day - at the end of the day it had downloaded an update so I let it update and restart. After saying to hold on it was updating (or whatever that message was), it rebooted but the screen stayed black. Waited for hours, nothing, so I held down the power button, it shut down. Pushed the power button, it came back on, but no beeps, just a black screen. Tried a different, PS, CPU, removing the memory, clear CMOS, removing the battery, removing all the cables. Determined it must be the main board. Now bear in mind that these PC have been running windows 10 just fine for many years. I chucked the mainboard and set the case aside. Booted up the next one to windows 10. Played with it for an hour, it works flawlessly. I set aside an image of windows 10 and loaded the same image of windows 11 on it. Seemed to work perfectly, even activated with a digital license, and no uninstalled devices in device manager. played with it for hours after which it wanted to update, which I did with the exact same unfortunate result. Different PC, power supply, main board, CPU, memory, hdd, case but same model motherboard just one was revision 4.1 (blue board) and one was revision 5 (black board). Two for two on two perfectly reliable, long running PC. Both dead - will not beep or post at all. I think windows 11 murdered them both. Any ideas, I might have missed?

 

[JohnBonhamsGhost]

the OS itself cannot physically damage components.
this "image" you mention being some malware loaded pirate release that could lead to it would be more likely but doubtful.

how are you getting past TPM and other security features to load Windows 11 on unsupported hardware?

 

[Lafong]

Is this correct:

PC 1 had Windows 10. You updated it successfully to Window 11.

You then made an image file of that PC1 Windows 11 installation.

You then restore that Windows 11 image file to PC 2 and later to PC 3, both of which had Windows 10 and are now problematic.

I'm wondering why this would be a NECESSARILY be a Window 11 problem...

 

[USAFRet]

I also fail to see how this is a Win 11 problem, and not a user procedure problem.

 

[Deleted member 14196]

I don’t know what you’re doing to image it but whatever you’re doing isn’t correct this is user air as mentioned above. Also please answer the question on how you’re able to install it on old hardware. Because this is probably your issue

 

[TerryLaze]

I installed windows 11 on my main PC (just vanilla) and imaged it. I loaded the image on the first PC
...
...
I think windows 11 murdered them both. Any ideas, I might have missed?

I think there is something in your hardware that screws things up through updates.

My guess would be that your mobo updates bios through windows updates and has zero safeguards to check if the actual mobo is there or not flashing any rom they find... resulting in killing mobos.

This is extreme and I never heard of this being a thing but it's the only thing that would explain it to me.

 

[SkyNetRising]

My guess would be that your mobo updates bios through windows updates

I have never heard of bios updating through windows updates. Doesn't seem plausible.

 

[Deleted member 14196]

Installing windows on your main PC and then imaging it and using that image is incorrect! You must install windows on each PC individually from USB installer

YOU screwed it up not windows. What you have done is never going to work ever so expect problems doing it this stupid way. And windows 11 IS NOT supported on any of the old PCs anyway

 

[econcepts]

I think there is something in your hardware that screws things up through updates.

My guess would be that your mobo updates bios through windows updates and has zero safeguards to check if the actual mobo is there or not flashing any rom they find... resulting in killing mobos.

This is extreme and I never heard of this being a thing but it's the only thing that would explain it to me.

good idea but the dual bios should prevent that - bios updates are manual on GA-78LMT-USB3 or through gigabyte @bios which is not loaded. I have been a system builder since '82 and only seen something like this once with bios virus. Even that would not work on this Mobo because of the dual bios (unless you leave it unlocked). It wont even post at all - usually you could at least get a peep out of it by removing the memory, but nada. I am out of AM3+ motherboards so I cant test the CPU, but I tried replacing the CPU with a known good one and still nada - seems like the Mobo was murdered by windows 11.

 

[econcepts]

Installing windows on your main PC and then imaging it and using that image is incorrect! You must install windows on each PC individually from USB installer

YOU screwed it up not windows. What you have done is never going to work ever so expect problems doing it this stupid way. And windows 11 IS NOT supported on any of the old PCs anyway

well that was about as helpful as a one legged dog in a sled race.

 

[punkncat]

I installed windows 11 on my main PC (just vanilla) and imaged it. I loaded the image on the first PC and

Ok, so what is the spec of your "main PC" in which you loaded the vanilla OS load?

Where did you get the download to create that installer?

well, this is odd - I have several older PC's with GA-78LMT-USB3 main boards in them. one had a FX-4100 (4 core) and the other had an FX-6100 (six core).

As has been pointed out a few times above, these are not supported hardware, so really not sure at all how they would have installed, aside from perhaps the situation being that you cloned the first install and then used it to boot these others, I am guessing?
In that instance, the drivers and such would be for the original system and should have given a little trouble on first boot as it looked for appropriate drivers and such. W10 is pretty good about that and would make assumptions that 11 does.....however it doesn't override the fact that none of the FX based systems 'should have' booted from 11 at all.

On these machines that now won't boot, I think you said you did attempt to put back in their original OS and they aren't responding to power cycle or anything, is that correct?

 

[econcepts]

the OS itself cannot physically damage components.
this "image" you mention being some malware loaded pirate release that could lead to it would be more likely but doubtful.

how are you getting past TPM and other security features to load Windows 11 on unsupported hardware?

No, I am careful, there is nothing "pirate" about it. I actually installed it from an official windows 11 pro OEM DVD from MS on new clean hardware without providing a product key so ti would remain un-activated. Imaged with x64 Macrium Reflect V8.0.6635 to an image file (done it thousands of times with windows 10). Restored the image to a wiped used HDD. Windows 11 actually activated with the windows 10 pro digital license assigned to the Mobo and appeared to work perfectly. It was during the update when windows said "dont turn off your computer..." that the screens, each in turn went dark. I suppose if it was just one PC, I could dismiss it as bad luck.

 

[econcepts]

I also fail to see how this is a Win 11 problem, and not a user procedure problem.

thats probably because you have a defective imagination.

 

[punkncat]

thats probably because you have a defective imagination.

I will say this. You came here asking for help or clarity on an issue you have. Being difficult with long time members and moderators will assure your stay is short. IF you want the help, consider it, take it, or don't, but no reason to be a jerk about it.

GL

 

[Darkbreeze]

I have never heard of bios updating through windows updates. Doesn't seem plausible.

It is not plausible, and in fact, could not ever happen.

 

[USAFRet]

I actually installed it from an official windows 11 pro OEM DVD from MS

Link to where you purchased this?

 

[Darkbreeze]

thats probably because you have a defective imagination.

No, you have a defective process. You can't create a Windows image that is intended for use on one machine, with specific hardware, and expect to be able to use it on another machine that has different hardware, and not have issues. It VERY RARELY works, and then, usually only if the hardware is very similar and uses the same chipset family. Occasionally I've seen some success with cross generation or cross platform usage of a Windows installation or image that was meant for something else, but it is the exception and not the rule. Even if it works you will almost always find yourself encountering some form of "ghost problems" or unexplained random issues, at the least.

And as already mentioned, that old AM3+ platform does not support Windows 11 as it lacks the TPM support required for it. I think there is likely more to this story or something here that hasn't been shared with the group, so to speak.

But regardless of any of that, it's a very poor idea to come to a place asking for help and then almost immediately start disrespecting the highest active member who also happens to be a long term member of the moderation team, whose answer WAS 100% accurate, and then expect people are going to want to continue offering you any kind of assistance. The fault is yours, in both regards, so maybe be a little humbler and a little more appreciative if you're going to go to a place and ask for help, else maybe, don't.

 

[Deleted member 14196]

So I was right he installed it on one pc. he made a Macrium image of it and tries to get that image to work with completely different hardware. Wrong it is an ever going to work

Wait did he want the magic answer? The magic answer is there is no magic answer you need to install windows on each box individually using the bootable USB

 

[econcepts]

Is this correct:

PC 1 had Windows 10. You updated it successfully to Window 11.

You then made an image file of that PC1 Windows 11 installation.

You then restore that Windows 11 image file to PC 2 and later to PC 3, both of which had Windows 10 and are now problematic.

I'm wondering why this would be a NECESSARILY be a Window 11 problem...

no, not quite correct... Both PC had windows 10 pro installed and activated. I pulled those OS hard drives, set them aside and replaced them with unactivated, cloned windows 11 from a fresh install. on a test bench hard drive. What I am so amazed about is that the main boards on both are janked as stated when there is a backup bios installed. Seems like it got janked some other way - maybe some tpm related proceedure when there is no tpm chip or fTPM support in CPU? It shouldn't be possible for the OS to fry the MB. I suppose there is some outside possibility (that is technically greater than zero) that the HDD I pulled off the bench for testing this mess was infected with something, but surely the previous erasure and the subsecquent cloning process would have foiled that,. Plus I am not in the habit of leaving infected crap laying around. Aside from that, I keep coming back to "Windows 11 murdered my PC" lol.

 

[econcepts]

I will say this. You came here asking for help or clarity on an issue you have. Being difficult with long time members and moderators will assure your stay is short. IF you want the help, consider it, take it, or don't, but no reason to be a jerk about it.

GL

Thank you for your answer. Sorry, I didnt mean to be a "jerk" I was merely stating the most likely reason for your apparent inability to see any other possibilities. No reason to get upset and make threats over it. Regardless, of whether it was wise or not, the OS should not be capable of damaging the main board, yet my results strongly suggest this conclusion. My post was more of a "this happened to me" rather than an actual question since the computers are permanently inoperative. Also, I assure you, a careful examination of my responses here will reveal every detail of import. I did not "leave anything out" or make a "fake post" I was merely adding information about something very unusual that happened to me, and therefore might help someone else.

 

[little_me]

I see three possible errors in what has been mentioned here:
Original poster mentioned he bought windows from MS.
As far as I know, MS does not sell OEM copies directly, only retail.
-This should not be an issue, oem or retail shouldn't affect things.

Windows cannot be installed on unsupported hardware
-This is wrong, it's been mentioned multiple times that installing from USB/ISO will work on almost all hardware, TPM or not, what might or might not work after that are windows updates.
IF they do work, they might still assume that computer WILL have TPM module, it's a requirement for windows 11. and subsequent boots will not work.
-computer should still run, do it's post check and you should be able to enter bios or reinstall OS on it.
-Microsoft has mentioned that this is only for testing purposes and it does not support this.

Installing image of computer 1's system to computer 2 with completely different hardware
-Original poster mentioned that he has multiple systems with same identical MB, which means that besides CPU and possibly GPU, 99% of systems are identical. (okay, GPU+CPU is more than 1% but still, if using integrated GPU, it leaves only CPU as different part)
it should and would quite likely work and could have some random ghosts in long run, stopping computer from booting? not quite.


Now.. I am no expert on computers that wont give a beep on startup even without memory (they should, it's standard POST startup thing) These things might sound dumb:
-You connected the front panel pc-speaker for beeps, right?
-have you tried to reset the cmos by shorting the pins or removing the battery?

I fear I have no better alternatives to try.

 

[econcepts]

Interesting, huh?

Ok, so what is the spec of your "main PC" in which you loaded the vanilla OS load?

Well, it was actually completely new -
Gigabyte B550M with F14 Bios, AMD Ryzen 5 5600G (zen 3), GSkill F4-3600C18D-16GTZRX (16Gb), Thermotake 500W, WD 500Gb SN500 NVMe, Samsung DVD, something like that. Basically the who is who from the windows 11 hardware compatibility matrix.

Where did you get the download to create that installer?

Installed from a builder sealed (you know, red label) OEM Windows 11 Pro DVD on "not previously used" hardware. As pristine as it gets.

As has been pointed out a few times above, these are not supported >hardware, so really not sure at all how they would have installed, aside from >perhaps the situation being that you cloned the first install and then used it >to boot these others, I am guessing?

Correct, Imaged with Macrium Reflect 8.0.6635, Then restored to a bench 1TB WD Black drive.

In that instance, the drivers and such would be for the original system and >should have given a little trouble on first boot as it looked for appropriate >drivers and such. W10 is pretty good about that and would make >assumptions that 11 does.....however it doesn't override the fact that none >of the FX based systems 'should have' booted from 11 at all.

Of course, I thought it was obvious I was just playing around. This is Tom's Hardware after all. I didn't expect it to boot, let alone work so well. No exclaims in device manager and ran like a dream. I literally played with it for an hour or more before restarting it for an update and a name change - during the "don't turn off your computer", is when (they both) went dark. On the other hand, I didn't expect it to be fried either.

On these machines that now won't boot, I think you said you did attempt to >put back in their original OS and they aren't responding to power cycle or >anything, is that correct?

Can't even get it to beep if I pull the memory. They wont post at all even without the hdd connected.. I pulled every cable out except the PCI and main power and no bios screen. The CPU fan comes on, power light. If it is progressing through the post at all, it never makes it to the point when it checks for the prescience of memory which is very early on. I don't know if its a perfect storm since the MB were nearly identical or maybe both 1TB mechanical drives I grabbed off the bench had something bad on them (wildly unlikely) When I put them away, I use diskpart and remove all the partitions and then full format them. Considering this level of crazy, I will of course, do a better check on them when I get back to the office and make an extremely humble report if I find anything.

 

[Rogue Leader]

I have never heard of bios updating through windows updates. Doesn't seem plausible.

I hate to "well actually" in here but my wifes HP Ryzen 5 2500U Laptop does install BIOS updates through Windows Update. My Microsoft Surface Go does as well (as does every Surface device).

That said a new-ish laptop is significantly different than a 10+ year old AM3 Motherboard. There is no chance this is the issue. That said I have no speculation as o what DID happen. If true very weird. I can't imagine Microsoft poison pilling Windows 11 to kill hardware if it detects the drive has been moved to a different machine. Technically possible, yes, but likely? No.

 

[TerryLaze]

That said a new-ish laptop is significantly different than a 10+ year old AM3 Motherboard.

He did do the initial install on a brand new system and used the clone from that on the old systems, so if the new system had this type of bios update...
The question is if it would just do it without checking if it's still on the same mobo.

 

[scottyswayne]

ihe used a image that was modified to bypass tpm i did that to my fx system and like said it wont cook your pc it will ether work or bsod on you my mb had an option for a tpm so i knew it could handle it even though at time it was sold did not come with it if you have a tpm port you can bypass tpm without problems but if your board has no tpm port wel it will bsod not frie i build my own pcs i never once had one fried by os worst it can do is bsod meaning ble screen of death crashes your stuff is faulty or you are overclocking it past its safty hold

when in doubt check your power option in windows make sure its not set on full performance as this would heat up you system lower it some but also motherboards will cut power to the compute if it detect a hot cpu onther reason i know windows did not fri it its a safty system it will lock the computer till the cpu is cooled down or 30 minutes mine did that before i put artic silver on it did a lot never fried that is my fx cpu model