bogus index value DWORD

[John]

I looked at my event viewer this morning and noticed that
last nite these errors occurred. I don't remember it
effected anything while I was using the PC last night.

Is this something serious? The errors are shown below:
the first error message also repeated itself in the 4th
message)

Thanks for your help.

"The performance counter name string value in the
registry is incorrectly formatted. The bogus string is
2338, the bogus index value is the first DWORD in Data
section while the last valid index values are the second
and third DWORD in Data section.

Unloading the performance counter strings for service
WmiApRpl (WmiApRpl) failed. The Error code is the first
DWORD in Data section.

LastCounter and LastHelp values of performance registry
is corrupted and needs to be updated. The first and
second DWORDs in Data Section are the original values
while the third and forth DWORDs in Data Section are the
updated new values.

The performance counter name string value in the registry
is incorrectly formatted. The bogus string is 2338, the
bogus index value is the first DWORD in Data section
while the last valid index values are the second and
third DWORD in Data section.

Performance counters for the WmiApRpl (WmiApRpl) service
were loaded successfully. The Record Data contains the
new index values assigned to this service."

 

[Sharon F]

I looked at my event viewer this morning and noticed that
last nite these errors occurred. I don't remember it
effected anything while I was using the PC last night.

Is this something serious? The errors are shown below:
the first error message also repeated itself in the 4th
message)

Thanks for your help.

"The performance counter name string value in the
registry is incorrectly formatted. The bogus string is
2338, the bogus index value is the first DWORD in Data
section while the last valid index values are the second
and third DWORD in Data section.

Unloading the performance counter strings for service
WmiApRpl (WmiApRpl) failed. The Error code is the first
DWORD in Data section.

LastCounter and LastHelp values of performance registry
is corrupted and needs to be updated. The first and
second DWORDs in Data Section are the original values
while the third and forth DWORDs in Data Section are the
updated new values.

The performance counter name string value in the registry
is incorrectly formatted. The bogus string is 2338, the
bogus index value is the first DWORD in Data section
while the last valid index values are the second and
third DWORD in Data section.

Performance counters for the WmiApRpl (WmiApRpl) service
were loaded successfully. The Record Data contains the
new index values assigned to this service."

Do you have any beta or tweaking software installed? Make a visit to
www.google.com. Type "bogus index value dword" as your search term. You'll
find several hits under "web" and under "groups." I glanced through a few
of the search results. Causes were varied. The first handful that I read
had various causes: underclocking/overclocking, beta software and tweaks
for older operating systems applied to XP.

 

[john]

thanks Sharon. I recently downloaded and ran Ad-aware, a
RAmtester shareware and a shareware that identifies all
the hardware components on my system. Maybe thats what
did it. Is this a serious problem though?
Thanks again for your time.
John

 

[Sharon F]

thanks Sharon. I recently downloaded and ran Ad-aware, a
RAmtester shareware and a shareware that identifies all
the hardware components on my system. Maybe thats what
did it. Is this a serious problem though?
Thanks again for your time.
John

I've never run into it, John. All that I know about the issue is what I
read in the discussion threads that I tracked down with with a google
search. It was mentioned in a few of those conversations that other than
the mention of an error in Event Viewer, there didn't seem to be an impact
on how the system ran.

I've used AdAware on a regular basis for years and haven't seen that
message show up here. What ram tester did you try out?

 

[John]

Hi Sharon, Thanks for responding.

The RAm tester I used was from HCI Design.
(www.hcidesign.com).

Also, You might not remember but I am the fellow whose XP
kept crashing (many but not all of them)while in Paint
Pro 8. Well I logged all the times it crashed. 12-13
times in Feb and another 11-12 times in March with all
kinds of stop error codes. I replaced the RAM 3 days ago
and it hasn't .... (c-r-a-s-h-ed yet.. shhh)

I just wanted to tell you because I was very frustrated
at that time and you gave me a breath of air to keep cool
when you responded to my email. So Thanks and in this
case, the RAM helped.

John

 

[Sharon F]

Hi Sharon, Thanks for responding.

The RAm tester I used was from HCI Design.
(www.hcidesign.com).

Also, You might not remember but I am the fellow whose XP
kept crashing (many but not all of them)while in Paint
Pro 8. Well I logged all the times it crashed. 12-13
times in Feb and another 11-12 times in March with all
kinds of stop error codes. I replaced the RAM 3 days ago
and it hasn't .... (c-r-a-s-h-ed yet.. shhh)

I just wanted to tell you because I was very frustrated
at that time and you gave me a breath of air to keep cool
when you responded to my email. So Thanks and in this
case, the RAM helped.

Hi, John. I'm not familiar with that RAM tester and it wasn't mentioned in
any of the threads that I found. However, as I said, no one that had the
error was complaining about performance. They were just wondering what
Event Viewer was trying to tell them. So hopefully, this is just one of
those reports on internals that can be considered informational.

Example: My Event Viewer sometimes mentions an error at startup with
network configuration. It really isn't an error because the network isn't
fully loaded. As soon as the network is fully initiated, everything is
sorted and works perfectly. Of course Event Viewer doesn't give me a green
light. The only clue that the "problem" is gone is that the network works.

I'm glad to hear that you're enjoying PSP once again and that those errors
are gone. Enjoy the new RAM and your image program(s)!