• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I did the unthinkable. Went from AMD to Intel and didn't do a fresh install

bbhaag

bbhaag

Diamond Member
A couple weeks back I finally got all the pieces to put my new i7-6700k build together and came to a precipice. Do I go through with a fresh install or do I just hook up the M500 SSD and plunge full steam ahead? I did the unthinkable. I put the i7-6700k together then took the SSD with all the info from my previous build which was a Phenom2 965 and pressed the power button.

To my surprise it booted and immediately started installing generic Microsoft drivers for the Intel devices like the chipset and the nic. Ten too fifteen minutes later and a couple reboots and the system was stable. I went too the Asrock website and proceeded to dl the latest manufacturer drivers and install them. Ten or fifteen minutes later and a couple reboots and the system was not only stable but humming along quit nicely.

What are the downsides of doing this? Should I expect system instability as time goes on? Has anyone else done this? If you have did you experience a different outcome then me?

EDIT: Forgot too mention the OS. It's Windows10 64-bit.
 
Last edited:
I did have to re-activate Windows. It was another nice surprise when I entered my $40 Windows8 upgrade key that I had already used to go from 7>8 and Windows10 activated. I felt like I was double dipping but hey it worked. haha
 
bbhaag said:
I did have to re-activate Windows. It was another nice surprise when I entered my $40 Windows8 upgrade key that I had already used to go from 7>8 and Windows10 activated. I felt like I was double dipping but hey it worked. haha
Click to expand...

I had the opposite happen. Went Win7 -> 10, everything active and happy, enabled UEFI, didn't have key, and MS tech support told me I had to buy another copy.
 
I didn't think this was that...uh, unthinkable.

I remember Windows 9x didn't give a crap if you moved the drive. But the install was probably suffering from some form of cancer at that point so you might as well do one anyway. 2000 on up it bluescreens unless its using the same disk controller type. Sure, you could do that hardware genericalization (not a word) thing if you were clairvoyant and remembered to run it before your motherboard failed but generally you were in for a rough time. Maybe Windows 10 is a bit more robust and falls back to generic SATA drivers or something. It was always kind of perplexing Windows didn't do that automatically to me.
 
I've switched a Win7 install between X58, Z87, Z77, 970, 760G, and 5520 with no issues other than some installing the appropriate chipset/USB drivers.
 
I have not but do you think I should? From the replies so far it seems as if my experience isn't all that uncommon and shouldn't be a cause for concern.
 
Windows used to go batsh*t if I did that during the <= XP days (never tried Vista), but Win7 and Win8 don't seem to care.
The most that happens is in inaccessible boot device due to AHCI funkiness, but switching over to IDE temporarily, installing the appropriate drivers and applying the registry fix always does the trick.
 
bbhaag said:
I did the unthinkable. I put the i7-6700k together then took the SSD with all the info from my previous build which was a Phenom2 965 and pressed the power button.

To my surprise it booted and immediately started installing generic Microsoft drivers for the Intel devices like the chipset and the nic. Ten too fifteen minutes later and a couple reboots and the system was stable. I went too the Asrock website and proceeded to dl the latest manufacturer drivers and install them. Ten or fifteen minutes later and a couple reboots and the system was not only stable but humming along quit nicely.

EDIT: Forgot too mention the OS. It's Windows10 64-bit.
Click to expand...

bbhaag,

Thanks for posting your experience. It's really good to know that it can work.

Skyzoomer
 
amd to intel was never an issue when i've done this, but intel to amd was a very different story. eventually found one particular intel driver file that would gum up the whole works, got rid of it, and everything went on fine. that was back in the core2 days so things may be different nowadays.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top