Printable View
it's a pain but strip it down to the cpu, single stick and stock cpu cooler - don't even bother with the GFX card!!
check to see if anything happened to the board when you were installing the water cooling
I take it you have blanked the BIOS for say 60 secs or so?
I've got it stripped to 1 stick of RAM, and the RAID card isn't in. When I get home I'm going to try pulling the CMOS battery for a few minutes and reseat the CPU. I'll try with no vid card too.
The water loop was already filled, nothing out of the ordinary hooking things up. The case is a U2-UFO so I had plenty of room to mount things without tearing apart the loop. I'm using a scythe backplate for mounting the Fuzion so I don't bend the mobo.
Man, something is definitely wrong with bios 12.09
Just changed my VGA card to a 8800 GT (I'll do some Vmods to my G80 GTS) and the mobo just went crazy. Didn't boot, restarted itself a few times, then let me into bios, loaded my settings and it went down again, showing 75 or 8E or whatever it felt like, argh.
Made a few CMOS clears, got into bios again and bootet with bios defaults, just enabled raid. I raised the FSB in windows via guru and now I'm at 333x9 running stable :D
However I'm afraid of rebooting.. oO
do you have a rpm sensing fan attached to the CPU fan header?Quote:
Originally Posted by AMDfreak
No, but I didn't need one on the first board. I'll give that a try too though.
Strange to see all the problem u guys got. I myself didn't encounter any single problem since I started to use this board from the first time, except the errornous "Load OC Profile" in BIOS . I think may be it's just because I only do a mild OC on this board so far...
Anyhow, I just also flashed my BIOS to version 12 final that I downloaded from abit site. It's still showing 12.B09 in BIOS screen, but so far still no issue, no double boot at all. Hope it stays this way forever. I'm using an 8800GT too with Q6600.
IMHO, this board's BIOS only has problems with Penryn. May be because it's a new technology, so they haven't implemented it well.
Btw, I just get good news today from abit representative in my country, that they have just received the missing retention clips from abit Taiwan, and they're sending it to me now. My long wait is finally over. :D
the only reason that i mention it is because my IP35 Pro board, for the first time, had a siren screaming at me with no fan attached to the CPU fan header...that was a first for me with this board...i had not used that fan header except in the first days that i bought this board about 5-6 months ago...it didn't shut down but it certinly let me know there wasn't something right!:)Quote:
Originally Posted by AMDfreak
I have had two set of OCZ PC2-8000 Titanium Alpha VX2 modules to play with, and this board only kicks out a C1 error when they are installed....
My G.Skill PC2-8000 HZ chips run OK...
Tried single modules in each slot and presetting the timings/voltages using my G.Skills but nowt works...
Anyones else had issues with the OCZ VX2 RAM and this board? Or is it just my dumb luck? :p:
Yeah there is something wrong with 9 or "final". the whole double boot crap will drive you crazy if you OC and I basically gave up trying to use the bios all together. back to 8.
btw I haven't had a fan hooked up to the cpu fan plug since I bought the board and i've had no issues.
lets see what i've seen wrong with this board is:
1 unplug power cable it will 90% of the time reset OC
2 Uguru for some stupid reason resets itself also.
Why not have a Profile saving system It gets really old having to set up uguru over and over.
3. uguru shows vcore higher then bios setting
4. OC on the fly feature in bios Locks up even with a setup thats 10 hours + stable.
5. IF you have a IDE cd drive hooked up, you have to hit a button or it sits for a few seconds during boot up.
6. Whats the point of having all these deviders when ddr2 doesn't go to 2000mhz :ROTF:
:lol: i got my 1st C1 errors with this board on flashing, My second came not long after on rebooting.:shrug:Quote:
jcool
However I'm afraid of rebooting.. oO
You seem to need to treat the board a little rough & pull the battery out when it misbehaves. I'm not convinced that it's a bios issue, i think that the board seems to be liable to DMAi corruption, pulling the battery seems to be the most effective way to clear it & force DMA rebuild.
Since using 12.09/official i've had a couple of occasions where I've had a 50h post code error , which is usb. I've had to pull usb pen drive. Now I've not had that up till now??? spooky.
luck:)
Flashed the official bios today. Also having alot of trouble with booting. Getting error 38 then it´s just shutting down. After that i have to remove powercable and then on again. Maybe will flash back to b08 or something, but i want a bios that likes 45nm cpus :)
from what i've seen that ain't 12 then Official Bios 12 (beta 09) is the worst ever! well from a 45nm perspective certainly.Quote:
but i want a bios that likes 45nm cpus
I've resigned myself to the fact that I need yet another RMA. :(
Pulled all connections other than power using the new PSU, and OMG it posted! I figure ok, cool, maybe I had a pin off on a usb header or something. I hook up the "old" PSU, power on and get infinite 90 to 99 loop again. DOH! I pulled the battery, got some dinner, put the battery back in, same problem. Hooked the new PSU back up, OMG it posted! So, I'm wondering if it's a bad BIOS or the old PSU at this point. I had my DOS usb stick at the ready and flashed to b09. Flash ended at C1, but it did post again. I set things up in a default config, save and exit BIOS, and it again goes into the 90 to 99 loop. AAARRRGGGHHHH!
I'm going to see if Newegg will take pity on me and let me get a different board.
@amdfreak
what psu do you use for the test?
i use fsp 1000w and have the 90 but can recover by take out the psu supply cable to mobo,never try with other psu though :)
PCP&C Silencer 750. I'm done with this board, and possibly done with Abit. There is no reason anyone should have these kinds of problems. If I have to get another IX38, I may just sell it and get an Asus.
Quote:
Originally Posted by AMDfreak
Sorry to here about all your troubles with the IX38, but you may not escape these issues by jumpin to Asus. In fact I had as many problems as your experiencing, only with the Asus Maximus Formula SE, went through a pair of them before I jumped to Abit.
Zero issues on my IX38 so far and running Bios 11, hope things work out for you as I know how frustrating this can be, so much that I will probably not lay eyes on another Asus mobo for quite awhile, if ever again.
Went back to 12.B08 and no problems so far. 1.25 divider didn't work over 1100 anyways so there would be no benefit in 12.09 for me, only issues and problems.
let me suggest DFI's LT X38 T2R board...i have it and switched back to the IP35 Pro board...DFI made a good board but FAR WAY to many hassles to get it working to optimum...it has warm re-boot problems but it is solved by increasing NB voltage higher than what i thought was needed...the bios provides a gazillion settings for memory and that makes it far to complicated to conquer for the average user....abit approaches memory settings via a simplified method, which i LIKE!...that all said, i think Abit is taking the right approach...every mobo maker have duds, QC wise....it is just a bit*ch getting stuck with the dud!Quote:
Originally Posted by AMDfreak
Whats the consensus about a cooler for the PWMs?
Does it make a difference at high FSBs? What have people found that can be attached?
I had tried this BIOS downloaded from abit official site and everything was great, no problem at all, until I tried to burn my files to DVD media...Quote:
BIOS: m704d12.zip
Bios Issue Date:2008/01/02
Mirror Site: ASIA Europe US
BIOS ID:12
1. Fixed Command rate function abnormality.
2. Fixed DRAM Timing abnormal.
3. Update JMB363 ROM version.
4. Fixed twice boot issue.
5. Enhanced Intel 45nm CPU compatibility.
6. BIOS compiled date: 01/10/2008.
I'm using PATA internal DVDRW drive which surely have to be attached to JMB363 as it doesn't have another option.
Well... using this official version 12 BIOS (as also known as 12.B09 BIOS), it gives me very high error rate when burning DVD media. From 6 DVD burned, 3 DVD are failed immediately! The chronology is when the first time I start to burn, it will be successful. But at the second burning, I always failed! And it will keep failing if you dare to try again and again until you restart your system, like there is something stuck in the IDE channel after the first successful burning. After you restart, this scheme repeats. So, in brief, one burn, one restart if you want to evade the failure!
I would say that was a 50% (in fact, more!) fail ratio. What a mess! :(
If you read the point I bold above, it was very suspicious for me from the first time. I did have the same problem when using the previous AB9 QuadGT.
And I thought it highly possible that this problem was caused by the upgraded JMB363 ROM version in the newest BIOS. I never got this problem when I was using 12.B06 BIOS.
So I flash back and downgrade my BIOS to 12.B08 and hope it doesn't upgrade my JMB363 ROM too as 12.B09 BIOS does.
And you guess it right. 12.B08 BIOS rocks. My problem above is story of the past now. I try to burn 5 DVDs and no failure at all with this BIOS. :)
Really... BIOS 12.B09 or final is a crap for me too. Although it fixes the 1.125 multi, but it's useless to me as I never touch the 1.125 multi.
I just wonder WHY abit engineers might do such mistakes? They fixed one issue, but readded another issue.
First they forgot to restamp the BIOS name in BIOS screen, and now..., IMHO the upgraded JMB363 ROM they provide ruins this new BIOS at all!
Still have a lot to learn for them I guess...
yep it hellps. Whatever can be wedged or fitted over it.Quote:
Whats the consensus about a cooler for the PWMs?
humble - sorry to see your making coasters m8. Usually when there is a rom upgrade there is an upgrade of drivers to support the new rom. It's possible you need the updated driver, the last driver on abit's site is v1.17.19.02 D.2007/04/07 so either they've not got it up yet or it looks like 12.B08 is best bet for now, as you say.
JMicron are not the best controller in the world, the sooner the motherboard industry takes that on board the better, I've lost count of the number of times these have causes people problems on a number of different platforms.Quote:
Originally Posted by Humble
It may be worthwhile going to their (JMicron) site and seeing about updating the driver for the controller, this may help somewhat. Also just for clarification the abit BIOS engineers did not forget to change that stamp on that BIOS - the BIOS on their website is 12 the BIOS I sent out was basically the same but because it was not official they could not change the date stamp, in order to avoid two different BIOSes with the same date stamp appearing.
Morning JohnTrue I forgot that essential bit of info:ROTF: :shrug:Quote:
Micron are not the best controller in the world, the sooner the motherboard industry takes that on board the better,
luck:)
Hello m8's, I'm newQuote:
Originally Posted by Humble
Thats why I fitted an ide to sata adapter on my ide dvdrw so I can avoid the jmicron controller all together.
This thread is kinda depressing me I spent alot of money to get this new rig, the DFI X38 TR2 was in stock but I choose the abit over it, now I'm not sure I did the right choice...
Humble
Abit's IP35 Pro board works very well!:)
i noticed on DFI's LT X38 T2R that it had a problem with the Jmicron controller dropping the SATA DVD drive offline about 30-40% of the time if i had Intel's Raid enabled...it's the same DVD drive that i have in my Pro system right now working flawlessly on the Intel controller.
i would recommend getting the latest Jmicron driver to see if that helps your situation
Oh I just don't believe it. I just refuse to believe it.
Looks like my second IX38 just crapped out just like the first one. Ran 1 week folding, just stopped the program and all of a sudden got these buzzing sounds again :mad:
And sure enough, µguru showa 100A in idle (!) and 162A under load just like it did last time. Unstable Vcore, too. I feel like history repeating itself :shakes:
Wasn't even on high voltages (1,33V CPU 1,4V MCH and so on) and the mobo is watercooled, after all. So wtf - can't this thing take even a week of continuous load? Have I had enough bad luck to get two boards from the same bad charge?
What else could it be? Maybe the PSU, but why now... I've had my Liberty 500 for over a year now and it ran fine with the old QuadGT.
I think the board is to blame.
My... I think I forgot that new driver option. :rolleyes: But, I'm using JMB363 driver version exactly as you mention above since the first time.Quote:
Originally Posted by Supershanks
But telling you the truth... My previous experience with AB9 QuadGT gives me big nerves to retry that 12.B09 or final BIOS. Back then, I had tried sooo many different attemps on that AB9 QuadGT board to persuade my JMB363 work properly, but all failed at that time:
- Update to newest BIOS version 15
- Download the newest JMB driver version 1.17.21 WHQL (have tried SCSI mode and native IDE mode)
- Use native M$ Windows built in IDE driver
- And even reinstal my Windows!
Everything was in vain at that moment. I then had no other choice, except to sell the board. :shrug:
Thanks for your input anyway brother, but I think I'll best stick with this 12.B08 BIOS for now, as it give me minimum error. But it's a bit slow if compared to 12.B06 BIOS in Everest benchmark.
Btw, have you also find this issue on your system brother? IX38 BIOS 12.B09 with IDE DVDRW drives? :)
Thank you Brother Johnny for your information about the BIOS. It's all clear now. But still, I do hope that abit engineers make a more good, stable BIOSes soon without readding previous BIOS errors in the future.Quote:
Originally Posted by Johnny Bravo
About the J-Micron, I still can remember the time when Intel started to remove IDE drive support on their new chipset. A very brave and controversial step, as there were still so many IDE drives on the market and SATA drives hadn't become common at that time. Even nowadays, SATA interfaces is just widely used on HDD and still implemented very few on CD/DVD drives. SATA CD/DVD drives itself still also have so many bug compared to IDE CD/DVD drives.
The motherboard manufacturers then didn't have the other choice except to integrate this JMB363 on their board to support IDE drives which are still widely used at that time. Abit AB9 QuadGT was one of the board, and the new implemented JMB363 really gave me hard time at that time. My other friends also had the same problem with this board as I did.
But, the one to praise is Gigabyte. Their restamped J-Micron controller, as known as Gigabyte SATA2 chip, worked flawlessly on the very first P965 board, 965P-DS3P that I used! Not even single issue come up. Great job really! :up:
Great idea there to use the adapter, brother! :)Quote:
Originally Posted by Beastage
Don't regret what you have decide. Abit IX38 is a great board but with more simple BIOS (not as complex as DFI; which keeps me away from using it) and it will show it's full capability after a few BIOS updates just like what happened to IP35 PRO. You just have to pray that moment will come soon. :D
Then I feel happy for you too brother. I think it's because of the maturity of IP35 PRO bios.Quote:
Originally Posted by Ace-a-Rue
Right now, if I don't miss remember, the newest version of J-Micron JMB363 driver on it's official site is version 1.17.31 WHQL, but I don't sure it'll help me out of the problem if I'm still using 12.B09 BIOS.
Well, I think I'm happy enough with this 12.B08 now, and will stick with it for a moment till abit release a new, proven good BIOS. Thanks for your input too. :)
Ok, I decided to have a go at 400x8, on stock voltages... why is it stable?
I running a Q6600 G0 cooled by ultra-120
I did it to see how long before it crashes... but its stable on full load for a few hours now.
Does that make sense?
On the topic of the JMicron driver , it was last updated on December 17th , 2007, so no new driver.
Hello im another new boy on here so HI ALL!!!
Just one question as i have just built my system about 5 days ago so any advice would be great.
I have raid0 on my two drives and am using intel`s matrix manager but not the J-Micron driver as everything works with only the intel installed. I even have my dvd drive in a sata port and so far have had no prob`s with it .
I have the new bios from abits site and am wondering if i need this J-Micron driver or not? I have raid enabled in my bios onchip SATA Device and in onboard PCI Device..
Do i make sence so far:shrug:
jcool have you tried running it outside the case those currents are WAY too big and this is more than coincidence!Quote:
Originally Posted by jcool
How can it be related to the case, if it runs 2-3 weeks w/o problems and then, suddenly, it dies?
It's kinda dead now btw, I made the mistake of shutting it down. It won't start now, shutting itself of after a few seconds, then staying with postcode 90. Tried other gfx card, removing ram, clear cmos, remove battery but I guess it's done for.
I just don't get it... it can't be the PWM freezer, cause the freezer doesn't make contact with anything else apart from the mosfets. And if it did, why would it run for a few weeks then die without me even touching the case?
Another reason could be my PSU, maybe these digital PWMs are very sensitive to spikes. Against this argument stands the fact that I have used my trusty Enermax Liberty 500 for nearly a year with my old QuadGT already (which has essentially the same digital phase unit), also running 24/7 folding.
So I'm gonna give it one last try... will test my third board without the PWM freezer with fan attached and see what happens.
The only explanation I have is that the pulse chip is getting too warm without airflow and that it just burns out when running high load 24/7.
We'll see.
No there's something more going on your current is messed up - I've had mine what 3-4 months now running on and off 1.6volts with a Q6600 and that is an idle currnet of 62A peaking at 120-130A fully loaded.
In effect I think you have a short developing somehow. This could happen by molten solder forming under the slave VRMs due to excessive heat, but this is unlikely as you are running a water cooling loop over that. However I think it would be in your best interest to run the next board with the stock cooler and a 60mm fan on it to assess if its the MIPS cooler or something else that is the culprit.
you say you ran 1 week of folding, did you keep a check on the PWM temps during this ?
Yeah I did... temps were between 70 and 75C which is quite ok.
And like I said, I will try the next one w/o the PWM Freezer. If it still burns out it's either my CPU being a mobo killer (:D) or it's the PSU...
sounds like something is up for sure, hope it all works out in the end!
This board is great i could never pass 3.6 with the Ip35 because of the vdroop probably. Now i can do 3,8 prime stable! :D
Vcore is 1,52 in bios goes 1,49 at load. I am still testing the memory.
Thanks m8, will keep you guys posted..Quote:
Originally Posted by Johnny Bravo
For now, back to P965 QuadGT :(
Wow like Johnny says's somethings seriously wrong there m8. What VTT Volts you on ??Quote:
And sure enough, µguru showa 100A in idle (!) and 162A under load just like it did last time. Unstable Vcore, too. I feel like history repeating itself
I'm on 1.36v & it's currently ticking away at 30~32A Idle
hope it's not another RMA M8
Edit:
grood going Daidalos that's the good thing about this board:)
i see some of you have had the dfi lp lt or ut models.. have you switched and not looked back i am looking into the dfi boards now.. i was sure about getting one and the more i read the more people seem to have reported issues.. but then there are issues with all mobo's lol.. they are never all going to be perfect.
this compared to the p35 pro ?? do you think the x38 really made a oc difference for you or was it something else.
are the bios chips soldered on these or are they chips that can be replaced?
Quote:
Originally Posted by jcool
what spec cpu do you have (45nm?)...what is the VID for your particular processor?
Quote:
Originally Posted by zfactor
the DFI X38 board is good...i have one..it's back in the closet..LOL..hehehe...actually, i like the IP35 Pro board...the DFI has a complicated bios for memory settings...you could run it in "auto" and never think about it, but, most people like to extract the most out of their boards....when you do that, it can be frustating
the big thing about the Pro board, it has a large Vdroop...the IX38 closed the gap on that issue...i think there is a small vdroop under load for the IX38.
lol wanna sell it..
do you think the abit can get up to the same speeds as the dfi.. most are telling me the dfi can run a quad stable at near 500 24/7.. think this is true or that the abit can do the same.. again 24/7...
thanks for the info..
Looks to be Q6600 unless I got that wrong AceQuote:
Originally Posted by Ace-a-Rue
i am also curious about the VID for that processor...i have a VID of 0.9625v and it draws a huge amount of power when i raise the vcore to 1.45v or 1.48v...it sends my PWM temp (Pro board) into the red at 1.45v....that NEVER happened before!Quote:
Originally Posted by Johnny Bravo
i am thinking his VID is lower around my number which could have overloaded the PWM....could be wrong...it won't be the first time.:D
i replied to your PM.Quote:
Originally Posted by zfactor
i put my good Q6600 (G0) in the DFi board and i got the same out of it that i got with the Pro board...the only real difference between the two; there is no Vdroop on the DFI board, besides the PCIe configuration....so...i didn't have to overvolt the DFI board....i still had to contend with the heat produced by the vcore...i used a TRUE heatsink.
In case it helps, I had this problem with my first IX38. I had the stock cooler with a 92mm fan directed on it. Without the fan, my PWM temps got to around 120C, with the 92 temps stayed under 90C. My CPU is a Q6600 G0 that I had vcore set as high as 1.6. The VID for my CPU is 1.2875.Quote:
Originally Posted by Johnny Bravo
I've got a 3rd IX38 on the way, so I'll let you guys know what's up.
Oc advice needed please.
Ok guys im oc`ing my Q6600 and am messing about with my multi and so far i am at 400 x 8 with the following volts
cpu 1.325v
cpu vtt 1.41v
mch 1.37v
ichio 1.50v
ich 1.11v
I am also running my 4gb of ram in 1.1 so it makes it 800Mhz.Do they look ok for volt`s ect or do i need to change anything b4 i start to bench as my cores are 38/38/39/41 on idle..And if i was to mount 2 x 120mm fans on my cpu cooler should i put them both blowing towards each other or not.
Cheers Paul.
It's a Q6600 G0, the evil type - Vid 1.225 (means it gets very hot and draws lots of A). "Normal" full load operation at 3,6Ghz and 1,32V put 107A through the PWMs (was the same on P965 QuadGT). Only my X3210 B3 Xeon was worse, I saw that one sucking up to 125A@3,2Ghz :ROTF:Quote:
Originally Posted by Ace-a-Rue
BTW, gotta love my Win XP x64 - just slapped in an IP35 Pro that happened to lie around (being a system builder does have its benefits) and it bootet straight into windows, including raid and all, just like it did when I changed from P965 to X38 :D
Supershanks: Was running a VTT of 1,36, like I said it's NOT the voltages being too high.
I think we have narrowed down the problem to either the mips PWM freezer or my liberty 500.
@AMDfreak: U also on ur 3rd board? Damn this sucks... you don't happen to have an Enermax PSU, by any chance?
OT: Can anyone tell me which bios to use for the IP35 pro? Since I'm gonna have the board for at least a week why not test it out a bit.
But I'll have to put a fan over NB and PWM, currently running stock idle, CPUtemp 25, System temp 30, PWM 60 - told you my CPU was evil :rolleyes:
Nope, PCP&C Silencer 750. Single 12v rail with 60A. My replacement for the 1st board was DOA. On power-up it would just do this code 90 to 99 to power off and back on again in an infinite loop. I did get it to post once and flashed to b09, but no change. :mad:Quote:
Originally Posted by jcool
Edit: Are there any Irishmen around that can send me and jcool some good luck? :idea:
IP35 pro sucks for me - been running 400x9 and got a bluescreen after 2 mins of prime, PWM reached 95C *g*
Anyway why the hell can't one adjust the VTT properly?!
Now running 375x9, droop is kinda ridiculous... 1,28--->1,23 load... I gotta get my X38 back :rolleyes:
yep the mips block was my next thought.Quote:
I think we have narrowed down the problem to either the mips PWM freezer or my liberty 500
I know people have had issues with Enermax Galaxy but not heard of anything with the liberty.
Sorry , i feel for you:shrug:Quote:
I gotta get my X38 back
ok...thanks!...the low VID thing is probably going to pan out for the 45nm cpu's...i have a low VID 45nm cpu, it overheated my IP35 Pro PWM temps...first time ever going into the red.Quote:
Originally Posted by jcool
try either 16.b03 or 16.b04 bios for the IP35 Pro
I'm gonna send my Liberty 500 to a friend who owns an oscilliscope - he will try to simulate my load of about 300W when folding and check the NT for any excessive ripple and stuff - I really need to know why these boards died.
IP35 Pro runs now@3,4Ghz - more is impossible due to the lack of decent VTT and PWMs overheating. 75C PWM with Fan and only 1,23V Vcore is high enough for my taste... using bios 16.B04 BTW seems to work ok. Can't run 1200 mem though.
i have the same problem with you bro... my IX38 QuadGT somehow start to buzz, ampere too high 126a on load and vcore problem. i bench a lot with my cascade + folding a lot too with q6700 and E6600...
Well... I had tested my system too at 3.2 Ghz today, and when priming, my board was also buzzing too. But everything else seem OK. Here's the screenshot:
http://img261.imageshack.us/img261/4...os12b08vu8.jpg
I think the PWM current is normal, ranging from 65 - 75A. Everything is OK and rock solid.
In my experiment, I heard the board start to buzz when the PWM current was exceed 70A, while when the current was below that number, there was no buzzing sound at all. This opinion rather makes sense as when I tested my system before at 3.0 Ghz, it was keeping silent during priming time and the current was never hit above 60A.
About the buzzing sound, I have had same experience with my previous Commando. Some people said that the sound was highly possible coming from the opened chokes. And may be the sound from this board also come from the same sources, the half opened chokes. May be they're trembling when handling high PWM current...
But, in my humble opinion, it's not a big deal, as long as everything is running normally on low temps, rite? :)
Well, may be I could use some help to running my system stable at 3.6 Ghz. I had raised:
FSB to 9 x 400 Mhz
Divider set to 1:1.5 (makes RAM running at 1200 Mhz@5-5-5-15 2.2v; tested more than 1000% dual Win Memtest stable, so it's not a RAM error)
Vcore to 1.45v
VTT to 1.4v
MCH to 1.45v
ICH to 1.1v
ICHIO to 1.55v
Both GTL to 68%
But, it always gave me error when priming in blend mode under 5 minutes.
What should I do to make it stable? I think raising a little Vcore may help, but any suggestion will be highly appreciated.
Thanks in advance. :)
I have mine priming about 6 or so hours everyday right now, and have had the board up just over two weeks now. No buzzing here.
I'm trying to get my cpu stable at 3.6ghz with a low vcore and temp, it's certainly been a struggle.
Anyhow, I have mine at 440mhz x8 right now (3520mhz) with the 12b09 firmware at about 1.5v
Just to note, my PWM currently idles at 39A, and at load, it can go up to 110A. I have a 40mm fan pushing air to the PWM right now. So, temps at load can go from 80 to 110c. Depending on the FFT in Prime. So, I don't think the board should have an issue at pushing the PWMs at 110A or so for a continous period of time.
What I have noticed, is that my VTT volt setting has literally no affect on the overclocking of the q6600 I have. When I had the 680i, the VTT made a huge difference when overvolting it. But, with the ix38, it makes no difference at 1.25v to 1.5v when pushing 440mhz. Has anyone else noticed this?
Well I finally screwed my IX38, flashed to the latest bios and all it does is repeadedly reboot and will not post anything.
I get message code 9.0 which is complete uguru initial process AWARDBIOS take over booting job , then I it goes to code 11 which of coarse there is no decription for.
I repeadly cleared cmos with no positive affect and removed mobo's battery for up to an hour with also no affect. I'll leave it out overnight to see if that helps.
Should have stuck to bios 11, I wasn't really having any issues, just wanted to flash to the latest bios which would have rectified a few minor issues with ram timings, now I have nothing ;(
Oh well, RMA time... Again!
Oh crap. And you've got an Epsilon 800 which means I'd better don't go for the Epsilon 700 I was planning for... this uncertainty is driving me nuts.Quote:
Originally Posted by andre X_X
If it's neither the PSU nor my PWM freezer (which doesn't touch anything but the phase chips) then what?!
Maybe this board just can't cope with continuously high A for long periods of time :(
I tell you this, if my third one's going down then I'll change mobos for good.
Andre what kind of cooling you got for your PWMs?
Edit: Come to think of it, 126A under load isn't that unusual if you're running a quad under phase change@4Ghz+... Remember, I got >160A at 3,6Ghz and only 1,32V (which was 107A before).
I think your mobo might actually be ok, buzzing seems to be the price of running excessive QC speeds...
i'll pick my ix38 QuadGT up tomorrow evening at the postoffice... wish me luck that i got one of those that work:cool:
They all work, just don't push it too far or have the wrong PSU ;(
If Abit thinks that's ok then I'll never buy another Abit mobo again. It amazes me that this stuff gets past quality control.:mad:Quote:
Originally Posted by jcool
check your choke coils to see if they are embedded in enough silicone.
@jcool: nope,not epsilon, now im using silverstone 1000w olympia, its an old siggy.
lol, 126A is on air... now even E6600 @ 3.6ghz 1.45v bios(uguru says 1.39v idle and 1.36v load) idling at 62a and loaded Folding at 146a. vcore is going crazy too... pwm always cooled by high cfm 7cm thermaltake fan.
Ok so yours is good as dead. I was thinking you'd be running a quad... Don't shut it down unless you've got a replacement, it will most likely not start again :rolleyes:Quote:
Originally Posted by andre X_X
But the fact that you kept your PWMs actively cooled all the time is a very interesting one - means that it's probably the PSUs killing off these phase chips :down:
OK guys I have an abit technician looking into this issue, he's gonna setup a board and running it flat out of a couple of weeks to see if he can establish the same issues.
Any/all information about your setups and what they were doing would be much appreciated :)
im very sure its because of continuos load from folding... since at first it happened when it shutdown cpu to connect other HDD. turn it on, start folding and an instant restart when cpu hits 100% load. its because the vcore is now idling @ 1.42v where it should at 1.49v (set in bios 1.52v). pwm current start going nuts, first only 121a now it even more than 140a. now i run it @ default but the pwm current still crazy high.....
Jap it's definitely a high load problem.
Both my IX38 died after at least 1 week of continuous folding operation.
Since I already had the exact same setup folding for month with the P965 QuadGT I'm once again pretty sure the mobo is to blame.
-Q6600 G0, running at 450x8 (drawing 107A@1,32V)
-Enermax Liberty 500
same as me... looks like >100A continuos load causes this problem. with E6600 @ 80A whole months no problem at all... my Q6700 takes only about a week then it start buzzing and another week for complete mess up...
Your efforts are much appreciated Johnny. :clap:Quote:
Originally Posted by Johnny Bravo
My first board started buzzing after 2 weeks. I was testing for high CPU clocks on a Q6600 G0. I had the CPU Orthos stable at 3.7 with 1.59 vcore. I raised the various other chipset voltages to their higher ranges trying to get higher FSB at lower multi's as well. Once I got it where I was happy for 24/7 use I ran the SMP Folding client 24/7. Unfortunately I did not think at the time to check the amperage on the PWM's.
The CPU is water cooled, and the mobo cooling was left unmodified other than pointing a couple 92mm fans at the PWM's and NB. I used 4x 1GB Crucial Ballistix PC2-8500, and my PSU is a PCP&C Silencer 750. In case it matters I did have 5 hard drives and 1 optical on the same PSU. I do not think the PSU was overloaded as my Kill-A-Watt showed about 450W usage at load.
Hope this helps, let me know if there's anything further I can answer. When I get my 3rd board back I'll keep it dialed down until something gets ironed out.
I finally started up my second ix38 with the e2160. A couple of things to note.
I'm running Prime95 on it now, and with the e2160 at 365mhz x9, it is only taking up 35A on load! and with a 40mm fan, the PWM temps are staying under 50c.
Now, I've noticed, with the e2160, Coretemp and uguru shows the exact same temps, at idle and load.
But, with my q6600, Coretemp Shows higher temps from 10c on the coolest core to 20c difference on the hottest core compared to Uguru Temps.
Along with that, PWM uses 100A easily, the q6600 is at 440mhz x8.
I'm worried about the diffrence in temps between coretemp and uguru, I can't use coretemp because I run vista64bit (and I prefer to keep the driver protection) , now during the winter it doesn't matter if the real temp is 20c higher, but in the summer that is critical.Quote:
Originally Posted by redmodel
What should be trusted?
Hi guys can you please tell me what setting you have this at?? 32 is default but it says you can go up to 250 or so with it. Is it worth putting 64 or 128 in and seeing what it does or should i leave it at 32?
Cheers Paul.
Just leave it at 32 unless you have problems with any PCI devices (e.g. a sound card that produces sound delays/lags or something).
You can use Coretemp with Vista64. That's what I am running now.Quote:
Originally Posted by Beastage
Here's How:
http://www.overclock.net/operating-s...emp-tweak.html
It should work with driver protection still on.
Right now, I am going by the CoreTemp reading, so I am doing okay right now. It would be quite nice, if the uguru temps was the right one, because than I can overclock even higher ;)
Thanks jcool..
I have another question that is does this mobo allow 4gb of ram to be run at 1066 or does it have to be run at 800 like most other boards? I have 4gb of dominators and was told to run them @ 800 Mhz but when i benchmark it gives worse results than when it had 2 gb @ 1066.:shrug:
you have FSB to memory ratios...1:1 and 1:1.2 are 1333 mhz memory straps...the next two, 1:1.25 and 1:1.50, are 1066 straps...super pi is memory speed dependent besides raw power of the processor.Quote:
Originally Posted by wilson
I think he wanted to know whether it's actually possible, not only in theory ;)
I have been running my 4x1GB D9GMH at 1080Mhz, that is FSB 450 and using the 5:6 divider. You can also try reach that memspeed by using the 2:3 divider, since the 4:5 won't work that high (they still have to fix that).
Ok so if im at fsb 1422 what divider should i use? and should i run them at 5.5.5.18. instead of 5.5.5.15 and will i need more NB volt and im using 2.24v on my memory now is that enough???
for 24/7 running ram <=1000Mhz youi can use tighter timings 4,4,4,12.
>1000 you slacken them to 5,5,5,10~12 depending on your ram spec.
is quad pumped /4 = 356 which is how people genarally talk about fsbQuote:
fsb 1422
Available straps are :-
1:1.00 = 356 x DDR2 = 712Mhz
1:1.20 = 426 x2 = 852Mhz
1:1.25 = 444 x2 = 888Mhz
1:1.50 = 533 x2 = 1067Mhz your rated memory speed.
However not all straps are equally stable. That's really where you need to experiment yourself. You may need to increase Mch 1.25v voltage to help when running a higher strap.
The other laternative is to run a higher FSB, perhaps with a lower CPU muyltiplier, this will allow you to use a lower memory strap.
luck:)
Nice explanation supershanks, I think he got it now ;)
@wilson: For your FSB, use the 1:1,5 (=2:3) divider to get your desired memspeed. Timings of 5-5-5-12/15 should be fine, just as Supershanks said.
And I don't think you need that much Vdimm, I was running 1080 with 2,1V so try to lower it a bit.
Ok cheers guys im now running @ 5.5.5.15. 1067Mhz with 2.3 divider and have passed two memtests. I am running my nb with 1.38v and sb with 1.15v and it seems to be stable :up: . Is running them at this speed putting strain on the mem controller or does it not really matter if ive upped the volt abit??
I guess it's ok, since you're using aircooling the NB won't get too hot.
Where's your mobo at now jcool ??
You mean the two dead IX38? Well, they're both in RMA (didn't send the first ahead out of laziness... saved me the freight)
But somehow I'm not looking forward to a 3rd try... honestly what's the fun in having a single stage unit and not being able to use it properly for fear of a dying mobo :down:
jcool, do you think your PWM cooling solution might have shorted out the digital PWM circuit?
Nope I don't. Since some other guys have the same problems now... And I triple-checked the PWM freezer, it does not touch anything except the PWMs.
And I don't think it's the PSU, not anymore. Not since my friend with the oscilloscope tested it and told me that it's perfectly fine, no ripple or spikes or whatever.
I think it's just >100A for a continuous period of time = goodbye PWMs, simple as that.
However, the guy that's developing these Mips freezers just sent a new prototype my way. This prototype is designed to use with thermal grease, not a pad. So maybe if I can keep the PWMs cooler with this prototype's help, the mobo won't die - I'll post some pics and let you know how it goes.
I am so not gonna step down from my OC because of a stupid mobo...
any chance of it wiggling or moving ever so slightly to touch the other circuits on either side of the digital chips?
anyone tried a e8400 yet? :shrug:
You could tie a rope onto the PWM freezer and play cowboy with the mobo and it still wouldn't move an inch so noooo way :rolleyes:Quote:
Originally Posted by Ace-a-Rue
:rofl: :ROTF:Quote:
Originally Posted by jcool
this is what i got out of this board so far ,http://service.futuremark.com/compare?3dm06=4931312
http://valid.x86-secret.com/show_oc.php?id=303631
just wierd comming back from a bad oc in biose
Hopefully i will get a E8400 tomorrow to test on the board...Quote:
Originally Posted by superbowtie
I've got the E8400 but no more boards to test on...
yepQuote:
anyone tried a e8400 yet?
Intel E8400 Wolfdale Living Review verdict sofar, cpu looks promising, board is @*!! :rofl: and the claim it's 45nm ready :shrug:
Edit:
got to here 495x9 Despite this board. using shipping bios 11. really perverse after 2 months of bios development, you get a new cpu & the shipping bios works. Feel like i've entered the twighlight zone. :lol:
SuperShanks, have you tried the beta 6 or 8 version? I wouldn't even waste my time with 9 or final. can't be much longer till another beta comes out with the penyrn releases. Doesn't make any since how a newer version of a bios would be worst then previous. someone forget to save their work at Abit?
Talk about a bad luck. Mwave is like 205 for the chip but shipping takes it up to 218.61, Newegg is 219 with free shipping :ROTF: .
It seems The Egg has turned out to be someone's Nest egg. Can we say someone got Greedy.
Hello All:)
I was reading your posts and since the moderator allowed me to write i will give you some of my reflection about this board:)
I have Q6600@3600 stable on 1.41 offset 0.10 and its 24/7
http://valid.x86-secret.com/show_oc.php?id=303487
Ofcourse its nothing to compare with 4700mhz:)))))
I thing that this board is great to oc and stabbility with ours Q proccesor:)
My Q6600 can more than 3600 but im using the Infinity AC so i dont want to make him to hot:) in couple of days i will buy a WC and then ill try to oc more:)
I have a little question about this BEEP on startup.
When my pc is off and after couple hours i will turn it on, some times(not always) i can hear only ONE beeep. Is it normal??
Thanks to giving me advice on this forum - thats why i have bought quadGT x38
Now i have recieved my new E8400 ( Q744A761 ).
Running with final 12 bios and this is really strange. It keeps changing to 9.5 multi when i´m in bios.
So i put a little lower clock and volts in bios and then i use uguru to raise FSB.
Testing 445x9 right now with 1.3125 and it´s seems to work right now. Will try more :) What do u think about the bios, should i try another one? If so do they support 45nm cpus ??
http://img150.imageshack.us/img150/7447/e84001jx6.jpg
Noticed that Cpuz reporting 1.448v but i have 1.3125 in bios :)
Changed Bios command line gets 45ns support in bios 12 using your command line cured screwed dmi & stopped the C1 erros.
Am running as smoothly as my ocing will allow now :)
Be interested to see if using your command line switches also get working multis
@superbowtie
Yep theirs a few price gougers on this side of the pond, I managed to gert mine at a decent £.Quote:
It seems The Egg has turned out to be someone's Nest egg. Can we say someone got Greedy.
As i said above i think i'm looking good on 12 now after flashing using ace's command line. thanks. Be interested if it makes any difference to others who have had multi issues.
luck:)
I have a problem with stabbility at memory on 1:1 25:( Any one know how to fix this issue?
Now i have on 1:1 20 and memory at 960 it would be nice to have at 1000:)
I'm settling for 3200mhz on the cpu (with almost stock volts) but when I overclock my ram I get terrible memory performance, its Geil DDR2 800mhz 5-5-5-15 , I overclock it to 1000mhz (1:1.25 divider) at same timings but memory performance drop to 4000MB/s! , memtest86 does fine... what gives?