I just moved my computer from its old mATX case and ASUS M4A785-M mobo to a newer ASUS M5A97 mobo. Everything seems to be in working order, except when I boot up I get a 0x0000007b error. I'm using the same sata cables for the HDD and DVD drive, and they're plugged into the same slots. I get the feeling like I'm getting an issue with my drivers, but I can't get into Windows to install the new ones. Am I going to have to reinstall Windows, or is there an alternative?
Blue Screen on boot
- Thread starter Tyg13
- Start date
Raiddinn
Splendid
- Oct 21, 2011
- 5,123
- 0
- 26,460
If it works it works.
Forcing it to function in IDE mode will make it slower and worse performing, but it shouldn't physically damage it.
I am more interested in the fact you didn't mention that you reinstall windows.
Did you move the hard drive between motherboards without reinstalling windows and get it to boot by setting it to IDE?
Or did you reinstall windows and not mention it?
Forcing it to function in IDE mode will make it slower and worse performing, but it shouldn't physically damage it.
I am more interested in the fact you didn't mention that you reinstall windows.
Did you move the hard drive between motherboards without reinstalling windows and get it to boot by setting it to IDE?
Or did you reinstall windows and not mention it?
I didn't reinstall windows, however windows upon finally booting up asked me to provide my product key to reactivate. Something about requiring reactivation due to a hardware change.
But yeah, I was able to switch motherboards without reinstalling windows. I was even able to install the drivers that came on the CD.
My video card has been acting up too, though I think that's a separate problem. I've always had problems with it overheating (which is why I switched to an ATX case), so maybe it's been damaged by overheating too frequently.
I'm more concerned right now if I can get my hard drive into SATA mode, without reinstalling windows of course. Eventually when I get a bigger hard drive I'm going to have to reinstall anyways, but if I can get it working before then, that'd be great.
But yeah, I was able to switch motherboards without reinstalling windows. I was even able to install the drivers that came on the CD.
My video card has been acting up too, though I think that's a separate problem. I've always had problems with it overheating (which is why I switched to an ATX case), so maybe it's been damaged by overheating too frequently.
I'm more concerned right now if I can get my hard drive into SATA mode, without reinstalling windows of course. Eventually when I get a bigger hard drive I'm going to have to reinstall anyways, but if I can get it working before then, that'd be great.
Raiddinn
Splendid
- Oct 21, 2011
- 5,123
- 0
- 26,460
I guess since the two boards are from Asus maybe they are close enough to the same thing for them to use all the same BIOS firmware. It is possible.
I would be interested to know if the exact same file is listed as a usable BIOS update file for both boards.
There is a kinda interesting formula that Windows uses to determine when hardware changes can cause you to need to update Windows. You can look it up if you want.
You basically need 4 "changes", and technically every part is counted for a possible change, but the RAM, for instance, looks like this:
64 MB = 1
128 MB = 2
256 MB = 3
512 MB = 4
1 GB+ = 5
So if you upgrade from 64 MB to 128 MB it will register as a hardware change. If you went from 64 MB to 1 GB it would also count as one hardware change.
If you went from 64 MB to 128 MB, booted into windows, then upgraded to 256 MB and booted into windows, then upgraded to 512 MB and booted into windows, then up to 1 GB and booted into windows, that would still only count as 1 upgrade.
Your computer checks everything against the original install, not any point later.
If you, however, started with 2 x 2 GB (common today) and upgraded that to 2 x 4GB (also common) that would not count as an upgrade. Both register as the same point value. Basically it is almost impossible today for a Windows install to recognize a RAM change and count it toward product re-activation.
Anyway, it can record a lot of things and 4 things in total must change for a reactivation, but some things count and some things don't due to the way it is programmed. MSFT never brought some aspects of this into the new millennium.
It is possible that it registered you using the drive in SATA and changing it to IDE with the exact same physical hard drive as a hardware change, strangely enough.
None of that really helps you, but you may be amused to learn more about the process.
As far as helping you is concerned...
Is there any specific reason you cannot reinstall Windows, or is doing so just undesirable?
That being said, the following is a thread where someone named Roli wanted to change from AHCI to IDE and the reason given was that it would be faster with IDE.
http://www.vistax64.com/general-discussion/271218-switch-ahci-ide-tutorial-howto.html
I don't know, maybe my understanding of the subject may be off based on that grounds so you may want to verify yourself how you would like this to be.
If you want to bring it from IDE to AHCI, then maybe you can do the opposite of what they said to do in here and change everything from 1 to 0 that they are changing from 0 to 1 and so on.
That being said, I think you will find it to be a major pain in the a@@ to try to pursue this effort.
It would probably be easier to just reinstall windows.
I would be interested to know if the exact same file is listed as a usable BIOS update file for both boards.
There is a kinda interesting formula that Windows uses to determine when hardware changes can cause you to need to update Windows. You can look it up if you want.
You basically need 4 "changes", and technically every part is counted for a possible change, but the RAM, for instance, looks like this:
64 MB = 1
128 MB = 2
256 MB = 3
512 MB = 4
1 GB+ = 5
So if you upgrade from 64 MB to 128 MB it will register as a hardware change. If you went from 64 MB to 1 GB it would also count as one hardware change.
If you went from 64 MB to 128 MB, booted into windows, then upgraded to 256 MB and booted into windows, then upgraded to 512 MB and booted into windows, then up to 1 GB and booted into windows, that would still only count as 1 upgrade.
Your computer checks everything against the original install, not any point later.
If you, however, started with 2 x 2 GB (common today) and upgraded that to 2 x 4GB (also common) that would not count as an upgrade. Both register as the same point value. Basically it is almost impossible today for a Windows install to recognize a RAM change and count it toward product re-activation.
Anyway, it can record a lot of things and 4 things in total must change for a reactivation, but some things count and some things don't due to the way it is programmed. MSFT never brought some aspects of this into the new millennium.
It is possible that it registered you using the drive in SATA and changing it to IDE with the exact same physical hard drive as a hardware change, strangely enough.
None of that really helps you, but you may be amused to learn more about the process.
As far as helping you is concerned...
Is there any specific reason you cannot reinstall Windows, or is doing so just undesirable?
That being said, the following is a thread where someone named Roli wanted to change from AHCI to IDE and the reason given was that it would be faster with IDE.
http://www.vistax64.com/general-discussion/271218-switch-ahci-ide-tutorial-howto.html
I don't know, maybe my understanding of the subject may be off based on that grounds so you may want to verify yourself how you would like this to be.
If you want to bring it from IDE to AHCI, then maybe you can do the opposite of what they said to do in here and change everything from 1 to 0 that they are changing from 0 to 1 and so on.
That being said, I think you will find it to be a major pain in the a@@ to try to pursue this effort.
It would probably be easier to just reinstall windows.
Facebook
Twitter
Instagram