How-Tos

How To: Diagnose Faulty RAM

comment Commentsprint Printemail EmailDeliciousDiggStumbleUponReddit

Diagnosing system failures and quirky behavior can be a crap shoot, as the same symptoms can point to any number of culprits. But unless you have reason to believe a specific component is at fault, most troubleshooting quests usually start with the RAM.

Telltale Signs

If you've recently started experiencing those dreaded blue screens of death (BSoD), then the first question most techs and forum gurus will ask is, "Have you checked your RAM?," and with good reason. Bad RAM is usually associated with the PFN_LIST_CORRUPT and PAGE_FAULT_IN_NONPAGED_AREA errors, but it's not exclusive to just these two. Other warning signs include system stalls, reboots, and generally abnormal behavior.

Run Memtest68

Testing for faulty memory is relatively easy to do thanks to a diagnostic tool called Memtest86. This handy program runs a series of tests on your RAM, spitting out any errors when/if it finds them. And because Memtest86 runs before Windows has a chance to load, you won't be interrupted by further blue screens while it tests your memory. If you have a faulty kit of RAM, you may see hundreds of errors right away, or in less severe cases, you may need to run several passes (I recommend you let it run overnight).

To get started, you'll need either a blank floppy or CD/DVD disk, then download the latest version of Memtest86 (v3.3 at the time of this writing) for whichever media you plan to use. If using a floppy, double-click the install file, which will open a command prompt with step-by-step instructions. For CD or DVD installations, burn the ISO file as an image, and NOT as a data file. Most CD/DVD burning programs, such as Nero and Roxio, will do this automatically upon double-clicking the ISO, and other programs, like the free CDBurnerXP Pro will not, requiring you to specify you're burning from an image (click on File and select Write Disk from ISO File...).

Once you've made your Memtest86 diagnostic disk, the next step is to boot from it. Stick the disk in the appropriate drive (if you manage to get the floppy to work in an optical drive, or vice versa, I'd like to hear about it!), then restart your system. You may need to change the boot priority in your BIOS so that your system doesn't automatically boot from your hard drive. If so, hit the DEL key during the POST screen (some older systems may require you push F1, F2, ESC, or other combinations). Once you've set the approriate boot priority, Memtest86 will load and run automatically.

It Found Errors! That's it Man, Game Over Man, Game Over!

Not so fast there, Hudson! While Memtest86 errors are almost always indicative of problematic RAM, the diagnostic also checks your CPU, L1 and L2 cache, and your motherboard. So you could have an even bigger problem on your hands, but don't panic, because it might also be as simple as an incorrect timing or voltage setting. Running aggressive latency timings or less than the manufacturer's specified voltage can cause RAM to churn out errors and act exactly like a defective kit. These settings are usually found in the Advanced menu of your BIOS (some Gigabyte owners need to hold CTRL-F1 on the main screen to access the hidden menu), and double-check that your kit of RAM is running within spec. For example, if your manufacturer specifies 5-5-5-15 @ 2.1V and you're running 4-4-4-12 @ 1.9V, then there's a good chance your RAM will choke. Up the voltage and rerun Memtest. If it passes and your system instability goes away, then congratulations, you not only saved yourself an RMA, but also discovered that your RAM is capable of running tighter (lower) timings than advertised. If on the other hand you continue to receive errors, raise those timings back to stock. Also check that the frequency is correct (running DDR2-800 at DDR2-1066 is overclocking).

If your RAM settings are correct, then test one stick of RAM at a time. While both sticks could be faulty, it's more likely that just one of them is defective. Also test the stick(s) in each DIMM slot to rule out the possibility of a faulty slot, while also providing you with an opportunity to verify you're using the correct slots for dual-channel operation.

I Have a Bad Stick, Should I Buy a New One?

