Memory problem, I think

A bad memory controller would not be out of the question.......

debgram1 said:

yes I'm running with the XMP profile and it is set to 1600. The last test that showed the passed, was after I set the 6 back to 7 and the 21 back to 24

essenbe said:

I assume you are running 1600mhz ram and that the Ripjaws x serise has an XMP profile. IShould I also assume that you enabled the XMP profile in BIOS? If so, bios should automatically set the timings and possibly the frequency to 1600. If bios set the frequency to 1333 you should be able to set it at 1600 manually, but let bios set the timings. The board should run the ram at that setting. I have asked for help as I am not qualified to read your dump files. Please also post a screenshot of the SPD tab from CPUz.

Also, I understand that the 8GB of ram with the timings showing in the memory tab of CPUz is passing the windows memory test? Are all of my assumptions correct? If they are I think you should run the memtest from the link I gave. It is a much better ram test than the windows memory test.

Did you get your RAM at the same time and from the same store?
One kit or two kits?

Your MemDiag test is showing errors.

debgram1 said:

Asus forum said to bump it up to 1.55.

I was able to open those .wer files in notepad

Code:

first test
Version=1
EventType=MemDiagV1
EventTime=129665490090145812
Consent=1
UploadTime=129665490090301813
ReportIdentifier=c21d6194-1606-11e1-b6aa-bcaec576ecdb
Response.BucketId=2591664676
Response.BucketTable=5
Response.type=4
Sig[0].Name=Range of memory size
Sig[0].Value=4097
Sig[1].Name=Launch type
Sig[1].Value=Manual
Sig[2].Name=Schedule type
Sig[2].Value=Immediate
Sig[3].Name=Completion type
Sig[3].Value=Fail
Sig[4].Name=Test type
Sig[4].Value=Standard
Sig[5].Name=Failed tests
Sig[5].Value=31
Sig[6].Name=Number of bad pages
Sig[6].Value=60
Sig[7].Name=Test duration in seconds
Sig[7].Value=300
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-1703302620/nBucketTable=5/nResponse=1/n
FriendlyEventName=Memory test results reported
ConsentKey=MemDiagV1
AppName=Windows Memory Diagnostic
AppPath=C:\Windows\System32\RelPost.exe
ReportDescription=The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement
second test
Version=1
EventType=MemDiagV1
EventTime=129665503502645179
Consent=1
UploadTime=129665503502645179
ReportIdentifier=e18fe13b-1609-11e1-b064-bcaec576ecdb
Response.BucketId=2591704860
Response.BucketTable=5
Response.type=4
Sig[0].Name=Range of memory size
Sig[0].Value=4097
Sig[1].Name=Launch type
Sig[1].Value=Manual
Sig[2].Name=Schedule type
Sig[2].Value=Immediate
Sig[3].Name=Completion type
Sig[3].Value=Fail
Sig[4].Name=Test type
Sig[4].Value=Standard
Sig[5].Name=Failed tests
Sig[5].Value=91
Sig[6].Name=Number of bad pages
Sig[6].Value=80
Sig[7].Name=Test duration in seconds
Sig[7].Value=330
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=-1703262436/nBucketTable=5/nResponse=1/n
FriendlyEventName=Memory test results reported
ConsentKey=MemDiagV1
AppName=Windows Memory Diagnostic
AppPath=C:\Windows\System32\RelPost.exe
ReportDescription=The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement
third test
Version=1
EventType=MemDiagV1
EventTime=129665533004604948
Consent=1
UploadTime=129665533004760948
ReportIdentifier=c0040f94-1610-11e1-b60e-bcaec576ecdb
Response.BucketId=79261410
Response.BucketTable=5
Response.type=4
Sig[0].Name=Range of memory size
Sig[0].Value=4097
Sig[1].Name=Launch type
Sig[1].Value=Manual
Sig[2].Name=Schedule type
Sig[2].Value=Immediate
Sig[3].Name=Completion type
Sig[3].Value=Pass
Sig[4].Name=Test type
Sig[4].Value=Standard
Sig[5].Name=Failed tests
Sig[5].Value=0
Sig[6].Name=Number of bad pages
Sig[6].Value=0
Sig[7].Name=Test duration in seconds
Sig[7].Value=300
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Memory test results reported
ConsentKey=MemDiagV1
AppName=Windows Memory Diagnostic
AppPath=C:\Windows\System32\RelPost.exe
ReportDescription=The results of running the Windows Memory Diagnostic were submitted to Microsoft for analysis and product improvement

Run Memtest86+, it is a much better RAM test.


When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Run the first memtest86+ test with all four RAM cards installed, if you get errors stop the test and then follow the procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
If you get any errors on any set of tests, you can stop the test and move to the next step.

RAM - Test with Memtest86+

Have you been checking your temperatures?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

This is very important, with four RAM cards or 4GB RAM or more you may need to bump the integrated memory controller voltage.
Go to your BIOS and tell us what the CPU and the CPU integrated memory controller voltages are.

What power supply are you running?

I doubt it's the psu then....have you been able to run the mem test with all 8 gigs?

So is the does system still get in a restart loop?

How high do you have your CPU overclocked? I know boards are different, but on most 1155 boards 1.3V is only needed at 4.5 or above. I'm running 4.2 with Vcore set at 1.272 and the offset at -.020 so I'm at 1.252V in bios.