Dont be sorry, i was complimenting your phrase, which is 100% accurate.
Printable View
Dont be sorry, i was complimenting your phrase, which is 100% accurate.
nVidia released 185.85 WHQL drivers, and for 8- series as well. Good thing, after rumours that only 9- series and up would be supported. That would be stupid since 9- is no different than 8-, give or take. Even 6- and 7- older series still kicking.
Has anyone tried the 20000.1 audio drivers yet? Didn't have the time to install, in the weekend I hope. Any improvements? They keep talking about the Vista GUI v2.0 (as opposed to GUI v1.8) but haven't seen it. What's with the legacy thing they refer in the drivers? It's so damned confusing reading the readme files from IDT/Intel, just read it very quickly but even the driver versions don't add up.
Also, Dolby Control Center hasn't seen an update in years.
Hello again, friends.
Finally i tried all things to start together, but got sort of MB failure, and can't get out of it.
What parts i actually used:
1) An brand-new Q9550 processor (SLB8V), swapped for a second with working one from
friend of mine to check if it's not CPU failure (Q9450 one);
2) Pair of OCZ3P18004GK (2x2Gb memory kit, 1800Mhz, 8-8-8@1.9v, but don't
know what actually these have in their SPDs). Used combinations (accurate to
my memory): two in black slots, one in black slot, one in blue slot, one in another
black slot;
3) Brand-new TT Toughpower 700W PSU.
In addition, the MB isn't a brand new one, but described as working. As
i never turned it on, i don't now how old BIOS version it actually has. BTW, i'm interesting,
if there were failures with starting this mobo with some BIOS version and 45nm CPUs
(actually i haven't had 65nm CPUs to check them, but can pick up 775 P4-one (don't think
it should work with this chipset and MB by the way, as i don't remember exact specs of
supported CPU families.))
I've got it without CMOS battery and with BIOS-jumper switched in BIOS mode.
What i've done by steps:
1) In hurry (without checking CPU + MB coworking without heatsink at first) seted up CPU and it's
cooler (cheap ih-4405, but it doesn't matter now, that what i had for my experiements) and connected
CPU fan;
2) Inserted pair of upper described pair of OCZ;
3) Inserted Nvidia NVS 285 PCI-E (just slot-filling card, capable of 2D handling) in old PCI-E port;
4) Powered on the PSU, the MB was short-blink with CPU LED red, was run on, run CPU fan, then
turned off, turned on again, and was doing this once and once again (the endless reboot).
5) Switched BIOS-jumper in Config mode and tried to boot again, and again got short CPU LED
blink on start, and then just idling and roaring the fan;
6) Pulled out one memory stick, nothing appeared again;
7) Pulled out NVS 285 card, and inserted an old PCI S3 Graphics card and -- nothing again!
8) Pulled out ALL memory sticks, and get as i should 3 PC Speaker BEEPS (what means too less
memory);
9) Processor pulled out -- no start at all.
Then was a short effort to boot with friend's one Q9450, the "initially working state" CPU, i just
inserted it in CPU slot, and tried to boot with Config switch, and the same error again.
P.S.:Connected with both 24ATX + 4+4 connectors.
If i'll pull out 4+4 connector, i'll get LONG CPU LED blink.
Any suggessions are welcome, any help is apprecated!
Is there any chance to boot up, or it's rather better to pull "so-working MB" to the trash?
What sort of failure it may be? MB one? Or memory?
I remember running into something like that. unplug you rig, push the power button a few times, pull out the bios jumper completely, plug it in push the power button this won't make it boot, but then pull out the plug again, push the power button, put the jumper in regular mode or whatever, then try booting. If the board is on the first bios just doing random combinations of things like that and few hail mary's may help you get a boot.
ok well this is where I'm at. somewhere around 420 host clock I hit a wall, which seems pretty low to me, but maybe its a power supply issue.
currently im at 413 and stress tests pass.
cpu is at default (1.325 v)
fsb is 1.75
MCH is 1.225
6x multi
When it was at 420 host clock, first I raised FSB twice to 1.3, didnt work. then raised the mch one notch, didnt pass, then raised it again. still no go. so i upped the core voltage which didnt help either. where should i go from here?
Pontius, thanks a lot!
Never thought that things could be simple!
Switch on/off several times helps.
Also, while in diagnostic mode, my processor is q9550 with SLB8V spec,
which needs 1782 bios, while this board currently flashed with 1513.
Friend's one is q9450 which requires 1782 bios again.
glad i could help! so you can't flash the bios? not sure what you mean.
What you are experiencing is not uncommon...took me some time to figure it out, but:Quote:
Originally Posted by Pontius
i am going to guess that 1.75 vFSB is a typo.
Second, there is a natural progression of failure with this board and quads @ lowest multi...1)vFSB needs to be increased...seem to have that covered,
2)the MCH is the "weakest link" in this board, especially at or near stock voltages...it easily gets overwhelmed with the quads, dont be affraid to crank it up. as you have water cooling, throw 1.4 at it, it will fix your problems.
while youre in the BIOS, take the vCore back down.
the most important voltage to focus on here is the vFSB, since everything else uses it as a reference. the second most important is the vCore, mainly because the more you give it, the more quickly it will degrade/die. For the MCH, i am confident that it can handle max voltage with water cooling...do you recall how big the chip was when you put the water block on? its almost as big as the CPU.
in essence, crank up the MCH for now, you can lower it back down later, same with the vCore, but there are other reasons to keep it as close to default values for now (once you hit that point where windows freezes on load and more vFSB or vMCH dont fix it, write all the voltage and clock values down, post them here, then increase the vCore and continue increasing the host clock).
the current exercise you are going through is to determine what vFSB you need to run at the desired speed, or to determine what speed the desired vFSB can attain. Once this is determined YOU WILL NOT lower the vFSB, unless memory issues arrise that force you to run a much slower host clock than the voltage supports. Then we will move on to the vCore, and after that start lowering the vMCH.
ok, since you can get to diagnostics mode, you can update the BIOS with a CD without getting to the OS.Quote:
Originally Posted by dukzcry
i dont remember the specifics, but they should be listed on Intel's site. when you go to the support page, BIOS updates, there are like 5 options, one of those is for updating from CD and there are instructions (albeit horrible ones...WAY TO GO INTEL) on how to do it.
another thing you can try if the bios update doesnt fix anything is to unplug the system and take out the coin battery that provides backup power to the CMOS. you will need to leave it out for several hours (overnight is the easiest), and afterwards reinstall the battery, plug in, turn on, and all BIOS options will be reset (may allow you to get into windows?).
Hrm well I'm not sure if raising the MCH is helping at all but I will post more details later once I do some more testing. I do have one question though, bot during stress testing and idle cpu-z will show the bus speed and core speed as fluctuating just slightly, for example it will go back in forth between 420.0 MHz and 419.9 MHz. is that pretty normal? or is that evidence of instability?
Pontius, Sean-E-Boy:
Yes, of course i've downloaded ISO image, and made "Boot from optical devices" on, and choose my PATA optical drive in boot priority list. Still it cant boot from CD in diagnostic mode, and go immediately to it's menu, while this Marvel controller sees my PATA device.
UPD: boot CD loads from another machine. So it's right.
Some short details: when i stucked in diagnostic mode, BIOS splash screen appears, then Marvell screen with
founded devices appears, and then it's show "E9" word in right corner and immediately get me BIOS Config settings screen.
As i said before, mine CPU isn't supported by currently flashed BIOS version, so i get following:
Microcode Revision: Not loaded
And processor type shows like something generic (Intel Genuine processor / Intel EM64T Capable),
and runs at low speed (2Ghz) but on right FSB.
Pontius, the fluctuation that you see is normal. While the CPU is designed to operate at a particular speed and will do so, once you start increasing there is no guarantee that it will operate at exactly the speed you have set.
dukzcry, i think to load BIOS from optical you have to remove the jumper completely, not just move it do diagnostic.
Sean-E-Boy, the main problem, that the monitor signal never appears not in diagnostic mode.
I tried boot both BIO and ISO as described in Intel guide, with jumper removed but it didn't help. Tried to power on/off, tried wait for several minutes, it's get nothing.
I'll try to swap with E7200 for flashing in near future which should work.
dukzcry, i would say to try 2 things while you are waiting to swap with the e7200.
try installing only 1 memory dimm in the blue slot closest to the processor (i think you may have tried this already, but try it again)
remove the power and remove the backup battery from the motherboard (near the SATA plugs) let sit for ~2 hours, replace battery, put jumper to normal position (if not there already), plug in, turn on and see if anything is different.
you mentioned earlier that "I've got it without CMOS battery..." does that mean that you do not have a battery at all?
i am thinking that if you can get into diagnostics mode, but cannot get into the BIOS under normal jumper that some BIOS setting must be incorrect. I remember with the early BIOSs that one had an issue where the default setting for eSATA was RAID, and if it is set this way it wouldnt boot to internal SATA. I am going to look through my settings and let you know what they are so you can compare with what you have in your BIOS.
ALSO, i had an issue where the MCH or one of the memory slots on my board was defective and got similar continual partial power ups, shut downs....but i dont think that i could get into maintenance mode either.
According to Intel, no need to remove the jumper to flash from CD.
Have you tried a USB stick as well?
The E9 code in the lower right corner is the mouse (I think) detection or keyboard, a few codes should appear in succession at boot.
Today I was in a shop looking at an HP notebook which used an IDT audio codec as well. Didn't check the codec type or driver version but the driver UI looked much better than the one I have installed. Maybe it's already the newer driver, I'll install it this weekend and see if at least these work.
Sean-E-Boy, Manel, Pontius: Sorry that i toke your time. Everything went up, after when i returned BIOS settings to default due diagnostics mode (BTW i didn't think that they affected for non-diagnostic mode settings).
Sean-E-Boy:
I meant that it came to me without CMOS battery at all. And i installed one. BTW as i described paragraph upper, it didn't affect on some settings.Quote:
you mentioned earlier that "I've got it without CMOS battery..." does that mean that you do not have a battery at all?
Next step i'll check stability of parts on stock settings at least via utils described in this topic.
dukzcry,
dont worry about our time...if we thought that it was being wasted, we probably wouldnt be here writing posts. the whole goal of this thread is to help people to get this board working, whether that is at default values, or overclocked.
so when you say that "everything went up," do you mean that it is working now?
Sean-E-Boy: Yes, it's fully working. I've installed WinXP x64 to do some tests for first time at stock settings.
ok good!
now you have had your first experience with how this board likes to act if the settings arent "just perfect." expect to encounter similar things as you begin to play with this board.
As Sean put it, and very well I might add, we're here to help. This is no waste of time for anyone here, I believe. We just like to help as much as possible.
Glad you have it working full steam. Keep us posted on your experiments.
You either hate this board's quirks for life or you begin to love it once you understand how it wants things done, I guess.
At first I damned the fricking board as it wouldn't boot with my mem. Both the board and mem cost me a fortune at the time. Took me weeks to have it going, couldn't even flash the latest BIOS as I couldn't even POST (dreaded 3 beeps all the time). Now, it's smooth as silk.
Today I had a few freezes in IE7. Had just installed DivX7 and, after a while Internet Explorer would just freeze and Vista for that matter. Had to hard reset. Uninstalled DivX and so far all is ok again. Anyone had such an issue?
Also, hasn't anyone installed the newer audio drivers yet? I was going to but with this issue haven't yet. Noticed anything different?
Hello everyone...
Has anyone done a crossfire setup? I ask because I am looking at purchasing another ATI RADEON 4870.
Currently I have two 18" montitors (both running off my single 4870). I am wondering if it would be worth getting a second card.
@dukzcry: man I was just happy to be able to help after so many have helped me out :D
Hello again!
Does this board supports *multiple* RAID-configurations, or i need an additional RAID-controller? I mean something like two 500gb drives in raid 1 mirror array and two separate 1tb drives into another raid 1 mirror array? Didn't checked it, but maybe should i turn on onboard devices prompts?
Does the Thermal Throttling belongs only to CPU, or is it a part of Intel SpeedStep technology?
Does C1E state still locked to enabled?
(I was out of PC market for at least 7 years...)
Does anyone have the DX38BT with Q9650?
For processor I have "Unknown Device". Is this normal?
i ran dual 3870's and dual 4870's on my Bone Trail. CrossFire worked great. anything longer than a 4870 will cover up SATA ports on the right side of this motherboard though.Quote:
Originally Posted by soccergeek24