Big memory problem but RAM OK

  • Thread starter Thread starter Lucius Snow
  • Start date Start date
L

Lucius Snow

Hello all,

I've got a computer to repair for somebody. The hardware configuration is :

Asus A7V333
Athlon XP 1800+
512 MB (2x256) of DDR PC2100 Elixir
HD 80 GB Seagate
GeForce 4 Leadtek A250
SBLive! 5.1

The problems are for example an EXE file that can't be run (Windows saying
the file is unfindable), services.exe crashing and, very often, an error
with rundll32.exe saying the memory can't be written at some hexadecimal
adresses. I got one or two BSOD as well (i forgot the message :/). I
installed Windows 2000 + SP4 twice on a new NTFS partition. The crash
already occurs just after the installation, before installing drivers,
softwares or anything. It was sometimes at the second logon. When that was
after, the drivers (4in1 and other peripherals) were installed properly and
all worked. I tested the RAM twice with Memtest86 3.0 (zero error found),
did many chkdik (with /p /r for full check) under the console, changed the
graphic card and tried with the drive mounted on RAID and then IDE. By the
way, the PC is not plugged on a network, not connected to Internet yet.

I'm not sure the BIOS is up to date. I'll get the last version but by
checking the history, i didn't see any improvement linked to that kind of
problem. I'm almost sure now it's a hardware problem but i don't see what.

Any suggestions ? Thank you.
 
"Lucius Snow" said:
Hello all,

I've got a computer to repair for somebody. The hardware configuration is :

Asus A7V333
Athlon XP 1800+
512 MB (2x256) of DDR PC2100 Elixir
HD 80 GB Seagate
GeForce 4 Leadtek A250
SBLive! 5.1

The problems are for example an EXE file that can't be run (Windows saying
the file is unfindable), services.exe crashing and, very often, an error
with rundll32.exe saying the memory can't be written at some hexadecimal
adresses. I got one or two BSOD as well (i forgot the message :/). I
installed Windows 2000 + SP4 twice on a new NTFS partition. The crash
already occurs just after the installation, before installing drivers,
softwares or anything. It was sometimes at the second logon. When that was
after, the drivers (4in1 and other peripherals) were installed properly and
all worked. I tested the RAM twice with Memtest86 3.0 (zero error found),
did many chkdik (with /p /r for full check) under the console, changed the
graphic card and tried with the drive mounted on RAID and then IDE. By the
way, the PC is not plugged on a network, not connected to Internet yet.

I'm not sure the BIOS is up to date. I'll get the last version but by
checking the history, i didn't see any improvement linked to that kind of
problem. I'm almost sure now it's a hardware problem but i don't see what.

Any suggestions ? Thank you.
Click to expand...

There are many things that could cause that. But I don't see enough
of a pattern there to say exactly what is wrong.

When you were running memtest86, did you try the extended tests ?
I think one of those is supposed to be good for finding marginal
terminations on the memory bus.

Try running with one stick of memory at a time (placed in the slot
furthest from the processor). The thing I'm looking for here, is a
change in the symptoms that can implicate one or the other stick
as being responsible.

Some people might suggest swapping the power supply, but since you
haven't mentioned any problems at POST, I don't see anything the
positively indicates a bad PS. A bad PS would be more likely to
cause a spontaneous reboot when you least expect it.

Another idea is that it might be a failing processor. Is the processor
overclocked or does it run abnormally hot ? Is Vcore at the proper
voltage for that model of processor ? If you can get into windows,
you might try running a copy of Prime95, just to see how long the
processor can take a pounding.

By running a bunch of tests, you might get enough unique symptoms
to suggest a more specific problem.

HTH,
Paul
 
Paul said:
There are many things that could cause that. But I don't see enough
of a pattern there to say exactly what is wrong.

When you were running memtest86, did you try the extended tests ?
I think one of those is supposed to be good for finding marginal
terminations on the memory bus.
Click to expand...

That was the normal test (default settings). I just did one in the extended
mode (7 hours of test :/), same result : zero error.
Try running with one stick of memory at a time (placed in the slot
furthest from the processor). The thing I'm looking for here, is a
change in the symptoms that can implicate one or the other stick
as being responsible.
Click to expand...

Ok i'll try that.
Some people might suggest swapping the power supply, but since you
haven't mentioned any problems at POST, I don't see anything the
positively indicates a bad PS. A bad PS would be more likely to
cause a spontaneous reboot when you least expect it.
Click to expand...

Nope, no problem mentionned at the POST.
Another idea is that it might be a failing processor. Is the processor
overclocked or does it run abnormally hot ? Is Vcore at the proper
voltage for that model of processor ? If you can get into windows,
you might try running a copy of Prime95, just to see how long the
processor can take a pounding.
Click to expand...

The processor is not overclocked, i use the default BIOS settings. Here are
the voltages :

Vcore : 1,77 V - 1,80 V (AMD says it must be 1,75 V).
3,3 V : 3,08 V - 3,10 V
5 V : 4,91 V - 4,94 V
12 V : 12,78 - 12,84 V

It doesn't look good, should i change the power supply ?

I didn't have the time to test Prime95 yet but i'll do it as well.

