Did New BIOS Flash Change My System Partition from GPT to MBR?

May 18, 2013
30
0
10,540
"Here's one for you tech gurus out there. I built my computer in 2013 with the foundation being an ASUS M5 A97 LE R2.0 motherboard. Everything went fine for the most part except a bent pin on the CPU since the packaging was total garbage and a corner of the chip slipped between the plastic clam shell bending one of the pins and a DOA hard drive that wouldn't show up in the BIOS. I fixed the bent pin (and hope I never have to again because it took forever) and the new HDD worked flawlessly. The computer got a nice clean OS install, a mild overclock since I'm not comfortable enough for the "extreme" route and without liquid cooling I probably wouldn't be able to go there anyway, and my GPU got a mild overclock as well. The computer worked well but wasn't the most stable thing. It would randomly crash, get hung up in feedback loops, and generally just acted a bit strange. Not enough to make me think there was something terribly wrong, but enough to be a nuisance. Finally I had enough of my games and internet browsing causing the computer to just stop responding, forcing a hard reset to get it to come back up.
So I started with the easiest things first. I reset the CPU, GPU clocks, and the RAM overclocks back to factory default. Still hang ups with the same frequency. I uninstalled AI Suite II thinking that maybe it was being belligerent and trying to set the BIOS back to the overclock (if it can even do that I don't know), though I did use it to keep an eye on my temps and fan speeds. Still no help. So I took more drastic measures and updated my chipset drivers thinking maybe something was outdated and causing weird problems. Nope...still crashes and generally bad behavior. So, for the first time in my life I decided that maybe the newest BIOS from ASUS would help.
I crossed my fingers as I went into the BIOS and flashed in the new version, 2501 that had about 2 years worth of updates mostly for "improved system stability". I said to myself, "I need some system stability and I tried everything else so"...biting my nails the whole time and being CONVINCED that I had lost my mind I watched the progress bar start, stop, start up again, stop, start. It probably only took a minute to complete but it felt like 5 hours. So the computer said it was installed successfully and rebooted, bringing me to the screen to reset my settings. I pressed F5 to reload the default settings, clicked save and exit, and the computer restarted...right into the Windows splash and eventually it took me to my desktop. I thought that I somehow missed the POST screen so I restarted and same thing. The motherboard speaker beeps once to let me know the BIOS is alright and skips the POST screen where it says you can press F2 or DEL to enter the BIOS. Bam, right to the windows splash screen.
I finally stopped trying to use DEL to get into the BIOS and used F2 and lo and behold that worked, and it works every time mind you. I also know that the BIOS is technically fine since the computers POSTs. If there was something wrong I wouldn't have a PC to type this up. I did notice that in the ASUS EZ Mode UEFI screen that the bar at the bottom that shows the boot order doesn't have the icon for the BIOS anymore. It's just an icon for my HDD and DVD drive. The computer works AMAZING after the new BIOS was flashed in. No crashes, hang ups, stutter, or anything. I restored my OC settings on my CPU, GPU, and RAM expecting them to make the system get yucky again but they work so well that I may try to bump things up a little bit more. Is the missing BIOS/UEFI icon something I should be concerned about, is the missing ASUS logo on start up a sign of a problem? Enabling or Disabling Fast Boot doesn't do anything either...the ASUS POST screen is still skipped even though I can easily get into the BIOS using the F2 key without the screen showing. Has UEFI been revised and somehow it's written in such a way now that it assumes the BIOS is always the first in the boot sequence and therefore having it listed as first in the bar is redundant? Any ideas?

I went into the BIOS and saw settings for the logo had been changed. I changed "Auto" to "Full Screen" and changed the POST delay from 3 seconds to 5. And guess what...the logo came back AND the computer adhered to the 5 second POST delay. I liked the smaller logo from before the new BIOS flash but I can deal with the stretched out full screen. I also noticed that if I leave the flash drive plugged in on start up where I stored the new BIOS, the icon will show up in the EZ Mode as the first in the boot order. I think I can use F12 to take a screen shot and show you what it looks like, it's exactly how it looked before the new flash. With the flash drive removed it just shows the HDD and DVD, in that order. I mean it's really more a cosmetic thing I think, but again you get used to the way something looks.

EDIT: Since you've been so helpful and seem to know computer software well I may have figured out why the UEFI tile in the BIOS has gone missing. I think that when I flashed in the BIOS Windows Boot Manager may be confused and looking for something from the old firmware. I took a picture of the EZ Mode with the flash drive marked as UEFI but I can't figure out how to get in in my posts. A dialuge box pops up asking for a URL but whatever. If it's that important I'll figure it out. But the boot order currently is P0: WD blablabla denoting my hard drive. I think the UEFI partition of Windows is looking for the old firmware, not finding it, and then loading in Legacy mode. I mean the computer still works and is stable as hell now but for whatever reason, God knows why, I want that damn UEFI back even though in the long run it probably doesn't mean anything that the computer is booting in legacy mode. Do you think if I pop in the Windows DVD and run the repair option that'll fix the boot sequence?

EDIT (uh...again?): After MORE digging, I found that the hard drive is now MBR (Master Boot Record) instead of being considered GPT (GUID Partition Table). So that's why the UEFI denoted tile in the BIOS is missing. The UEFI boot process got lost somwhere. Again...will the repair function on the Windows disc fix this and get the UEFI partition to be recognized again in the boot sequence? EDIT AGAIN!!!: So if I boot using the Windows installation disc it says that System Recovery Options are not compatible. Use a compatible version. It's impossible it's incompatible since it's the disc I used to install Windows in the first place! I made a System Repair disc and it opens if I boot into it but it seems it's tracking my OS to the D:\ drive which is my DVD drive, not the C:\ drive where Windows is. Running the Startup Repair options obviously finds nothing since it's apparently not even looking at the OS at all. ???"

So that's the story from another thread I have open. Is it even possible for the partition to be changed from GPT to MBR due to improper settings after the new flash? It's not technically a big deal since I can boot into Windows fine and the computer works as expected. Sorry another EDIT: In Windows\Booot I have .efi files so...I'm going to assume Windows is set to boot in UEFI but it's somehow not and I cannot force it to boot in UEFI mode by changing the BIOS settings and possibly self repair boootmgr or whatever. I'm getting tired of trying to figure this out so I feel like I'm tossing around incorrect terminology all over the forum and upsetting a lot of people in the process. Any ideas on what could have happened?
 
May 18, 2013
30
0
10,540


So I'm at error? Figures. I see there are .efi files in Windows\Boot. I am going to assume that what I can browse on C:\Windows is NOT what's on the 100Mb System partition. If it is then scratch that and chalk it up to me not having to build a computer for so long that I become so out of touch with the changing industry.

I do remember after the new flash, in the Boot menu under CSM or Compatibility whatever the entries were set to Legacy first then UEFI. I'm pretty much super confident that the System partition cannot spontaneously change from GPT to MBR or vice versa. Unless, however, Windows somehow rebuilt portions of the partition in order to operate in legacy mode, thereby chaning the format? I seriously doubt it and maybe it really was MBR all along and I never realized? I do know for a FACT that before the flash an HDD icon with UEFI over it was first, then the hard drive with no UEFI on it, then the DVD drive with no UEFI on it in the boot sequence.

When you say the memory too, do you mean memory overclocks? Does Windows even care about overclock speeds?
 
May 18, 2013
30
0
10,540


That still doesn't explain why Windows isn't booting into UEFI mode anymore. Again, maybe I borked it when I installed Windows to begin with (I'm pretty sure I had UEFI First/Only set BEFORE I put the disc in) and a clean install of Windows with the proper UEFI/BIOS settings will cure it? I'm not concerned about the data on the drive. I have no pictures, all my music has been uploaded to Google Play Music so it's safe and since I don't listen to the .MP3's on my hard drive anymore wiping them wouldn't be a big deal, and I can always reinstall/redownload my games with the only important files being my partner's The Sims 4 save file which is already stored on a thumb drive as a precaution. That's a REALLY long way of saying wiping the hard drive and reinstalling Windows is a viable option.
I notice my drive is formatted in NTSF which apparently the UEFI mode of Windows 7 doesn't support adding FURTHER intrigue. I'm also perplexed by the .efi files being in C:\Windows\Boot making me wonder what the heck went wrong. Either I'm REALLY missing something or...I don't know.
 
May 18, 2013
30
0
10,540


So it seems to be me not installing Windows correctly in UEFI mode. After doing even MORE research I finally found some other forums that directed me to C:\Windows\Panther\setupact.log. Using CTRL+F and searching the document for "callback" I eventually found that the boot environment is set to BIOS, not UEFI like it should read if it's installed under UEFI conditions. I suspect it's because of the downright horrid documentation that came with my motherboard I didn't set the correct parameters BEFORE I put the Windows disc into the drive. It could also have been from me messing with the BIOS settings trying to figure out why the hard drive wasn't being detected. It wound up being DoA and in the process I could have set the motherboard to Legacy mode in my vain attempts of trying to get the HDD recognized when it was actually outright failing out of the box. I built the computer RIGHT as UEFI was being released to the mass market and was all the rage so there was no real documentation to explain exactly how to install under UEFI. And forget Windows saying "Hey, before you install me make sure you have your motherboard set to UEFI before you shove me onto the hard drive. Shall I exit so you can check to make sure everything will be correct?" In a perfect world...

Should I set the motherboard to default settings, than make sure I set CSM to UEFI only, and then put the Windows disc in to format the drive? I see tutorials online that have the user opening a command prompt to wipe the drive but doesn't Windows do that already prior to a reinstallation? Is there any benefit of using the command prompt prior to the reinstallation? I know that the computer works and I really have no business worrying about BIOS or UEFI but the motherboards at the time made such a big deal about it and darn it I want to use it. I didn't buy all this stuff not to take advantage of it. Anyone have suggestions? I mean I find it VERY strange that the boot environment is BIOS yet I still have a EFI folder in the Windows directory. One of two things happened. I set up Windows in the BIOS environment (which I'm not sure I did since before the flash there was something labeled UEFI on a HDD as the first in the boot priority) OR I messed up the Windows boot files a bit and forced them into legacy mode with the incorrect motherboard settings before booting into Windows after the flash occurred and now it's somehow "stuck".

I agree that it's weird that a BIOS flash would have changed the format. The entire problem is extremely bizarre. I don't remember the exact settings that I had when I put the computer together and installed Windows, it was back in 2013 I believe. It's been so long I don't really remember the exact date I received the components. After the overclock was stable I never went back into the BIOS so I would never know the settings before the flash. I CAN confirm the BIOS is working correctly and it IS the most up to date so a new install of Windows, if I can pull THAT off without making more mistakes or whatever, should fix this snafu. After that it's just a matter of installing my games again. They're really the only thing on my HDD. Again, I don't know if I'm making a mountain out of a mole hill but I just can't be comfortable knowing I'm not using the "advanced technology" I paid for.
 
May 18, 2013
30
0
10,540
So just a question for anyone who reads this. Because I'm...me...and I feel like I'm not using a big portion of the functionality of my motherboard I'm becoming more comfortable with reinstalling Windows under UEFI conditions, now that I know I have to pay close attention to the settings. Should I clear my CMOS fully by moving the jumper and holding the power button to drain all electricity first? Upon a nice clean CMOS I will have to make sure that all my CSM settings are set to "UEFI Only" or "UEFI First, Legacy OpROM Second" and then Save & Exit the BIOS screen. Turn the computer back on and spam F8 to open the list of bootable devices. As long as the Windows DVD says UEFI BEFORE the drive name, Windows will install under the UEFI parameters. Here's where I'm finding a lot of confusing information. Some folks say that you just have to make sure the UEFI drive is launched and from the Windows install screen you can select the option to delete all partitions, effectively wiping the drive, others say to open a command prompt after the language selection screen through Shift+F10 and use Diskpart to delete the partitions. Which way is better or is there no difference. I can forgo a computer for a day or two but beyond that I'm a little scared that I'm entering territory I have no business in, especially reading the problems people have getting Windows 7 to boot in UEFI mode. Either that or they're creating their own problems by messing around with BIOS functions they don't understand and are more curious to see what will happen if they start changing stuff. I'm all for curiosity but computers are sensitive things and one small error and the whole thing comes apart. I'm no expert, obviously, since I can't even get settings correct BEFORE tossing an OS onto a drive : ) Any help in figuring out if converting to UEFI is even worth it and it offers and benefits over BIOS such as decreased boot time or program start-up or anything like that or if my simple steps to getting a clean version of Windows 7 is correct and accurate so I DON'T do this again?
 
May 18, 2013
30
0
10,540


Thanks for the info! It's what I get for not going over my board's setting one last time before installing the OS. I guess in the confusion between troubleshooting the defective HDD and then not working on the computer for a few days until the new one arrived things didn't get set back to what they should have been. Anyway, now it's time to figure out if running Windows 7 in UEFI is even worth the conversion, and if it is backing up the few things that need to be saved before deleting the partitions and starting over. It's a good thing I've learned to store extremely critical stuff to external sources over my many years of using computers so in the case of catastrophe it's not crippling to have to format. Even in the face of total system failure all my important stuff is already in a safe place that's not even connected to the computer. Save games are either not terribly important, or if they are they too are stored "off site". Thanks again for all your help!