F5F Stay Refreshed Software Operating Systems Xeon vs win 10

Xeon vs win 10

Xeon vs win 10

D
DatZeez_
Member
54
09-09-2016, 01:29 AM
#1
I have a setup in my hometown, India. My PC specs are: Xeon X5430, modified for socket 775 Gigabyte G41 M combo motherboard, 4GB DDR3 RAM at 1333MHz, and a 500GB hard disk with a GTX 710 graphics card. I believe this configuration is suitable for running Windows 10, but an issue arose during the installation process—specifically, an error stating that the processor cannot run Windows 10 (error compare exchange 128). Many users have encountered similar problems but haven’t found a fix. After trying a dual-core E5300 instead, I attempted to install Windows 10 again and was surprised by the results.
D
DatZeez_
09-09-2016, 01:29 AM #1

I have a setup in my hometown, India. My PC specs are: Xeon X5430, modified for socket 775 Gigabyte G41 M combo motherboard, 4GB DDR3 RAM at 1333MHz, and a 500GB hard disk with a GTX 710 graphics card. I believe this configuration is suitable for running Windows 10, but an issue arose during the installation process—specifically, an error stating that the processor cannot run Windows 10 (error compare exchange 128). Many users have encountered similar problems but haven’t found a fix. After trying a dual-core E5300 instead, I attempted to install Windows 10 again and was surprised by the results.

H
Heather_Games
Junior Member
40
09-09-2016, 07:59 AM
#2
Display an image of the error. Specify the Windows 10 version you're using. You mentioned compatibility with older chips, which is good to know.
H
Heather_Games
09-09-2016, 07:59 AM #2

Display an image of the error. Specify the Windows 10 version you're using. You mentioned compatibility with older chips, which is good to know.

S
Sage_Deceit
Member
65
09-27-2016, 04:57 PM
#3
I cut off the graphics card from the system once I got the fix, and after switching to the built-in VGA port, I managed to set up Windows 10 on an Xeon CPU, though it didn’t work as expected.
S
Sage_Deceit
09-27-2016, 04:57 PM #3

I cut off the graphics card from the system once I got the fix, and after switching to the built-in VGA port, I managed to set up Windows 10 on an Xeon CPU, though it didn’t work as expected.

E
eastland97
Senior Member
644
09-28-2016, 10:49 PM
#4
It's not about the number of cores—it's the design of the CPUs. There are some strange issues where Windows 10 64-bit fails to install while 32-bit works. Consider installing an older version of Windows 10 64-bit on the desired CPU.
E
eastland97
09-28-2016, 10:49 PM #4

It's not about the number of cores—it's the design of the CPUs. There are some strange issues where Windows 10 64-bit fails to install while 32-bit works. Consider installing an older version of Windows 10 64-bit on the desired CPU.

G
GamingOcelot
Member
118
09-29-2016, 05:44 PM
#5
I reviewed your updates and downloaded an older version of Windows 10 (build 9841). After restarting on January 1, 2014, the date issue was resolved. However, a new error now appears—please let me know what it says so I can assist further.
G
GamingOcelot
09-29-2016, 05:44 PM #5

I reviewed your updates and downloaded an older version of Windows 10 (build 9841). After restarting on January 1, 2014, the date issue was resolved. However, a new error now appears—please let me know what it says so I can assist further.

S
SnailNugget
Junior Member
40
10-09-2016, 12:23 AM
#6
Restore BIOS to its original settings and check functionality. Alternatively, activate DEP (disable bit), which is commonly referred to as "XD disable bit."
S
SnailNugget
10-09-2016, 12:23 AM #6

Restore BIOS to its original settings and check functionality. Alternatively, activate DEP (disable bit), which is commonly referred to as "XD disable bit."

C
195
10-10-2016, 10:57 AM
#7
Following your instructions, I restored the BIOS to its default settings and turned on the no-execute memory protection feature, yet the issue persists with an ongoing error.
C
commander_mais
10-10-2016, 10:57 AM #7

Following your instructions, I restored the BIOS to its default settings and turned on the no-execute memory protection feature, yet the issue persists with an ongoing error.