Blue screen

  • Thread starter Thread starter HB
  • Start date Start date
H

HB

I have gotten the following bsod message
"memory parity error'
"please contact your hardware vendor"

I restarted the computer and all is fine for a few days, then another bsod.
Not running anything unusual.
Is my memory going bad?
The machine is older,
Dell P3 600 MHz
756 mg of ram

Thanks for any info
Jim
 
HB said:
I have gotten the following bsod message
"memory parity error'
"please contact your hardware vendor"

I restarted the computer and all is fine for a few days, then another
bsod.
Not running anything unusual.
Is my memory going bad?
The machine is older,
Dell P3 600 MHz
756 mg of ram
Click to expand...

It certainly sounds like a memory error. You can easily test this. I
like Memtest86+ from www.memtest.org. You will either download the
precompiled Windows binary to make a bootable floppy or the .iso to
make a bootable cd. If you want to use the latter, you'll need to have
third-party burning software on the machine where you download the file
- XP's built-in burning capability won't do the job. In either case,
boot with the media you made. The test will run immediately. Let the
test run for an extended period of time - unless errors are seen
immediately. If you get any errors, replace the RAM.

Malke
 
In
HB said:
I have gotten the following bsod message
"memory parity error'
"please contact your hardware vendor"

I restarted the computer and all is fine for a few days, then
another
bsod. Not running anything unusual.
Is my memory going bad?
Click to expand...


The result of many errors is an ambiguous message, because it
isn't always clear what the problem is. This message, on the
other hand, is clear and unambiguous; it *says* your memory is
going bad.

If I were you, I would believe the message.
 
Malke said:
It certainly sounds like a memory error. You can easily test this. I
like Memtest86+ from www.memtest.org. You will either download the
precompiled Windows binary to make a bootable floppy or the .iso to
make a bootable cd. If you want to use the latter, you'll need to have
third-party burning software on the machine where you download the file
- XP's built-in burning capability won't do the job. In either case,
boot with the media you made. The test will run immediately. Let the
test run for an extended period of time - unless errors are seen
immediately. If you get any errors, replace the RAM.

Malke
--
Click to expand...

Thanks for the suggestion. I downloaded and ran memtest for a single pass
which took over two and a half hours to complete. It ran all tests. The test
reported no errors. Should I let it test for more than one pass? Also, I
googled a search for "troubleshooting memory" and "memory parity error" and
got a lot of hits. Could you recommend a method for troubleshooting /other
possible causes?

Thanks, Jim
 
S.Sengupta said:
The cause is typically failed or defective RAM. (including motherboard,
Level 2 cache, or video memory), incompatible or mismatched memory
hardware, or when a device driver attempts to access an address in the
0x8xxxxxxx range that does not exist.
Re:-http://www.theeldergeek.com/stop_error_messages.htm

Windows Memory Diagnostic
http://oca.microsoft.com/en/windiag.asp

http://www.memtest.org/

regards,
ssg MS-MVP
Click to expand...
I downloaded the win mem diagnostic tool and cant get the iso file to burn
properly. It cant be my burning software because it will burn other iso
files with no problem. I tried copying to a floppy and that wont work
either. I tried downloading several times with the same result, Is there a
problem with the diagnostic program or am I doing something wrong?
 
HB said:
They gave you an MVP award for snide useless answers like this???

The result of many errors is an ambiguous message, because it isn't always
clear what the problem is. This message, on the other hand, is clear and
unambiguous; it *says* your memory is going bad.

If I were you, I would believe the message.
Click to expand...


Ah.... Ken's answer was neither snide nor useless.


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
Click to expand...
 
In
Bruce Chambers said:
HB said:
They gave you an MVP award for snide useless answers like
this???

message



Ah.... Ken's answer was neither snide nor useless.
Click to expand...


Thanks, Bruce. I was going to reply similarly, but I decided to
let it go, and let him believe what he wanted.
Click to expand...
 
Ken said:
Thanks, Bruce. I was going to reply similarly, but I decided to
let it go, and let him believe what he wanted.
Click to expand...


No problem, Ken. Besides, I tend to think of "snide" as _my_
territory. ;-}


--

Bruce Chambers

Help us help you:



You can have peace. Or you can have freedom. Don't ever count on having
both at once. - RAH
 
What I "believe" is irrelevant. Your answer sucked and contributed nothing
to the thread. BTW it was not a memory problem so I should not have
"believed what the message said". Nice job.
 
Oh wow you are the op. Hmmm...try to thank those even for the wrong answers.
Who knows the right one may happen. In your case I don't have the right
one. Seems to me if this was a memory issue it should occur right in the
post. Have you tried resetting CMOS?

--
George Hester
_______________________________
HB said:
What I "believe" is irrelevant. Your answer sucked and contributed nothing
to the thread. BTW it was not a memory problem so I should not have
"believed what the message said". Nice job.
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Windows 10 One of my previous builds is experiencing random, multiple BSODs 9
[Updated Repost] Hardware malfunction 1
Blue Screen Issue 2
Blue Screen of Death 4
Blue Screen of Death Top 10 1
Driver Verifier question 1
Login screen not coming up 1
Blue Screen Error...... 10

Back
Top