Blue screen

[Guest chequer]

WindowsXP Pro SP2

I have been getting blue screens lately

I cannot recall all the incidents that may have caused them but one was when

I tried to open a Notebook file.

The last line in all the blue screens is 0x000000F4.

I tried to get a fix for this but couldn't fimd the right Microsoft page to

get and run the fix.

Could someone please supply the link?

--

chequer

When the game is over, the King and the pawn share the same box.

[Guest PD43]

Re: Blue screen

 

chequer <chequer@discussions.microsoft.com> wrote:

>I have been getting blue screens lately

>I cannot recall all the incidents that may have caused them but one was when

>I tried to open a Notebook file.

 

You're gonna have to remember a LOT more than that.

[Guest chequer]

Re: Blue screen

 

All I want to get the link to MS support where I can get the fix for 0x000000F4

 

I could not open the reply with the supplied link

I finished up searching for it

--

chequer

When the game is over, the King and the pawn share the same box.

 

 

"PD43" wrote:

> chequer <chequer@discussions.microsoft.com> wrote:

>

> >I have been getting blue screens lately

> >I cannot recall all the incidents that may have caused them but one was when

> >I tried to open a Notebook file.

>

> You're gonna have to remember a LOT more than that.

>

[Guest PD43]

Re: Blue screen

 

chequer <chequer@discussions.microsoft.com> wrote:

>All I want to get the link to MS support where I can get the fix for 0x000000F4

 

http://preview.tinyurl.com/33ywxx

[Guest chequer]

Re: Blue screen

 

Thanks,

I didn't run the program as I don't want ' RegCure ' on my computer

I thought that there was an MS secure fix for it

--

chequer

When the game is over, the King and the pawn share the same box.

 

 

"PD43" wrote:

> chequer <chequer@discussions.microsoft.com> wrote:

>

> >All I want to get the link to MS support where I can get the fix for 0x000000F4

>

> http://preview.tinyurl.com/33ywxx

>

[Guest Gerry]

Re: Blue screen

 

The Stop Error report for this error is less helpful than most:

http://msdn2.microsoft.com/en-us/library/ms797140.aspx

 

You may get an answer by running the Windows Debugger on the memory dump

but it ids a challenging task for a typical user:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

 

Have you examined the System and Application logs in Event Viewer for

clues?

 

 

--

 

 

 

Hope this helps.

 

Gerry

~~~~

FCA

Stourport, England

Enquire, plan and execute

~~~~~~~~~~~~~~~~~~~

 

 

chequer wrote:

> Thanks,

> I didn't run the program as I don't want ' RegCure ' on my computer

> I thought that there was an MS secure fix for it

>

>> chequer <chequer@discussions.microsoft.com> wrote:

>>

>>> All I want to get the link to MS support where I can get the fix

>>> for 0x000000F4

>>

>> http://preview.tinyurl.com/33ywxx

[Guest chequer]

Re: Blue screen

 

The Stop Error report for this error is less helpful than most:

http://msdn2.microsoft.com/en-us/library/ms797140.aspx

You may get an answer by running the Windows Debugger on the memory dump

but it ids a challenging task for a typical user:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Have you examined the System and Application logs in Event Viewer for

clues?[end quote]

 

Thanks Gary

No. I do not know how to you examine the System and Application logs in

Event Viewer for clues?

I'll have a look at the 2 web sites but wouldn't know what to do.

 

 

 

--

chequer

When the game is over, the King and the pawn share the same box.

 

 

"Gerry" wrote:

> The Stop Error report for this error is less helpful than most:

> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

>

> You may get an answer by running the Windows Debugger on the memory dump

> but it ids a challenging task for a typical user:

> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

>

> Have you examined the System and Application logs in Event Viewer for

> clues?

>

>

> --

>

>

>

> Hope this helps.

>

> Gerry

> ~~~~

> FCA

> Stourport, England

> Enquire, plan and execute

> ~~~~~~~~~~~~~~~~~~~

>

>

> chequer wrote:

> > Thanks,

> > I didn't run the program as I don't want ' RegCure ' on my computer

> > I thought that there was an MS secure fix for it

> >

> >> chequer <chequer@discussions.microsoft.com> wrote:

> >>

> >>> All I want to get the link to MS support where I can get the fix

> >>> for 0x000000F4

> >>

> >> http://preview.tinyurl.com/33ywxx

>

>

>

[Guest Gerry]

Re: Blue screen

 

Please post copies of all Error and Warning Reports appearing in

the System and Application logs in Event Viewer for the last boot. No

Information Reports or Duplicates please. Indicate which also appear in

a previous boot.

 

You can access Event Viewer by selecting Start, Control Panel,

