I am experiencing misterious parity errors on an HP ML570 G2 system running
32GB of memory and quad 2.8 CPU's.
Windows 2003 Enterprise and SQl Enterprise SP3A.
I have updated all drivers and firmware and ran comnprehensive diags on the
system and everything checks out OK.
The system misteriously goes to a blue screen stating a parity errors.
Unfortunately, there are no errors generated that I can go on.
Has anyone experienced this in their envirionments.
teh boot.ini switches are set correctly and AWE is enabled.
Anything would help. Thanks
Garry.First, have you tried the MAXMEM switch in the Boot.ini? maybe limit the OS
to, say, 8GB to see if the issue resolves itself (could still be bad memory
as I rarely trust memory diags). Microsoft does have it's own memory diags.
that I have seen somewhere...I will try to dig it up
What is the exact error your do see with the BSOD? anything helpful at the
HP site?
Neil MacMurchy
"GSM" <gsm@.mris.com> wrote in message
news:ebyIFBTBEHA.3284@.TK2MSFTNGP09.phx.gbl...
> I am experiencing misterious parity errors on an HP ML570 G2 system
running
> 32GB of memory and quad 2.8 CPU's.
> Windows 2003 Enterprise and SQl Enterprise SP3A.
> I have updated all drivers and firmware and ran comnprehensive diags on
the
> system and everything checks out OK.
> The system misteriously goes to a blue screen stating a parity errors.
> Unfortunately, there are no errors generated that I can go on.
> Has anyone experienced this in their envirionments.
> teh boot.ini switches are set correctly and AWE is enabled.
> Anything would help. Thanks
> Garry.
>|||We are not using MAXMEM, only the /PAE switch.
Unfortunately HP is pointing at firmware and drivers. All updated as per
forum visits.
The exact error at BSOD states:
Hardware Error
Call your hardware vendor for support
NMI: Parity check/memory parity error
***The system has haulted***
"Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
news:%23XwrsYTBEHA.3928@.TK2MSFTNGP09.phx.gbl...
> First, have you tried the MAXMEM switch in the Boot.ini? maybe limit the
OS
> to, say, 8GB to see if the issue resolves itself (could still be bad
memory
> as I rarely trust memory diags). Microsoft does have it's own memory
diags.
> that I have seen somewhere...I will try to dig it up
> What is the exact error your do see with the BSOD? anything helpful at the
> HP site?
> Neil MacMurchy
> "GSM" <gsm@.mris.com> wrote in message
> news:ebyIFBTBEHA.3284@.TK2MSFTNGP09.phx.gbl...
> running
> the
>|||<flame>Harumph, typical HP </flame>
http://support.microsoft.com/defaul...kb;en-us;222973
If you have a support contract I would have them come in. is this straight
off of startup all the time or is it intermittent and not reproducable?
Neil
"GSM" <gsm@.mris.com> wrote in message
news:O$XUcrTBEHA.892@.TK2MSFTNGP09.phx.gbl...
> We are not using MAXMEM, only the /PAE switch.
> Unfortunately HP is pointing at firmware and drivers. All updated as per
> forum visits.
> The exact error at BSOD states:
> hardware Error
> Call your hardware vendor for support
> NMI: Parity check/memory parity error
> ***The system has haulted***
> "Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
> news:%23XwrsYTBEHA.3928@.TK2MSFTNGP09.phx.gbl...
> OS
> memory
> diags.
the
on
>|||Unfortunately intermittent and it's never been reproducable. That's what is
killing me. Diagnosing and troubleshotting is not quick. We find ourselves
waiting for the problem (sometimes for days) after taking different measures
to correct it.
"Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
news:u$i$9zTBEHA.3776@.tk2msftngp13.phx.gbl...
> <flame>Harumph, typical HP </flame>
> http://support.microsoft.com/defaul...kb;en-us;222973
> If you have a support contract I would have them come in. is this straight
> off of startup all the time or is it intermittent and not reproducable?
> Neil
> "GSM" <gsm@.mris.com> wrote in message
> news:O$XUcrTBEHA.892@.TK2MSFTNGP09.phx.gbl...
per
the
> the
> on
errors.
>|||Again I would hassle HP. unit should be under wty (my DL580 G2s are still
under wty). I would start stripping out some of the RAM to double check.
Possibly down to 4GB.
Were there any changes just prior to all of this? Don't discount NICs or
other adapters as possible sources.
We had some problems with an old 6500 recently and it was RAM. Diags tested
ok, but after we stripped it down to 256MB our reproducable error (could
make it happen every time we did a BIG copy) went away. I had the benifit of
a reproducable error . See if you can find a way to make yours reproduce
(little baby errors all over the place <gr> )
Neil
"GSM" <gsm@.mris.com> wrote in message
news:uRWwVQUBEHA.712@.tk2msftngp13.phx.gbl...
> Unfortunately intermittent and it's never been reproducable. That's what
is
> killing me. Diagnosing and troubleshotting is not quick. We find
ourselves
> waiting for the problem (sometimes for days) after taking different
measures
> to correct it.
>
> "Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
> news:u$i$9zTBEHA.3776@.tk2msftngp13.phx.gbl...
straight
> per
> the
at
system
diags
> errors.
>|||I will keep at it on all fronts and will repost for everyones benefit.
Please keep me posted should you come across anything.
Many thanks.
"Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
news:ujnAwUUBEHA.3204@.TK2MSFTNGP10.phx.gbl...
> Again I would hassle HP. unit should be under wty (my DL580 G2s are still
> under wty). I would start stripping out some of the RAM to double check.
> Possibly down to 4GB.
> Were there any changes just prior to all of this? Don't discount NICs or
> other adapters as possible sources.
> We had some problems with an old 6500 recently and it was RAM. Diags
tested
> ok, but after we stripped it down to 256MB our reproducable error (could
> make it happen every time we did a BIG copy) went away. I had the benifit
of
> a reproducable error . See if you can find a way to make yours reproduce
> (little baby errors all over the place <gr> )
> Neil
> "GSM" <gsm@.mris.com> wrote in message
> news:uRWwVQUBEHA.712@.tk2msftngp13.phx.gbl...
what
> is
> ourselves
> measures
> straight
reproducable?
as
limit
bad
memory
helpful
> at
> system
> diags
>|||Wait for the bill (I take my coffe with 2 cream and 2 sugar, but please
don't send it thru the mail...)
;-)
(ps...good luck)
Neil
"GSM" <gsm@.mris.com> wrote in message
news:u5xL6gUBEHA.1732@.TK2MSFTNGP12.phx.gbl...
> I will keep at it on all fronts and will repost for everyones benefit.
> Please keep me posted should you come across anything.
> Many thanks.
> "Neil MacMurchy" <neilmcse@.hotmail.com> wrote in message
> news:ujnAwUUBEHA.3204@.TK2MSFTNGP10.phx.gbl...
still
> tested
benifit
> of
> what
> reproducable?
> as
> limit
> bad
> memory
> helpful
>
Wednesday, March 28, 2012
Parity
Labels:
cpu,
database,
enterprise,
errors,
experiencing,
memory,
microsoft,
misterious,
ml570,
mysql,
oracle,
parity,
quad,
running32gb,
server,
sql,
system,
windows
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment