Asus P5B DX 56K WARNING

Printable View

Show 100 post(s) from this thread on one page

03-01-2007, 01:30 PM
sdgserv

Quote:

Originally Posted by gtj

Ext PEG is the pci-e video card.

The 975X chipset supports 1 x16 or 2 x8. Can't change it.

Thank you..also should I leave it on Auto or set it at EXT PEG?
03-01-2007, 02:29 PM
gtj

Quote:

Originally Posted by sdgserv

Thank you..also should I leave it on Auto or set it at EXT PEG?

Leave it auto. Unless you also have a regular PCI video card, this option doesn't do anything.
03-01-2007, 02:52 PM
J@mmer

Quote:

Originally Posted by Blacklash

Shut your system down and move the mobo jumper to position 2 or "config". The jumper is near the bottom of your memory slots. Then when you post go into the BIOS it will be on the first page. You may disable C1E here as well if you wish. Save. Power off and move the jumper back to position 1 or its default.

Anybody with overclocking problems needs to kill that feature. Some may want to disable C1E and EIST because they reduce the system voltage and lower the multi in an idle state. That could cause freezing or crashing in rare cases with a high OC. YMMV.

Details on EIST:

http://www.intel.com/cd/channel/rese...eng/203838.htm

C1E:

http://techreport.com/reviews/2005q1...0/index.x?pg=2

Thanks Blacklash! I have disabled C1E but left watchdog on. Still no luck with OC'ing. I can run stock no problems, then I OC to 3GHz, no problems. Then maybe 3 reboots later or even 1 reboot later I get OC failed. Like the BIOS loses settings or doesen't save them properly. Could this be the watchdog feature playing funny buggers? I'd like to leave it on if possible because without it, recovering from a failed oc is a NIGHTMARE. I have to remove the CMOS battery.
03-01-2007, 03:05 PM
gtj

Quote:

Originally Posted by J@mmer

Thanks Blacklash! I have disabled C1E but left watchdog on. Still no luck with OC'ing. I can run stock no problems, then I OC to 3GHz, no problems. Then maybe 3 reboots later or even 1 reboot later I get OC failed. Like the BIOS loses settings or doesen't save them properly. Could this be the watchdog feature playing funny buggers? I'd like to leave it on if possible because without it, recovering from a failed oc is a NIGHTMARE. I have to remove the CMOS battery.

The watchdog is severely broken. You're going to have to disable it to get anything serious out of the board. Yeah it's a pain to keep moving the jumper but it's the only way. If you have a 3-pin fan extension cable you can plug it into the header and use the jumper on the end of the cable. Or you could wire up a switch.

EDIT: You shouldn't have to remove the battery. Just move the config jumper and power cycle.
03-01-2007, 03:05 PM
sdgserv

Quote:

Originally Posted by gtj

Leave it auto. Unless you also have a regular PCI video card, this option doesn't do anything.

Roger that..:)
03-01-2007, 03:18 PM
Salamander 2

Quote:

Originally Posted by gtj

It was tier 2 support I talked to. I'm just grateful they had a system they could play with while I was on the phone with them.

Create a support request first to get a reference number...

http://supportmail.intel.com/scripts...d=36,2386,2578

Be very specific about the problem so they route it correctly. Something like...

On the Intel 975XBX2 motherboard runinng BIOS 2634, disabling C1E on the BIOS maintenance screen doesn't actually disable C1E on the processor.

I have Bios 2634, and I disabled C1E in the bios. If this didn't really disable it, what does that mean in terms of overclocking or other performance? And if I really need it disabled, how do I - short of installing a different bios?
03-01-2007, 03:34 PM
gtj

Quote:

Originally Posted by Salamander 2

I have Bios 2634, and I disabled C1E in the bios. If this didn't really disable it, what does that mean in terms of overclocking or other performance? And if I really need it disabled, how do I - short of installing a different bios?

You can turn it off from Windows with RMClock or Everest. It's only a pain when you're tuning/benchmarking and even then, it's minor. Long term, it's a good thing since it will keep your temps down when the cpu is idle.
03-01-2007, 03:45 PM
Salamander 2

So, should I go back into the bios and enable it - just in case Intel fixes this with a later bios?

Also, I downloaded the TAT and turned it on while using Orthos. The temps for both cores varied in the 50 degrees, occasionally ramping up to 58 and 59. When I turned off Orthos and then started the workload analysis tool in TAT, the temps jumped into the low 60s. Is the workload analysis a better stress test than Orthos? What is the maximum temps at which point I should back off a bit on the overclocking?
03-01-2007, 03:50 PM
J@mmer