Administrative Tools, and Event Viewer.

 

A tip for posting copies of Error Reports! Run Event Viewer and double

click on the error you want to copy. In the window, which appears is a

button resembling two pages. Click the button and close Event

Viewer.Now start your message (email) and do a paste into the body of

the message. Make sure this is the first paste after exiting from

Event Viewer.

 

 

--

 

 

 

Hope this helps.

 

Gerry

~~~~

FCA

Stourport, England

Enquire, plan and execute

~~~~~~~~~~~~~~~~~~~

chequer wrote:

>

The Stop Error report for this error is less helpful than

> most: http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> You may get an answer by running the Windows Debugger on the memory

> dump but it ids a challenging task for a typical user:

> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> Have you examined the System and Application logs in Event Viewer for

> clues?[end quote]

>

> Thanks Gary

> No. I do not know how to you examine the System and Application logs

> in Event Viewer for clues?

> I'll have a look at the 2 web sites but wouldn't know what to do.

>

>

>

>

>> The Stop Error report for this error is less helpful than most:

>> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

>>

>> You may get an answer by running the Windows Debugger on the memory

>> dump but it ids a challenging task for a typical user:

>> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

>>

>> Have you examined the System and Application logs in Event Viewer for

>> clues?

>>

>>

>> --

>>

>>

>>

>> Hope this helps.

>>

>> Gerry

>> ~~~~

>> FCA

>> Stourport, England

>> Enquire, plan and execute

>> ~~~~~~~~~~~~~~~~~~~

>>

>>

>> chequer wrote:

>>> Thanks,

>>> I didn't run the program as I don't want ' RegCure ' on my computer

>>> I thought that there was an MS secure fix for it

>>>

>>>> chequer <chequer@discussions.microsoft.com> wrote:

>>>>

>>>>> All I want to get the link to MS support where I can get the fix

>>>>> for 0x000000F4

>>>>

>>>> http://preview.tinyurl.com/33ywxx

[Guest Colin Barnhorst]

Re: Blue screen

 

Right click on My Computer and select Manage. In the Computer Management

windows that opens expand the Event Viewer (on the left side) and select the

Application and System icons.

 

"chequer" <chequer@discussions.microsoft.com> wrote in message

news:07C30BD8-6434-479D-83A0-D1F8DC17B8B3@microsoft.com...

>

The Stop Error report for this error is less helpful than most:

> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> You may get an answer by running the Windows Debugger on the memory dump

> but it ids a challenging task for a typical user:

> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> Have you examined the System and Application logs in Event Viewer for

> clues?[end quote]

>

> Thanks Gary

> No. I do not know how to you examine the System and Application logs in

> Event Viewer for clues?

> I'll have a look at the 2 web sites but wouldn't know what to do.

>

>

>

> --

> chequer

> When the game is over, the King and the pawn share the same box.

>

>

> "Gerry" wrote:

>

>> The Stop Error report for this error is less helpful than most:

>> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

>>

>> You may get an answer by running the Windows Debugger on the memory dump

>> but it ids a challenging task for a typical user:

>> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

>>

>> Have you examined the System and Application logs in Event Viewer for

>> clues?

>>

>>

>> --

>>

>>

>>

>> Hope this helps.

>>

>> Gerry

>> ~~~~

>> FCA

>> Stourport, England

>> Enquire, plan and execute

>> ~~~~~~~~~~~~~~~~~~~

>>

>>

>> chequer wrote:

>> > Thanks,

>> > I didn't run the program as I don't want ' RegCure ' on my computer

>> > I thought that there was an MS secure fix for it

>> >

>> >> chequer <chequer@discussions.microsoft.com> wrote:

>> >>

>> >>> All I want to get the link to MS support where I can get the fix

>> >>> for 0x000000F4

>> >>

>> >> http://preview.tinyurl.com/33ywxx

>>

>>

>>

[Guest chequer]

Re: Blue screen

 

I'll have a go but I think the computer is very sick

--

chequer

When the game is over, the King and the pawn share the same box.

 

 

"Gerry" wrote:

> Please post copies of all Error and Warning Reports appearing in

> the System and Application logs in Event Viewer for the last boot. No

> Information Reports or Duplicates please. Indicate which also appear in

> a previous boot.

>

> You can access Event Viewer by selecting Start, Control Panel,

> Administrative Tools, and Event Viewer.

>

> A tip for posting copies of Error Reports! Run Event Viewer and double

> click on the error you want to copy. In the window, which appears is a

> button resembling two pages. Click the button and close Event

> Viewer.Now start your message (email) and do a paste into the body of

> the message. Make sure this is the first paste after exiting from

