ASUS P5W DH - Problems + Fixes Thread

[nickfd]

Hi all.. So last night I took out my e6600, cleaned off the AS5, and installed the g0 q6700 that arrived. Prior to doing this, I had installed lawry's g0 200(4/6?) modified bios on the mb, and was content with it working OK.

So when I booted the box, I went into the bios and started looking at the hardware monitor page. I think it was like 1.21 or 1.23vcore by default, and temperature was 24-25c at idle on my water. I started by mildly overclocking, and got it to post at 333mhz*10 at 1.45vcore. I didn't go into the OS at all, just sticking in the bios.

Then I upped the vcore and went up to 366x10. Still posted fine. Then did 400x10, and did 1.50vcore. Black screen, no post. After several hours of clearing the CMOS many, many times, and doing so without the battery in the mb, I finally got my bios back. I decided to go back to 333x10 and see if my os worked, testing the OS for the first time.

Bad news, nope. It would start booting, give the windows xp splash screen, then bluescreen immediately, and reboot. I couldn't tell what the msg was, since it rebooted so fast. Safe mode did the same thing. Then I tried Vista Ultimate 64bit, which I had on the same hd in a dualboot scenario. Same thing.. It would die shortly after splashscreen.

I was thinking worst case scenario.. something happened in the hd, and it corrupted the OS. K, so I formatted (reluctantly, since there was some stuff I didn't have backed up), and went to install XP SP2. It would finish installing the console/text portion of the OS, and when you reboot to have it go into the GUI, it would reboot constantly. Broke.

Testing the memory with memtest86 showed that there was no errors after an hour of crunching, back at normal 2.66ghz, with auto vcore. I tried upping the voltage to the cpu and it still made no difference. I also upgraded the mb bios from lawry custom to 2206, which had no impact or change on functionality, or lack thereof.

So I'm kinda stumped. I'm going to take out the q6700 tonite and pop my e6600 back in to see if it works. I don't know if the problem is the mb or the cpu may be a lemon, or got messed up while I was testing for higher oc? Either way, i'm frustrated.

I'm happy that other people posted pics with their g0's working on our mb, so at least I know mine SHOULD work. But I don't understand why it's not.

[GFORCE100]

Hi all.. So last night I took out my e6600, cleaned off the AS5, and installed the g0 q6700 that arrived. Prior to doing this, I had installed lawry's g0 200(4/6?) modified bios on the mb, and was content with it working OK.

So when I booted the box, I went into the bios and started looking at the hardware monitor page. I think it was like 1.21 or 1.23vcore by default, and temperature was 24-25c at idle on my water. I started by mildly overclocking, and got it to post at 333mhz*10 at 1.45vcore. I didn't go into the OS at all, just sticking in the bios.

Then I upped the vcore and went up to 366x10. Still posted fine. Then did 400x10, and did 1.50vcore. Black screen, no post. After several hours of clearing the CMOS many, many times, and doing so without the battery in the mb, I finally got my bios back. I decided to go back to 333x10 and see if my os worked, testing the OS for the first time.

Bad news, nope. It would start booting, give the windows xp splash screen, then bluescreen immediately, and reboot. I couldn't tell what the msg was, since it rebooted so fast. Safe mode did the same thing. Then I tried Vista Ultimate 64bit, which I had on the same hd in a dualboot scenario. Same thing.. It would die shortly after splashscreen.

I was thinking worst case scenario.. something happened in the hd, and it corrupted the OS. K, so I formatted (reluctantly, since there was some stuff I didn't have backed up), and went to install XP SP2. It would finish installing the console/text portion of the OS, and when you reboot to have it go into the GUI, it would reboot constantly. Broke.

Testing the memory with memtest86 showed that there was no errors after an hour of crunching, back at normal 2.66ghz, with auto vcore. I tried upping the voltage to the cpu and it still made no difference. I also upgraded the mb bios from lawry custom to 2206, which had no impact or change on functionality, or lack thereof.

So I'm kinda stumped. I'm going to take out the q6700 tonite and pop my e6600 back in to see if it works. I don't know if the problem is the mb or the cpu may be a lemon, or got messed up while I was testing for higher oc? Either way, i'm frustrated.

I'm happy that other people posted pics with their g0's working on our mb, so at least I know mine SHOULD work. But I don't understand why it's not.

Yeah I had the scenario you're having with my QX6700 at 10x333. It would work at 11x300 but not 10x333. The same situation with Windows XP not loading and rebooting at one point during start-up (though I'm sure the latter is because I had the restart after BSOD option enabled in device manager).

Finally I figured out one had to disable EIST and C1E for it to work, this was with the 1506 BIOS. Since then I just disable both regardless what BIOS I'm using when overclocking the QX6700.

[nickfd]

Yeah I had the scenario you're having with my QX6700 at 10x333. It would work at 11x300 but not 10x333. The same situation with Windows XP not loading and rebooting at one point during start-up (though I'm sure the latter is because I had the restart after BSOD option enabled in device manager).

Finally I figured out one had to disable EIST and C1E for it to work, this was with the 1506 BIOS. Since then I just disable both regardless what BIOS I'm using when overclocking the QX6700.

Well, I can't get into any OS to disable the autoreboot, and now after format and start of xp install, the gui part of the install doesn't work.

My CPU settings are:

Microcode Update : Enabled
Max CPUID Value Limit : Disabled
Execute Disable Function : Disabled
CPU Internal Thermal Control : Disabled
Virtualization Technology : Enabled
Intel SpeedStep Technology : Disabled

^- all the same stuff I had on my e6600 that worked an hour before I took it out and popped in the q6700.

And also remember that even when not overclocking, I can't get an OS either. So like I said, I think it must be the CPU that's messed up, or my frankenstien p5w dh deluxe that finally threw in the towel. If that's the case, Im gonna get a p35. I'll update after I put the e6600 back in tonight after work.