xp pro sp2 32 bit
Printable View
xp pro sp2 32 bit
Has anyone had the "CPU INIT" error with this board? From what I've read it is not too infrequent of an occurrence with the Striker boards. Had just assembled a rig consisting of (CPU and mobo brand new):
MIIF mobo
e8600 with TRUE 120 push/pull fans
4x1gb crucial ballistix 1066 (the oldies-double sided memory banks)
evga 9800gtx
wd raptor
pcp&c 750 watt psu
antec 1200 case
winxp64
I had loaded the OS without issue and had already run (DOS based) memtest for several rounds without errors. Then a few minutes into running two instances of windows memtest, the computer powered down. I tried powering back on the system numerous times which only resulted in the system fans and led's coming on for a few seconds or flickering on and off repeatedly for a few seconds, but it wouldn't post and LCD monitor displayed "CPU INIT". I tried resetting CMOS (pulled battery), tried BIOS 2 jumper, tried a different pcp&c psu from another computer, tried booting with only cpu, graphics card, and only one stick of RAM, but no love.
At the time of the crash I was running 8x450fsb, vcore 1.26, CPU PLL 1.5, vdimm 2.1, vFSB 1.25, vNB 1.29, mem at 5-5-5-15 with 333 strap, all else pretty much on auto. Temps before crash looked ok according asus probe- cpu low 40's and NB 47C.
RMA time for the mobo? The board was purchased from local retailer and still within return period...I was going to swap it for a new one.
Hey there,
I've been following this thread for a while now, since I too got an M2F. Ever since I got it,
it has been nothing but trouble and frustration. When I first recieved the board only changing
the AI overclock tuner option to manual would made it fail to post, after getting some help
from another forum we fixed the problem. On my former XFX nForce 780i board I was able to run
my lapped Xeon 3110 at 4.2Ghz @ 1.37v and ram set to 1171mhz. Now even 3.6 isn't getting stable.
I'll post my specs and make a small list of what strange problems I'm experiencing.
My Specs;
Intel Xeon 3110 Lapped
Thermalright Ultra-120 Extreme Lapped
Asus Maximus 2 Formula bios 1307 & Ket's 1307
Corsair Dominator Pc8500-C5D 2x2Gb
Corsair Dominator Airflow Fan
Gainward Radeon HD4870 875/4800
Thermalright HR-03GT
Level-One WBR-0601 W-NIC
Seagate Barracuda 7200.11 2x750Gb RAID 0
Antec Truepower Quattro 850w
My Problems;
PC fails to post when changing PCIE frequency and hangs at "DET_RAM"
PC fails to post when changing GTL voltages
PC fails to start windows when overclocked even a little bit (like 400x9 @ 1.4v)
PC fails to post when USB devices are attached when overclocked.
PC needs alot of voltages when attempting an overclock (1.8v CPU PLL 1.5V Vcore 1.4 vFSB)
If the system does post it hangs with BSOD "IRQ not less or equal" error.
and it's overall very unstable.
I did try changing some components (CPU, RAM, VGA) to see if it would solve the problems but
unfortunately after 2 months I hardly have had any fun with it and seeing as some of you get
4Ghz out of a Q9550 ;) I really hope you guys can help me out a little.
By the way I've been into overclocking for a long long time now.
Greetings,
ECPowers
Pop the chip and clear the cmos, put the chip back in and see how it goes.Quote:
Originally Posted by drnick
I know its a bit of a hassle but it will take less time than an RMA.
For now get rid of Ket's bios and flash back to an Asus bios.Quote:
Originally Posted by ecpowers
IRQ not less or equal to is a ram error, so start there.
You want to manually enter each value and set everything to stock speed, then test stability.
Once you have stock running stable you can move up.
Start by clocking the chip first and testing the CHIP ONLY, once its stable you can bring the ram into play.
Trying to do it all at once makes it very hard to pinpoint the problem.
QFT! :up:Quote:
Originally Posted by Grnfinger
Thanks for the quick reply Grnfinger!Quote:
Originally Posted by Grnfinger
I'll give that a try. I'm curious though...could a CPU INIT error like the one I've described by an indicator of a faulty board (or CPU)? Or have you seen this error message before on this board when your OC settings caused a reboot?
Yes it could be caused by a faulty board, and no I have never seen it hand on CPU INIT when overclocking.
The board sounds like it has issues, but as Grnfinger said, try the Asus 1307 BIOS and the oter suggestion first. I have used Kets bios for the board with no issues so I know the BIOS works, but its worth a try. The fact it needed excessive voltages to overclock may indicate something wrong with the VRM.
are these good over clock speeds?
Temperatures
CPU 26 °C
CPU #1 / Core #1 52 °C
CPU #1 / Core #2 51 °C
CPU #1 / Core #3 57 °C
CPU #1 / Core #4 57 °C
North Bridge 48 °C
South Bridge 51 °C
Voltage Values
CPU Core 1.36 V
CPU VTT 1.36 V
CPU PLL 1.59 V
North Bridge 1.36 V
South Bridge 1.12 V
South Bridge 1.50 V
DIMM 2.20
For the past week i've been playing with EVGA 780i FTW, MSI p&N Diamond, Rampage Formula and a MIIF. The Maximus i am the most pleased with so far.
I've ran a couple of 1 hour Blend/Small FFT with no errors. Definatley more to Stability tests to come.
Memory is on auto, i'll tweak that after i find my max fsb. Needless to say I'm pleased with this 9650 and Maximus II Formula.
http://img131.imageshack.us/img131/4461/62753409ma5.jpg
I had the error once when swapping cpu's, I pop'd the Q6700 and got a CPU INIT error, cleard cmos ect and still would not post.Quote:
Originally Posted by drnick
After reseating the cpu it never happended again. If it happens frequently then I would suggest RMA'ing the board.
Thats a nice chip you have there :up:Quote:
Originally Posted by nugzo
I askd to flash back to a Asus bios to help eliminate a ram issue, ruling out hacks and mods would be the first logical step imo. Seeing as Ket just copies memory tables and calls it something special (plagiarism comes to mind) when he is clearly having a ram related issue I thought it would be a good idea, I have tried Kets bios and see zero improvement with my hardware so I see no reason to run something when I have no idea what was modded if anything at all. I think its more a education/learning thing but yes his board could be bork'd,Quote:
Originally Posted by CryptiK
I totally agree with the suggestion and the reasoning behind it, that's why I backed it up. I actually run Asus BIOS now as Ket's gives no improvement for me. I just said that I'd run Ket's BIOS without issues to assuage any fears that he had flashed a dodgey BIOS to his board.Quote:
Originally Posted by Grnfinger
That's a sweet OC for that Quad do you think you could please post your exact bios settings I see most of your voltages there on the side but the GTL and the finalized memory settings would be awesome once you dial it in... Thanks....Quote:
Originally Posted by nugzo
Hello,
anyone figure out how to run the bottom PCI-E slot at x16 with one video card? I know Asus claims both slots are x16 with one video card, and auto-switch to x8 mode with two video cards. But with my 4870x2 it shows in the CCC as x8 when in the bottom slot, but x16 when in the top slot. Both CPU-Z and GPU-Z shows x16 no matter which slot I have it in.
Any ideas?
Have you mentioned any performance difference??Quote:
Originally Posted by SkOrPn
Maybe it's a CCC bug.
offtopic question: How your Gkskill PI perform on M2F?Can you run them 1200Mhz stable?
Yes I did see a slight perf diference but only had time to check in cod4. Never went over 150fps on the bottom slot but seem to stay around 110 or so, but did manage to see a few 300+ fps moments on the top slot, but over all seems about the same really between 130-150 on the top slot. Did not do any synthetic benchies as I just got the card installed a few hours ago and have to remove it yet again to install the EK fc water block (Currently making sure the card works before going thru the trouble). REALLY wanted to run the card in the bottom slot for tidyness and to keep the extra heat as far away from the NB, memory and cpu as possible. Besides, it just looks better that way. Any way to know for sure if its a bug in ccc or really at x8 on the bottom slot?
The G.Skill runs fine at 1200, but I keep it at 1100 because I like the stock 1.8v better than 1.9... I love this memory tho.... seems to play nice both on my P5B Dlx and this MaxIIForm.
it is possible to boot from SpeedingHDD as a raid-0 config in bios yes?
And use it as the C: for windows install.:shrug:
Seen some info that it can't boot from speeding HDD as a main drive.
Could you please find what the max FSB the M2F will run the 9650 at? 3D stable is fine.Quote:
Originally Posted by nugzo
Anyone running on the 266 strap with FSB above 450?
If so can you provide some voltage's, been trying to run 459 FSB on the 266 strap 1147MHz ram will post but wont boot into vista.
Running out of ideas here and open to suggestions
Have you installed the Latest catalyst??Quote:
Originally Posted by SkOrPn
----------------------------------------
1200Mhz with 1.9v??:eek::eek:
WoW..
very good news for me..:D:D
Yes, I tried the hotfix ones, newer than the official 8.10's. But I doubt this is the problem. Wish I could find someone on the internet who can confirm there card runs at x16 in the bottom slot.Quote:
Originally Posted by GeorgeVasil
Going to install fresh copy of Vista 64 to see if that changes anything on the CCC info page. Also will try official 8.10 release... May also move card back to bottom slot and see what Everest says, but so far GPU-Z and CPU-Z says bottom slot is working at x16 but CCC says x8. Maybe I should try testing with 3Dmark or Crysis bench at highest possible settings to see what happens in both slots.
I need to know for sure. Thanks
Where do you get those hotfix drivers???Quote:
Originally Posted by SkOrPn
I am having trouble running CF with 2 4870/512 cards I went to play Crysis and my FPS dropped about 15 to 20FPS lower than just 1 card am I missing something here????
Have you tried 8.11 beta? supposed to get 20% more FPS in CrysisQuote:
Originally Posted by Guacomole
I have it but have yet to test it out.
Guys, looking for advice on a problem and hoping you can help. The reason I got this board is that my DFI P35 died on me eventually. Slowly, it became harder and harder to get it to boot. At first, it took a couple of tries before it booted, then 3-5, then quickly it escalated to the point where I could not get it to boot anymore. I am seeing the same problem starting on my M2F. It's not taking me 1-3 tries to get it to boot, even at just stock settings. Something is putting a lot of pressure on the motherboard, it feels like, and is causing it to degrade until it won't start anymore. The components I have that were on the DFI P35 are these: CPU (QX9650) and RAM (2 GB G.Skill DDR2 800 non-MicronD9). I am suspecting that the RAM may be killing my motherboards. Does anyone else have any feelings about this?
My other components: Radeon 4870 X2 (bought after the M2F)
Areca 8 port RAID card PCIE
Tbalancer fan controller
Auzentech sound card (same from DFI)
Corsair 1Kw PSU (bought after M2F)
I am not an ATI guy for sure I can mod an Nvidia driver in my sleep but I can't even find 8.11 beta anywhere on the ATI site where might it be???Quote:
Originally Posted by Grnfinger
Nevermind I found them....
@ elsupremo, are you on the 1307 bios? Improve compatibility with some PCI-E Raid Cards. But not sure which ones.
Well, even Everest shows the bottom slot to be running at x16 as does GPU-Z and CPU-Z. But I get slight fps increases going to the top slot. Results below.
Run #1- DX10 1900x1200 AA=16xQ, 32 bit test, Quality: VeryHigh ~~ Overall Average FPS: 28.6375 (bottom slot) 5 Runs
Run #1- DX10 1900x1200 AA=16xQ, 64 bit test, Quality: VeryHigh ~~ Overall Average FPS: 27.96 (bottom slot) 5 Runs
Run #1- DX10 1900x1200 AA=16xQ, 32 bit test, Quality: VeryHigh ~~ Overall Average FPS: 31.2525 (Top slot) 5 Runs
Run #1- DX10 1900x1200 AA=16xQ, 64 bit test, Quality: VeryHigh ~~ Overall Average FPS: 29.1025 (Top slot) 5 Runs
One things for sure not much difference from top slot to bottom slot, or 64bit to 32bit. But there is clear enough evidence that the bottom slot is in fact x8. Anyone agree?
I have not tried the beta 8.11's yet.