Just changed motherboards now pc won’t boot

[SalvatoreLacorte]

Hello, I recently changed my mother board with a core i7 6700k to a core i5 8600k. I also replaced my 980ti with a 1080. When I try to boot it won’t let me enter bios and it says repairing drive then shows windows blue screen error. I am so confused on what to do... any help will be great. Thx

[SalvatoreLacorte]

Also to add more. Sometimes afterwords I boot into a black screen with a moveable pixelated mouse. 

[Skiiwee29]

Full system specs... 

[SalvatoreLacorte]

22 minutes ago, Skiiwee29 said:

Full system specs... 

GTX 1080 intel i5 8600k 16 FB ram samsung ssd(sata) 

[glenalz81]

What motherboard?

[SalvatoreLacorte]

Just now, glenalz81 said:

What motherboard?

Gigabyte z370 ultra gaming wireless 

[Stormseeker9]

23 minutes ago, SalvatoreLacorte said:

GTX 1080 intel i5 8600k 16 FB ram samsung ssd(sata) 

Please make a list. Cpu all the way to your PSU.

 

you can use pcpartpicker.com if you wish

[homeap5]

What operating system? If it's Win7 - use bootable Paragon Adaptive Restore 2010 and "Adjust OS".

 

Set your current bios the same way as previous one (legacy or UEFI).

 

[ImDaMan]

When you change any major hardware, you will not be able to run your old OS just by plugging in your old SSD.

[homeap5]

5 hours ago, ImDaMan said:

When you change any major hardware, you will not be able to run your old OS just by plugging in your old SSD.

Really? Wow. That is amazing what I can learn after years of changing all computer parts and booting the same system on many configurations.

 

It's not true - you would know that if you tried at least once. Otherwise it's only repeating crap you read on internet.

[Falkentyne]

7 hours ago, SalvatoreLacorte said:

Gigabyte z370 ultra gaming wireless 

Assuming you didn't get unlucky with the RAM, you changed chipsets so windows might be throwing a tantrum.

Did you try installing windows from scratch?

Your data would still be there, (in windows.old), including the old users and documents folders but you would have to reinstall all your programs.  But that fixes problems like this if the hardware itself is not defective.

[Tristerin]

1 hour ago, homeap5 said:

Really? Wow. That is amazing what I can learn after years of changing all computer parts and booting the same system on many configurations.

 

It's not true - you would know that if you tried at least once. Otherwise it's only repeating crap you read on internet.

Both statements are true.  Yours and his.  Or you haven't built enough PCs to actually know that.  Windows 10 is good about getting into the OS via use of generic drivers, but that by NO MEANS makes it an optimal experience for components you are paying for.  Windows 7 - sucks in comparison.  Good luck swapping out major components thinking it will always work lol.

 

Based on what the OP says, his drive needs a reinstall as its not compatible to boot into the system as the generic drivers he HAS isn't enough.  Id do a fresh install and call it a day.  Takes what, 15 minutes on a bootable USB @ 2.0 speeds lol.

[homeap5]

59 minutes ago, Tristerin said:

Both statements are true.  Yours and his.  Or you haven't built enough PCs to actually know that.  Windows 10 is good about getting into the OS via use of generic drivers, but that by NO MEANS makes it an optimal experience for components you are paying for.  Windows 7 - sucks in comparison.  Good luck swapping out major components thinking it will always work lol.

 

Based on what the OP says, his drive needs a reinstall as its not compatible to boot into the system as the generic drivers he HAS isn't enough.  Id do a fresh install and call it a day.  Takes what, 15 minutes on a bootable USB @ 2.0 speeds lol.

I don't need luck with win7, I have tools in rare cases I cannot boot system on different hardware. I call it experience, you may call it luck or whatever. I build and configured lot of computers so I think I can say that I know what I'm talking about.

 

