Motherboard/Video Card Issue!!! Urgent Help Needed!!!

[bunit]

which part the mem test, or 1 stick of ram?

 

I need to do both, but i am at work right now. I just got the system back together today so I havent had a lot of time for even more diagnostics.

 

Plus its making me too frustrated I needed to take a break.

[cull]

one stick

 

you need to take a break, on my first cheepy build, i put a hole through an $80 mobo when trying to use a flat head screw driver to put the hsf on. It was partially an acident and I kinda did it on purpose : )

[bunit]

is it better to use the orange or yellow dimm slots?

[espeed]

use the orange slot closest to the edge of the board, and start with one stick. mem test it for about an hour or so i guess and just check it doesnt poo itself in windows like you described. Try the other stick, if it happens on one and not the other you know what the issue is.............

 

also make sure you keep to rated timings for the ram

[bunit]

now the rated timming would be the ones from this site correct ? http://www.bleedinedge.com/forum/sh...143&postcount=2

 

Tommorow, maybe even saturday ill test it out. Im working all night tonight and tommorow night so i probably wont feel like it tommorow. But I am determined to get this fixed ASAP, it has been too much of a problem.

[bunit]

Also do I need to set the voltages to match as well ?

[bunit]

Here is my most recent update on this issue, I have requested a RMA for my ram and I will be sending them back ASAP.

 

Now so far the tests I have tried is setting the timmings recommended at http://www.bleedinedge.com/forum/sh...143&postcount=2.

 

The following are the timmiring I have set:

 

FSB Bus Frequency............................. 200

LDT/FSB Frequency Ratio....................... Auto

CPU/FSB Frequency Ratio....................... auto

PCI eXpress Frequency......................... 100

 

CPU Voltage .................................. 1.400v

LDT Voltage .................................. 1.30v

ChipSet (NF4) Voltage ........................ 1.60V

DRAM Voltage ................................. 2.60V

+0.03 if not 3.2V ............................ enabled

 

Memclock (DRAM Frequency) .................... 200

1T/2T Timing (Command Per Clock).............. 1T

CAS Latency (Tcl)............................. 2

RAS# to CAS# delay (Trcd)..................... 2

Min RAS# active time (Tras)................... 8

Row precharge time (Trp)...................... 2

Row Cycle time (Trc).......................... 10

Row refresh cyc time (Trfc)................... 16

Row to Row delay (Trrd)....................... 3

Write recovery time (Twr)..................... 3

Write to Read delay (Twtr).................... 2

Read to Write delay (Trwt).................... 3

Refresh Period (Tref)......................... 3120

DRAM Bank Interleave.......................... Enabled

 

DQS Skew Control.............................. Auto

DQS Skew Value................................ 0

DRAM Drive Strength........................... Weak 3 (Level 5)

DRAM Data Drive Strength...................... Level 2

Max Async Latency............................. 8ns

DRAM Response Time............................ Normal

Read Preamble Time............................ 6ns

IdleCycle Limit............................... 256

Dynamic Counter............................... Disable

R/W Queue Bypass.............................. 16x

Bypass Max.................................... 7x

32 Byte Granularity........................... Disable (4 Bursts)

 

Now the only thing I havent changed in the CPU Voltage. I am not sure what the LDT Voltage is or does?

 

Now What I have noticed is that running 1 stick of ram in DIMM Slot 1 with the above timmings, 1 stick boots and runs fine and the other does not even load windows and will continue to reboot, So I guess 1 stick is toast for sure, not the next thing, is the one stick that will boot and run fine for the most part will eventually still lock up and turn the screen black forcing a reboot. Now I do not get any error messages, and it will run fine for about 5-10mins or so. So there still seems to be something wrong. Now I am currently running in safe mode and there is no issues so far, so what seems odd is if there is a memory issue why is it not doing it now in safe mode??

 

I am going to run memtest and a few other tests on my system tommorow before I RMA the ram just to see what happens.

 

Now is there anything else other then the ram that would cause this? And when I run the memtest should I run 1 stick at a time?

 

I have also update my screenshots as well.

 

Thanks guys.

[bunit]

any ideas?

[Minsc]

FSB Bus Frequency............................. 200

LDT/FSB Frequency Ratio....................... Auto

CPU/FSB Frequency Ratio....................... auto

PCI eXpress Frequency......................... 100

 

CPU Voltage .................................. 1.400v

LDT Voltage .................................. 1.30v

ChipSet (NF4) Voltage ........................ 1.60V

DRAM Voltage ................................. 2.60V

+0.03 if not 3.2V ............................ enabled

 

Memclock (DRAM Frequency) .................... 200

1T/2T Timing (Command Per Clock).............. 1T (Set this to 2T, aka disabled)

CAS Latency (Tcl)............................. 2 (Set this to Auto)

RAS# to CAS# delay (Trcd)..................... 2(Set this to Auto)

Min RAS# active time (Tras)................... 8(Set this to Auto)

Row precharge time (Trp)...................... 2(Set this to Auto)

Row Cycle time (Trc).......................... 10(Set this to Auto)

Row refresh cyc time (Trfc)................... 16(Set this to Auto)

Row to Row delay (Trrd)....................... 3(Set this to Auto)

Write recovery time (Twr)..................... 3(Set this to Auto)

Write to Read delay (Twtr).................... 2(Set this to Auto)

Read to Write delay (Trwt).................... 3(Set this to Auto)

Refresh Period (Tref)......................... 3120(Set this to Auto)

DRAM Bank Interleave.......................... Enabled (Set this to Disabled)

 

DQS Skew Control.............................. Auto

DQS Skew Value................................ 0 (Set this to Auto)

DRAM Drive Strength........................... Weak 3 (Level 5)(Set this to Auto)

DRAM Data Drive Strength...................... Level 2(Set this to Auto)

Max Async Latency............................. 8ns(Set this to Auto)

DRAM Response Time............................ Normal

Read Preamble Time............................ 6ns(Set this to Auto)

IdleCycle Limit............................... 256 (Set this to Auto)

Dynamic Counter............................... Disable(Set this to Auto)

R/W Queue Bypass.............................. 16x(Set this to Auto)

Bypass Max.................................... 7x(Set this to Auto)

32 Byte Granularity........................... Disable (4 Bursts)(Set this to Auto)

 

I did this on my goofy Corsair memory and it worked. With further exploration it showed it wasn't all the Autos the mattered as much as using known-good settings for those, and then using 2T and no Bank Interleave, which my memory doesn't hate.

 

I just replaced it with G.Skill DDR500 memory which writes at 1 GB/s faster because it supports 1T and Bank Interleave even when clocked at 250 FSB.

 

 

1-stick at a time is always a good method for testing. If they both pass, put them both in yellow slots to disable Dual Channel and test that. If that passes and it only crashes in Dual Channel, well that's something.

 

I don't think you're ready to RMA that memory yet, you're just giving up. I was told after I bought my Corsair that it's really bad, won't work, etc with my board, but I made it work. Wasn't as good as other memory but memory speed increases don't affect benchmarks and games that much anyway. This supposedly unworkable memory stayed in my system running 24/7 overclocked at 250 MHz (as high as 275 stable at times) for over a year.

[gil_grissom]

my pc was freezing and restarting a horrible amount of times... after . loads of testing everything I found out that the pc worked fine with catalyst not running... so yes there are still little glitches here and there. lol