[Jahocowi]

So I'm not really sure what's going on here.

Long story short I've been having memory issues for a very long time. Many many RMAs have happened and I got ADATA to exchange 4x 2GB sticks to 2x 4GB sticks (plus some swag lol). So far everything has been a little weird.

The sticks are AX3U1600GC4G9-2G. They are 1600 and as we know when you first put the sticks in there the system defaults to 1333. I put it 1600 from the bios and used it for a few days.

I started noticing a few weird things with my system. I wasn't sure if it was just a crappy program or something bad. I started running Prime95. When I came back to check on progress it was gone. My computer restarted. I found it weird cause I have it to not auto reset on stuff like BSOD.

So I started again and watched very close. After around 10 mins my computer just restarted. No errors nothing. So I went from 1600 to 1333 and ran Prime again for 24 hours. Everything went fine there was no errors. So I then decided to run MemTest 86+ just to rule out stuff. Ran it for 24 hours no issues.

After those two tests I figured everything would be fine. Then last week and yesterday was when some other stuff happened. At the end of the day I shut down my computer, I don't flip the switch on the back but I just leave it off. After around 2 days of no use I turned on my computer and before I even got into Windows I BSODed. There was no error with it like about the pagefile or anything. It did give me a stop code:

Here is the one from today. So far it only comes up if I've had my computer off for a few days. After restarting the computer everything is fine. No BSODs or anything.

Today though my computer did freeze. So I ran SuperPi (I believe that was the name) on the highest MB setting and it's fine. Running IntelBurnTest now.

I guess i don't know what's going on. From the tests I've done everything should be fine.

Are there other tests I can run to see how it's going, or should I be looking at something else? Could it be something connected to my computer causing it?

The following is connected to my computer:

I have my bluetooth keyboard/mouse dongle plugged in one of the USB ports, a external HDD by the mobos esata ports, a internal memory card reader by USB, 2 monitors, speakers, and a USB webcam.

Any ideas? Am I over reacting?

I feel like I should also be able to get these to 1600 fairly easy. My other sticks where able to do it with no effort.

 

[Aeschylus]

Did you run memtest with each stick individually?

 

[xd_1771]

That RAM is known to not work very well on AMD platforms... you're not the first user to have problems
Try raising the DRAM voltage, you are fine up to the rated max of 1.75V

EDIT: Never mind this is the 2x4GB kit not 2x2GB, that is the one with known problems. Do try raising DRAM voltage though.

The issue might not even be RAM. I had a PCI Wi-fi card that caused problems on a certain motherboard/computer. Always froze upon startup. It seemed like a RAM issue but the RAM was totally fine. Took out the wi-fi card and that was all. It did work, however, in other systems, no issue.

 

[evilferret]

Do you have Norton installed?

Google search for the bad sys file shows http://community.norton.com/t5/Norto...OD/td-p/229252

Sounds like a corrupt driver from Norton.

Edit: more links with work arounds.

http://community.norton.com/t5/Norto...date_ascending

I would just re-format though. I love a good re-format every once in awhile. Its like a good cleaning.

Edit: This made this think that somebody needs to create a boot OS for overclock testing.

I've had to reformat my computer mid OC multiple times due to a corrupt driver or lost files from BSOD's.

 

[Jahocowi]

@Xd: Yeah I USED to have 4x2G sticks. Got them replaced with the 2x4G sticks.

I wonder if it is my WiFi card. I'm having SOME questionable issues with it. But it's mainly build quality over performance.

@evilferret: YUP! I do have norton. Can uninstalling Norton and reinstall it? I reinstalled my OS not even 4 months ago. Or are we talking about something else?

 

[evilferret]

Well if you had it installed and BSOD'ed a few times you could have corrupted Norton.

Every BSOD = a chance to corrupt files. Heck running a slight unstable OC can cause corruptions.

The links I posted have threads on fixing it. You should also run sfc /scannow to make sure non of your Window's files are corrupted.

The BSOD you posted shows Norton causing the failure. So maybe you should start from there. A ram BSOD would usually show a kernel BSOD (or something Windows related).

symefa64.sys = Symatec Norton file.

 

[Jahocowi]

Cool did what they suggested and haven't had a BSOD since.

Ran sfc /scannow using this guide:
http://www.sevenforums.com/tutorials...ompt-boot.html

Came up with nothing so I guess that's a good thing.

 

[Jahocowi]

I got to 1600!

Instead of increasing the DRAM voltage I should have decreased it! I got 24 hours Prime95 with my DRAM voltage at 1.55v!

That's good right?

 

[xd_1771]

Decreased it!?
RAM can be weird sometimes

there are quite a few examples I know where RAM stability may respond better to less DRAM voltage

 

[Jahocowi]

I caught on to it when I noticed my computer restarting sooner and sooner with each increase. By the time I got to 1.67 just opening Prime95 would cause my computer to restart. I remembered that it would at least go for an hour without issue at 1.65 so I thought going down from there would fix it. lol.

But 1.55v for 1600 is good right? It means better OCing?