Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows 98 / Performance / November 2008

Tip: Looking for answers? Try searching our database.

Dr Watson Reports

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Dougair - 29 Jan 2006 15:57 GMT
With limited RAM at present (64MB's), I'm working hard to keep up with a
selection of fault messages and reboots, and in the last few days, Dr Watson
is reporting:-

"Windows User-interface core component attempted to access memory that does
not exist.

Module Name: user.exe
Description: Windows User-interface core component
Version: 4.10.1998
Product: Microsoft(R) Windows(R) Operating System
Manufacturer: Microsoft Corporation

Application Name: Iexplore.exe
Description: Internet Explorer
Version: 6.00.2800.1106
Product: Microsoft® Windows® Operating System
Manufacturer: Microsoft Corporation"

This is mainly with IE but other programmes also bring up same fault.
Two points, the IE vers. is shown as 5.6.0.2800 as well as 6.00.2800 (as
above) - is it an IE5 or 6? and is the fact that the 'user.exe' (dated
4.10.98.) is in need of an update?

Would appreciate any help!
Thanks
Signature

Dougair

Jeff Richards - 30 Jan 2006 08:16 GMT
If you get rid of Dr Watson then you will be able to see the real error
message, and you can search on it in the MS knowledgebase, or in Google.
Signature

Jeff Richards
MS MVP (Windows - Shell/User)

> With limited RAM at present (64MB's), I'm working hard to keep up with a
> selection of fault messages and reboots, and in the last few days, Dr
[quoted text clipped - 24 lines]
> Would appreciate any help!
> Thanks
Dougair - 30 Jan 2006 11:27 GMT
Jeff,

The reason I used the data from Drwatson, was because Microsoft stated in
the early days that the lengthy 'data' that is recorded - and there's much
more than the brief summary I put, PLUS, the fact that I got, and get, along
with the DrW report, a 'Fatal Exception' (or other) message; these tend to
differ and depend on program I'm working with at the time - that the
'snapshop' would show up the problem!?!

Although I do get problems sometimes right after rebooting, usually, Windows
works well for up to 2 hours and then suddenly slows and shows reluctance to
act on a 'click', when I know that it's just about to freeze.    Sometimes I
can save it doing so by Ctrl-Alt-Dlt and removing the working program (or
'not responding') - other times not!

It's not a heat problem, the fans are working AND after a 'reboot' the
system will work again for up to 2 hours.
It has been exacerbated by putting in Norton 2005, because I suspect, the
greedy RAM taker, and I believe IE and Norton do clash, but is not the
primary reason as it was suddenly rebooting before Norton.    

It is possible that the sudden reboot is causing damage and loss to files,
but when all systems are working, it goes on for some time working well,
which, if there was damaged or missing NECCESSARY files, would be unlikely.

I am no expert, but am having to learn fast, and I DO use the Knowledge
Base, which is excellent, and the Internet to find out what ALL the messages
mean.     There however must be a common cause at the centre of most of the
spread of 'problem messages'.     We'll get there, and thanks for your help,
but apart from reinstalling Windows - which until I can save much info. I
have no intention of doing, any thoughts are appreciated.    
I have a lot of time for Microsoft design - and the ability of the system to
overcome!

Thanks,

Signature

Dougair

> If you get rid of Dr Watson then you will be able to see the real error
> message, and you can search on it in the MS knowledgebase, or in Google.
[quoted text clipped - 26 lines]
> > Would appreciate any help!
> > Thanks
Richard G. Harper - 30 Jan 2006 22:38 GMT
The Dr. Watson dump file and log are for software developers to troubleshoot
a problem with a program or a driver.  For human beings they are completely
useless and they obscure the error message that might allow humans to figure
out the problem.

Turn off Dr. Watson, then post the actual error message excluding the
register data.

Signature

Richard G. Harper [MVP Shell/User]  rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all.  Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

> Jeff,
>
[quoted text clipped - 5 lines]
> differ and depend on program I'm working with at the time - that the
> 'snapshop' would show up the problem!?!
Jeff Richards - 31 Jan 2006 09:38 GMT
Even though there might be a common cause, you can only track it down using
a specific error, and for that you need the message without the Dr Watson
embellishments.
Signature

Jeff Richards
MS MVP (Windows - Shell/User)

> Jeff,
>
[quoted text clipped - 38 lines]
> to
> overcome!
Dougair - 01 Feb 2006 11:54 GMT
Drwatson has been stopped - thanks!

Sorry for the delay, the computer yesterday (Tues 31st) behaved impeccably
until on Shutdown, it rebooted instead of shutting down, twice, but then a
normal shutdown.
It's still working pretty well today, but after initial start and feeling
that something was not quite right, checked and 'CCAPP' (Symantec, and needed
for virus protection) shown as 'not responding'.    Did a restart, which hung
just before Win Shut Dn page, and on initiating manual reboot with a Scandisc
check, started with no problems and worked well for 20 minutes.     Then,
with one page in IE open and in pressing 'delete' button to remove part of an
address in 'bar', up came 'Programme has performed an Illegal Operation and
will be Shut Down.     Details: showed 'IExplore caused an Invalid Page Fault
in Module User.Exe @ 001e:0000166c'.
Explorer closed and the rest remained normal, and, on reopening Explorer it
has continued as if nothing had happened.

I said rest remained normal, as sometimes something is removed from
'desktop' and often slow or a freeze takes place.

In the last couple of weeks, I haven't recorded the same fault and they
range from MSGSRV32 caused a segment not present fault in Module KRNL386.exe
@ 001:00001c33, to 'blue screens' and an OE fault, thro' SCANDSKW caused an
Invalid Page Fault in Module Kernel32.dll@015f:bff9dba after I ran a
'thorough' SCAN in 'Safe Mode' to see if anything was reported.  
The report was that the disc was working perfectly and no problems.

I suspect, now that the 'Doctor has been relieved of his job, it might be
better just to keep recording each 'blip' and see if a common 'theme' shows
up, especially as it's not throwing fault messages out every few minutes, as
it did for a while.

Thanks again for excellent support!
Signature

Dougair

> Even though there might be a common cause, you can only track it down using
> a specific error, and for that you need the message without the Dr Watson
[quoted text clipped - 41 lines]
> > to
> > overcome!
Jeff Richards - 02 Feb 2006 09:17 GMT
A common theme that can be quite revealing is no theme at all.  That would
indicate a hardware problem, of which memory (RAM) would be a good suspect.

Before starting any serious trouble shooting, get a good RAM diagnostic and
give it a thorough run - at least overnight.  Then you can debug the
software confident that you're not being led up the garden path by random
hardware errors.
Signature

Jeff Richards
MS MVP (Windows - Shell/User)

> Drwatson has been stopped - thanks!
>
[quoted text clipped - 98 lines]
>> > to
>> > overcome!
Dougair - 02 Feb 2006 15:30 GMT
Yes, thanks, Jeff, I will do that, and get back to this page when I get some
results.    I had been thinking about adding some more RAM anyway once I know
what type I have so will concentrate on that aspect.
Thanks again for your advice,
Doug J
Signature

Dougair

> A common theme that can be quite revealing is no theme at all.  That would
> indicate a hardware problem, of which memory (RAM) would be a good suspect.
[quoted text clipped - 105 lines]
> >> > to
> >> > overcome!
Dougair - 04 Feb 2006 18:37 GMT
4/2/'06 After your suggestion, downloaded 'Microsoft Windows Memory
Diagnostic' to run that night, but on 'bootup', the computer brought up the
'details' page but failed to do anything further.   In case it was a faulty
copy, downloaded to another 'floppy' the Diagnostic, but the same result!    
  So, normal boot to go and look at Knowledge Base for suggestions or
suggested diagnostic tools - nothing found, other than the above, so went to
the 'aumha.org' site for a safe alternative, and found 'DocMemory v2.2'.      

The 'normal boot' in fact was into a very unstable computer (due 'floppy'
attempt?), with a number of sudden reboots (without 'fault windows')  as well
as various 'faults', ending with a 'Fatal Exception OE @ 0177:BFF9DBA7' on
final shutdown.       Because it was late and the computer was so unstable,
closed down for the night.
Following day, the computer booted and ran perfectly for 8 hours, then a
sudden reboot and continued with no problems.

The 'floppy' was inserted for DocMemory and booted into the 'index.page'.  
The 'mixed test program' (burnt-in) was selected and started first loop.      
It continued thro' night and with some 60 loops - all were a pass!    No
failures shown.    
The computer has again booted up normally and is running without problems.

One fault has now shown up 4 times in the last three days, it is : IExplore
caused an Invalid Page Fault in Module User.Exe @001e:0000166c', but, in the
last 36 hours, there has been no sign (other than the one sudden reboot
mentioned) of problems.

A 'bootlog' made a few days ago, ends 'Terminate= 'User';  Terminate= 'Query
Drivers';   End Terminate= Query Drivers';  but I suspect this is another
issue, or is there possibly a Driver issue connected?

Thanks Again  
Signature

Dougair

> Yes, thanks, Jeff, I will do that, and get back to this page when I get some
> results.    I had been thinking about adding some more RAM anyway once I know
[quoted text clipped - 111 lines]
> > >> > to
> > >> > overcome!
Jeff Richards - 06 Feb 2006 08:10 GMT
Sudden reboots without a fault report suggest hardware, such as power
supply, or socket connections somewhere.

DocMemory is an adequate memory tester, so I think you've eliminated RAM.

However, getting periods of stability and periods of instability also
suggests hardware issues.  Power supply faults can cause random reboots.

For the IE error, check
   Add-ins, such as browser bars or pop-up blockers (remove them all).
   Viruses and adware
   Clear all temporary files and offline data, history, etc.
   Remove startup items you don't really need.

Also, explore here for a variety of useful tips, including installing a
replacement browser.
http://inetexplorer.mvps.org/ie.html

When troubleshooting, always do one thing at a time and test thoroughly
before moving on.
Signature

Jeff Richards
MS MVP (Windows - Shell/User)

> 4/2/'06 After your suggestion, downloaded 'Microsoft Windows Memory
> Diagnostic' to run that night, but on 'bootup', the computer brought up
[quoted text clipped - 190 lines]
>> > >> > to
>> > >> > overcome!
Dougair - 06 Feb 2006 15:30 GMT
Yes, thanks Jeff; I've taken all you say on board and will follow it up!    
I have qualifications in electrical engineering (from 50 years ago) so am
perfectly happy working with the hardware.    The fans are inspected and
dust/dirt cleaned out, contacts, etc., checked, but will have a more detailed
check and see if I can see any intermittent 'snags.
Will also get to work on a replacement 'Browser' - so many of the fault
messages do have the present ' Browser as one item.

Very many thanks for all your advice!
Doug J
Signature

Dougair

> Sudden reboots without a fault report suggest hardware, such as power
> supply, or socket connections somewhere.
[quoted text clipped - 210 lines]
> >> > >> > to
> >> > >> > overcome!
newscruzer1 - 06 Nov 2008 03:55 GMT
> If you get rid of Dr Watson then you will be able to see the real error
> message, and you can search on it in the MS knowledgebase, or in Google.
[quoted text clipped - 26 lines]
> > Would appreciate any help!
> > Thanks
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.