Memory Diagnostic results?

Hello,

I ran the Memory Diagnostics tool and after it completed and rebooted
back into Windows, I didnt see any results. Where do you see the
results of the test? I'm trying to diagnose this problem where my PC is
rebooting at random, but I can't determine if it's a memory problem or
not.

So where can I find the results of this test?

Thanks,

Jeff

winston
Fri May 09 10:00:19 PDT 2008

The MD tool reports in the memory diagnostic screen during the test being run. After reboot the MD tool places an icon in the
Systray with the results. If it did find an error it will also attempt to indentify the memory module causing the error.

For additional info
Click on the Orb/enter "memory" in the search box(omit the quotes), wait a few seconds for the Memory tool options box to
appear[uac may prompt for permission to run the tool] , click on the link ' How does Windows diagnose memory problems'

--
...winston
ms-mvp mail


"Jeff Ingram" <ingramje@gmail.com> wrote in message news:upYYa9WsIHA.5268@TK2MSFTNGP06.phx.gbl...
> Hello,
>
> I ran the Memory Diagnostics tool and after it completed and rebooted back into Windows, I didnt see any results. Where do you
> see the results of the test? I'm trying to diagnose this problem where my PC is rebooting at random, but I can't determine if
> it's a memory problem or not.
>
> So where can I find the results of this test?
>
> Thanks,
>
> Jeff

Donchik
Tue May 20 23:45:01 PDT 2008

Hi,

I've had a similar issue, and found the results under the Problem Reporting
tab.

What I'd appreciate is help with is how to use the results?