By running a bunch of tests, you might get enough unique symptoms
to suggest a more specific problem.

HTH,
Paul
Click to expand...

Cheers Paul.
 
Lucius Snow said:
The processor is not overclocked, i use the default BIOS settings.
Here are the voltages :

Vcore : 1,77 V - 1,80 V (AMD says it must be 1,75 V).
3,3 V : 3,08 V - 3,10 V
5 V : 4,91 V - 4,94 V
12 V : 12,78 - 12,84 V

It doesn't look good, should i change the power supply ?
Click to expand...

Hmm odd. I just flashed the BIOS to the last version 1.17 and now the
voltages are stables. They don't oscillate anymore. Before, the values
changed constantly into these ranges i gave, like every 1/4 sec. I looked at
the change log of the BIOS and there was no mention of improvement about the
voltage thing.

Now i'm running a new install of Windows 2000. I'll let you know how it
goes.
 
Lucius Snow said:
Now i'm running a new install of Windows 2000. I'll let you know how
it goes.
Click to expand...

Alright. it went almost ok. I installed everything (drivers, softwares,
updates) during 2-3 hours. I only got one crash, a blue screen with
ntoskrnl.exe. At this time, my graphic card drivers had those from Leadtek
site. But i've seen that Windows Update proposed others drivers so i
installed them. I don't know if this crash was link to this (i hope).

By the way, i ran Prime95. Here are the results after i launched a "torture
test" :

[Tue Mar 30 14:19:03 2004]
ERROR: ROUND OFF (0.4976577759) > 0.40
Possible hardware failure, consult the readme file.
[Thu Apr 01 00:34:45 2004]
Self-test 1024 passed!
[Thu Apr 01 01:19:13 2004]
Self-test 896 passed!
ERROR: ROUND OFF (0.4373588562) > 0.40
Possible hardware failure, consult the readme file.

I don't understand really them. Where do these errors come from if the
self-test passed ?

Cheers.
 
"Lucius Snow" said:
Lucius Snow said:
Now i'm running a new install of Windows 2000. I'll let you know how
it goes.
Click to expand...

Alright. it went almost ok. I installed everything (drivers, softwares,
updates) during 2-3 hours. I only got one crash, a blue screen with
ntoskrnl.exe. At this time, my graphic card drivers had those from Leadtek
site. But i've seen that Windows Update proposed others drivers so i
installed them. I don't know if this crash was link to this (i hope).

By the way, i ran Prime95. Here are the results after i launched a "torture
test" :

[Tue Mar 30 14:19:03 2004]
ERROR: ROUND OFF (0.4976577759) > 0.40
Possible hardware failure, consult the readme file.
[Thu Apr 01 00:34:45 2004]
Self-test 1024 passed!
[Thu Apr 01 01:19:13 2004]
Self-test 896 passed!
ERROR: ROUND OFF (0.4373588562) > 0.40
Possible hardware failure, consult the readme file.

I don't understand really them. Where do these errors come from if the
self-test passed ?

Cheers.
Click to expand...

Prime95 is finding a marginal condition. It is either on the
processor or the Northbridge. You know the memory is good,
because you've tested that with memtest86. I would reach
in the drawer and pop another processor in there. Then,
repeat the memtest86 and the Prime95 again. If all passes,
then the CPU is the problem. If the symptoms are the same,
then replace the motherboard. (Or do more testing...)

HTH,
Paul
 
Paul said:
Prime95 is finding a marginal condition. It is either on the
processor or the Northbridge. You know the memory is good,
because you've tested that with memtest86. I would reach
in the drawer and pop another processor in there. Then,
repeat the memtest86 and the Prime95 again. If all passes,
then the CPU is the problem. If the symptoms are the same,
then replace the motherboard. (Or do more testing...)

HTH,
Paul
Click to expand...


After these last tests, i ran Toast during an hour. Just after, i got a new
blue screen (MEMORY_MANAGEMENT) so i got really sick and bought directly a
new motherboard, an A7V8X-X (only cost 56 Euros). Everything has worked well
since. I gave back the computer to the person yersterday so she tests it
during a few days. I'll let you know how it goes. Cheers.

*Fingers crossed*
 
Lucius Snow said:
After these last tests, i ran Toast during an hour. Just after, i got a new
blue screen (MEMORY_MANAGEMENT) so i got really sick and bought directly a
new motherboard, an A7V8X-X (only cost 56 Euros). Everything has worked well
since. I gave back the computer to the person yersterday so she tests it
during a few days. I'll let you know how it goes. Cheers.

*Fingers crossed*
Click to expand...

A while back I had problems that are similar to yours. It turned out
to be a hardware problem on the graphics card. Either a bad memory or
the graphics processor itself.

As far as the oscillating voltages are concerned, don't trust anything
except a good voltmeter.

arnie
 
Arnie Berger said:
A while back I had problems that are similar to yours. It turned out
to be a hardware problem on the graphics card. Either a bad memory or
the graphics processor itself.

As far as the oscillating voltages are concerned, don't trust anything
except a good voltmeter.

arnie
Click to expand...

I haven't got any news from the person yet so i guess everything works good
now. So it was certainly the motherboard itself.
 
Back
Top