F5F Stay Refreshed Hardware Desktop Windows 7 x86 installs successfully, but the x64 version triggers a BSOD on the latest build?

Windows 7 x86 installs successfully, but the x64 version triggers a BSOD on the latest build?

Windows 7 x86 installs successfully, but the x64 version triggers a BSOD on the latest build?

M
mineuout482
Posting Freak
812
09-09-2020, 01:28 AM
#1
Hi everyone,
I hope you're all doing well.
I've been a quiet observer on this platform for quite some time, and like a few of you, I'm still using Windows 7.
Last week I chose to upgrade my PC, which now features the Ryzen 9 5950X CPU on an ASRock X570 Pro4 motherboard.
To my surprise, it didn't boot fully—it displayed the Starting Windows logo and then restarted into an endless loop.
Typically, a Start-up repair from the installation disc would fix this, but once I finished with "Windows Loading Files," it would suddenly crash with a BSOD.
However, when using an x86 disc for repair, everything loads correctly.
I've tried various approaches so far, but the method that seemed promising didn't work.
I'm currently using a spare 3TB hard drive and planned to install a fresh Windows 7 x64 version, but again, after "Windows Loading Files" it still triggered a BSOD.
But with an x86 disc, the setup boots up and the installation finishes successfully!
I even managed to boot straight into the newly installed OS.
This is puzzling—I've checked the BIOS, adjusted settings, and tried different configurations, but the system consistently rejects 64-bit options, even though the hardware meets the requirements.
Anyone have any advice or insights on what might be going on? I really appreciate your help!
M
mineuout482
09-09-2020, 01:28 AM #1

Hi everyone,
I hope you're all doing well.
I've been a quiet observer on this platform for quite some time, and like a few of you, I'm still using Windows 7.
Last week I chose to upgrade my PC, which now features the Ryzen 9 5950X CPU on an ASRock X570 Pro4 motherboard.
To my surprise, it didn't boot fully—it displayed the Starting Windows logo and then restarted into an endless loop.
Typically, a Start-up repair from the installation disc would fix this, but once I finished with "Windows Loading Files," it would suddenly crash with a BSOD.
However, when using an x86 disc for repair, everything loads correctly.
I've tried various approaches so far, but the method that seemed promising didn't work.
I'm currently using a spare 3TB hard drive and planned to install a fresh Windows 7 x64 version, but again, after "Windows Loading Files" it still triggered a BSOD.
But with an x86 disc, the setup boots up and the installation finishes successfully!
I even managed to boot straight into the newly installed OS.
This is puzzling—I've checked the BIOS, adjusted settings, and tried different configurations, but the system consistently rejects 64-bit options, even though the hardware meets the requirements.
Anyone have any advice or insights on what might be going on? I really appreciate your help!

K
ketman34
Posting Freak
834
09-09-2020, 05:21 AM
#2
Where were the drivers for Win7 obtained? The manufacturer of the motherboard does not supply Win 7 drivers for that board.
K
ketman34
09-09-2020, 05:21 AM #2

Where were the drivers for Win7 obtained? The manufacturer of the motherboard does not supply Win 7 drivers for that board.

T
tikitiki250
Junior Member
14
09-11-2020, 12:16 AM
#3
Certainly yes, during the fresh installation almost nothing functions properly, though there is a workaround that I plan to fix soon.
It’s surprising that the new build can install and boot into Windows 7 x86, but it won’t start, let alone set up Windows 7 x64.
This is what really confuses me. Am I overlooking something?
T
tikitiki250
09-11-2020, 12:16 AM #3

Certainly yes, during the fresh installation almost nothing functions properly, though there is a workaround that I plan to fix soon.
It’s surprising that the new build can install and boot into Windows 7 x86, but it won’t start, let alone set up Windows 7 x64.
This is what really confuses me. Am I overlooking something?

