Strange problem

[SmoulderingCircuits]

My ram is rated 9-9-9-24 @1.5v but actually runs @1.57v when below 1333Mhz rated speed. So @1.6v I had 8-8-8-22 timings stable. Then I tryed 8-8-8-20 @1.65v which booted into windows fine but then I couldn't open Ai Suite to change my fan speeds more than once in the same session. And now even changing fan speeds in CCC is causing problems.

Whenever I change any fan speeds, the next session I will boot into windows then the screen will turn into vertical stripes alternating grey and whatever colour the cursor was on. Yet this is on 1237Mhz @1.57v/ Auto which has been stable for months back at the sock 9-9-9-24 timings. The system behaves normally so long as I don't change fan speeds the previous session.

Now I have a hunch I have corrupted some files but no idea if reinstalling Ai Suite will solve anything.

Any ideas?

[System is Crysis 2 @Ultra stable and P95 blend stable]

 

[AdrianD2]

Just put the RAM back to stock, it's not hurting you.

 

[SmoulderingCircuits]

Just put the RAM back to stock, it's not hurting you.

Read my post again

 

[Scoob]

Hi,

Sound like your motherboard isn't detecting the ram properly, which is a little worrying. Possibly there's a BIOS update to address the issue?

When I first upgraded to my 2500k with 2x 4gb Vengeance @ 1600 with 9,9,9,12 timings I was using a cheaper MSI motherboard. This board wanted to run my memory at 1.65v by default, at 1333mhz but with the correct timings for 1600mhz! A bit messed up plus I didn't want to over-volt and under clock my new memory on first power up! Especially considering Sandy B. is supposed to be pretty sensitive to that sort of thing.

I had to enable the XMP memory profile stuff for it to read the memory correctly, as this wasn't on by default.

On my replacement motherboard, an ASUS P8Z68-V Pro, it detected everything correctly except it was at 1333. Again enabling XMP sorted everything.

In principle I'm fine overvolting CPU, ram, GPU etc, when overclocking but having the motherboard do it incorrectly is worrying.

I assume for your memory 1.57v isn't so bad (within tolerances), I guess I just like control over exactly what's set. Obviously you're running an AMD system, I'm not really familiar with their newer stuff. Last time I play around was with a Phenom tri-core and my last personal AMD rig was a 2400+

Still, some very odd symptoms you're getting there. Usually I'd put any sort of striping on the screen down to VRam.

I had some memory fail a few years back. Having no error checking it proceeded to corrupt basically EVERYTHING it wrote to disk. Ironically I'd performed a HUGE backup and restore processs (to new drives) when I had this error (I didn't know at the time obviously) and it corrupted pretty much everything.

Things like my MSDN iso files...I could mount say the Office DVD, it'd start to install but would crap out with an error part-way through. Loads of other installers etc. were like this too. Luckily I could of course just re-download from MS, but things like all my development folders were basically toast.

On a related note: I find when overlclocking - so including RAM - an unstable overclock can often get me into windows but things like gadgets and the like fail. This is the first sign of instability.

Cheers,

Scoob.

 

[tinytomlogan]

@ Scoob

Motherboards normally run at 999-24 1333mhz stock. You normally have to manually set the ram to get it to run at rated

 

[Scoob]

@ Scoob

Motherboards normally run at 999-24 1333mhz stock. You normally have to manually set the ram to get it to run at rated

Hi,

Sandy B. works a little differently it seems, well at least in my fairly limited experience. On the three systems I've built they've defaulted to slack timings @ 1333 but as soon as you enable XMP it switches the ram to it's rated speeds and voltages. XMP is something that's present on RAM "designed for Sandy B." I think the older ram will likely work, but may need things to be set manually. I know setting XMP to "on" is a manual process, but it does the rest for you just enabling that one feature.

I've jumped from an older socket 775 Q6600 to Sandy B. so not sure what the Intel chips in between did. Interestingly both my Q6600 and Q6700 systems, on P35 and P45 motherboards respectively, got the timings bang on by default, as per the Rams spec. No need to change anything at all.

Cheers,

Scoob.

 

[SmoulderingCircuits]

Hi,

Sound like your motherboard isn't detecting the ram properly, which is a little worrying. Possibly there's a BIOS update to address the issue?

When I first upgraded to my 2500k with 2x 4gb Vengeance @ 1600 with 9,9,9,12 timings I was using a cheaper MSI motherboard. This board wanted to run my memory at 1.65v by default, at 1333mhz but with the correct timings for 1600mhz! A bit messed up plus I didn't want to over-volt and under clock my new memory on first power up! Especially considering Sandy B. is supposed to be pretty sensitive to that sort of thing.

I had to enable the XMP memory profile stuff for it to read the memory correctly, as this wasn't on by default.

On my replacement motherboard, an ASUS P8Z68-V Pro, it detected everything correctly except it was at 1333. Again enabling XMP sorted everything.

In principle I'm fine overvolting CPU, ram, GPU etc, when overclocking but having the motherboard do it incorrectly is worrying.

I assume for your memory 1.57v isn't so bad (within tolerances), I guess I just like control over exactly what's set. Obviously you're running an AMD system, I'm not really familiar with their newer stuff. Last time I play around was with a Phenom tri-core and my last personal AMD rig was a 2400+

Still, some very odd symptoms you're getting there. Usually I'd put any sort of striping on the screen down to VRam.

I had some memory fail a few years back. Having no error checking it proceeded to corrupt basically EVERYTHING it wrote to disk. Ironically I'd performed a HUGE backup and restore processs (to new drives) when I had this error (I didn't know at the time obviously) and it corrupted pretty much everything.

Things like my MSDN iso files...I could mount say the Office DVD, it'd start to install but would crap out with an error part-way through. Loads of other installers etc. were like this too. Luckily I could of course just re-download from MS, but things like all my development folders were basically toast.

On a related note: I find when overlclocking - so including RAM - an unstable overclock can often get me into windows but things like gadgets and the like fail. This is the first sign of instability.

Cheers,

Scoob.

It's doing it at stock. But like I said, only when I change any fan speeds previous session - and only since I overclocked - but I don't have the ram overclocked any longer

 

[SmoulderingCircuits]

@ Scoob

Motherboards normally run at 999-24 1333mhz stock. You normally have to manually set the ram to get it to run at rated

It runs it correct timings and frequency by stock but the auto voltage is 1.5v @1333Mhz yet 1.57v @1237Mhz

It was stable for yonks so I didn't change it manually