ASUS P5B-Deluxe; Problems & Fixes

Quote:

---

Originally Posted by MARINECOP

So should I just leave it at 266? As for the settings they are here on the first post. http://www.xtremesystems.org/forums/...d.php?t=115217Only the first two pics.

---

Don’t take some of those settings literally.
That’s a guide to get you started.
For a beginner you have to input lower settings at first
Then work your way up to your highest stable settings.

Use these settings to get you started.
CPU Frequency = 333
Dram 667
PCI Exp 105
PCI clock 33.33
CPU Vcore 1.4
Memory voltage 2.05
FSB Term 1.4
NB Vcore 1.45
SB Auto
ICH Auto
CPU multiplier 9X
Memory latency 4-4-4-12
In CPU settings enable execution disable bit the rest disable
Take your time and raise the FSB until your no longer stable then make your adjustments.
If you have already run this rig at 533 X 7 then I would say you have a nice CPU there and if you start low at 9 X multiplier you’ll end up with some pretty nice clocks at lower Vcore.
Also your limiting your rams bandwidth and Frequency at 533 7 X .
Your ram should be able to hit DDR 1000 at 5-5-5-15 @ 2.1 volts DDR 800 for sure.
Like I said take your time and use the recourses on this site but don’t get discouraged if you can’t run the same as others (you have to find your own sweet spot)
:cool:

This is what I went with, but it doesn't appear to be overclocked. http://i162.photobucket.com/albums/t...g?t=1172189406http://i162.photobucket.com/albums/t...g?t=1172189439
http://i162.photobucket.com/albums/t...g?t=1172189470http://i162.photobucket.com/albums/t...g?t=1172189485
http://i162.photobucket.com/albums/t...g?t=1172189505http://i162.photobucket.com/albums/t...g?t=1172189521

It's because you lowered the multi. 7*333=2331Mhz
Increase FSB to 400 and the multi to 8. You'll get 3.2Ghz. Leave the vcore at 1.400v and see if it boots. If it does run Orthos to see if it's stable, check temps with CT and Probe. CT should be under 85 and CPU temp reported by Probe under 60. And put the mem frequency at 533, you will go 1:1.
Also disable SpreadSpectrum. In CPU Function leave CPU TM, Modify Ratio Support, Execute Disable Bit and PECI enabled, the rest disabled.

he is 1:1. the asus autochanges the number, thus 666 when hes at 333.

Oh, yes. Missed that, it's late night here and I'm pretty tired.

Quote:

---

Originally Posted by Blackoberst

It's because you lowered the multi. 7*333=2331Mhz
Increase FSB to 400 and the multi to 8. You'll get 3.2Ghz. Leave the vcore at 1.400v and see if it boots. If it does run Orthos to see if it's stable, check temps with CT and Probe. CT should be under 85 and CPU temp reported by Probe under 60. And put the mem frequency at 533, you will go 1:1.
Also disable SpreadSpectrum. In CPU Function leave CPU TM, Modify Ratio Support, Execute Disable Bit and PECI enabled, the rest disabled.

---

So should I disregard this?

No, skip the part with mem at 533. You already did that.
The rest is ok.

I changed it from 7 to 8 and 333 to 400 like you said. I am now at 3.2. Hip hip horay. By the way, what is orthos, ct and probe? I now have a power fan warning. 0rpms.

Orthos is for stability testing. Download link Core Temp is for temp monitoring. Asus Probe monitors MB temp, CPU temp, voltages, fan rpms, etc.
You'll find ASUS Probe on ftp.asus.com and there is a thread around here whre you can find CT.
Where do you get the power fan warning?
When running Orthos check temps with CT and Probe. Max cpu temp for CT is 85 and for Probe is 60. Make sure you don't go over.

lol you have a fan plugged into the power fan lead?

Quote:

---

Originally Posted by ziddey

lol you have a fan plugged into the power fan lead?

---

What does that mean?

This what ORTHOS gave me.

Type: Blend - stress CPU and RAM Min: 8 Max: 4096 InPlace: No Mem: 767 Time: 15
CPU: 3600MHz FSB: 400MHz [400MHz x 9.0 est.]
CPU: 3600MHz FSB: 400MHz [400MHz x 9.0 est.]
2/22/2007 9:14 PM
Launching 2 threads...
Using CPU #0
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
Torture Test ran 16 minutes 3 seconds - 1 errors, 0 warnings.
Execution halted.

