Memory checking

[demon angel]

Yup its still memory.
I have proof for you here:http://support.microsoft.com/kb/315335

 

[attuu]

Yes, that's what I think I should also try.
I will also run a test when I switch the ram to another slot, see what the results it will be

 

[attuu]

But, the stop code changes everytime, that's the thing confuses me. Check this out:

 

[Conradl]

But, the stop code changes everytime, that's the thing confuses me. Check this out:

Faulty RAM can either cause a direct error, like in the first BSOD, where your system realised that the RAM was buggered and malfunctioned; or it can cause an inconsistency within another process that manifests in the second BSOD. The second BSOD for example could also be due to a virus, or any other event that could corrupt a DLL, but I think it is safe to say that the memory is faulty.

Try test it in another machine if possible.

 

[attuu]

Hi Guys,

I have swithed the ram to second slot, and it is working fine, no blue screen since last night. Also, I run memtest for 15 min. no errors found.

Is this good news?

 

[Conradl]

Hi Guys,

I have swithed the ram to second slot, and it is working fine, no blue screen since last night. Also, I run memtest for 15 min. no errors found.

Is this good news?

If a faulty motherboard is better news than faulty RAM then yes - it is good news If you only need one stick of RAM then you should be fine....

 

[Drake2007]

The good news is you succesfully diagnosed your PC, the bad news is it's broken

On the flip side, you still need to check the suspect DIMM slot with a known working RAM module and if it is blown and your mobo is still under warranty you can claim it (before warranty expires).

 

[Hectic]

You need to run the extended test on that memory. Press"T" as soon as memtest start. It will change from 7 to 11 tests to be done. It is a much longer test and at times looking if it is standing still. If you past that test, the memory should be ok.