Ratdude's Main rig V3.5

[ratdude747]

Re: Ratdude's Main rig V3.5

I'm not worried. the drive it's replacing had 27... and given that what killed it wasn't a platter issue, it should be fine.

[Uranium-235]

Re: Ratdude's Main rig V3.5

they will ether get marked bad and you'll be fine

or its the beginning of some worse problem and its only the tip of the iceberg

[Ami Sapphire]

Re: Ratdude's Main rig V3.5

May be fine, may not be. I have two HDDs with >400 bad sectors and they still work properly. They're both Seagate drives, too.

[ratdude747]

Re: Ratdude's Main rig V3.5

Hdd came in, smart says it has 15 Bad sectors. Wish me luck.

[shovenose]

Re: Ratdude's Main rig V3.5

Moving this thread back on topic...

Anyway, it looks like it's gonna be 8gb @400... 16gb @266 with all the cards installed and all did the same crap 400 did a few minutes ago. Took out 8gb, (one DIMM per channel) and bumped it back to 400 and all is well (so far).

Kinda sucky... but at least I have Spare RAM modules now.

edit- I looked things up, I'm very wrong. (shovenose, you may virtually kick me in the face). My understanding was that x86-64/EMT64 used both 64 bit words and addresses... now that I look, words (or operands specfically) are still 32 bit. Instructions are indeed 64 bit though.

My apologies. Please, if you do hang me, use the long drop (the short drop is far more brutal).

I just get the satisfaction of being right. It's all good I'm not going to kick you in the face or hang you ... injured/dead people can't buy stuff from me

[RJARRRPCGP]

Re: Ratdude's Main rig V3.5

May need more VDIMM. Or time to clean the slots.

[ratdude747]

Re: Ratdude's Main rig V3.5

Moving this thread back on topic...

Anyway, it looks like it's gonna be 8gb @400... 16gb @266 with all the cards installed and all did the same crap 400 did a few minutes ago. Took out 8gb, (one DIMM per channel) and bumped it back to 400 and all is well (so far).

Kinda sucky... but at least I have Spare RAM modules now.

edit- I looked things up, I'm very wrong. (shovenose, you may virtually kick me in the face). My understanding was that x86-64/EMT64 used both 64 bit words and addresses... now that I look, words (or operands specfically) are still 32 bit. Instructions are indeed 64 bit though.

My apologies. Please, if you do hang me, use the long drop (the short drop is far more brutal).

[mariushm]

Re: Ratdude's Main rig V3.5

Please do, because that's news to me.

Even if you directly port 32bit programs to 64bit executables, you don't get twice the memory usage.... and it's the first time I hear about memory addressing making applications use twice the memory.

For example, let's say an application holds a bitmap or an icon in memory, using 4 bytes (32bits) for each pixel (red,green,blue, alphablending/transparency).. when you port the application to 64bits, you won't suddenly have 8 bytes per pixel, only the one variable holding the location in memory of the bitmap changes from 4 bytes to 8 ... so you get 4 bytes extra per pointer.

Sure, the OS would use a bit more memory as well to keep track of each app's memory pool but there's things like binary trees and so on on, the os doesn't just double the ram it uses and blocks it, that's silly... and even if it does we're talking a few hundred mb at best from 8-16 gigs.

Anyway, I'm gonna stop, like i said it's off topic.

[ratdude747]

Re: Ratdude's Main rig V3.5

Not going to start discussion (at least i hope so) but no, 64 bit operating systems don't use twice the memory.
The memory usage does increase a bit, but only by about 10-15% and 32bit applications running on 64bit windows would use the same amount of memory as on 32bit OS.

On that old system, you would be fine even with 8 GB of memory, but it's not worth dropping down to 8 or 12 just to get higher frequency.

The reasons which I won't go into actually are at the core of memory addressing (I took a college digital class where we actually built memory arrays with bare IC's). There are ways around it, which if done properly can often reduce the effects. However, with directly ported x32 programs, it will use double the ram. I may write a thread on how this works...

[mariushm]

Re: Ratdude's Main rig V3.5

Yeah

8gb is what V2 had, and it was more than plenty... but that was x32, this is x64 so I'll be using double the RAM (or roughly so). I'll probably run 16gb to start and see where my RAM usage is, and then decide.

*please no x32 vs x64 discussions here, if you want me to explain why this is, I'll make a new thread*

Not going to start discussion (at least i hope so) but no, 64 bit operating systems don't use twice the memory.
The memory usage does increase a bit, but only by about 10-15% and 32bit applications running on 64bit windows would use the same amount of memory as on 32bit OS.

On that old system, you would be fine even with 8 GB of memory, but it's not worth dropping down to 8 or 12 just to get higher frequency.

[ratdude747]

Re: Ratdude's Main rig V3.5

