Printable View
my guess is the ICH8R driver, that you are using, is corrupted...or...the floppy head needs to be cleaned or the floppy disk needs to be re-formatted.Quote:
Originally Posted by xitars
usually error codes (BSOD) during installation (when not overclocking) are a result of a corrupted driver, dirty floppy head or bad floppy disk.
one other thing!...try increasing your Vdimm to 2.1 for your corsair memory to make sure it is getting enough voltage for them to work properly.
oh yes you CAN! just check the option in the configuration of the flasherQuote:
Originally Posted by loc.o
ok,I got a brand new DVD ROM but that didnt help. SO Im gonna try making a copy of the CD rom. Now, how to do this? Make a disc copy in nero? Or extracting all files from the cd and then make it into a bootable iso? Also on what speed should I burn the cd, any special format?
is this a store bought XP install CD that you are talking about making a copy???...if so, i presume you have used it before to install???
Quote:
Originally Posted by Ace-a-Rue
Yes it is. But because it doesnt work and some ppl on this forum claims that the cd-format might be incompatible with the jmicron IDE controller I need to make a copy of it and hope for the best.
I was able to save the rom file to the root of c: on a ntfs hdd and could get to it with the bios utilityQuote:
Originally Posted by loc.o
the 7B stop error is a common one and usually corresponds to bad/incorrect raid drivers
Quote:
Originally Posted by Pyr0
ok, however that is not the problem in my case since I do not use a raid array.
Thank you i missed that one.Quote:
Originally Posted by heikis
it would seem after a lil bit of playing that 0903 bios runs a 4:5 better, and also runs tighter latencies better at higher FSB..... I ran orthos for 24 1/2hrs and didnt get a single error with my memory after i used this one, I would get errors at about 10hrs in with 0804
Cool thanks for the test, i may update after all!Quote:
Originally Posted by ChaoSMinionX
So I made a copy of the xp installation cd.
Still the same error. I hate this jmicron controller
Don't know if its been discussed yet, but I was having a problem with cold boots over 400 and think I may have figured it out.
Symptom: After cold boot or occasional warm boot after changing fsb or memory timings, system would not post. Keyboard lights up, then 1 long beep followed by 3 short ones.
Solution: AMI Beep codes say thats a memory error above 64k. Actually it maybe a memory problem, but its cause by some combination of PCIe, VCore and FSB. Lowering PCIe fixes it right away (I have it set to 96 with no problems). Other fix is to raise VCore, problem with that is I would have to raise VCore roughly .375V over its stable point for any given OC. I tried this with two cards (albeit identical EAX1900 (X1900XTs))
My system:
E6600 (tried E6400 too)
G.Skill 2gb ZH
P5B-Deluxe
2x320GB Seagate in Matrix raid (0 and 1)
Xclio 600W Greatpower
This was a HUGE pain in the ass for me. I nearly rma'ed my G.Skill HZ (which I may still do if I can't get it to 500 at any timing, thats a different topic), nearly RMA'ed the board, etc. Got to eat lunch now, wanted to post that.
What bios are you using?Quote:
Originally Posted by xitars
Are there any other differences between SCSI and IDE other that i couldnt access the SMART info when my drives where SCSI?Quote:
Originally Posted by Malk
Well i wasnt losing my mind. For those who dont remember i was stuck @ 2.765mhz @ 1.375 (bios vcore) on my e6400 l626a. I could make it to 3.0ghz but needed 1.48 (actuall) which seemed crazy. I was also having problems booting with setting that others were 8hours orthos stable on. Well i wasnt losing my mind it was the crappy chip. I received a new demo model PC at work today that had a e6300 L629B in it. I figured i would "borrow" it for the weeked before pulling anymore hair out and if it works i will just order a new one and sell this POS on ebay.
To my amazement...
http://img144.imageshack.us/img144/9875/gtbenchjn9.jpg
It was the chip.. this was on my 2nd boot. 1.4bios/1.33-1.34 actuall 2.25v vdim and all other volts were still set auto.
FYI not using AS5 just some crappy HP thermal paste for testing.
more to come.
-GT
Don't know about that. But I can't get any smart info (other then temps) in speedfan with my matrix raid setup. (2x320gb Seagate sata)Quote:
Originally Posted by Malk
Im using the 0804 bios.Quote:
Originally Posted by Psyire
However, i figured I would try to install windows from the harddrive by using W98 MSDOS diskette. That way I would be able to put all files needed for the installation on the hard drive itself, and so i would not need the damn jmicron controller activated. BUT of course I CAN NOT copy the files from the CD to the hard drive in MSDOS because MSDOS is unable to initiate any working drivers for the damn IDE ROM.
Really, this motherboard was the worst buy I've ever made. Never ASUS again. (Probably Jmicrons fault, but ASUS could have picked a better IDE support supplier).
boot up #3 with 629b e6300 (literally the third time i booted)
http://img213.imageshack.us/img213/1...nch2cp6.th.jpg
Dont get me wrong im no asus fan boy, this is my first asus mobo in years but coule things are bothering me.
Guys you can thank Intel for mobos that use Jmicron, since they removed Pata support from ICH8 not Asus! from what i gather (i could be wrong) Jmicro is the only controler that can utilise a optical drive, that means that mobo makers are forced to use it with p965 chipset
on another note, for ppl with slow boots, why do you care so much, do you reboot all day long and need it to be fast, as long as its fast in windows, why a bar or two extra are such a big deal, i have been into and worked with PCs for many years, and been OCing since before celly 300a days, and i dont remember such a speed boost as this one from newer gen cpus, ya im annoyed that i got to unplug my machine for every boot cause of the pcix x1 prob, but when it boots its bloody fast, my ultra-d didnt wanna boot for like 10min after i shut it down but i still think it was the best mobo till now.
I managed to get all the windows installation files onto the hdd. So I start up the new system with the single SATA drive connected and the jmicron controller disabled. SAME ERROR. Must be a faulty motherboard right?
You using the 804 BIOS ghettotech?
@ghettotech,i have a l629b as well.what a champ of a chip.mine will do that 3.5ghz too,and it does 3.2ghz with the vcore set to 1.25v in the bios.
i reckon these l629b's are pretty sweet.
http://loader.sc0rian.com/users/publ...36pi35p197.jpg
at same 3.5ghz as yours,nearly identical score.is your ram running at 1000mhz 1:1?.
mine is 0804 bios.
yesQuote:
Originally Posted by Noob-ftw
Too bad its not mine! its borrowed from work for the weekend. I just wanted to see if my old e6400 was the reason i am stuck @ < 3hz and it was the chip.Quote:
TI66ER @ghettotech,i have a l629b as well.what a champ of a chip.mine will do that 3.5ghz too,and it does 3.2ghz with the vcore set to 1.25v in the bios.
i reckon these l629b's are pretty sweet.
Have any of these issues with the new bios (903) been fixed ?
PCIe 1x ?
Slow Boot - On Board Sound ?
400Mhz & 4:5 ?
edit: To ghettotech.... how would work know the week of the chip they got? Its not like your work is going to oc them right? Ya know... they look very similar to me. Be careful otherwise you might mix them up ya know.... ya know ?