Yeah, at worse the Voltages are ~0.03v below, normally above the specified rail though. At least RAM isn't a hassle to change over at all. Still, FIVE AND A HALF DAYS!!! GAAAAAHH!! If I didn't have my laptop I think I would go insane.
God damn Twinmoss RAM, always hated it, always....
I've had a personal 5 days of A64 hell, I hear ya mate, I hear ya.
CPU didn't show up, then the first board was a dud, second board wouldn't post. Then after two days.. discovered RAID controller PCI card wasn't compatible... then had to lose 512mb of my DDR ... fun fun fun.
I've had a personal 5 days of A64 hell, I hear ya mate, I hear ya.
CPU didn't show up, then the first board was a dud, second board wouldn't post. Then after two days.. discovered RAID controller PCI card wasn't compatible... then had to lose 512mb of my DDR ... fun fun fun.
I want to lie, shipwrecked in comotose, drinking fresh, mango juice. Gold-fish sholes, nibling at my toes, fuuun fuuun fuuuun, in the suuun suuuun suuun.........
Then this must be your week then shorty. So kingston is the way to go. Well so far i've only been able to find shops that sell pc3000 and pc3500. Which should i choose. Is it worth going for the bigger since i'll prolly just run things stock.
Are you sure it was PC3000? Not PC3200? As I have never seen PC3000 anywhere....
If you are going stock then get PC3200 with the lowest timings you can find (2-2-2-5-CMD1 is pretty much it).
What silly numbers. But yeah, I would say PC3200 is the lowest. PC3000 probably came out in the very early days of PC3200 when maufactuers were trying to get the fastest RAM possible but some couldn't cut it.
Hmm... Not sure the serial number of mine, I'll have to check later as all my invoice says is "TwinMOS PC3200 DDR-DIMM 512MB w/Winbond Memory 184-P (for DDR-PC400MHz)".
Yeah, it can't be RAM related. As Prime95 ran fine for 3 hours before I went to bed, and F@H ran all night without errors, but about 15 minutes after me using the machine, nothing moved but the mouse, and then complete lock-up (with the HD light stuck on).
Enverex, is there a setting in bios where you can set it to DDR 333 but still push the fsb up?
Doesn't matter what I set the RAM to. I even set it to DDR200 before (effective) but it would still lock up randomly. Me and Shorty came to the conclusion that the RAM isn't compatible (read back through the thread) as he has the same problem and the same RAM. Thus, we have both ordered some Kingston HyperX instead.
Other news, not problem related: The boards max seems to be 233 as if I go any higher the screen turns to garbage when the framebuffer is initiated. The processor is perfectly stable at 2.3GHz @ 1.65v, but needs more voltage to go higher (2.32Ghz @ 1.65v errors out in Prime95), which I don't want to do as then it starts topping out just over 63'c. So, better cooling is needed for higher speeds. Another thing is that I don't seem to be able to use AGP 8x at anything other than default speeds, but that isn't really an issue as it does next to nothing.
I have a feeling, contrary to popular belief, this is actually upping the PCI and AGP bus too, not just the CPU <<>> MEM controller, so that may explain the graphics manglage at 234MHz+ FSB.
That makes me think.... F@H only uses about 11MB, and Prime was on Processor only test mode using 8MB of RAM, which may explain why those don't cause the computer to crash, which gives more value to the "It's the RAM" argument.
Ive isolated when I get my freezes... if this helps...
When Im accessing one of my hard drives. That's the only time and only my slave WD 120gb JB drive.
When just working on things.. and so on.. the PC goes like crap off a shovel.
Thats also interesting as mine seems to lock up when I try to do lots of things at the same time, i.e. when my PC is still booting, if I tell it to open Trillian, Firebird and other things at the same time. It also seems to make sense with the crash I had in Far Cry when it was loading, I tried to move which makes it load more... basically, whenever the hard-drive was hammered...
Though, that still could be RAM related due to Read/Write caching...
One bad thing about the motherboard though. OTES is noisy and pointless. It's noisy because its a fast small fan, and it's pointless as everyone nowerdays have an 80mm fan on the bottom of their PSU which does a better job, which OTES just gets in the way of, best thing to do it set the low speed to 60'c and the high to 70'c so it never turns on.
Right, yes, it's hard-disk access. I just had 12 pictures from Gunship 2000 I had taken, still open in PSP, saved a crop mask, and the instant I hit "Save" it locked up. ARGH. Got to take them all again now (taking them so I can add the game to my gallery for people).
I'm getting the same lockups when attempting to run more than 1.8Vcore and 2.4GHz+. No errors in prime95...runs fine for anything from 30min to 2hours, then decides to lockup out of the blue. I'm going to try a few things
I have had this issue with several SocketA mobos in the past. Disabling ACPI or "CPU Disconnect" usually fixed the problem on those boards. It's a power saving feature that shuts down most of the CPU when idle. The extremely low idle temps I'm getting indicates that a similar feature is active on my A64 setup. DeltaT from idle to full is ~15-20°C on water.
I don't have the means to check this out (would need an ocsilloscope), but my theory is that the CPU powersupply (MOSFET's, Coils and caps) is unable to maintain a noiseless Vcore feed when the load spikes from say 20% to 100% power drain
Hmm.... seems that this board can't actually go any higher than 228 due to the unlocked PCI/AGP bus (a while in 3D the GFX card just shuts off) .
I may be giving the proc too much voltage. I'll see how it copes with lower levels... EDIT: Ah, 1.8, not 1.58. Nevermind.
EDIT: Nope, seems the nForce3 would have been a better choice as 3D doesn't work above 228 and 2D doesn't work above 233. Even though via may have a lead normally, I'm sure the increased speeds would have more than made up for it :shakehead
Tried turning off Fastwrites, has no effect on anything. As I said about AGP 8x before, doesn't work at anything other than default, I have it set to AGP 2x the rest of the time. I cant find anyway of dissabling SBA, but that wont be much help at other times when I cant dissable it as I wont be able to get into the OS or whatever. Hmm, may be interesting to try my Voodoo 3 (or GF4 MX) and see if I can boot into Windows above 234 (just out of interest)...
Comments
If your voltages look clean in your BIOS.. then I sounds more like DDR to me.
God damn Twinmoss RAM, always hated it, always....
CPU didn't show up, then the first board was a dud, second board wouldn't post. Then after two days.. discovered RAID controller PCI card wasn't compatible... then had to lose 512mb of my DDR ... fun fun fun.
I want to lie, shipwrecked in comotose, drinking fresh, mango juice. Gold-fish sholes, nibling at my toes, fuuun fuuun fuuuun, in the suuun suuuun suuun.........
If you are going stock then get PC3200 with the lowest timings you can find (2-2-2-5-CMD1 is pretty much it).
It does exist but i think i'll go with the 3500 just in case i do feel like up the clock sometime.
http://www.abit.com.tw/test_report/KV8-MAX3/index.php
Shorty has already linked to that.
When Im accessing one of my hard drives. That's the only time and only my slave WD 120gb JB drive.
When just working on things.. and so on.. the PC goes like crap off a shovel.
Doesn't matter what I set the RAM to. I even set it to DDR200 before (effective) but it would still lock up randomly. Me and Shorty came to the conclusion that the RAM isn't compatible (read back through the thread) as he has the same problem and the same RAM. Thus, we have both ordered some Kingston HyperX instead.
Other news, not problem related: The boards max seems to be 233 as if I go any higher the screen turns to garbage when the framebuffer is initiated. The processor is perfectly stable at 2.3GHz @ 1.65v, but needs more voltage to go higher (2.32Ghz @ 1.65v errors out in Prime95), which I don't want to do as then it starts topping out just over 63'c. So, better cooling is needed for higher speeds. Another thing is that I don't seem to be able to use AGP 8x at anything other than default speeds, but that isn't really an issue as it does next to nothing.
I have a feeling, contrary to popular belief, this is actually upping the PCI and AGP bus too, not just the CPU <<>> MEM controller, so that may explain the graphics manglage at 234MHz+ FSB.
That makes me think.... F@H only uses about 11MB, and Prime was on Processor only test mode using 8MB of RAM, which may explain why those don't cause the computer to crash, which gives more value to the "It's the RAM" argument.
Thats also interesting as mine seems to lock up when I try to do lots of things at the same time, i.e. when my PC is still booting, if I tell it to open Trillian, Firebird and other things at the same time. It also seems to make sense with the crash I had in Far Cry when it was loading, I tried to move which makes it load more... basically, whenever the hard-drive was hammered...
Though, that still could be RAM related due to Read/Write caching...
I have my hopes
Have you ordered yours yet? and if so, when does it arrive?
I have had this issue with several SocketA mobos in the past. Disabling ACPI or "CPU Disconnect" usually fixed the problem on those boards. It's a power saving feature that shuts down most of the CPU when idle. The extremely low idle temps I'm getting indicates that a similar feature is active on my A64 setup. DeltaT from idle to full is ~15-20°C on water.
I don't have the means to check this out (would need an ocsilloscope), but my theory is that the CPU powersupply (MOSFET's, Coils and caps) is unable to maintain a noiseless Vcore feed when the load spikes from say 20% to 100% power drain
I may be giving the proc too much voltage. I'll see how it copes with lower levels... EDIT: Ah, 1.8, not 1.58. Nevermind.
EDIT: Nope, seems the nForce3 would have been a better choice as 3D doesn't work above 228 and 2D doesn't work above 233. Even though via may have a lead normally, I'm sure the increased speeds would have more than made up for it :shakehead
Yes, the NF3 has locked AGP but unfortunatly not PCI
Yes, I'm just testing high Vcore. If I only found a way to disable CPU Disconnect on this board. Do you have that setting on your board?
No CPU disconnect type options on the BIOS