Hi all,
Hopefully you can help me with some issues i'm having.
I wanted to upgrade my CPU to something a bit more powerful but was tight on budget, so found out that I could fit an Intel Xeon to replace my old Core 2 Duo. I bought a CPU that has been pre-modified so I didn't have to try fit the adaptor myself or cut the tabs out of my motherboard.
Fitted the new CPU (X5460) to my motherboard (ASUS P5P41D) with no issues and it boots to the bios and seems to recognise the new CPU with no issues and will allow me play with the settings.
However, when exiting the bios to boot into Windows (Windows 10) the blue Windows logo appears and then the computer seems to freeze, any lights on the keyboard go off and it doesn't progress to the log on screen or the system repair menu.
I have read a few bits that suggest that it may be due to the bios reset (done with the jumper) messing with the hard drive settings, but haven't had a chance to look at this.
Does anyone have any suggestions for getting around this issue, could it be the hard drive not being properly recognised, if so, what can I do to fix this, or what other issues could it be?
Thanks,
Steve
Hopefully you can help me with some issues i'm having.
I wanted to upgrade my CPU to something a bit more powerful but was tight on budget, so found out that I could fit an Intel Xeon to replace my old Core 2 Duo. I bought a CPU that has been pre-modified so I didn't have to try fit the adaptor myself or cut the tabs out of my motherboard.
Fitted the new CPU (X5460) to my motherboard (ASUS P5P41D) with no issues and it boots to the bios and seems to recognise the new CPU with no issues and will allow me play with the settings.
However, when exiting the bios to boot into Windows (Windows 10) the blue Windows logo appears and then the computer seems to freeze, any lights on the keyboard go off and it doesn't progress to the log on screen or the system repair menu.
I have read a few bits that suggest that it may be due to the bios reset (done with the jumper) messing with the hard drive settings, but haven't had a chance to look at this.
Does anyone have any suggestions for getting around this issue, could it be the hard drive not being properly recognised, if so, what can I do to fix this, or what other issues could it be?
Thanks,
Steve