Quote:

Originally Posted by gtj

The watchdog is severely broken. You're going to have to disable it to get anything serious out of the board. Yeah it's a pain to keep moving the jumper but it's the only way. If you have a 3-pin fan extension cable you can plug it into the header and use the jumper on the end of the cable. Or you could wire up a switch.

EDIT: You shouldn't have to remove the battery. Just move the config jumper and power cycle.

Ahh roger that. I was hoping you wouldn't say that but I'll give it a shot tonight. Cheers GTJ and BLacklash, you guys are invaluable on this thread. :clap:
03-01-2007, 04:13 PM
argylesocks

help with windows instal (raid)

i got everything going in the bios. set it to RAID
then rebooted... hit CTL - I and setup a raid volume.
everything looked correct in the bios after that.

now i have 2x36 raptos that show up as 72gig
and 1 320gig drive

i popped in the Vista x86 cd. booted up. plugged in my code.
then it says "where do you want to install vista"

i have 2 options:
0 unallocated space 68gig
1 unallocated space 320gig

i picked the 68 & hit "new" for partition. created with the entire size.

then i get "this computer's hardware may not support booting to this disc"

hit "next"

"windows is unable to find a system volume that meets its criteria"

ugh. suggestions? i tried loading to my 320gig storage with no luck as well.
F6 method is not necessary, right? nor is loading any raid drivers at this stage?

hmmm.
03-01-2007, 04:14 PM
gtj

Quote:

Originally Posted by Salamander 2

So, should I go back into the bios and enable it - just in case Intel fixes this with a later bios?

Also, I downloaded the TAT and turned it on while using Orthos. The temps for both cores varied in the 50 degrees, occasionally ramping up to 58 and 59. When I turned off Orthos and then started the workload analysis tool in TAT, the temps jumped into the low 60s. Is the workload analysis a better stress test than Orthos? What is the maximum temps at which point I should back off a bit on the overclocking?

Nah don't worry about C1E right now.

Tat definitely does stress the cores more than orthos but doesn't test your memory at all so orthos is a better all around stress tester.

Your temps are not bad at all. If you start seeing anything higher than the mid 60's under an orthos test, I'd back off a little.

Anything above 70 is getting dangerous. 85 is pretty much fatal.
03-01-2007, 04:18 PM
gtj

Quote:

Originally Posted by argylesocks

i got everything going in the bios. set it to RAID
then rebooted... hit CTL - I and setup a raid volume.
everything looked correct in the bios after that.

now i have 2x36 raptos that show up as 72gig
and 1 320gig drive

i popped in the Vista x86 cd. booted up. plugged in my code.
then it says "where do you want to install vista"

i have 2 options:
0 unallocated space 68gig
1 unallocated space 320gig

i picked the 68 & hit "new" for partition. created with the entire size.

then i get "this computer's hardware may not support booting to this disc"

hit "next"

"windows is unable to find a system volume that meets its criteria"

ugh. suggestions? i tried loading to my 320gig storage with no luck as well.
F6 method is not necessary, right? nor is loading any raid drivers at this stage?

hmmm.

No drivers required.

First, double check that the array is the first boot drive in BIOS. If it isn't make it the first one and try again. If that doesn't work...

Boot the CD again but press "repair".
Open a command window.
type...
diskpart
select disk 0
clean
create partition primary
select partition 1
active
format fs=ntfs quick
assign
exit

Now reboot and try again.
03-01-2007, 04:36 PM
argylesocks

Quote:

Originally Posted by gtj

No drivers required.

First, double check that the array is the first boot drive in BIOS. If it isn't make it the first one and try again. If that doesn't work...

Boot the CD again but press "repair".
Open a command window.
type...
diskpart
select disk 0
clean
create partition primary
select partition 1
active
format fs=ntfs quick
assign
exit

Now reboot and try again.

yes, the array was the first.
i just deleted the array, then recreated it... (same info)
then loaded windows again... this time, i didnt hit "advanced" and didnt create a partition... i just hit "next" now its copying files.. hmm
ill keep ya posted. thanks :)

ps: my cpu temps in the bios are at 30C thats normal, right? i was worried i messed up installing the cpu/zalman

edit: dunno what i did different.. but vista is installed :)
03-01-2007, 04:49 PM
gtj

Quote:

Originally Posted by argylesocks

yes, the array was the first.
i just deleted the array, then recreated it... (same info)
then loaded windows again... this time, i didnt hit "advanced" and didnt create a partition... i just hit "next" now its copying files.. hmm
ill keep ya posted. thanks :)