Almost all RAM manufacturers offer lifetime warranties on their chips, so long as you didn't kill the modules by overclocking/volting. And if you inadvertently OC/d/OV'd, be upfront with the manufacturer (you're on the honor system with this one) - the companies worth giving your business to will be more apt to work with you in these situations.

If you do RMA a dual-channel kit, insist on returning both sticks, even if only one is defective. Why? Because dual-channel kits are supposed to be tested by the manufacturer to ensure they play nice together. The chips under the heatspreader on your replacement kit may differ from the ones on your existing kit, even if the make and model are the same, and it's when you mix and match chips that incompatibilities are most likely to occur in a dual-channel environment.

COMMENTS
avatarIt WORKED!!! Thanks again MaximumPC

I have been trying to track down why Oblivion kept dying on my new C2D machine. It worked, albeit slowly, on my old Athlon XP 2800+ with ATI AIW9800Pro. The BSOD only happened in Oblivion and it was not heat related. Someone suggested that there was a lot of talk on the net about BSOD's with a 680i SLI/8800GT_ combination. I did find a lot of that, but with no real solutions. When I saw this article, I ran home and immediately starting it running. Low and behold, there were errors. Well, it turned out not to be bad memory, but bad voltage settings. I had taken the time to set the timing parameters in the BIOS, but did not even think to look at the voltage, a new task for non-OCer's. I set the voltage to the lower of the recommended voltages and it worked. I can now play Oblivion with all the eye candy turned on.

Thanks again MaximumPC

Login or register to post comments
avatarMemtest86+ doesn't always identify bad memory.

I've passed Memtest86+ for 8 or more loops to have MS Vista memory checker, advanced/extended test, to promptly find problems. Mostly prevalent on 680i motherboards...

Login or register to post comments
avatarDavid McNamara I had Patriot

David McNamara

I had Patriot memory that passed Memtest but still caused BSODs in Vista. The Nvidia Control Panel stability test finally suggested that memory was the problem. I got my system stable by lowering the ram voltage (2.0 vs recommmended 2.2V) - contrary to the usual wisdom. I think it was a thermal problem that only showed up when the system was going full bore.

Login or register to post comments
avatarI have used MemTest

When I first built my PC I was getting errors for the memory. I ran MemTest and all 4 sticks failed the last 3 of 6 checks. Had to change the memory timing manually in the BIOS, because the mobo over clocked it by speed by default. Also, you can turn off the cashe of the CPU for testing to maybe help pin down where the problem is in the memory system, but it takes a very long time.

Login or register to post comments
avatarOlder mem testers

Many proc. gens. ago, I used a memory tester that came with a memory manager from the old DOS days. Simular to EMM 386 (or it was that) came with one. It was quite extensive and took way too long on current gen rigs with large amounts of memory (for the day).

Oh, and speaking of days or Yor, I have met many people who tried to make their CDs work in their 5.25" floppy drives. Most of them have kids who wanted to help daddy play with the PC... Have dissected many drive to removed the pretty round disks that Jr. found around the play...er...desk area.

**********
Every morning is the dawn of a new error.

Login or register to post comments
avatarExcellent article!

I can't count the amount of times I've ran into this issue and used BIT and MemTest.

Login or register to post comments
avatarIf you have PNY memory and

If you have PNY memory and have lost the receipt or the original packaging, PNY will not accept nor honor the lifetime warranty.

copied from an email when I requested replacement :

Warranty coverage requires proof of purchase documentation evidencing the date of purchase (sales receipt or invoice) and original packaging. To obtain warranty service during the warranty period, contact PNY at 1-800-234-4597 or visit us at http://www.pny.com. The consumer is responsible for all shipping costs. When shipping from outside the United States this will include freight, duty, customs fees and taxes. All pricing is in USD. FOR WARRANTY INFORMATION AND REGISTRATION VISIT US AT http://www.pny.com. The PNY logo is a trademark of PNY Technologies, Inc. Other trademarks are owned by their respective companies. Rev. 07-13-06

Login or register to post comments
avatarDifference?

What is the difference between Memtest86 v3.3 and
Memtest86+ v1.7? Is there one? and why the 2 versions?

Bg

Houston Tx

Login or register to post comments
avatarMemtest86 and Memtest86+

Developer Samuel Demeulemeester released Memtest86+ as an update to the original Memtest86 (written by Chris Brady), since the original hadn't been worked on for several years. That's recently changed, with both Memtest86 and 86+ receiving updated code as of this past January. Both diagnostics do essentially the same thing, and you'd be fine to user either one.

Login or register to post comments
RESOURCE CENTER

KICK ASS OFFERS

THIS MONTH's ISSUE
FEATURE Awesome Upgrades: The best PC upgrades in every price range.HOW TO Connect your PC to your surround-sound audio systemProtect Your PC We put 10 of the most popular antivirus programs to the test to see which will protect you best. Android Revealed Find out how the Google-powered HTC G1 stacks up against its rivals.

Don't have an account? Register Now! Forgot password?