YellowPeril
Gawd
- Joined
- Nov 20, 2003
- Messages
- 666
i just want to say that i hate you... ![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
![]()
Here is my testing setup. Surrounded by stackers. ^_^
DaCoOlNeSs said:what kind of monitor is that?
SelRahc said:Well, ran into yet another problem with my system (naturally... its ALWAYS my system)
It appears that I got a bad 512mb from crucual. I ran the memory tester they recommended and got nothing but errors on 1 of them. /cry
Initiated RMA on it through crucial. I am hoping this is the reason for the minor quirks I have been having.That makes me so upset.....
I've been working on the FRAPS for the Nvidia system. Now if I could only get my wife to benchmark the software rather then play it HAHA. Farcry @ 1600x 4aa max settings looks SOOOOOOO nice ^_^
EDIT : by the way, i find stackers to be very ugly. Why didnt you get like lian li v2000/21000/2000b/2100b ????
the_village_treky said:my god, and i thoght I had to much money on my hands(belive me, i would be building a 5k rig right now if i had my own credit card)
Impulse said:Memory problem != memory conflict... If whatever issues you're having are resolved by switching memory or whatnot then it's a conflict, not their fault but still related to the memory and/or the mobo.
SelRahc said:See I would have kinda thought that too, but the other stacker is running perfectly fine with no problems at all.... and using the same memory. I'm going to trade them out later, but do you think that still could be the issue?
If they're both running the same mobos I wouldn't think one could have issues with the RAM and not the other, unless Crucial is using different chips on the same RAM but they use their own chips AFAIK and it's a new model so I really doubt it. I'm at a loss, sounds like it's magical parts time, trial by error.SelRahc said:See I would have kinda thought that too, but the other stacker is running perfectly fine with no problems at all.... and using the same memory. I'm going to trade them out later, but do you think that still could be the issue?
LyCoS said:EDIT : by the way, your airflow isnt optimal...
the PSU on the bottum, even tho it isnt really conventional, its better. and exaust fans on the bottom serv beens. everyone nows how hot (not) USB/firewire and IO headers get...
put the PSU at the bottom and the exaust fans at the top...
SelRahc said:Oya. This is a temporary setup. Once my water cooling gets in, the PSU will go to the bottom and a 2x120mm rad will go on top, as well as the 2 80mm exhausts.
yup yuppers.
PS: I'm ganna run that test tonight. Thanks.
SelRahc said:Got it, ran it, errors up the wazoo. I'll know exactly which one today cause ill test each one, but the memory is bad. Thanks for the link.
SelRahc said:It seems I was mistaken??
The memory errors when run together, but when tested individually, there are no errors after 6 hours memtest86 runtime on each one. Also, when they are run together on single channel, they run fine as well. When run together in DULE channel mode, errors within minutes. So its dule channel mode that's failing me.
I have a troubleshooting thread established to discuss this problem, so please take a look for the latest info and to discuss it there. There is more information post there as well. That way we dont fill the project log up with troubleshooting posts
>>> THE THREAD <<<
Thanks
LyCoS said:by dule understand dual![]()
SelRahc said:Yes dual. Sorry my speelink is baad. It honestly feel like a duel to me though. I have only been fighting with this system haha.. >.<
As for the unused parts, I'll sell them probably.