Windows crashes caused by bad RAM?

Ferris

Hi,

After running rock solid for 7 months, Windows XP recently started rebooting itself randomly. I now get regular (4-5 times/day) BSODs with a range of messages. The behaviour is completely unpredictable.
Based on the error report feedback I get from Microsoft, I suspect it may be a RAM issue. But does RAM go bad over time? It ran perfectly solidly for months and then suddenly went bad. Also, it seems to be getting worse (crashing more frequently) as each day goes by. Why should this be the case?

I have tried four memory test programs: Prime95 (failed after 18 mins and 1 min), MemTest (running under windows, 4 errors), MemTest86+ (from boot floppy, 1 error), and Windows Memory Diagnostic (from boot floppy, 7 errors all with an address like xxxxb53c).

Does this sound like a RAM problem? I need to know so I can determine whether the PC can go back to be fixed under a hardware-only guarantee (moneysaving to the last!). Are these progs usually accurate?

Thanks,

Ferris.

quixy_2

Yep first search on the full data given on the BSOD.

Did it work fine before you added the ram? why not remove the ram and see if this works.

How old is the pc? Is it an older machine with new xp put on it, then ur bios might need updating (exercise caution here).

You should look at windows update too in case any hardware updates needed, and check the chipset manufacturers website too in case h/w drivers need updating.

Ferris

Thanks for the replies... the address I quoted was not the BSOD code, but the failing memory addresses identified by Windows Memory Diagnostic... all seven of them ended in b53c. I was hoping that this would mean something to someone... if a program finds lots of errors in addresses that look like xxxxb53c, does that mean there is an error in a particular area of memory, or is this kind of behaviour a common false positive?

The BSOD codes I got all seemed to point to drivers or memory, but event viewer doesn't point to any particular driver.

quixy, I got the PC last May with the RAM already in and XP Pro SP1 installed, and it worked fine from May to December. I have not made any changes to the system (no overclocking, no additional hardware) apart from installing lots of programs (no one program coincided with the failure).

Debt_Free_Chick

You might want to check that the memory modules are firmly seated on the MoBo. There's no reason for them to "work loose" unless they were badly inserted on assembly - or unless you've been lumping the PC around the room

however, it may be worth checking the seating first.

Where did you get the PC from ? Dig out the paperwork as RAM should not fail within 12 months and you may want to gear up for a warranty claim - so check the paperwork first!

Joe_Bloggs

@Ferris
I'm glad that you ran memtest86. It is an inbuilt boot option on newer DFI motherboards. You may have discovered a memory problem. The cause at this stage is a mystery. If the problem is repeatable and demonstratable then you can prove it is hardware related because of the minimum amount of drivers and software in memtest86.

You can't fix a memory module but can give it an easier time.
The memory timing parameters and voltages can be adjusted with bios settings.The requested values are often built in to the memory modules. Relaxing these may help with reliability and reduce thermal stresses, for an acceptable perfomance loss prior a refund claim .

J_B.
I am currently running FSB ram frequency 133 MHz, Multiplier x10 hence CPU 1333MHz. I can goto FSB 200, multiplier x12 CPU 2.4GHz.

Ferris

Mr_Skint wrote:

can you post the full number for starters (copy and paste)

the failing memory addresses were:
0192b53c
054ab53c
01cab53c
10aab53c
042ab53c
0072b53c
00cab53c

BSOD codes included (there were more than this)
0x0000004E (PFN_LIST_CORRUPT)
0x0000008E (win32k.sys)
C000021A
0x00000024 (ntfs.sys)
0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA - win32k.sys)
0x0000000A (IRQL_NOT_LESS_OR_EQUAL)

thanks.

Joe_Bloggs

Read all you want! If your ram fails on memtest86 it is going to be unreliable running micosoft stuff so you can take any error message it produces with a pinch of salt.
J_B.

amit_1

i would forat the whole c drive again and have windows installed fresh should fix the prob but remember to back up all your work

Joe_Bloggs

@amit_1
The system fails diagnostic tests that run from a floppy disk. What have these failures this to do with a possibly suspect operating system on the hard disk ?
Should we reformat the floppy and reinstall memtest86 if it fails ?
J_B.

Joe_Bloggs

@Mr Skint
Thankyou for your constructive suggestion and thanks to amit_1 for the concern and boldness of the proposed solution.

Ferris has the tools to do the job. It is just a question of applying them in a logical order. More feedback is required from Ferris. Here is a list:
1) Motherboard. These things have version numbers. The motherboard has a bios program that can affect its stability so quote it if you can.
2) The processor range can be determined from the motherboard make but it would save time if the exact model was stated.

3) Temperature. I have experienced the same problems through over clocking which caused temperature related problems. Can you monitor the temperature of key components during normal operating conditions ? A few utilities are available for this purpose. Motherboard Monitor is one example.

4)Memory. What memory are you using. What front side bus (FSB)? how many sticks of memory and in which slots. What are the memory timings and memory voltage ?

Many motherboards/systems have a pathology that eventually gets published on the web so disclose as much as you can and maybe a pattern will emerge.

J_B.
PS what happened from December to the present Date ?

Toxteth_OGrady

Sure sounds like a hardware problem to me.

As j_b alluded to, sounds to me like one of the big three:

Memory-Heat-Power

Given the gradual worsening of the problem over time my hunch would be a failing psu.

If op could swap out the psu for a spare (borrowed) and rerun memtest and p95 it would help the diagnostics.

You could also download SpeedFan and post your CPU temps, both idle and load, along with CPU model.

To try and bowl out the psu, try running Memtest in min h/w power config. Disconnect power and IDE leads from all disk drives and optical drives, except for your floppy and main boot disk (C: ).

Disconnect all peripherals except mouse/keyboard. Remove all internal cards (sound, NIC, modem etc) except for graphics card. Just use one stick of RAM.

Boot and run Memtest, see if it improves. If not swap to your other RAM stick and repeat.

:cool:

TOG