The Vista Memory Diagnostics run and in my case report an Error! Just that
an Error! To be blunt what use is that unless its going to tell me what the
error is, or even what it thinks the error might be :-(

I located a bin file with the results, but cannot use it or understand it.
Can anybody help with the diagnosis of the diagnosis tools report?

Many thanks,
Donchik

"...winston" wrote:

> The MD tool reports in the memory diagnostic screen during the test being run. After reboot the MD tool places an icon in the
> Systray with the results. If it did find an error it will also attempt to indentify the memory module causing the error.
>
> For additional info
> Click on the Orb/enter "memory" in the search box(omit the quotes), wait a few seconds for the Memory tool options box to
> appear[uac may prompt for permission to run the tool] , click on the link ' How does Windows diagnose memory problems'
>
> --
> ...winston
> ms-mvp mail
>
>
> "Jeff Ingram" <ingramje@gmail.com> wrote in message news:upYYa9WsIHA.5268@TK2MSFTNGP06.phx.gbl...
> > Hello,
> >
> > I ran the Memory Diagnostics tool and after it completed and rebooted back into Windows, I didnt see any results. Where do you
> > see the results of the test? I'm trying to diagnose this problem where my PC is rebooting at random, but I can't determine if
> > it's a memory problem or not.
> >
> > So where can I find the results of this test?
> >
> > Thanks,
> >
> > Jeff
>
>
>

propman
Wed May 21 00:20:43 PDT 2008

Donchik wrote:
> Hi,
>
> I've had a similar issue, and found the results under the Problem Reporting
> tab.
>
> What I'd appreciate is help with is how to use the results?
>
> The Vista Memory Diagnostics run and in my case report an Error! Just that
> an Error! To be blunt what use is that unless its going to tell me what the
> error is, or even what it thinks the error might be :-(
>


Would you want to receive an error message logging onto your computer
like this one from:

http://support.microsoft.com/kb/276304


Error Message: Your Password Must Be at Least 18770 Characters and
Cannot Repeat Any of Your Previous 30689 Passwords
View products that this article applies to.
Article ID : 276304
Last Review : January 29, 2007
Revision : 3.3
This article was previously published under Q276304
SYMPTOMS
If you log on to an MIT realm, press CTRL+ALT+DELETE, click Change
Password, type your existing MIT password, and then type a new, simple
password that does not pass the dictionary check in Kadmind, you may
receive the following error message:
Your password must be at least 18770 characters and cannot repeat any of
your previous 30689 passwords. Please type a different password. Type a
password that meets these requirements in both text boxes.
Note that the number of required characters changes from 17,145 to
18,770 with the installation of SP1.

<grin>

Donchik
Wed May 21 01:58:00 PDT 2008

Sweet, but still not much use ;-)

Problem is that the Diagnostics find an error, but tell me nothing about
what it thinks is wrong.

I need a way to interrogate the BIN file it creates with the error.

Cheers,
Donchik

"propman" wrote:

> Donchik wrote:
> > Hi,
> >
> > I've had a similar issue, and found the results under the Problem Reporting
> > tab.
> >
> > What I'd appreciate is help with is how to use the results?
> >
> > The Vista Memory Diagnostics run and in my case report an Error! Just that
> > an Error! To be blunt what use is that unless its going to tell me what the
> > error is, or even what it thinks the error might be :-(
> >
>
>
> Would you want to receive an error message logging onto your computer
> like this one from:
>
> http://support.microsoft.com/kb/276304
>
>
> Error Message: Your Password Must Be at Least 18770 Characters and
> Cannot Repeat Any of Your Previous 30689 Passwords
> View products that this article applies to.
> Article ID : 276304
> Last Review : January 29, 2007
> Revision : 3.3
> This article was previously published under Q276304
> SYMPTOMS
> If you log on to an MIT realm, press CTRL+ALT+DELETE, click Change
> Password, type your existing MIT password, and then type a new, simple
> password that does not pass the dictionary check in Kadmind, you may
> receive the following error message:
> Your password must be at least 18770 characters and cannot repeat any of
> your previous 30689 passwords. Please type a different password. Type a
> password that meets these requirements in both text boxes.
> Note that the number of required characters changes from 17,145 to
> 18,770 with the installation of SP1.
>
> <grin>
>

propman
Wed May 21 12:14:11 PDT 2008


just off the top of my head (and only on my 3rd coffee of the morning)....

In the old days, if I didn't have a specific program for reading binary
(eg *.bin, *.exe etc) log files or wanted to search for a particular
string within a binary file, I would use a hex(adecimal) editor/viewer.

In fact I just saw a notification about about one I used to use all the
time but at the present time it's name totally eludes me (did I mention
that I am only on my 3rd cup of coffee this morning?).....I'm sure if
you do a quick Google Advanced search, something will turn up pretty quick.


Donchik wrote:
> Problem is that the Diagnostics find an error, but tell me nothing about
> what it thinks is wrong.
>
> I need a way to interrogate the BIN file it creates with the error.

Donchik
Wed May 21 13:54:03 PDT 2008

Hi Propman,

Not quite what I'm after. Without knowing what Microsoft intend the bytes to
represent a binary viewer is not any use.

Still looking for the way to read and understand these data.

Cheers,
Donchik

"propman" wrote:

>
> just off the top of my head (and only on my 3rd coffee of the morning)....
>
> In the old days, if I didn't have a specific program for reading binary
> (eg *.bin, *.exe etc) log files or wanted to search for a particular
> string within a binary file, I would use a hex(adecimal) editor/viewer.
>
> In fact I just saw a notification about about one I used to use all the
> time but at the present time it's name totally eludes me (did I mention
> that I am only on my 3rd cup of coffee this morning?).....I'm sure if
> you do a quick Google Advanced search, something will turn up pretty quick.
>
>
> Donchik wrote:
> > Problem is that the Diagnostics find an error, but tell me nothing about
> > what it thinks is wrong.
> >
> > I need a way to interrogate the BIN file it creates with the error.
>

propman
Wed May 21 15:26:35 PDT 2008


How do you know until you tried one.....used to that all the time as a
last resort. Sometimes the contents of such a viewing will surprise a
person or give a another clue one can use. Anyways, just a suggestion.

PS.....used to load binary files into text viewers too for a quick and
dirty look at them....hex editor/viewer was definitely more versatile
though.


Donchik wrote:
> Hi Propman,
>
> Not quite what I'm after. Without knowing what Microsoft intend the bytes to
> represent a binary viewer is not any use.
>
> Still looking for the way to read and understand these data.
>
> Cheers,
> Donchik
>
> "propman" wrote:
>
>> just off the top of my head (and only on my 3rd coffee of the morning)....
>>
>> In the old days, if I didn't have a specific program for reading binary
>> (eg *.bin, *.exe etc) log files or wanted to search for a particular
>> string within a binary file, I would use a hex(adecimal) editor/viewer.
>>
>> In fact I just saw a notification about about one I used to use all the
>> time but at the present time it's name totally eludes me (did I mention
>> that I am only on my 3rd cup of coffee this morning?).....I'm sure if
>> you do a quick Google Advanced search, something will turn up pretty quick.
>>
>>
>> Donchik wrote:
>>> Problem is that the Diagnostics find an error, but tell me nothing about
>>> what it thinks is wrong.
>>>
>>> I need a way to interrogate the BIN file it creates with the error.