ps: my cpu temps in the bios are at 30C thats normal, right? i was worried i messed up installing the cpu/zalman

Glad it going now.

30's is good.
03-01-2007, 05:49 PM
shogo_ca

Quote:

Originally Posted by gtj

If you start seeing anything higher than the mid 60's under an orthos test, I'd back off a little.

Anything above 70 is getting dangerous. 85 is pretty much fatal.

I agree with you that over 70c is bad, but doubt 85c is fatal.... I mean, 85c is the Tjunction temp, your core throttle down at that point or your cpu freeze. I got mine at 85c while doing some benching and it just froze. I would defenitly not run that for more then small benching sessions but i was wondering if you can actually kill your chip with 85c.... The reason why i have doubts is that QX6700 are actually 2 E6700 stuck together and their tjunction temp are 100c and while running them at stock speed with stock cooler 85c load is "normal"...
03-01-2007, 05:52 PM
shogo_ca

Oh btw anyone here plannig to do crossfire with some R600s on this board?
03-01-2007, 06:09 PM
gtj

Quote:

Originally Posted by shogo_ca

I agree with you that over 70c is bad, but doubt 85c is fatal.... I mean, 85c is the Tjunction temp, your core throttle down at that point or your cpu freeze. I got mine at 85c while doing some benching and it just froze. I would defenitly not run that for more then small benching sessions but i was wondering if you can actually kill your chip with 85c.... The reason why i have doubts is that QX6700 are actually 2 E6700 stuck together and their tjunction temp are 100c and while running them at stock speed with stock cooler 85c load is "normal"...

Not fatal for you, or I under controlled circumstances, but for those less experienced "pretty much fatal" is probably true. :)

BTW the default state for the thermal protection is "disabled". Check Everest or RmClock and you'll see it disabled.
03-01-2007, 06:25 PM
screwtech02

Quote:

Originally Posted by shogo_ca

Oh btw anyone here plannig to do crossfire with some R600s on this board?

Well, we'll see if they are ever released :rolleyes: , and if they are gonna need 2 x16 slots...
03-01-2007, 06:44 PM
LazyBum

Quote:

Originally Posted by jetjaguar

yeap all psu cables are in ..

i dont get it .. i set the mem to 533 and left the other thing at default

You need to set all settings to default, changing only the watchdog/c1e settings and successfully boot before you try to change anything else. After successfully booting at default settings you can reboot and start tuning :cool:
03-01-2007, 07:03 PM
argylesocks

Quote:

Originally Posted by gtj

Glad it going now.

30's is good.

:)
so how long before i can start OC'ing??
should i let things 'settle in' for a few days...
03-01-2007, 07:13 PM
jetjaguar

this sucks .. i guess ill try to overclock later .. im sitting here at stock 2.13ghz .. its so beyond slow .. vista is like crawling .. i cant believe this crap .. hopefully i can get this board overclocking or im gonna have to go back to the 680i
03-01-2007, 07:23 PM
gtj

Quote:

Originally Posted by jetjaguar

this sucks .. i guess ill try to overclock later .. im sitting here at stock 2.13ghz .. its so beyond slow .. vista is like crawling .. i cant believe this crap .. hopefully i can get this board overclocking or im gonna have to go back to the 680i

Recap please. Exactly what settings are you trying.
03-01-2007, 07:48 PM
Bama Badaxe

I have just started tweaking after loading XP & 71 critical updates.:)
With cpu @ 333 x 9 and TAT running 90% workload in the background coretemp is showing 55*C & TAT reads consistantly 12 degrees higher @ 68-69*c. VID is set @ 1.325v. Idle temps are 29*c:banana:
03-01-2007, 08:19 PM
J@mmer

Hehehe it's as soon as you go over 334FSB is when the problems start. ;)
03-01-2007, 09:17 PM
bobov

I have tried bios 2333/2507/2634, all bios can run 400MHz X 9 without any problem, as long as you disable watchdog in maintennance mode.

Mobo: D975XBX2 Rev. 503
CPU: E6600
vFSB: 400MHz
vMCH: 1.50v
vFSB: 1.20v
vCore: 1.3625v
Mem ref: 266MHz
Mem runs @ 1:1 400MHz 3-4-3-8 2.2v

Hope it helps. :)

Show 100 post(s) from this thread on one page

All times are GMT -8. The time now is 03:55 PM.

XtremeSystems

Testing / comparing : Intel D975XBX2 / Asus P5B DX ***56K WARNING***

Testing / comparing : Intel D975XBX2 / Asus P5B DX 56K WARNING