Story of ocUK incompetance

My brother bought a ABIT IP35 Pro and 4x 2GB OCZ PC6400 C5 not the value stuff from ocUK a month ago, when he recieved the parts and installed them he started getting device driver stopped responding errors in Windows when running games. So he took it round to my cousins where they tested the memory, they found that 3 of the sticks passed memtest but 1 of the sticks failed. This stick was also tested in a P965-DS3 board where it also failed memtest.

So thinking it was a memory problem they arranged an RMA to send the memory back, he then ran the system on the 2 remaining sticks which passed memtest but the problem still occured, so thinking it was the board they RMA'd the board and the rest of the memory and sent it all back at the same time under 2 RMAs.

ocUK returned the RAM that failed memtest as OK and then returned the motherboard and remaining RAM as OK too, having tested it with memtest 10 cycles and Prime95 for 8 hours, they said the motherboard/RAM combo is fine the problem is in the rest of your system.

So on this advice my brother bought a new PSU which didn't resolve the problem and then a new graphics card, on the day he got the new graphics card I went round as he was just testing it for the first time, we had no problems initially but then he could sometimes run games for a while without any errors, so it took time to reproduce.

I suggested we run 3D Mark Vantage to get a benchmark, so installed it and it didn't complete 1 run before the error occured again, so we ran it again same thing happened and again. Then I suggested we try my RAM in the system so I went home yanked it out of my PC and we installed it, 3D Mark Vantage run over and over about 30 times without problem, put his ocUK OCZ ram in and it failed again, passed the 2nd time, but failed the 3rd and kept failing almost everytime.

So there is a problem with the motherboard and RAM combo or just the RAM and ocUK failed to pickup on this in their testing + the stick that still fails memtest was supposed to be OK. We're waiting to see what happens next.

.

Relevant Pages

  • Re: ASUS P5N32 SLI E and RAM errors
    ... RAM with another set of RAM. ... Also checked- my RAM is on the QVL ... Just to be sure, did you install just one stick, run Memtest on it, then ... - does this mean the memory is OK and I should be looking at the ...
    (alt.comp.periphs.mainboard.asus)
  • Re: How do I test memory failure?
    ... > party USb card and a video card with maxed out 6 MB of ram. ... Use memtest to test RAM ... job of testing memory. ...
    (comp.sys.mac.system)
  • Re: ASUS P5N32 SLI E and RAM errors
    ... replacing all RAM with another set of RAM. ... Also checked- my RAM is on the QVL ... Just to be sure, did you install just one stick, run Memtest on it, ... or point to a bad memory stick. ...
    (alt.comp.periphs.mainboard.asus)
  • Re: [PATCH] x86_64: early memtest to find bad ram
    ... > if find some bad ram, use reserve_early to exclude that range. ... memtest - and we could in fact also do something like this after SMP ... and hit the memory bus via multiple CPUs. ... distributions can enable this by default in their debug kernels. ...
    (Linux-Kernel)
  • Re: Get blue screen with "PAGE_FAULT_IN_NONPAGED_AREA" on boot-up
    ... Sometimes some faulty ram can pass memtest .Reset ... Ram Take out one memory stick And Run "Memtest" on each separately. ...
    (microsoft.public.windowsxp.general)
Loading