I had this problem with this MB. I could not boot with the dual core CPU. I would get one beep and the screen froze. I put in a older HT processor and had a good boot. I updated to a later bios and was all set.Quote:
Originally Posted by Ancient1
Printable View
I had this problem with this MB. I could not boot with the dual core CPU. I would get one beep and the screen froze. I put in a older HT processor and had a good boot. I updated to a later bios and was all set.Quote:
Originally Posted by Ancient1
Quote:
Originally Posted by leejsmith
I found the answer to this problem on asus forums.
with remap disabled all 4gb of ram is address together as one big junk so xp pro can see 3.2gb and the rest is used for buffers ect.
with remap enabled the mobo splits the ram into 2 parts of 2gb each but the 2nd 2gb is address between 4gb and 6gb so xp will not see it. 64bit os's can address the 4gb - 6gb range so can use it no problem.
interesting. why would you want to remap then?
because my customer wanted dual boot xp pro and vista basic 64bit and need to enable the remap to get 4gb in 64bit..Quote:
Originally Posted by ziddey
so i am going to write some instructions for him so it's easy for him to do.
Well the easy part of that at least with this is save 2 different profiles in the bios and have like 1 be 32-bit and 2 be 64-bit. Gotta love that wish you could rename them though like on the DFI boards.Quote:
Originally Posted by leejsmith
OK I just built a backup rif with this mobo, an E6600 with stock HSF from X6800, 2x1gb Corsair XMS2 DDR2 800, an Ultra V series 400W PSU, WD 74GB Raptor 16MB cache and Samsung DVD RAM +/-R/RW running WinXP Pro.
The BIOS that came on the board was 0701 I believe. I didn't like it because it would take about 1 hour of power disconnect and CMOS jumper in clear position to recover from bad OC. I used Asus EZ Flash to flash BIOS 1101. Now I got it to boot only once with this new BIOS, but only after having power off and CMOS jumper in clear position overnight. Windows seemed OK so I decided to go for a mild OC.
300 on CPU...DDR2 600 for 1:1 stock vcore and vdimm...PCI-E 100...33.3...NB 1.55 all the rest auto. When I went into CPU setup and tried to enable ratio support the BIOS froze. Now I have the CMOS jumper in clear...1 hour later it POSTS. I try to change in the CPU section to disable C1E...BIOS freezes. It has been more than 3 hours and CMOS does not clear, not even with battery removed. This board is more trouble than it is worth. I think I will trade it in for another P5W DH which I have never had any problems with at all.
OK it appears I had a bad stick of RAM. The board seems to be working OK. I have my E6600 at 400x8 using 1.3875vcore, not stable. On my P5 W DH the same chip was stable at 400x8 1.37vcore. But then again I had 2gb RAM. Anyway I guess the board is OK and I just need to learn it a bit.
I have yet to try an older PROC than C2D. But I am pretty much done with this motherboard. I tried a E6400 CPU and some Corsair DDR2 667 RAM with no success! This has got to be the worst pc building experience I had in years!Quote:
Originally Posted by chuckbam
How is Asus's RMA process? How long am I looking at for the wait?
Thanks again for all the help guys.
Ok I just got back my p5b deluxe from RMA and it is a rev 1.10G motherbaord and here are a few things I noticed
Caps around CPU are purple
Traces are rewired around the marvel Yukon lan chip
The north bridge cooler is a deeper gold (could be just the RMA)
A few gold traces exposed on the board (no idea why)
Socket retention bracket has less of a dip on it.
The Temperature winbond sensor chip read correct temps (didnt happen on my old mother board)
I currently have a small farm folding 24/7 (only 4 machines at present), I haven't had the first problems with either of the 2 P5B Dlx's I have. Now all of a sudden when I try and fold on one it keeps giving me a communication (or some thing) error (I checked RAM, software, PSU, folding client, HD, cpu, etc) I tried it first with a E6600, then with a E6420 and finally with a E6300 (I only have one more cpu to try, a E6400) Does it sound like I might have burned the board out (my cpu temps are cool) Please anybody, I'm at my wits end with this board, I even took the E6300 out of the P5B and put it in a Asrock 775DUAL-VSTA (bad overclocker) and it folds like a "mad rabbit". :confused:
jws2346 try reinstalling the LAN drivers and update to the latest BIOS
Got ya, you mean the drivers on the CD right ? (excuse this statement if it's dumb :rolleyes: ) ThanxQuote:
Originally Posted by mukmaster
Phew! I finally made it all the way through this thread! This thing is epic! But learning takes effort, right? Thanks to all who have contributed thus far. I'm pleased to say that although this was my first build everything has gone pretty smoothly. I've got my e6400 running at 3.01Ghz (430x7) 24/7. It is an L2-stepping, so that be what has limited me, although I've recently done the Vdroop pencil mod and may try for 3.2 again (before it just needed too much vCore - although now that the new 6x20s are out maybe I'll just let this one get hot...)
Anyway, the one thing that has me a touch concerned is my "motherboard" temp (reads as "MB" in Probe and "System" in Speedfan). It had been reading 47-48C for a while, so I pulled off the NB and SB heatsinks and applied AS5 (but not to the Mofset - that didn't seem right...)
The temp now hovers around 44-45, but that still seems high compared to what others get (I often see mid-30s).
Basically, should I be concerned about this? How hot can/should it get? I have a Nzxt Appollo mid-tower case, with front and side intake fans and a rear exhaust fan (all 120mm). Also running a Tuniq Tower on the processor. If I should be concerned, what else can I do?
Also, what is the general concensous on processor (core) temps? I have been trying to keep things at under 60 during Orthos load, but can I go higher? I've noticed that nothing real-world seems to get the temps that high, so can I go to 65-67 in Orthos? What if I dont care too much about the life of the processor? Will overheating the processor fry other parts, too?
thanks
ScottieB
I have a question.
It is a problem to set the MCH (chipset) voltage to 1.55 by aircooling?
I want to use FSB400 with 5:4 @ DDR1000 but sometimes at startup my pc is freezing. Don't know why... I have 2 GB cellshock DDR800 (D9GMH) and it doesn't work with DDR1000 @ CL5 @ 2.3V @ 5:4. my pc won't boot (mch currently @ 1.45V).
But if i change cl4 to cl5 (5-5-5...) than he starts, but sometimes i get freezes at startup.
maybe it will work without problems if i set MCH to 1.55V ?
update:
I have set NB volatge @ 1.55 but problem still exist.
My pc freezes at startup if I start from standbye...
I don't get a freeze if i turn my PSU off and on and start my pc.
wtf?!
for 4:5 you need more vdimm due to much tighter latencies on 4:5 versus 2:3 dividers or you can set CAS5 to help loosen it up at 4:5 divider. vMCH set at 1.65v might helpQuote:
Originally Posted by lew187
i.e.
http://fileshosts.com/intel/Asus/P5B...3m21s125ms.png
I have tryed:
FSB400, DDR1000 (4:5 @ CL5 @ 2,3V), NB @ 1,55V
=> after 1 successfull boot... freezed while booting again from standybe after shutdown.
FSB422, DDR10xx (4:5 @ CL5 @ 2,3V, NB @ 1,55V
=> freezed.
But.. 1 time i could boot and ran Aquamark 3 without problems. Then I shutdown my pc and started it again.. -> freeze (bios resett necessary because pc wont boot, absolutely no boot.. black screen).
Is it my memory (Cellshock DDR800 cl4 D9GMH) what makes the problems or is it the 4:5 dividers who won't work on my P5B Deluxe ???? :(
I have a problem with my board. It's a rev. 1.03G with BIOS 0507. I've tried it with two different CPUs (Xeon 3060 and Celly 326), several memory sticks, PSUs and graphics cards.
It worked fine until a mosfet above the pci-e slot burnt. The board was running at stock when that happened. Then I soldered on a mosfet from a dead P5B-E Plus, but the Dlx won't boot now.
It turns on, stays on for some seconds, turns off and on again and keeps on like that, no post. Do you think there is any hope for my board?
I've tried replacing the CMOS battery.
Updated to latest bios 1101 with latest Asusupdate software
i restart and get an bios checksum error, changed back to original overclocked settings and boots into windows
is there something wrong?
now i restart the asusupdate thing and now it says on the bios rom info = unknown and "Due to BIOS inner framework was changed, please download the latest software from the asustek website"
so i cant rollback to 1004?
Hmm, bios checksum isn't out of the ordinary. Besides, people advise against flashing when o/ced but I say if it's known to be good, why not?
But have you tried downloading 1101 or whatever the newest is and flashing it again?
Did you try setting every thing to default, reboot and then set up your custom settings? Or, try to clear the bios with the jumper.Quote:
Originally Posted by flopplop
You can only rollback to 1004 with the Dos program Afudos. The Asusupdate software will not let you go back-wards. I only use the Dos program. I think the Windows program can cause problems. Just to much going on at the same time.
http://support.asus.com/download/download.aspx?SLanguage=en-us&model=P5B%20Deluxe&type=map&mapindex=1
Looking for a P5B-Deluxe Combo heatsink. PM me if you have one. Thanks.
has anyone of you had any CDBOOT: memory overflow errors with its P5bdlx?
Hi I need some help with my Asus P5B-Deluxe setup with an E6600 and some Crucial Ballistix DDR2-800 memory.
I had been running very stable at 356x9 for quite awhile now, but then I learned that 400x8 is better because the FBS and the mem would be running at matching speeds.
Anyway, no luck at 400x8. System fails to power back on. Any ideas? Here are my settings btw:
CPU Frequency 400
DRAM Frequency DDR2-800MHz
PCI Express Frequency 100
PCI Clock Synchronous Mode 33.33MHz
Memory Voltage 2.00V
CPU VCore Voltage 1.4000V
FSB Termination Voltage 1.2000V
And I'm running my memory at 4-4-4-12 timings also.
hmm, sorry to hear your troubles. I'm able to do 400fsb 1:1 fine with all stock settings.
But have you tried:
105pcie or 110?
you try 2.1v for vdimm?
how about applying 1.45v to nb?
perhaps slightly higher vcore too for whatever reason
how about defining timings manually. you can give 5-5-5-15-5-42-3-11-7-13 a shot to start with. turn off static read control to start too as well.
also, does 401fsb work? how about if you drop the multiplier to 7x to see if it'll do that fsb?
what bios are you running?
that said, if 401fsb works, you'd be better off either proceeding to 467fsb+ if possible, or sticking with 356fsb. 401fsb is pretty weak.
If you're indeed limited to 356fsb, you can at least try 4:5 or 2:3 ram dividers with more vdimm and run your ram faster. Ballistix should be decent clocking.