TBH, I think that unless you're actually using applications which need more than 8GB (which few do), then you're better off with 8GB at 400MHz. The speed of the RAM will always be an improvement (at least in theory), but the amount won't make a difference unless you actually use it

My thoughts exactly. Hence why I'll try 16gb and see how much actully use, and if I'm nowhere close to breaking 8gb, pull 4 modules and drop the speed.

[c_hegge]

Re: Ratdude's Main rig V3.5

TBH, I think that unless you're actually using applications which need more than 8GB (which few do), then you're better off with 8GB at 400MHz. The speed of the RAM will always be an improvement (at least in theory), but the amount won't make a difference unless you actually use it

[ratdude747]

Re: Ratdude's Main rig V3.5

^
Honestly, I'd run the RAM clock @ 266 and call it a day. Unless you're doing some really memory-intensive things like massive rendering applications, you won't really feel it.

I see. V2 ran at 266 as well... I'll see how my RAM usage is under load and see what I get.

[Topcat]

Re: Ratdude's Main rig V3.5

^
Honestly, I'd run the RAM clock @ 266 and call it a day. Unless you're doing some really memory-intensive things like massive rendering applications, you won't really feel it.

[ratdude747]

Re: Ratdude's Main rig V3.5

removed the last DIMM in each channel. Won't run in dual channel (atleast the bank that's missing a DDIMM), but it was all detected. Run 8GB if you want full dual channel @ 400MHz.

Yeah

8gb is what V2 had, and it was more than plenty... but that was x32, this is x64 so I'll be using double the RAM (or roughly so). I'll probably run 16gb to start and see where my RAM usage is, and then decide.

I'm not big on mixed single/double channel setups, as it leads situations resembling clock skew.

*please no x32 vs x64 discussions here, if you want me to explain why this is, I'll make a new thread*

[Topcat]

Re: Ratdude's Main rig V3.5

removed the last DIMM in each channel. Won't run in dual channel (atleast the bank that's missing a DDIMM), but it was all detected. Run 8GB if you want full dual channel @ 400MHz.

[ratdude747]

Re: Ratdude's Main rig V3.5

I ran 12gb @ 400MHz when I was using it for some GPU/SLI and gaming tests. When I began using it as a server (of sorts), I put all 16gb in and clocked the RAM speed down to 266, and it was fine, 100% stable....and as a server, I didn't even feel the downclock.

No problem bud....I ran into this same problem with mine, and was scratching my head....and upon research, experimenting, and some select 4-letter words, I figured it out.... haha

How were you doing 12gb?

This board will only do 1, 2, or 4 DIMMs per CPU... not 3.

Clarify?

[RJARRRPCGP]

Re: Ratdude's Main rig V3.5

Just a hint with this board, if all DIMM's are populated, you can not run the RAM at full speed (400MHz), it will crash (BSoD0, fail MEMTEST, and cause all kinds of havoc. .

Back in 2004, I may have uncovered a bug with the Asus A7N8X family. (or the nForce2 chipset)


Memtest86 failed at anything higher than 195 Mhz. After 195, it was at least roughly 1.5 errors per Mhz.
I got at least 1 error at 196 Mhz and 10 errors at 200 Mhz within 1 hour, IIRC.

I dunno if it was even the RAM, even though it was with only PC2700.

[Topcat]

Re: Ratdude's Main rig V3.5

I owe you big time. Good call. Stepped it down to 266, all is well with all 16gb.

So, I can pick either Faster RAM or more RAM.

Thoughts and ideas?

Edit- tried 333 and 366, no dice. I wonder if that's partially why V3.0 never ran well (I ran all 16GB at 400)... But given the AGP issues on all but Xp x64, It wasn't viable in the long run.

I ran 12gb @ 400MHz when I was using it for some GPU/SLI and gaming tests. When I began using it as a server (of sorts), I put all 16gb in and clocked the RAM speed down to 266, and it was fine, 100% stable....and as a server, I didn't even feel the downclock.

No problem bud....I ran into this same problem with mine, and was scratching my head....and upon research, experimenting, and some select 4-letter words, I figured it out.... haha

[ratdude747]

Re: Ratdude's Main rig V3.5

Found the COD of the dead hdd... bad I/O board. it's not spinning up and a specifc part of the baord gets really hot...

I may see how cheap I can find another disk... as the only point in saving this one is to maintain a corruped xp x64 install (haven't redone the array just yet). That would save me maybe 30 mins... but given that it has 27 bad sectors, I don't see putting good money after bad.

edit:

Bid on this:

http://www.ebay.com/itm/Western-Digi...torefresh=true

Offered on this:

http://www.ebay.com/itm/Western-Digi...torefresh=true

As I don't think anybody here on BCN has any WD740's sitting around... if you do, then if the following doesn't work out, then let me know.