Question...
How how fast has anybody gotten a QX6850 and at what voltage?
Thanks
Printable View
Question...
How how fast has anybody gotten a QX6850 and at what voltage?
Thanks
Hmmm. I think I posted an interim version by mistake. You shouldn't have needed any patches. Sorry.Quote:
Originally Posted by vipertwo
Clark is correct about the mch fan header. It isn't monitored.
in0 = vMCH
in1 = vCORE
It looks like sensors is scaling them incorrectly though.
I'll have to dig out my notes on the temp and fan mappings. I don't have them with me at work so I'll grab them tonight.
Thanks gtj and clark.Quote:
Originally Posted by gtj
gtj did you intend the scaling to be set up in sensors.conf ? ( actually sensors3.conf -- I'm using sensors version 3.0.1 with libsensors version 3.0.1). If so then we would just need to know how to set it correctly.
I haven't touched it so far.
I have now attached fans to the CPU fan header, the "Rear Fan" header and the "Rear Fan 2" header (called Aux in BIOS). Can't get at the front fan header without dismantling the computer so will leave it for now.
The CPU fan shows up in the sensors display as fan1, RearFan2/Aux shows up as fan 2, but the Rear Fan RPM is missing.
The BIOS also shows zero RPM for the rear fan but it's definitely turning. Is this a known problem?
By the way all speeds and voltages are at default - no overclocking or overvolting.Code:$ sensors
asc7621a-i2c-0-2e
Adapter: SMBus I801 adapter at 2000
in0: +1.21 V (min = +0.00 V, max = +3.31 V)
in1: +1.01 V (min = +0.00 V, max = +2.99 V)
in2: +3.24 V (min = +0.00 V, max = +4.36 V)
in3: +4.99 V (min = +0.00 V, max = +6.61 V)
in4: +11.84 V (min = +0.00 V, max = +15.94 V)
fan1: 1753 RPM (min = 0 RPM)
fan2: 906 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -62.0°C (low = -127.0°C, high = +0.0°C) ALARM
(crit = -21.0°C) sensor = diode
temp2: +42.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = thermal diode
temp3: +45.5°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = transistor
temp4: +41.5°C (low = -127.0°C, high = +127.0°C)
(crit = -128.0°C) sensor = Intel PECI
temp5: -62.0°C sensor = Intel PECI
temp6: -85.0°C sensor = Intel PECI
temp7: +96.0°C sensor = Intel PECI
temp8: +118.0°C sensor = Intel PECI
There should be no scaling in sensors.conf. The driver outputs the correct values for voltage, temp and rpm directly. I'll look at the 3.0.1 version and see what it's doing but now that I think about it, they look actually correct for the Bonetrail and a QX9650, especially when idle. I may have been thinking about the XBX2.Quote:
Originally Posted by vipertwo
Are you sure you have the rear fan plugged into the correct header on the MB? There are 2 in that general vicinity. The one behind the audio stack is the MCH fan and isn't monitored or controlled. The one behind the mounting hole next to the audio stack is the rear fan header.
Same thing, CPU voltage is 1.238V with CPU voltage set to 1.400v.Quote:
Originally Posted by gtj
jerry
Load BIOS default, then set vcore to 1.40 again.Quote:
Originally Posted by GJW
Wow,this board is "intresting" to set up to say the least:yepp: .Gun shy to start overclockin:rofl: .
gtj,thanks for memory calculator.
My case is such that I can get close enough to read all the labels on the motherboard so I'm sure about which header is which.Quote:
Originally Posted by gtj
Anyway I investigated a bit more and discovered a curious thing -- I do see an RPM reading for some fans but not others: the RPM sensing seems not to be working for all kinds of fans at low voltage. In particular I have some Noctua fans which are not sensed correctly.
Rear Fan header at 5.55V (CPU idle with case lid off):
Scythe 80mm (DFS802512L from Ninja Mini HS): 1134 RPM
Sharkoon 80mm golf ball: 367 RPM
Noctua NF-R8 80mm: zero RPM reading (but it is spinning)
Rear Fan 2 (Aux): 11.95V
Scythe: 2063 RPM
Sharkoon: 778 RPM
Noctua: 1909 RPM
Has anyone seen this before?
It's not an issue with one particular Noctua fan -- I have several of them and they consistently give an RPM reading with the Aux header but not the Rear Fan header. I won't be changing the Noctua fans though -- they are really nice and quiet :up: .
CPU fan = fan 1, Rearfan2/Aux= fan 2, Rear Fan = fan 4, so I guess the front fan will turn out to be fan 3.
It would be nice to know what all the temp readings are in the sensors output.
Tried it, same thing. I really think that either the board is bad or the bios is messed up and won't let me change it.....Quote:
Originally Posted by bobov
j
After you change the vCORE, completely power off the system by cycling the switch on the power supply or pulling the plug.Quote:
Originally Posted by GJW
Hmmm. The fans all read for me so I'm not sure what's going on.Quote:
Originally Posted by vipertwo
temp1_input = cpu on-die sensor (NOT the core temps)
temp2_input = motherboard (the asc7621a chip itself)
temp3_input = memory (between the 2 sets of dimm sockets)
The rest are assigned by various peci settings but really are not much use. Use the coretemp driver to get the individual core temps.
Wow, after reading the whole thread at once I'm tired... joking!
I was kinda hoping to find a solution to my problem. It's been 3 weeks since I started assembling my rig, with no other than the here discussed BoneTrail. I had really high hopes for this mobo, and I still do, but I'm stuck. Setup is the BoneTrail of course, C2D E8200, 8800GT and the, as far as I can tell, offender - OCZ Platinum 1333 (10666) 2x1Gb dual channel kit.
So far, not even my monitor has even displayed a thing, no boot, no POST, nothing, only the 3 beeps. I know this is a memory issue. the sticks seem to be fine, the shop I got them from tested them with an Asus board and they're ok. OCZ states that these are 777-20 at 1.8V although SPD on them seems to be 777-20 at 1.5V, probably for safe booting. However, for me it seems to be preventing correct boot, maybe insufficient voltage is applied.
Tried only one stick in the first slot, both sticks, no sticks all with the same result - 3 beeps.
Also tried setting the jumper to diagnostic mode without any luck, also removed the jumper with the same outcome.
Can't think of anything else and I was trying to find an answer here but I'm not sure anyone can help.
I guess I need at least one stick of some other mem that can boot so I can gain access to BIOS, since I couldn't even do that, I don't even know what BIOS version I have!!
GTJ, you are the man!! Any thoughts?
I have seen people with a similar setup, Platinums 1333 and working. I guess maybe it's this particular sample that is more voltage sensitive than others or there's a trick to make it work that I've missed.
Mr Steveo, nice to see you back!! I remember a few years back exchanging posts, back in the times of the good old Coppermine and Mushkin PC150 and i815 was king of the hill. Nice to see you back, like you I've been kinda away for a while...
thanks you guys for any help you can provide and sorry for the already long post.
What does that newest bios change?
Can someone post the way to get into watchdog.So it can be turned off.When i put bios config jumper on 2-3 at start up,it either gives 3 beeps or no post.Put it back to 1-2 and boots into windows fine.
Does setting bios config jumper pins to 2-3 set ram voltages to spd while booting into maintenance mod?If so this maybe the issue.
yes, it will boot with default "safe" settings. One way to get it to work is to pull one stick and then boot to maintenance mode. it should boot that way. Basically this is normaly due to the memory vendor not coding stable spd settings onto their stuff.Quote:
Originally Posted by Forsaken1
Unfortunatelly it doesn't work for me.
I've tried diagnostic with either one or two sticks but it's a no go.
Normal mode also with 1, 2 or no sticks is also no good, only 3 beeps.
I don't know what else to do.
I guess SPD on OCZ Platinum is not good for this mobo, maybe voltage is too low but can't enter BIOS to correct that.
I have probably done this 100 times before, but I did it once again. Same result, vCORE is always 1.238 no matter what I do. Has any used Everest and verified that the vCORE does change with a QX6850 and/or a QX9650? I just can't believe that this is a problem with my board, I really think it's a bios problem of some sort. Overall I am pretty disappointed with this board....Quote:
Originally Posted by gtj
jerry
yes, CPU-Z doesn't read Vcore accurately for me either. i have to use Everest or another program to read it. not a big deal - Everest is a must-have anyway.
Thanks Blahung.This board does not play nice with ocz plats.
Manel,keep at it with one stick.It may take several(alot) trys.
Thanks for the temp assignments. I had already tried the coretemp kernel module but the version in Linux kernel 2.6.24 does not recognise the QX9650 CPU. Fortunately support for it has been added to the prerelease version 2.6.25 in the last few days :) !Quote:
Originally Posted by gtj
With a little work I managed to get the new version from 2.6.25 to work in 2.6.24 too. So the sensors output now also shows the 4 core temps:
Code:$ sensors
asc7621a-i2c-1-2e
Adapter: SMBus I801 adapter at 2000
in0: +1.21 V (min = +0.00 V, max = +3.31 V)
in1: +1.01 V (min = +0.00 V, max = +2.99 V)
in2: +3.24 V (min = +0.00 V, max = +4.36 V)
in3: +4.99 V (min = +0.00 V, max = +6.61 V)
in4: +11.84 V (min = +0.00 V, max = +15.94 V)
fan1: 0 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: -55.2°C (low = -127.0°C, high = +0.0°C)
(crit = -21.0°C) sensor = diode
temp2: +47.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = thermal diode
temp3: +45.0°C (low = -127.0°C, high = +127.0°C)
(crit = +65.0°C) sensor = transistor
temp4: +48.0°C (low = -127.0°C, high = +127.0°C)
(crit = -128.0°C) sensor = Intel PECI
temp5: -56.0°C sensor = Intel PECI
temp6: -85.0°C sensor = Intel PECI
temp7: +96.0°C sensor = Intel PECI
temp8: +118.0°C sensor = Intel PECI
coretemp-isa-0000
Adapter: ISA adapter
Core 0: +41.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +37.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0002
Adapter: ISA adapter
Core 2: +45.0°C (high = +76.0°C, crit = +100.0°C)
coretemp-isa-0003
Adapter: ISA adapter
Core 3: +45.0°C (high = +76.0°C, crit = +100.0°C)
You're welcome.Quote:
Originally Posted by Forsaken1
Quote:
Originally Posted by Manel
Quote:
Originally Posted by Manel
This is pretty weird that both of you are having the same type of problem. I saw your threads over at OCZ Forums as well.Quote:
Originally Posted by Forsaken1
While I have the OC3P1800 sticks the SPD is the same as yours: 7-7-7-20 @476MHz and I boot fine but maybe it's because of the extra headroom I have with the 1800s.
The 1 thing I DON'T have is an E8000 series processor which both of you have. Do either of you have a 6000 series processor to try out?
How about a DMM to see if the vDIMM really is at 1.5v? I can point you to the correct place on the MB to check.
Manel: You're running the 1333s and can't boot at all, right?
Forsaken1: You've got the 1600s and have to juggle to get going, right?
Maybe a combination of the Bonetrail and the 8000 processors is causing the MB to not set the correct timings.
gtj,yes i have a fluke 87 meter.Point me to the correct spot to measure voltage.I do have a E6600 in another setup.Last resort to pull it.
Yes,i have to "juggle" memory.Eventually it work.
It's the tab on the voltage regulator in the blue circle...Quote:
Originally Posted by Forsaken1
Hi gtj
Yes, I can't boot at all. it is a coincidence we both having these problems with E8000, but I can't even say which BIOS version I have since I still couldn't boot.
I'm gonna try the suggestion of populating other slots other than the first, maybe it'll work, although intel states that this slot should always be populated.
I don't have a E6000 processor to test, I thought of it, maybe lower FSB would set lower mem freq and it would boot but unfortunatelly I can't find one to test.
Regarding DMM I do have a couple of Flukes laying around somewhere. Do you measure against a ground spot somewhere or between the other 2 VR pins?
Thanks for your help.
I did´nt see that earlier, changelog of bios 1478:
New Fixes/Features:
- Fixed issue where Intel Desktop Control Center failed to start
with certain processor.
- Updated processor support.
- Fixed language switching and 'Exit discard Changes' could slow
down the responsiveness of BIOS setup page.
- Fixed issue where optical drive and hard drive is not booted in
the order according to Boot Order.
- Added ability to underclock production non-XE processor
multipliers.
- Fixed issue on getting the Max Ratio of the CPU.
- Fixed issue where L2 cache size will not be displayed in BIOS
setup.
- Fixed POST code 5Ah hang with SATA HDDs and PCI Graphics card
in Slot 2.
- Added a workaround of option ROM which has an invalid PCI
Expansion ROM Header.
- Hid AHCI option ROM text when not running in RAID mode.
- Fixed issue causing Watchdog Timer firing to not be detected.
- Fixed blue screen during Vista* UEFI installation.
- Fixed issue where graphics cards that don't support 800x600
mode will not display anything on screen during POST.
- Added PCIe Link Width information for all PCIe Slot in Video
Configuration Setup page.
- Added support for booting El-Torito HDD emulation Memtest86+
with AHCI Option ROM.
- Fixed hard drive detection after cold reboot in AHCI mode.
BTW is here still way to disaple C1E from bios in newest bios? I haven't yet tested that 1478 bios
From everest it's possible...
Definitely try each stick by itself in all 4 slots to see if you can at least get to the BIOS.Quote:
Originally Posted by Manel
The measurement is between the tab in the picture and any good ground.
Be careful with 1478. Others are reporting issues with sleep and hibernate.Quote:
Originally Posted by BulldogPO
Nope.Quote:
Originally Posted by s0lid
Measured ram volts.Bios set at 1.9v,meter is reading 2.0v.:shrug:
Thanks for location to measure gtj.
I'm getting pretty pi#$ed off now, tried all slots with either stick and it's still a no go. No normal boot, no diagnostic, nothing...
One thing happened a couple of times though - several times, in slots other than the first, the board wouldn't beep at all but wouldn't boot as well, power was on, board was powered, fans would rotate but no display as well. But only sometimes this happened, next boot would go 3 beeps again.
I really don't know what else to do.
I guess next step is find that Fluke.
Any thoughts?!
I'm wondering if you don't just have a bad board.Quote:
Originally Posted by Manel
Have you swapped out video cards and PSU's ? Just a thought.Quote:
Originally Posted by Manel
i'm starting to wonder if Intel had some quality control issues with their first release. i sent my RMA out a little while ago and am expecting my replacement to arrive soon. i have high hopes for the new one.
No problem, it was close enough for me to get it working -- perhaps you could update the code at http://www.peakin.com/x38/asc76xx.zip for other people.Quote:
Originally Posted by gtj
Will you soon be submitting your asc76xx kernel module for inclusion in the Linux kernel? Thanks again.
Here is where I am on my lack of ability to change core voltage.
I tried the last three bios versions that support a QX9650, 1358, 1397 and 1478. This is actually all the bios's that support a QX9650. Based on Everest no matter what you change the CPU voltage to, there is no effect on CPU voltage. However if I use the 300mV offset (I know this is bad but max CPU temp was 145F during 2 minutes of 100% load so I don't think I'm in the danger zone) Everest shows the CPU voltage going to 1.48 volts (it seems to read about .05 volts low based on what I have observed). So if it's running stock voltage of 1.238, add .300 volts you get 1.538, allow for Everest error, and it's accurate. While I can certainly live with this voltage based on the core temp, I'd really like more ability to change the voltage other than +.300 volts.
I have turned it on and off, cleared CMOS, tried just about every combination I can think of to see if it works and every time the changes I made to CPU voltage don't happen, based on Everest. At this point I really don't know what else to do. I have not tried putting the QX6850 back in and trying the various bios's and what not, but I'm not optimistic. There is one older version I can run with a QX6850 for testing purposes to see if that has any impact, 1308.
If I knew for sure this was a board problem, I'd buy another board in a heartbeat, but I just don't know for sure....I'm open for anymore thoughts.
jerry
Quote:
Originally Posted by GJW
Seeing similar results with a QX6850. I can set the voltage to 1.4V for example in the BIOS, and it shows the change. However, Everest only shows the default 1.35V. Severely putting a damper on my overclocking efforts. BIOS 1307. I've got the FSB at 375 with my memory now running at 1500MHz stable, however, I can't get the multiplier past 8 (3GHz).
Don't take this the wrong way, but I'm glad you are having the problem. That means I'm not going crazy and validates my issues with at least one other person. I also had a QX6850 in this board with the same results. I really feel there is a bios problem with this board with respect to these CPU's. I did try to pass this information to Intel but the didn't want to hear anything about it.Quote:
Originally Posted by clark_carty
j
so nice to know Intel is having trouble writing a BIOS for... Intel chips. very reassuring.
A few more things. What is the rest of your hardware? I am really hoping that Intel just hasn't messed up that much and that there may be something we have in common in our setups that is interacting and causing this. What brand of memory, video card, etc. If we have something in common that we may think may be interacting and causing lack of core voltage control, I'll get some other hardware and try it and let you know.Quote:
Originally Posted by clark_carty
Second, I have found that much over about 360 on the bus speed and it gets unstable. I used 360 and 10 on the QX6850 and the QX9650, with stock core voltage, with pretty decent sucess and stability. If I went much over about 365 on the bus speed it would be unstable. I also found a mention of this on a pretty detailed review of the board from several months back. You were probably shooting for 1500 MHz FSB. Try 360 and 10 and see what happens. Not that it's a huge improvement, but it's something to try.
jerry
Hi again
Been away for a couple of days.
Bad board is an option, but I wanted to be sure. Haven't swaped any hw yet since I have no other spares to.
I'm about to buy a stick Kingston Value RAM which was tested with the board by Kingston (funny how Intel directed me to their mem support page for mem sticks compatibility but there are is no mem tested with this board) and it's rated at 1.5V, if this does not boot then it will be the board.
Another option is to take it all to the shop and have them test it with other sticks which I believe I'll try first.
By the way, the Fluke measured 1.539V in the spot you mentioned Jerry, thanks. I believe we can rule out supply to mem problem, it's even a bit higher than the 1.5V it should be.
Hi again
Been away for a couple of days.
Bad board is an option, but I wanted to be sure. Haven't swaped any hw yet since I have no other spares to.
I'm about to buy a stick Kingston Value RAM which was tested with the board by Kingston (funny how Intel directed me to their mem support page for mem sticks compatibility but there are is no mem tested with this board) and it's rated at 1.5V, if this does not boot then it will be the board.
Another option is to take it all to the shop and have them test it with other sticks which I believe I'll try first.
By the way, the Fluke measured 1.539V in the spot you mentioned Jerry, thanks. I believe we can rule out supply to mem problem, it's even a bit higher than the 1.5V it should be.
New BIOS 1500 out. Check the downloads page.
Left mobo to test, did anyone test this 1500 yet? S3 problem solved?
I asked Intel regarding the S3 issue, they said they didn't know about it, but would check.
I see they read their bug reports! I filed a bug on it over a week ago!Quote:
Originally Posted by Manel
I'll try it tonight when I get home.
Still no word about disabling C1E :F
Does anyone know where the Motherboard temperature sensor is? I'm measuring about 45c with everest and was wondering if that's to high. All other temps are very low as it is a watercoooled system, also I have the fan installed on the NB.
For some reason I always thought the Motherboard temp in everest Was the NB, is this true..
It's between the cpu socket and the leftmost dimm socket. The 3rd temp reading in everest is between the dimm sockets. What does it read compared to the motherboard?Quote:
Originally Posted by rchelicopter
don't ever let anyone tell you Intel has a bad return policy. they received my bad motherboard two days ago and shipped a replacement 24 hours later. nice quick turnaround.
I think Jerry is correct regarding the sensors positions, however, both MCH and ICH are supposed to have thermal sensors too I believe.
I think it may be a limitation of the monitoring chip aSC7621, it measures 2 remote diodes, it's own internal diode as well as a PECI, which I'm not sure if it's used for the processor digital thermometer or if the processor uses one of the remote sensor inputs. If it doesn't use the PECI, which I think it doesn't, this is not in favour of Intel since the digital is more accurate, although more difficult to handle I think. This is a rather old and limited chip.
My mobo is being tested at the moment, they'll let me know (soon I hope) if it'll be RMAed or if it hasno problem at all, and it's somewhere else.
A couple of days ago it stopped the 3 beeps (mem related), it would just power the fans but still no boot, without the sticks it still beeps. I'm not sure of anything anymore. I'm wondering if my vid card is ok? Can anyone confirm if this mobo during normal boot beeps once, like most do, when everything is ok? Is there any sound during normal boot?
Also, does anyone know what revisions of the board there are, and what differences between them? Mine is 503 but I believe I saw somewhere there is a 505, am I wrong?
BIOS 1500:
S3 Standby Mode Still Busted with Vista 32bit - Upon powering up, the machine hangs, then needs to be power cycled. After power cycling the machine resumes from Hibernate mode, so it never entered S3 mode to begin with.
Still no core voltage override sticking on the QX6850.
USB Keyboard at Startup - Issued fixed.
Hey Clark
Intel is really at it, they just released BIOS 1507, it seems to fix the S3 Vista issue, if it was related to RAID that is. Did you have RAID enabled in your system when S3 fails?
Let us know if it's fixed.
wow, these guys left me a good impression now, they seem to be working hard to fix all issues.
Soon enough this will be a hell of a board, can't wait to get mine back.
Found this from 1507 bios change log:
Updated X48 MRC timing table values.
So they have "accidentaly" proofed the X48 Bonetrail :D
But here is the whole list:
- Added option for memory command rate.
- Updated X48 MRC timing table values.
- Updated BIOS Setup to detect the supported XMP profile speed.
- Fixed long boot time due to no media in SATA optical drive when
set to AHCI/RAID mode.
- Fixed issue where Aggressive Link Power Management could not be
enabled on the ICH SATA AHCI controller.
- Fixed RAID Fail to Resume from Standby (S3).
- Fixed Windows* Vista 0xC4 BSOD when running Driver Verifier on
TPM.SYS.
- Fixed time-out failures with Extended INT 13 Seek Function (INT
13 Function 47).
- Fixed issue where certain SAS HBA card was not booting.
- Fixed issue where certain USB hard drive did not work in USB
legacy support.
- Fixed IDCC2 on handling automatic mode for PCIe values.
- Fixed IDCC2 to reset the last known good values upon WDT reset
from OS.
- Fixed the title of the BIOS setup page get overlap by certain
condition.
Yes, I had RAID enabled. Will give it a try today.Quote:
Originally Posted by Manel
UPDATE:
S3 Standby Fixed
Voltage change to QX6850, still not fixed.
New bug - All temps, voltages, and fans speeds busted in the latest IDCC 4.0.0.11 beta. Bugged this.
UPDATE UPDATE:
Opened IDCC again and they all show up now!
Yes,IDCC works sometimes and other times not.Thats was 1478 and 4.0.0.11.My boards out for rma:( .
Need to have tRFC setting in bios for ram timings and other options,as of now it does not.Everyone subimit this to intel:up: .The options in bios are so limited on this board.Makes me appreciate DFI.There is nothing extreme about this board:) .
Mailed my board to intel on wed,they shipped a "new" one out friday.Will arrive tues.Great rma process.
Interesting. My Bad Axe 2 has had S3 standby problems since day 1. There was one BIOS revision where they greatly improved the probability of success for resuming from standby, but it was still 25%-50% miss.Quote:
Originally Posted by clark_carty
Seems like the problem is more systemic than I had thought.
Cool, clark, finally the S3 issue is fixed. As soon as my board is back this will be the first thing to update.
IDCC is also good news. And hw monitor in BIOS, finally all the info there, right?
forsaken1, one other thing missing regarding timings, tRD. At least command rate is already there, hope all other missing will get there eventually.
When D48BT2 is out we'll have all a brand new X48 board, at least the BIOS is going that route, with XMP and all... it's the same MCH anyway, just better bin.
Well I agree that the new bios does not address the ability to control the core voltage that I am experienceing. I could even be convinced that it may be a little more unstable than the previous versions. Using the same settings I've had the machine re-boot a few times.
There are some more controls in the bios, but at this point I'm not sure what they are and I don't want to start changing them yet to see what happens. I am really getting tired of this board and it's problems....
jerry
hey their guys i am new to these forums. This is my first build, i recently won a DX38BT at a lanfest from a raffle so since it was free i decided to build up my own computer. As of right now i have a E6750 CPU, 9600Gt Graphics card, and the DDR3 Corsair 1333 Ram 2gb, and a 160gb Western Digital Sata drive.
I was having problems at first with installing windows because of the CD/DVD rom was not a sata drive. I purchased a sata drive and it was found in the bios and was able to boot the cd. But thats when i faced another problem in the beginning of the install of windows when it is installing devices with the little green bar on the left as soon as it gets about half way it happens to BSOD on me.
I did do some research on it and tried many different things such as changed the memory voltage and timing and so on. I also tried the corsair timing and volt they tell you to use but also didnt work. Tried one stick of ram each time and changed the slots the ram was in but still BSOD. I put the bios on default settings and it also BSOD.
So basically i need some help here, i noticed most of you have the quad where as i have a dual core. Is anyone running their bone trail with a E6750? Any tips or things that someone could think of for me to try would be great and greatly appreciated.:)
Ok this is my great luck once again my bt got broke whitout any reason.
At boot it just draws "_" up corner of screen and stops there. Debug mode doesn't work and either bios recovery mode.
Well now i've removed bios battery and atx connector.
who knows? i think the first revision had some quality control issues or something. i returned mine and my replacement arrives tomorrow. fingers crossed for better luck this time around. if i hadn't already bought this expensive DDR3 memory, i'd just stick with my old 975X Asus, which has been nothing but wonderful since i bought it a year and a half ago.Quote:
Originally Posted by mindoftw
Phef it wake up =)
Hey if somebody has vmods for this board could u submit them to link below?
http://www.xtremesystems.org/forums/...d.php?t=179080
vMCH and vFSB needed for upcoming dice runs!
What version of windows are you installing?Quote:
Originally Posted by mindoftw
It happened to me the first time, i was trying to install windows XP SP1, after that i change the cd and installed Windows XP SP2, i think the mobo has some issues with the original drivers of windows, give it a try and let me know.
It was a pretty old CD the only one i could find so im pretty sure that it was SP 1 Cd, i am going to try vista and see if that works. I also have SP2 XP so i will be trying that to just to see if it is infact SP1 that is causing this problem.
Does your machine cycle on and off when you boot it after it's been sitting for a bit, or during some bios changes? I finally got through to someone at Intel with some intelligence and he's working with me on this. I don't want to say what he has told me yet since it's not verified, but this could be related to not being able to change core voltage.Quote:
Originally Posted by clark_carty
jerry
xMrBunglex
How can you tell which are the first revisions? I have 503 i believe, what other revisions are there?
My mobo seems to be working, tomorrow I should have it back, still being tested. However, my vid card seems to have gone dead, never was alive that is. It spins the fan (8800GT) but no video output. All being tested at the moment.
S0lid
Those pics are of the aSC7621A, which is the hardware monitor chip.
The ADP3189 is the 5 phase voltage regulator for the core supply.
Mine does with the E6850. After power's been removed from the board the following sequence is required to get the board to boot completely...Quote:
Originally Posted by GJW
Restore power
Press power button
Board spins up for a second, then powers down for a 3 seconds.
Board power back up on its own but there's no video.
I hold the power button for 5 seconds to soft power down.
I press the power button to power back up
Board boots completely.
Manel
Looks like u know these things pretty well, if u know could u tell me which are mch and vfsb regulators?
And thx already from your valuable info :)
From Intel "The behavior you describe is normal for a system that has our "management engine" running. The trouble is that the engine is supposed to be disabled on the DX38BT.Quote:
Originally Posted by gtj
I'll see if I can find out if there are any circumstances where we would expect this to happen."
I did respond back and asked him if my lack of voltage control could be related to this. I'll probably hear back in the next day or two.
j
hey guys i just wanted to let you know that it was in fact the SP1 CD that caused the problem for my BSOD. I got the vista CD today installed it and my computer has been running smoothly every since.:up:
Hey guys can someone tell me if it is normal for the red cpu led on the motherboard to flash when powering on:shrug: .
i got my BT back today and will probably rebuild tomorrow. two questions before i get started:
are there any aftermarket NB and SB heatsinks that are compatible with this board yet that don't require any modifications or mickey mousing?
what do you guys have the PCI-E set at when you overclock? do you do auto or force it to 102 MHz (or whatever the value is - i remember it wasn't exactly 100).
Cool.Quote:
Originally Posted by GJW
If it just flashes once quickly, then it's OK.Quote:
Originally Posted by FX4BAJA
Nothing that I know of for the NB. The SB is the standard ICH loop retention mechanism.Quote:
Originally Posted by xMrBunglex
I've never touched the pci-e settings on any motherboard I've overclocked. It just adds too many variables for little or no gain.
so you leave it at Auto or set it to ~102 MHz? i think it overclocks itself automatically based on the FSB if you leave it on Auto, doesn't it?Quote:
Originally Posted by gtj
Well, yes and no. What I have done is use the Danger Den 975 water block. You don't have modify anything, but I got some 6/32 stainless coupling nuts and attached them to the "studs" that stick out from the board. After that I just put the block on and used the threaded rod (threaded into the coupling nuts), springs, washers and what not to attach it. It attaches this way without any mods or anything like that.Quote:
Originally Posted by xMrBunglex
It's worked for me and looks and attaches pretty well.
j
Thanks,yes just a quick fash of the led than a double boot with another quick flash.I could use some more help im a newbie to overclocking ive only used mATX boards in the past so this is my first motherboard to give me that option.I have it runing now with the q6600 cooled using a Tuniq Tower heatsink and 2GB of OCZ DDR3 PC3-10666 1333 MHz ReaperX.Ill list my Bios's settings as of now if you could look over them and see if it looks ok are not any suggestion's are welcome.Quote:
Originally Posted by gtj
Performance tab in Bio's
Processor overrides
CPU Voltage Override <Default>
CPU Voltage Offset <Disabled>
Enhanced Powerslope <Enabled>
Front Side Bus Voltage Override <1.200>
MCH/ICH Voltage Override <1.250>
Processor Multipier Override <Automatic>
Host Clock Frequency Override <Manual>
Processor Multiplier 9
xHost Clock Frequency(MHz)[334]
--------------------------------------------
Processor Speed 3.00GHz
Current Processor Voltage<1.3250v>
MemoryConfiguration
Memory Correction <Non ECC>
Performance Memory Profiles <Manual-User Defined>
Reference Frequency <266 MHz>
Memory Frequency <800 MHz>
tCL <6>
tRCD <5>
tRP <5>
tRASMIN <18>
Memory Channel A:
Slot 0: 1024MB SPD:6-5-5-20
Memory Channel B:
Slot 0: 1024MB SPD:6-5-5-20
BUS Overrides
---------------------------------------
PCI Express Burn In Mode <Default>
PCI Configuation
--------------------------
PCI Bus Frequency 33.33 MHz
PCI Lattency Timer<32>
HPET <Disabled>
Main Tab
Overridden Processor Speed 3.00GHz
System Bus Speed 1066 MHz
System Bus Frequency override 1336MHz
System Memory Speed 1066 MHz
System Memory Speed Override 1004MHz
Also im using the second PCI Express slot for my video card is there any performance loss do to that.
Thanks
http://img248.imageshack.us/img248/985/85420621qt1.jpg
Guys
Was at the shop today testing the rig and finally it boots. it was really the mem which was preventing boot. Used a stick of Asus DDR3 1333 (didn't know they make them, rebranded?!) to boot, set mem voltage to 1.82V, put in my mem and that was it, boot away.
Unfortunatelly, the board came with a rather old BIOS 1251, and at the time i had no way to flash to the latest 1507, so now I have a problem if I try to flash, I might have to go back to the shop which I wanted to avoid.
Anyway, mem support might be better in 1507 so maybe no need.
Tomorrow I'll install Vista ans see how it goes.
I'm finally getting happier with all this.
However, please check if this happens to anyone:
When booting, a couple of seconds blank screen, then SATA AHCI BIOS loading, then Intel splash screen, then Intel Boot Agent GE and PXE which ends up in failure because I have no boot device I think.
The strangest hing is that during the splash screen and also a bit after it's gone, in the lower right corner, the characters cycle between EB and 94 and 0, does it happen to anyone else?
Should I set SATA configured as AHCI or RAID? I believe it should be RAID otherwise you will not be able to set it to RAID again once you install Vista, unless you do a full re-install. However I'm not using RAID at the moment, maybe never will, don't know. In RAID the detected drives are not shown for each individual port in BIOS-Drive Configuration, only in AHCI.
In memory reference frequency, we're talking boot strap here, right? What's the behaviour of thisboard regarding that? What have you guys set?
Does anyone know if there will be (or there is) UEFI for this board, instead of dying old BIOS? I'd love to replace this old bugger...
This BIOS is really slugish and has lots of quircks, maybe newer versions are better?
s0lid
Sorry, don't know which are the right ones but I'll dig into it.
New board arrived today.Not much luck at all with the ocz3p16002gk plats.Appears from Manel history and mine this motherboard does not play nice with ocz plats.Hope the guys at ocz can help me out.Maybe a new spd dump?
"The strangest hing is that during the splash screen and also a bit after it's gone, in the lower right corner, the characters cycle between EB and 94 and 0, does it happen to anyone else?"
Yes,it happens to me.94 is usb keyboard.
"This BIOS is really slugish and has lots of quircks, maybe newer versions are better?"
Not much better,but a little bit.Comparing 1251 and 1478.
With 266/800, you're not really using the bandwidth your memory can provide. Try 266/1600 or 333/1333. With a 334 FSB that'll put the memory right at its rated DDR-1333.Quote:
Originally Posted by FX4BAJA
The rest of the settings look good.
Shouldn't have any issues with the second pci-e slot. They're both rated x16.
Oh yeah...:welcome:
Thanks gtj,the 266/800 is the only one that will boot up to Windows i get a black screen using either 266/1600 or 333/1333 and have to move my jumper to be able to get back to Bio's to change it back to 266/800:shrug:Any thought's on that.Quote:
Originally Posted by gtj
Thanks Again.
got my BT back and set up today. i kept rebooting for no apparent reason, but a quick bump of the Vmem one notch over the SPD settings and i'm stable so far. 45 minutes of Orthos and counting.
my only problem now is the same problem i've had since i got my E8400 CPU. my old Asus motherboard did the same thing and now my BT is as well. i can either set my Vcore to Auto or 1.28 and up. it won't let me manually set it below 1.28. is anyone else having this problem?
it's alive!!! and the onboard sound on this motherboard is better than my SoundBlaster Audigy 2ZS :clap:. i finally get to set that stupid sound card on fire :D
Forsaken1
Guess that's normal then, I find it odd that it will appear that way on screen, never had a mobo that did this. Do you know what the other might be? Is it sort of hardware detection? USB mouse was not connected.
There really is an issue with the Plats I guess. I can see things didn't improve with newer BIOS versions, which is disappointing, everytime I flash the BIOS I'll have to borrow another stick, I guess I'll have to buy one.
xMrBunglex
Sweet, I was wondering what the sound would be like, I hoped it was good, by the specs. Haven't tried yet.
Just an FYI update on the 1507 bios. In my experience, the same sleep issues occur as in any bios past 1478. Unusual USB issues, bios does not report the memory and CPU speed correctly, EIST does not disable, etc. Same old issues.
I sure that Vista probably has it's hand in here somewhere as well. Except for the gaming performance, I miss my Badaxe and XP :(
I totally understand that. I actually have an Asus Maximus Extreme that I will install at some point unless I can get the issues fixed with this board. I'll build a Skulltrail as soon as I can find all the parts and go from there. I still use XP, but will probably migrate to Vista before too long.Quote:
Originally Posted by Randy
j
Was difficult with e8400.Installed e6600 and things went "fairly" smooth.Yes,manel it is hardware detection.The reason i know 94 is it would hang there often and contacted intel for info,sorry dont recall the other codes.Quote:
Originally Posted by Manel
The boards working methods are odd to me,not like most motherboards.Maintenance mod is a pita.Manel,before i flash bios i install 1 stick of ram,set timings loose 7-7-7-24 1066 and voltage normal 1.86v.Then after bios update enter maintenance mod(jumper pin 2-3) and re set ram settings.Will try with 2 sticks next time.
The more time i spend with the board the more i am beginning to understand what it wants.Just need some more time.It's a odd board for sure.The onboard sound is some of the best i have heard.
Hi Forsaken1
I guess it's also a matter of luck, with the specific samples of the mobo and sticks, it can all go well or it can be hell.
I guess with time, one starts to get to know the board and even like it a lot, I hope so at least. As the BIOS matures things will be better I hope...
Speaking of BIOS, anyone knows when, more like if that is, there will be a version of UEFI for this board to replace the BIOS? Intel is so believer in this step forward but when it come to boards with it it will not be the first one out. At least in the desktop market, server and workstation boards already have it as far as I know. MSI has a sample working and will be the first out. Thinking that Intel first started this, and released it to open source and now doesn't have it out yet seems strange. Support from Intel, as usual, does not comment on unannounced products.
Regarding flashing, when you set looser timings before and higher voltage, after you flash can you still boot? I'm asking because I believe, after you flash a new BIOS, you will probably loose those settings you made and the board will default back to SPD timings and 1.5V or not? Can you please confirm if at least the voltage remains at the value you set before flashing, like 1.82V or will it go back to 1.5V default value. If it remains at the 1.82V I'll flash right away, otherwise only when I have another stick at hand.
Jerry
Does Santa come to you everyday? Man, you get all the good hardware coming out.
Randy
You still have issues with S3 with 1507? Maybe you have to reinstall Vista, maybe power management went south with the older BIOS and now you need a fresh install to fix it - just a thought.
Does anyone have any info on SLI for this board, or X38 for that matter? I believe some time ago there was someone hacking nVidia drivers to run SLI on intel chipsets. I don't think there is any hardware issue here, contrary to what nVidia would like us to believe, it must be enabled in the drivers only.
Maybe Intel will force them to allow SLI, now that they need the license for new chipsets. What if nvidia really buys AMD? No more Intel chipsets for them.
great job describing what it's like to own a BT. it's an oddball that just takes some time to get used to - and the sound quality is excellent.Quote:
Originally Posted by Forsaken1
i have mine 10+ hours Orthos stable at 400 FSB and want to put up my volts and settings in a bit to see if anyone wants to help me trim some volts to cool things down a bit. i'm not joking when i say i'm sick and tired of Maintenance Mode and don't feel like ever moving jumpers around again.
PS Manel, SLI is available on the Skull Trail but not the Bone Trail. i don't think those hacked drivers will ever be the way to go.
Put the e8400,alls well.
Regarding flashing, when you set looser timings before and higher voltage, after you flash can you still boot?
Yes.Turn off watchdog first.If for some reason it will not reboot.Power off.Set pin to 2-3 and power up.Enter maintenance mod.Adjust/save and when windows boots it says update succesful.
I'm asking because I believe, after you flash a new BIOS, you will probably loose those settings you made and the board will default back to SPD timings and 1.5V or not?
Just flashed from 1507 to1507 to check manel.It held all ram settings.
Yes,xMrBunglex.Was looking for a challange and this board is intresting from that standpoint.Let us know when you hit 450+fsb.
i just flashed the other day and it held my RAM settings. and i had 450 FSB going earlier, but that was on an older BIOS that wouldn't let me set the command rate. after a successful run of Memtest and an evaluation of my volts, i'm gonna go for 450 FSB and probably stop there. i assume i'll have to raise the boot strap to go to 450 FSB? right now i'm at 333/1333 and will probably have to go to 400/1600?Quote:
Originally Posted by Forsaken1
Hmmm anyone has friends or etc at intel?
Bios with working EIST disablation would just be perfect!
Well capablity to increase vMCH and vFSB over 1.5v from bios would sound good at dice/ln2 sessions.
Forsaken1
Cool to know about 8400, I guess I should have gone to that one too, those babies easilly hit 4+GHz, let's see what the 8200 can do.
Will try flashing to 1507, I really hope the RAM settings will be kept so I can boot normally.
How do you turn watchdog off, only in Maintenance mode right? So, the procedure would be go to Maint mode 8pins 2-3), turn off Watchdog, power down, go to normal mode (pins 1-2), boot, flash, reboot and enjoy? If can't boot after flash go to Maint again, change and save, go to Normal and all should be well?
Thnx for the tips
Yes,this 8400 runs well.Will see what the bonetrail can do.500fsb max in bios:( .
http://www.xtremesystems.org/forums/...&postcount=425
Yes,manel.That process worked for me.Good luck.
EDIT Did not notice this in prior bios,1507 has:
GTL REF
MCH DAR REF
DIM CHA A&B REF
Nicee, must flash that bios when i get home at sunday :DQuote:
Originally Posted by Forsaken1
To cold to go to work.I played a little bit with the board.Once i understood(still learning)what it likes,not to many issues.Majority of clocking was done using intel idcc.Works well as long as it's the only program running.The voltages and other settings are not tweaked.Will work on that.All GTL set at auto.E8400,bonetrail,ocz3p16002gk,water cooled and 68F ambient.
Need a new bios with 500fsb max lifted:D .
http://i126.photobucket.com/albums/p...s/ebab592e.jpg
wow, that's impressive. is your north bridge water cooled? i just noticed your vMCH is lower than mine and i'm only running 400 FSB right now, which means i can lower mine. what's your vFSB at?
Forsaken1
Thanks, I just hope it works well also between different BIOS versions, since you tried going from 1507 to 1507 as well. The settings are exactly the same. Between different versions there might be new parameters in new BIOS versions and the programmed settings may not remain.
Well, I guess I'll have to try to find out.
What are those values you mentioned, those REFs? Are those voltages? What's MCH DAR?
MrBunglex,cpu on water and videocard only.Have several 80mm fans over ram,nb and voltage reg area. My notes say vfsb is set at 1.4v.Idcc says 1.425v in ss above.Note,i just tossed alot of volts at it.Should be able to tweak lower.
Manel,flashing from 1251 to 1507 if i remember did not save anything.May want to wait.Heres a good read on gtl's:
http://www.thetechrepository.com/showthread.php?t=87
With a dual core here are the GTL options and default settings.Bios 1507.
CPU GTL REF0 61
CPU GTL REF1 61
MCH GTL REF 67
MCH DDR REF 50
DIMM CH A DQ REF 50
DIMM CH A CA REF 50
DIMM CH B DQ REF 50
DIMM CH B CA REF 50
So, you think I might loose the ability to boot again if I flash?
No way, not going that route again, I'll wait till I get some mem that can boot again.
Thanks on REFs, Asus boards also have the option to adjust if i recall correctly.
What are you using for WC system ?
Quote:
Originally Posted by Forsaken1
Yes,i think the chances are greater then not,it will not save prior settings after bios flash.1251 bios is buggy.I under stand your pain on waiting for ram:yepp: .Your welcome on ref's.Quote:
Originally Posted by Manel
Randy,at this momenent i have two seperate loops for water cooling on this setup.Mounted on bench,no case here.
As a question to toss out there, in Everest there is a Voltage value of +2.5V. Mine reads 1.32V. What do other peoples read? In the Bios when you look at voltages it doesn't show a 2.5V value, only 3.3, 5.0 and 12.0.
Intel is going to RMA my board but I am curious about this voltage value....
jerry