Issues with MB: Won't run Windows?

[KalebJohns]

First off, sorry if this is in the wrong section. I believe my problem lies in the motherboard, but unsure. Second, I'm still fairly new to computer troubleshooting and repair.

For a recent computer repair, I received an old computer as payment. Turns out this old computer has a Core 2 Quad Q6600, 4GB DDR2 800MHz, and an Intel DQ965GF motherboard. The computer posts fine, runs Ubuntu LiveCD just fine. However, when I try to install Ubuntu or any version of windows, I either get an error in Linux's verbose boot or a BSoD with no error code. The BSoD error suggests updating the BIOS, which I've done. Both hard drives are tested good, power supply and RAM are known to be good. What else could be the problem here? Thanks for any help.

 

[cklaubur]

What is the error you are getting?

Casey

 

[KalebJohns]

What is the error you are getting?

Casey

That's the thing, it doesn't give me an error, it just says that windows couldn't run, then told me to update my BIOS, which I've ale easy done.

 

[smorizio]

check to see if the ram on the mb ram guild. some ram and mb dont run well. they wont fail memtest but they wont install an os right. try using one dimm if the install fails try bumping up the ram voltage. if it fails try turning off cpu cache and other parts of the cpu to see if the cpu has heat damage.

 

[smorizio]

have you tried booting from hirem boot disk/usb stick they have mini xp boot to see if it hardware or the drive. (with the drive did you fdisk the mbr to remove non windows boot manager???

 

[KalebJohns]

have you tried booting from hirem boot disk/usb stick they have mini xp boot to see if it hardware or the drive. (with the drive did you fdisk the mbr to remove non windows boot manager???

Sorry for the late reply. I tried installing with one stick and it didn't do anything different. I installed XP and it booted fine once or twice, the blue screened. I have not used Hirem's boot cd, but I'm 98% sure it isn't the drive.

I also recently used DBAN on this drive, so it shouldn't have an MBR on it at all

 

[smorizio]

if it not the ram..may be bad cpu cach or bad cpu. try running the intel cpu test.

 

[Calvin7]

The Q6600 only is compatible with some board revisions. You should check for compatibility information. The board revision AA# can help determine your board name. It can be found on the box label as well as the serial number label on the motherboard.

 

[KalebJohns]

The Q6600 only is compatible with some board revisions. You should check for compatibility information. The board revision AA# can help determine your board name. It can be found on the box label as well as the serial number label on the motherboard.

I checked the compatibility and the intel information site said it supported Core 2 Duo's but didn't list any specific processors. I figured that the Core 2 Quad could have some issues, but I didn't think that would be a major factor.

 

[KalebJohns]

if it not the ram..may be bad cpu cach or bad cpu. try running the intel cpu test.

I will test this shortly, and will post the results when done.

 

[KalebJohns]

if it not the ram..may be bad cpu cach or bad cpu. try running the intel cpu test.

The Intel CPU test came back with no errors, but suggested I clear CPU caches. Not too sure how to do this, but I've been researching to no avail. Suggestions?

 

[smorizio]

in the bios there setting to turn off cpu cache sometime or hyperthreading.

 

[KalebJohns]

check to see if the ram on the mb ram guild. some ram and mb dont run well. they wont fail memtest but they wont install an os right. try using one dimm if the install fails try bumping up the ram voltage. if it fails try turning off cpu cache and other parts of the cpu to see if the cpu has heat damage.

This board did not like the fact that there were two different speeds of RAM; 800 and 667 DDR2. Now that it has 4 sticks of 1GB 800MHz DDR2, I can't seem to keep "SW Single Processor Mode" off. It's almost as if every time I boot the computer, it switches itself back on. I'm going to try clearing the BIOS.