• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New processor, No OS (Windows, Ubuntu) will load

JustWhitman

Senior member
The PC I'm playing with is using a Gigabyte 965P-DS3 rev2.0, which originally was paired with an Intel C2D E6300 (1.86GHz, 2MB, 1066FSB). The new processor I put in is an Intel C2D E6550 (2.33GHz, 4MB, 1333FSB). Now I know that on Gigabytes website it says that the rev2.0 board will NOT support 1333MHz FSB, only the rev3.3 will. But I've read that the rev2.0 "unofficially" supports the 1333FSB CPUs. I don't see why it's causing a problem, because it seems to me that if the mobo wouldn't work with the CPU that it wouldn't even POST. But it boots, POSts fine, can install Windows, but then when it gets ready to load the first time it freezes. I've even tried various Linux LiveCDs and what-not and every single one freezes when the OS gets a few seconds into the loading screen (never makes it to the desktop).

At first I thought it was a setting in the BIOS as it loaded the defaults with the new processor in. Tried everything possible, problem was still there. Then I thought maybe a reinstall of Windows would solve it, reformatted, same problem. Then thought, ok maybe the RAID array is causing problems. Blew away the array, and reloaded Windows, same problem.

I know the problem is the new processor, but I don't understand why really. So I'm wondering if there is anyway to work around this or if I'm just going to have to go back to the older processor.
 
Well it looks like putting the old processor in fixed nothing. WTF? MemTest shows no errors with the memory, obviously not the processor, switching to an old video card does nothing, tried putting OS on a different HDD, no change. So whats left? Bad mobo? Why would it ONLY do this after it goes through the install process? This makes no sense and now I'm to the point of wanting to pull my hair out. Ugh.
 
Two thoughts occur...

1. Did you update the bios for the new CPU?

2. Have you checked the CPU socket for bent pins?

HTH
 
Back
Top