Anyway - "15 minutes" means preparing USB and install (and no, it's not usually 15 minutes, it takes longer, but that not the point). But what then? That "15 minutes" does not contain reinstalling all your programs, configuring system, installing tools you're using every day, moving all savegames (if you're gamer), optimize programs' settings etc. You're right if we're talking about "empty" system with one browser and few games - but if we're talking about serious computer work, installing new system is more like few days of hard working with restoring everything.

 

Operating system is not something magical that needs to be install for every hardware. You have already installed on your system thousands of drivers for hardware you don't have and system can change registry entries according to what you're using now. If you want to be more "clean" you can always use tools like Ghostbuster, RAPR etc. to clean unused / ghosted or old drivers. And I never said that you must use generic drivers - it's obvious that if you change motherboard, cpu, ram, gpu etc. you must install proper drivers for all your hardware. But it's still much faster than perparing all your software again and again every time you change something in your computer. Windows is smart enough to handle hardware changes - it's not MacOS.

 

[Tristerin]

12 minutes ago, homeap5 said:

I don't need luck with win7, I have tools in rare cases I cannot boot system on different hardware. I call it experience, you may call it luck or whatever.

 

Anyway - "15 minutes" means preparing USB and install (and no, it's not usually 15 minutes, it takes longer, but that not the point). But what then? That "15 minutes" does not contain reinstalling all your programs, configuring system, installing tools you're using every day, moving all savegames (if you're gamer), optimize programs' settings etc. You're right if we're talking about "empty" system with one browser and few games - but if we're talking about serious computer work, installing new system is more like few days of hard working with restoring everything.

 

Operating system is not something magical that needs to be install for every hardware. You have already installed on your system thousands of drivers for hardware you don't have and system can change registry entries according to what you're using now. If you want to be more "clean" you can always use tools like Ghostbusters, RAPR etc. to clean unused / ghosted or old drivers. And I never said that you must use generic drivers - it's obvious that if you change motherboard, cpu, ram, gpu etc. you must install proper drivers for all your hardware. But it's still much faster than perparing all your software again and again every time you change something in your computer. Windows is smart enough to handle hardware changes - it's not MacOS.

 

Sure thing.  You just responded like someone talking to someone who knows what they are doing.  Now, take what you just said and help the OP.  Oh wait, he clearly isn't a power user of any sort, so...how would you recommend him get this going?  Keep banging his head onto a wall trying to get a HDD that wont boot up, to repair, without the proper tools to do it?  Isnt that the point of this thread - to help the OP?  

 

We can dick wave all day long, in the end this poster needs a fresh install of the operating system to clear out any chance its a software related boot issue. imho, so I personally will continue helping him in this direction - until a better one arrives.

 

@SalvatoreLacorte - pull your CMOS so you can reset BIOS, to ensure some sort of Fast Boot option isn't on keeping you from entering the BIOS (you don't need an HDD to enter the BIOS, or an OS).  We need to get in here to do much of anything.

 

How did you originally install your OS that you are attempting to migrate over to this build?  For example, I have a USB 2.0 stick with Win 10 ISO on it I use. 

 

 

 

 

[homeap5]

19 minutes ago, Tristerin said:

Sure thing.  You just responded like someone talking to someone who knows what they are doing.  Now, take what you just said and help the OP.  Oh wait, he clearly isn't a power user of any sort, so...how would you recommend him get this going?  Keep banging his head onto a wall trying to get a HDD that wont boot up, to repair, without the proper tools to do it?  Isnt that the point of this thread - to help the OP?  

Yes, of course, helping OP is what we should do in the first place. But problem may be different - if drive don't boot and OP uses UEFI bios in previous installation, then something is wrong with new config (I assume that he move system from modern to modern computer) and fresh install may still be impossible before problem will be resolved. I mean - resolving one problem solves another.

 

But there may be also problem with bad settings at the beginning that screw something up during first boot and yes - easiest solution may be reinstall. Maybe better trying to install windows on second drive just to be sure that hardware is ok? If Windows trying to repair itself, it may be some hardware problem and trying to reinstall system on bad hardware is not a good idea.

 

[Tristerin]

1 minute ago, homeap5 said:

Yes, of course, helping OP is what we should do in the first place. But problem may be different - if drive don't boot and OP uses UEFI bios in previous installation, then something is wrong with new config (I assume that he move system from modern to modern computer) and fresh install may still be impossible before problem will be resolved. I mean - resolving one problem solves another.

 

But there may be also problem with bad settings at the beginning that screw something up during first boot and yes - easiest solution may be reinstall. Maybe better trying to install windows on second drive just to be sure that hardware is ok? If Windows trying to repair itself, it may be some hardware problem and trying to reinstall system on bad hardware is not a good idea.

 

Cant disagree with any of this - most users don't have the extra hardware we do laying around though (and likely OP does not have any sort of media to install Win 10 as it is based on most regular users who swing by here) but if he does, he should let us know so we can help him help himself  

 

TBH we should have him breadboard his PC first to see if there ARE hardware issues (since he is saying he cant even get into BIOS)

[SalvatoreLacorte]

32 minutes ago, Tristerin said:

Cant disagree with any of this - most users don't have the extra hardware we do laying around though (and likely OP does not have any sort of media to install Win 10 as it is based on most regular users who swing by here) but if he does, he should let us know so we can help him help himself  

 

TBH we should have him breadboard his PC first to see if there ARE hardware issues (since he is saying he cant even get into BIOS)

UPDATE: I have now tried to re install windows but every time i do the screen stays purple until i get a blue screen of death that says system thread exception not handled! I am still trying to get into the re installer, ntfs.sys is what failed on the blue screen. any help? I can now get into bios.

[Tristerin]

1 minute ago, SalvatoreLacorte said:

UPDATE: I have now tried to re install windows but every time i do the screen stays purple until i get a blue screen of death that says system thread exception not handled! I am still trying to get into the re installer, ntfs.sys is what failed on the blue screen. any help? I can now get into bios.

I get this exception and BSOD when my RAM is OCd beyond memory controller compatability.  What RAM?

[SalvatoreLacorte]

1 minute ago, Tristerin said:

I get this exception and BSOD when my RAM is OCd beyond memory controller compatability.  What RAM?

gskill ripjaw 8x2 ddr4 3200

[Tristerin]

5 minutes ago, SalvatoreLacorte said:

gskill ripjaw 8x2 ddr4 3200

Intel has only validated this CPU up to 2666mhz, downclock it (RAM) in BIOS and see how it goes.  After all updates are done to computer and Mobo you may be able to drive it at 3200mhz.  Get it stable first, then work on boosting beyond.  Your motherboard supports up to 4000mhz with the proper bios updates, just not your CPU memory controller.

 

It SHOULDNT have an issue running at 3200mhz - however we should get everything in spec, and updated - before going out of spec.