F5F Stay Refreshed Hardware Desktop Updated the motherboard recently but the computer still can't start.

Updated the motherboard recently but the computer still can't start.

Updated the motherboard recently but the computer still can't start.

Pages (2): Previous 1 2
M
Massaker
Member
70
03-21-2017, 12:12 AM
#11
You avoided bad luck with RAM and swapped chipsets to see if Windows could handle it better. You also considered installing Windows from the ground up. Your files would remain intact in Windows.old, keeping old users and documents, though you’d need to reinstall everything. This approach works when the hardware isn’t faulty.
M
Massaker
03-21-2017, 12:12 AM #11

You avoided bad luck with RAM and swapped chipsets to see if Windows could handle it better. You also considered installing Windows from the ground up. Your files would remain intact in Windows.old, keeping old users and documents, though you’d need to reinstall everything. This approach works when the hardware isn’t faulty.

E
eritu007
Junior Member
20
03-21-2017, 04:04 PM
#12
Both points are accurate. Your experience and his suggest Windows 10 offers better compatibility with hardware, while Windows 7 falls short. It’s not worth risking major upgrades without certainty. A fresh install should be enough—quick setup on a bootable drive works well.
E
eritu007
03-21-2017, 04:04 PM #12

Both points are accurate. Your experience and his suggest Windows 10 offers better compatibility with hardware, while Windows 7 falls short. It’s not worth risking major upgrades without certainty. A fresh install should be enough—quick setup on a bootable drive works well.

R
repsajwa
Junior Member
12
03-21-2017, 05:40 PM
#13
I don't rely on luck with Win7; I have tools available in rare situations where I can't boot the system on different hardware. This is just experience, whatever you call it. I set up and adjusted many computers, so I believe I understand what I'm discussing. Still, "15 minutes" usually means more than just a quick setup—it often involves longer processes, but that's not the main point. What matters is that it doesn't include reinstalling everything, configuring the system, adding daily-use tools, moving save games (if you're a gamer), tweaking program settings, or optimizing configurations. You're correct if we're talking about a bare system with minimal software; but for serious work, rebuilding from scratch can take several days of effort to restore everything properly. The operating system isn't some magical fix that needs reinstalling for every hardware change. You've already loaded thousands of drivers for devices you don't own, and the system adapts its registry based on what you're using now. If you want a cleaner setup, tools like Ghostbuster or RAPR can help remove unused or outdated drivers. I never suggested using generic drivers—clearly, when you replace components like the motherboard, CPU, RAM, or GPU, you need proper drivers for each part. Still, it's much quicker than reconfiguring all your software every time something changes on your machine. Windows handles hardware updates intelligently; it's not like MacOS.
R
repsajwa
03-21-2017, 05:40 PM #13

I don't rely on luck with Win7; I have tools available in rare situations where I can't boot the system on different hardware. This is just experience, whatever you call it. I set up and adjusted many computers, so I believe I understand what I'm discussing. Still, "15 minutes" usually means more than just a quick setup—it often involves longer processes, but that's not the main point. What matters is that it doesn't include reinstalling everything, configuring the system, adding daily-use tools, moving save games (if you're a gamer), tweaking program settings, or optimizing configurations. You're correct if we're talking about a bare system with minimal software; but for serious work, rebuilding from scratch can take several days of effort to restore everything properly. The operating system isn't some magical fix that needs reinstalling for every hardware change. You've already loaded thousands of drivers for devices you don't own, and the system adapts its registry based on what you're using now. If you want a cleaner setup, tools like Ghostbuster or RAPR can help remove unused or outdated drivers. I never suggested using generic drivers—clearly, when you replace components like the motherboard, CPU, RAM, or GPU, you need proper drivers for each part. Still, it's much quicker than reconfiguring all your software every time something changes on your machine. Windows handles hardware updates intelligently; it's not like MacOS.

I
InfernoSteel
Junior Member
27
03-23-2017, 10:46 AM
#14
I
InfernoSteel
03-23-2017, 10:46 AM #14

C
CastleHD
Junior Member
1
03-24-2017, 05:50 AM
#15
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.
C
CastleHD
03-24-2017, 05:50 AM #15

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.

B
BrighFigter
Junior Member
12
03-24-2017, 10:06 AM
#16
Everyone agrees with the general point—most people don’t own the extra gear we have, and it’s probably not the OP who has any special media for installing Windows 10 since it targets typical users. If someone does have it, they should let us know so we can assist them. We should try to test the PC first by breadboarding it to check for hardware problems, especially since he mentions he can’t even reach the BIOS.
B
BrighFigter
03-24-2017, 10:06 AM #16

Everyone agrees with the general point—most people don’t own the extra gear we have, and it’s probably not the OP who has any special media for installing Windows 10 since it targets typical users. If someone does have it, they should let us know so we can assist them. We should try to test the PC first by breadboarding it to check for hardware problems, especially since he mentions he can’t even reach the BIOS.

D
DragonTTK
Member
52
03-26-2017, 02:25 AM
#17
I recently attempted to reinstall Windows but the screen remained purple until a blue screen appeared with a message about an unhandled system thread exception. I’m still trying to access the reinstaller, and it seems NTFS.SYS failed during the blue screen. Any assistance would be appreciated. I’ve managed to reach the BIOS now.
D
DragonTTK
03-26-2017, 02:25 AM #17

I recently attempted to reinstall Windows but the screen remained purple until a blue screen appeared with a message about an unhandled system thread exception. I’m still trying to access the reinstaller, and it seems NTFS.SYS failed during the blue screen. Any assistance would be appreciated. I’ve managed to reach the BIOS now.

M
meneo5
Junior Member
9
03-26-2017, 08:01 AM
#18
The issue occurs with RAM that exceeds the memory controller's compatibility limits. Which specific type of RAM are you using?
M
meneo5
03-26-2017, 08:01 AM #18

The issue occurs with RAM that exceeds the memory controller's compatibility limits. Which specific type of RAM are you using?

I
icedragon0525
Member
142
03-29-2017, 12:24 AM
#19
GSKILL Ripjaw 8x2 DDR4 3200 MHz
I
icedragon0525
03-29-2017, 12:24 AM #19

GSKILL Ripjaw 8x2 DDR4 3200 MHz

I
iLwRo
Member
130
04-05-2017, 07:48 AM
#20
Intel only confirmed this CPU up to 2666mhz. You can downclock it via BIOS and test performance. Once all system updates are applied, you might reach 3200mhz. Ensure stability first, then aim for further improvements. Your motherboard can handle up to 4000mhz with the right BIOS updates, though the CPU memory controller may need attention. It shouldn't cause problems at 3200mhz, but everything should meet specifications before exceeding them.
I
iLwRo
04-05-2017, 07:48 AM #20

Intel only confirmed this CPU up to 2666mhz. You can downclock it via BIOS and test performance. Once all system updates are applied, you might reach 3200mhz. Ensure stability first, then aim for further improvements. Your motherboard can handle up to 4000mhz with the right BIOS updates, though the CPU memory controller may need attention. It shouldn't cause problems at 3200mhz, but everything should meet specifications before exceeding them.

Pages (2): Previous 1 2