I
icantswim
Member
112
09-12-2020, 10:34 AM
#4
I believe the issue lies in the fact that the motherboard doesn't support Win7, while the X370 did but not the X570. It's like trying to mix oil and water—just a mismatch.
I
icantswim
09-12-2020, 10:34 AM #4

I believe the issue lies in the fact that the motherboard doesn't support Win7, while the X370 did but not the X570. It's like trying to mix oil and water—just a mismatch.

C
CrazyBessyCat
Posting Freak
912
09-12-2020, 03:14 PM
#5
I understand your perspective, but I managed to set up Windows 7 x86 without any major issues.
C
CrazyBessyCat
09-12-2020, 03:14 PM #5

I understand your perspective, but I managed to set up Windows 7 x86 without any major issues.

E
Eppikx
Senior Member
447
09-14-2020, 01:28 PM
#6
So the 32-bit MS default drivers are sufficiently close to work on newer hardware without causing issues, though the 64-bit versions have stricter requirements. Observe that these aren't meant for everyday use; they're designed solely to facilitate proper driver installation, which means they won't activate any advanced hardware acceleration or special features, resulting in poor performance (for instance, the Microsoft Basic Display Adapter/Standard VGA Graphics Adapter driver used before installing specific GPU drivers). However, if no suitable drivers exist...

If you needed a fully compatible setup, Windows 9x remains the best option because it can revert to 16-bit MS-DOS compatibility mode, allowing operation even when working drivers aren't available. This mode is significantly slower and more restrictive, potentially capping device usage at 64MB of RAM. Still, it functions technically enough to complete the installation process.

Considering that 32-bit Windows 7 only supports booting from MBR and thus Legacy BIOS mode, you might attempt to enable the same setting in a 64-bit environment by using a 2TB drive and enabling "Legacy Option ROM only" for Storage, disabling Secure Boot and CSM mode. Installing Windows 7-64 in UEFI mode has proven more challenging than in Legacy BIOS mode, so the latter is likely more compatible—though it means you can't boot from a 3TB GPT disk.
E
Eppikx
09-14-2020, 01:28 PM #6

So the 32-bit MS default drivers are sufficiently close to work on newer hardware without causing issues, though the 64-bit versions have stricter requirements. Observe that these aren't meant for everyday use; they're designed solely to facilitate proper driver installation, which means they won't activate any advanced hardware acceleration or special features, resulting in poor performance (for instance, the Microsoft Basic Display Adapter/Standard VGA Graphics Adapter driver used before installing specific GPU drivers). However, if no suitable drivers exist...

If you needed a fully compatible setup, Windows 9x remains the best option because it can revert to 16-bit MS-DOS compatibility mode, allowing operation even when working drivers aren't available. This mode is significantly slower and more restrictive, potentially capping device usage at 64MB of RAM. Still, it functions technically enough to complete the installation process.

Considering that 32-bit Windows 7 only supports booting from MBR and thus Legacy BIOS mode, you might attempt to enable the same setting in a 64-bit environment by using a 2TB drive and enabling "Legacy Option ROM only" for Storage, disabling Secure Boot and CSM mode. Installing Windows 7-64 in UEFI mode has proven more challenging than in Legacy BIOS mode, so the latter is likely more compatible—though it means you can't boot from a 3TB GPT disk.

T
TheFreshestAC
Member
182
10-04-2020, 11:07 AM
#7
I considered providing a brief update just to let you know, but it seems the ACPI on the Asrock motherboards might be blocking the process. I went into the BIOS and turned off all ACPI-related settings—secure boot was enabled, CSM was active, and legacy mode was turned on. Despite these changes, nothing worked. Would there be any chance to fix this on an Asrock board?
T
TheFreshestAC
10-04-2020, 11:07 AM #7

I considered providing a brief update just to let you know, but it seems the ACPI on the Asrock motherboards might be blocking the process. I went into the BIOS and turned off all ACPI-related settings—secure boot was enabled, CSM was active, and legacy mode was turned on. Despite these changes, nothing worked. Would there be any chance to fix this on an Asrock board?