> Event Viewer.

>

>

> --

>

>

>

> Hope this helps.

>

> Gerry

> ~~~~

> FCA

> Stourport, England

> Enquire, plan and execute

> ~~~~~~~~~~~~~~~~~~~

> chequer wrote:

> >

The Stop Error report for this error is less helpful than

> > most: http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> > You may get an answer by running the Windows Debugger on the memory

> > dump but it ids a challenging task for a typical user:

> > http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> > Have you examined the System and Application logs in Event Viewer for

> > clues?[end quote]

> >

> > Thanks Gary

> > No. I do not know how to you examine the System and Application logs

> > in Event Viewer for clues?

> > I'll have a look at the 2 web sites but wouldn't know what to do.

> >

> >

> >

> >

> >> The Stop Error report for this error is less helpful than most:

> >> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> >>

> >> You may get an answer by running the Windows Debugger on the memory

> >> dump but it ids a challenging task for a typical user:

> >> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> >>

> >> Have you examined the System and Application logs in Event Viewer for

> >> clues?

> >>

> >>

> >> --

> >>

> >>

> >>

> >> Hope this helps.

> >>

> >> Gerry

> >> ~~~~

> >> FCA

> >> Stourport, England

> >> Enquire, plan and execute

> >> ~~~~~~~~~~~~~~~~~~~

> >>

> >>

> >> chequer wrote:

> >>> Thanks,

> >>> I didn't run the program as I don't want ' RegCure ' on my computer

> >>> I thought that there was an MS secure fix for it

> >>>

> >>>> chequer <chequer@discussions.microsoft.com> wrote:

> >>>>

> >>>>> All I want to get the link to MS support where I can get the fix

> >>>>> for 0x000000F4

> >>>>

> >>>> http://preview.tinyurl.com/33ywxx

>

>

>

[Guest chequer]

Re: Blue screen

 

Gary,

I had the doctor call this morning and he confirmed that my computer has a

terminal ailment and has to have a Re-formant transplant.

 

I'll be off the air for a few days

--

chequer

When the game is over, the King and the pawn share the same box.

 

 

"Gerry" wrote:

> Please post copies of all Error and Warning Reports appearing in

> the System and Application logs in Event Viewer for the last boot. No

> Information Reports or Duplicates please. Indicate which also appear in

> a previous boot.

>

> You can access Event Viewer by selecting Start, Control Panel,

> Administrative Tools, and Event Viewer.

>

> A tip for posting copies of Error Reports! Run Event Viewer and double

> click on the error you want to copy. In the window, which appears is a

> button resembling two pages. Click the button and close Event

> Viewer.Now start your message (email) and do a paste into the body of

> the message. Make sure this is the first paste after exiting from

> Event Viewer.

>

>

> --

>

>

>

> Hope this helps.

>

> Gerry

> ~~~~

> FCA

> Stourport, England

> Enquire, plan and execute

> ~~~~~~~~~~~~~~~~~~~

> chequer wrote:

> >

The Stop Error report for this error is less helpful than

> > most: http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> > You may get an answer by running the Windows Debugger on the memory

> > dump but it ids a challenging task for a typical user:

> > http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> > Have you examined the System and Application logs in Event Viewer for

> > clues?[end quote]

> >

> > Thanks Gary

> > No. I do not know how to you examine the System and Application logs

> > in Event Viewer for clues?

> > I'll have a look at the 2 web sites but wouldn't know what to do.

> >

> >

> >

> >

> >> The Stop Error report for this error is less helpful than most:

> >> http://msdn2.microsoft.com/en-us/library/ms797140.aspx

> >>

> >> You may get an answer by running the Windows Debugger on the memory

> >> dump but it ids a challenging task for a typical user:

> >> http://www.microsoft.com/whdc/devtools/debugging/default.mspx

> >>

> >> Have you examined the System and Application logs in Event Viewer for

> >> clues?

> >>

> >>

> >> --

> >>

> >>

> >>

> >> Hope this helps.

> >>

> >> Gerry

> >> ~~~~

> >> FCA

> >> Stourport, England

> >> Enquire, plan and execute

> >> ~~~~~~~~~~~~~~~~~~~

> >>

> >>

> >> chequer wrote:

> >>> Thanks,

> >>> I didn't run the program as I don't want ' RegCure ' on my computer

> >>> I thought that there was an MS secure fix for it

> >>>

> >>>> chequer <chequer@discussions.microsoft.com> wrote:

> >>>>

> >>>>> All I want to get the link to MS support where I can get the fix

> >>>>> for 0x000000F4

> >>>>

> >>>> http://preview.tinyurl.com/33ywxx

>

>

>