Warning! Aegis might kill your ram!

[negev]

So I was trying to get my ram timings tighened up and I found a review of the sticks I have to compare settings, anyway I was experimenting and decided to open Aegis and drop the vdimm down a couple of notches from 2.1v. As soon as I did this, Aegis suddenly reported 2.89v vdimm!!!! I panicked but before I could do anything the box bluescreened.

It's booted back up now, I just hope they aren't damaged :/

[HDCHOPPER]

ya eye quit using aegis panel for any overclocking or voltage changes
went back to the old version for now for that very reason
BUT it did work flawlessly when only going UP with anything but not down

[negev]

I'm just hoping that it was mis-reporting the voltage and that I didn't really put 2.89v through my dimms :/

[grungero]

I don't use aegis as my overclocking tool, i always use the gladiator bios. Let's hope that it is just a wrong report by aegis.

[negev]

I think it must be +2.2v is meant to be a death sentence, 2.89 must be instant beheading!

[HDCHOPPER]

donno my Dominators are rated at 2.4v ppl have put 2.7v in em without them dieing
ofcourse thats with some good cooling on em, my dimms never got over 20*c~40*c max norm is 22*c

[negev]

Joy oh joy, I just got a BSOD after 5mins of prime at my settings which were 24-hour stable the other day

[grungero]

Maybe a problem with your memory?

[negev]

One extra notch of vNB seems to have fixed it... weird

[Xello]

I've always maintained, as accurate as Aegis Panel is for me now regarding voltages and temps, never use software programs like this for changing your overclock, always restart and use the bios.

It's a pain, but it's what has to be done, in my opinion.

Likely you haven't 'fried' your ram, hopefully you will be ok with it :)

[negev]

Yeah I don't think its fried, but its weird that I needed to bump the vNB up one notch to stop it crashing when it was 24-hour prime stable the other day.

I've been working on tightening my ram timings since temps are stopping me going any higher with the cpu/fsb. Currently priming 7-7-8-20-2T, 1h 30 so far :) I think tRP might be the key, 7-7-7-20 fails prime very quickly.

[Gendo]

I'm thinking there's something with the vNB on the blackops. I also ran into something kinda weird while testing for fsb.

Read here: http://www.xtremesystems.org/forums/showpost.php?p=3346484&postcount=67

[LordIT]

I was experimenting and decided to open Aegis and drop the vdimm down a couple of notches from 2.1v. As soon as I did this, Aegis suddenly reported 2.89v vdimm!!!! I panicked but before I could do anything the box bluescreened.

You could adjust your low vdimm settings in BIOS and start Everest and Aegis Panel to watch. So you could prove if Aegis works properly.

[saaya]

Yeah I don't think its fried, but its weird that I needed to bump the vNB up one notch to stop it crashing when it was 24-hour prime stable the other day.

I've been working on tightening my ram timings since temps are stopping me going any higher with the cpu/fsb. Currently priming 7-7-8-20-2T, 1h 30 so far :) I think tRP might be the key, 7-7-7-20 fails prime very quickly.

mhhh maybe higher nb temps now so you need more nb voltage?
damn, that sounds really bad... even if its only showing it wrong its bad... i really dont like aegis panel personally... its nice to have a tool to change the voltages and read everything in windows, but it seems unreliable :(
i talked to the api engineer several times but things dont seem to be improving a lot... im sory guys... ill do my best to push for a better aegis panel tool! :toast:

hdchopper, hes using ddr3, so 2.8v vdimm is definately not very healthy... while i know some chips can run this even for weeks, you do need very good cooling on the mem, and some chips def get damaged from 2v already...

[HDCHOPPER]

ya my bust figured out he's using ddr3 after post

got plenty of faith in ya to get them engineers in line :D