System drives are connected to the Intel SATA (matrix) in IDE mode, 2 drives in raid on the Marvell.Quote:
Originally Posted by gtj
So you are saying that the memory limitation of 32bit will not hinder performance of high end apps and there is no advantage to 64BIT using intel chips? How about AMD chips?Quote:
The industry will support 64bit when Intel comes out with a better native x64 cpu. The EM64T extensions don't really cut it.
I know it's a pain but you might want to go back to the stock HSF just to make sure the Tuniq isn't stressing the board a little too much.Quote:
Originally Posted by Speederlander
Do you have a spare proc you can swap in?
This is discouraging. Everything came up so nice right off the bat and then this happens and it seems so odd.
The only thing I can think of was perhaps windows had nothing to do with it. There was a different problem (heat?) that took time to build up. But BIOS temps looked fine, and I even have it in a hot room, so 41*C idle (the average) seemed reasonable for a QX6700 given the ambients.
I will try my SI-128 first maybe. That uses pretty much the same mounting system as the stock heatsink, with the push pins.Quote:
Originally Posted by gtj
If that fails, I will try a different processor.
Does this BIOS fix the issue with C1E changing the multiplier even when disabled????Quote:
Originally Posted by cyber_terror
The backing plate of my tuniq was shorting out all kinds of vias and pads on the back of the board!!
I only had time to pull everything apart and check it out before I had to get back to work again, but it is obvious a lot of stuff was shorted. The new foam on the backing plate was flat as a pancake, so it must have stress relaxed overnight, explaining the delayed bullsh*t after it was initially doing fine. I will put on the SI-128 after work.
What are the odds I fried the CPU? Anyone? Please give me some hope I didn't just create a $1000 paperweight CPU because of backing plate foam...
if it works then it's fine, don't sweat it continue overclocking :D
looks like the BX2 will be on the top of my shopping list
If you're sticking with 32bit for now, disable the Marvell in BIOS for the install. Once Vista is succcessfully installed, re-enable the Marvell and install the drivers. If you still get the "unable to find a drive" message with only the Intel enabled, let me know, there's another work around that involves manually partitioning the drive.Quote:
Originally Posted by tom8881
I'm not an expert but EM64T is an emulation of 64 bit instructions on a natively 32-bit processor and while it allows access to more memory, the execution speed drops. I believe it was meant as a temporary solution until new processors come out. Can't speak for AMD.
Nope. I'm still engaged in an e-mail conversation with Intel about it.Quote:
Originally Posted by theonlybabyface
Not sure. Holding my breath for you.....Quote:
Originally Posted by Speederlander
Quote:
Originally Posted by gtj
Then it's useless to update to it. :rolleyes:
So I broke a pin in the bottom left hand corner of the socket, and wound up with 400x6 lol for 2.4ghz... I ordered a new board, but kinda funny found a multi breaking off a pin messin with mounting and remounting.
Which pin? Giot a pic?Quote:
Originally Posted by ChaosMinionX
QX6700 posts on my Asus board. Everything reads there and I can even overclock it. HAven't gone into windows since HD is unplugged but I think this means I am ok on the processor.Quote:
Originally Posted by gtj
I suspect the Intel board is zapped, which while bad, is FAAAAARRRRR less bad than zapping a LAPPED QX6700.
QX6700 posts into BIOS at 3.6GHz with 1.328v on my Asus. :eek:
Quote:
Originally Posted by gtj
I will get a pic of this board before I send it out, but heres a CPUZ
http://i11.photobucket.com/albums/a1...ionX/weird.jpg
I'd say you lucked out. :)Quote:
Originally Posted by Speederlander
I have an odd one. Received a replacement drive for my raid mirror today so I brought my PC down and swapped the drives out. When I went to restart it, it wouldn't post! The video card fan was running at full speed (I know when the fan slows down that the post is occurring), and nothing was displaying on screen. Needless to say I was pissed off, so I pulled the recovery jumper and tried to boot again. Still no post. Thinking it couldn't possibly be my memory but figured why-the-hell-not, I pulled all 4 sticks of my 2.3v required OCZ Titanium Alpha (always running at 4-4-4-12). Swapped in a stick of G.Skill HZ's and the damn thing booted.
I was happy to see my BIOS again, but I was only in it for a few seconds before it LOCKED up. Anyone else experience lockups in the BIOS? This isn't the first time this has happened to me. I have been running a mild OC on my e6600 @ 333fsb. Any idea what causes this?
Anyway, on to my original problem...
So I set the memory voltage to 2.36v, lower the FSB to 325 and put a stick of OCZ back in - STILL no post. Getting frustrated at this point, so I put the G.Skill back in so I can boot and up the voltage to 2.4v save & exit. Put all 4 sticks of OCZ back in and attempted to boot - STILL NO post. Turned off the power, back on again, and it finally posts! :eek: This seems like very flaky behavior to me. I'm not sure where the problem lies, and I'm not sure how to diagnose it. Do you think perhaps I should RMA my memory? I don't even want to restart my PC at this point... no idea if it'll want to come back up. :(
- Sker
Relax fella. So I made a mistake. From MC's online description it appeared to be the OEM version of the MB. Thanks for being so gracious in your retort.Quote:
Originally Posted by C'DaleRider
- Sker
did you try putting a load on the cpu?Quote:
Originally Posted by ChaosMinionX
because EIST doesn't get disabled...
the thing is, before cpu-z 1.39, i think a lot of people didn't know this or it was known but no one said anything in this thread (at least from what i can remember reading) because other programs including 1.38 didn't read the real clocks correctly.
Quote:
Originally Posted by shimmishim
interesting, let me check that.
-EDIT: wow it isnt disabled, stupid. So I just have a slow bootup from breaking a pin hte bios takes forever to load etc etc
but everything else works fine?
Quote:
Originally Posted by shimmishim
yes and no, the pin i bent and sort of broke off resulted in a freaking slow post, and some loss in performance I dunno what exactly it was, but I guess thats why they make more boards haha.
okay, this machine is driving me to distraction.
brand new bad axe 2 running bios 2333 according to cpu-z anyway.
if the machine soft resets it hangs.
if I cold boot, it's fine.
when I say hang, I mean immediately after posting. I get a blinking underscore top left of the screen and nothing else happens.
I have the secondary on board sata controller disabled as well as C1 and EIST in bios. everything else at this point is stock as I am getting the machine set first before I start overlocking it.
I've tried various search words like bad axe hang, bios hang etc but can't find anything that mentions this.
anyway got a suggestion?
try updating your biosQuote:
Originally Posted by lancer
hmmmm bit extreme.
isn't updating the bios for something like this more of a last resort?
I know a new bios got released a day or two ago and I know that an older bios, 2159? was buggy and should be avoided.