ASUS P5N-E SLI 650i Thread

[DADBBAD]

Originally Posted by SSJVegeta

How do I take the stock northbridge heatsink off without breaking the mobo or the black clips?

Just trying to be careful.

The black clips have wings on them that when pushed through cant be removed unless you go from the bottom of the board and push them together. Or grab them with some needle nose and pull till they break if you have replacements.

[pheoxs]

Originally Posted by DADBBAD

The black clips have wings on them that when pushed through cant be removed unless you go from the bottom of the board and push them together. Or grab them with some needle nose and pull till they break if you have replacements.

I just used needle nose pliers, pinched the bottom-side of it while gentle pulling upward and I removed them without destroying them.

[SSJVegeta]

Just replaced the stock heatsink with the Thermalright HR-05 SLI and my PC still reboots like before when I OC to 3GHz. In fact, its made no difference at all

I also reseated my Thermaltake Big Typhoon 120 and temps are the same too, hitting 60c at full load with 2.8GHz and 67c at full load with 3GHz.

With the case side panel off, temps drop 3-4c but PC still reboots with 3GHz.

Tried different northbridge volts upto 1.56v and upto 1.45v CPU vcore with +100mV set.

What a waste of time and money replacing the stock heatsink...

[pheoxs]

Originally Posted by SSJVegeta

Just replaced the stock heatsink with the Thermalright HR-05 SLI and my PC still reboots like before when I OC to 3GHz. In fact, its made no difference at all

I also reseated my Thermaltake Big Typhoon 120 and temps are the same too, hitting 60c at full load with 2.8GHz and 67c at full load with 3GHz.

With the case side panel off, temps drop 3-4c but PC still reboots with 3GHz.

Tried different northbridge volts upto 1.56v and upto 1.45v CPU vcore with +100mV set.

What a waste of time and money replacing the stock heatsink...

drop the LDT frequency to 4x, or maybe 3x ( i think its called LDT frequency, something like that) I had to lower mine to get 3ghz and 3.2ghz stable.

[Euthanasiast]

I wonder if someone could assist me in getting a stability issue resolved with this motherboard. I have been plagued with the dreaded NVLDDMKM.SYS error for weeks and I have done just about everything to combat it. I think I have it narrowed down to either RAM issues or mainboard settings. I was thinking I could get a general setup guide from those with similar setups to my own in an attempt to rid myself of this problem--which seems to be a stability issue.


The funny thing is that I have been running applications for months with the identical setup and then out of the blue I started receiving these error messages, and despite my attempts at EVERYTHING, I have still been unable to rid myslef of the problem. At this point it simply must be a problem with either my settings for the mainboard or the RAM.

The RAM that I am running is G.SKILL 6GB(3 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Model F2-6400CL5D-4GBPQ, The motherboard is obvious. I am running Vista Ultimate x64 and I have an 8800 GTX. I am currently overclocking my Core 2 Duo E6700 to 3.4ghz (yes I have tried setting back to stock to no avail).

What I am looking for from you guys is your stable setup for your mainboard and your RAM (especially if you have the same as I do) so I can compare and see where I may have something wrong. Currently the only way I can get Company of Heroes to run without bombing out is if I pull all of the RAM save for one stick as I have been seeing in research on the various forums that this is a temporary fix. I think it's entirely possible that I just have something setup wrong.

I'm not in front of the device at the moment, but I have the memory timings set manually and I will publish them the moment I get home.

Thank you in advance for your collective help in the matter.

Chris

[pheoxs]

Originally Posted by Euthanasiast

I wonder if someone could assist me in getting a stability issue resolved with this motherboard. I have been plagued with the dreaded NVLDDMKM.SYS error for weeks and I have done just about everything to combat it. I think I have it narrowed down to either RAM issues or mainboard settings. I was thinking I could get a general setup guide from those with similar setups to my own in an attempt to rid myself of this problem--which seems to be a stability issue.


The funny thing is that I have been running applications for months with the identical setup and then out of the blue I started receiving these error messages, and despite my attempts at EVERYTHING, I have still been unable to rid myslef of the problem. At this point it simply must be a problem with either my settings for the mainboard or the RAM.

The RAM that I am running is G.SKILL 6GB(3 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Model F2-6400CL5D-4GBPQ, The motherboard is obvious. I am running Vista Ultimate x64 and I have an 8800 GTX. I am currently overclocking my Core 2 Duo E6700 to 3.4ghz (yes I have tried setting back to stock to no avail).

What I am looking for from you guys is your stable setup for your mainboard and your RAM (especially if you have the same as I do) so I can compare and see where I may have something wrong. Currently the only way I can get Company of Heroes to run without bombing out is if I pull all of the RAM save for one stick as I have been seeing in research on the various forums that this is a temporary fix. I think it's entirely possible that I just have something setup wrong.

I'm not in front of the device at the moment, but I have the memory timings set manually and I will publish them the moment I get home.

Thank you in advance for your collective help in the matter.

Chris

First download memtest86, burn it to a cd and run it overnight to check if the ram is bad. then try perhaps only running two 2gb sticks, i've had some experiences with 3 sticks giving instability issues, perhaps just try two and see if you keep getting the error. not sure what else really it could be.

[Euthanasiast]

Originally Posted by pheoxs

First download memtest86, burn it to a cd and run it overnight to check if the ram is bad. then try perhaps only running two 2gb sticks, i've had some experiences with 3 sticks giving instability issues, perhaps just try two and see if you keep getting the error. not sure what else really it could be.

I plan on running memtest sometime in the next day or so. I already went to two sticks (which gave a performance boost in WEI because it meant I was running in dual channel mode, but the problem persisted. I am now running with one stick and so far (knock on wood) it has been running, though not with the same smack of a system with more RAM.

[slaney30]

Originally Posted by SSJVegeta

Just replaced the stock heatsink with the Thermalright HR-05 SLI and my PC still reboots like before when I OC to 3GHz. In fact, its made no difference at all

I also reseated my Thermaltake Big Typhoon 120 and temps are the same too, hitting 60c at full load with 2.8GHz and 67c at full load with 3GHz.

With the case side panel off, temps drop 3-4c but PC still reboots with 3GHz.

Tried different northbridge volts upto 1.56v and upto 1.45v CPU vcore with +100mV set.

What a waste of time and money replacing the stock heatsink...

Not necessarily, try dropping you cpu multiplyer at the same FSB and see what happens. Also definitely drop your LDT to like 2x. It would help to know what your temps are like under idle and load....

[pheoxs]

Originally Posted by Euthanasiast

I plan on running memtest sometime in the next day or so. I already went to two sticks (which gave a performance boost in WEI because it meant I was running in dual channel mode, but the problem persisted. I am now running with one stick and so far (knock on wood) it has been running, though not with the same smack of a system with more RAM.

If it works fine with just one stick, but not two, perhaps slightly raise the voltage for the RAM, make sure its manually set at the rated specs. Also try different combinations in sets of two, maybe just one of the sticks is bad and thats whats messing it up.

[Euthanasiast]

Good idea, I'll try that as well.