Using CPU #1
Beginning a continuous self-test to check your computer.
Press Stop to end this test.
Test 1, 4000 Lucas-Lehmer iterations of M19922945 using 1024K FFT length.
Test 2, 4000 Lucas-Lehmer iterations of M19922943 using 1024K FFT length.
Test 3, 4000 Lucas-Lehmer iterations of M19374367 using 1024K FFT length.
Test 4, 4000 Lucas-Lehmer iterations of M19174369 using 1024K FFT length.
Test 5, 4000 Lucas-Lehmer iterations of M18874369 using 1024K FFT length.
Test 6, 4000 Lucas-Lehmer iterations of M18874367 using 1024K FFT length.
Torture Test ran 16 minutes 3 seconds - 0 errors, 0 warnings.
Execution halted.

ASUS PC Probe II

Alert Log Report

Number = 4
================================================== =

[02/22/2007 at 08:49 pm] POWER Fan Abnormal, 0 RPM
[02/22/2007 at 08:50 pm] POWER Fan Abnormal, 0 RPM
[02/22/2007 at 08:59 pm] POWER Fan Abnormal, 0 RPM
[02/22/2007 at 08:59 pm] POWER Fan Abnormal, 0 RPM
Orthos brought my temps up way high during the test. In AI SUITE I observed temps at, CPU 132F and System at 84F.

more vcore. p5b droops like a mother. 1.4v wouldn't even get me 3.2 before droop mod

Well, I just played Half Life 2 and my MOBO is beeping like crazy during game play. I will have to load all my settings to default and give up on overclocking this board. I must say that this is the worst motherboard that I have ever had. The first one died on me and now this. I should have known to stay away from ASUS. A couple of years ago I had an ASUS mobo that died on me before without any overclocking. I wasted weeks of time trying figure this board out. Thank you to all that have helped me. I am in your debt.

http://chuckbam.com/Vista/AI_Suite.jpg

Quote:

---

Originally Posted by MARINECOP

Well, I just played Half Life 2 and my MOBO is beeping like crazy during game play. I will have to load all my settings to default and give up on overclocking this board. I must say that this is the worst motherboard that I have ever had. The first one died on me and now this. I should have known to stay away from ASUS. A couple of years ago I had an ASUS mobo that died on me before without any overclocking. I wasted weeks of time trying figure this board out. Thank you to all that have helped me. I am in your debt.

---

before you give up just set your bios up like you showed but set all voltages to auto except cpu and ram set those at the settings that worked well before. also i bet the beeping is a reminder that the fan isn't working disable the warning for that fan and the beeping will stop i bet.

You are right about the fan. I contacted ASUS and they told me it was because pc probe was monitoring my fans, but I only had my PSU connected to the mobo. I disabled all the chassis 1, 2, 3. I still get a beep because my rear power fan is not turning on. I will have to figure that out. Could that be something that I have to enble in the bios? Power is 0rpms. I have kept my bios overclock settings and it is stable except for that power fan beep. Looks like that is where my problems lie.

ouch lol

I need some help with the onboard audio.

When I go into dxdiag and perform all the sound tests (you know, where it plays all those ancient nature bird sounds from win95 at different sample rates?), and after it gets through a few it comes up with the dialog:

"Your sound card does not support hardware buffering. Sounds will only play back from software buffers."

I believe this is the reason when I play emulator games (different emulators, most of which probably use fmod as the sound library), the audio becomes badly distorted, crackly, and time-warped after a certain period of time. Then it pops back and plays normally again for a few more seconds, then goes all screwy again. I seriously doubt my sound hardware does not have any hardware buffering capability. So is this another ASUS driver issue for this board, or is there something else I can try? Thanks.

I just tested mine and all were successful. Not sure what that means. Sounds like a driver / software issue

Grrr...

http://img.photobucket.com/albums/v2...ODonP5B002.jpg
http://img.photobucket.com/albums/v2...ODonP5B001.jpg

Bad board or RAID software/iastor.sys issue? It happens on 2 different hdd's. RAM goes through memtest fine. I used Nlite the first time and a usb floppy the second time. Reg gets pounded and it makes me sad. :( I'd go right for a 680i, but the 7.2ms RAT and 171MB/s STR from the matrix RAID won't let me. :(

I've had that dreaded error a ton of times on my ds3. a lot of times, a reboot and it'd just go in for whatever reason.

Yeah, I can F8 it in, but I'd rather not get the error. :D

Marinecop, what cpu heatsink/fan do you have?
What's your cpu temp?
Do you have a digital multimeter?
What powersupply are you using?
What slots do you have the ram in?
Do not mix ram. Use the same ram. Preferrably bought in "dual channel" sets, not individually.

i can't get rid of the pcie x1 issue, and i am unstable at 3.3 ghz, any help is appreciated.

http://img85.imageshack.us/img85/6707/statsmm9.gif