Archived from groups: microsoft.public.windowsxp.newusers (
More info?)
"Freezing up or locking up is very rarely a result of defective hardware"
I would disagree with that assertion, and I think you will find a fair
number of others do as well. Years of experience tell me otherwise. As a
recent example, a machine i just worked on this week had had random freezes
for months before she brought it to me. No error messages, nothing in the
event viewer, just a solid freeze and nothing worked. This person had good
user habits, system and AV were kept updated, there were no bugs, ads, or
spy programs present. Pulled the processor, counted 7 leaky capacitors on
the board that two other previous techs had missed. New m-board and all is
well in the world for her.
This is a new system under warranty. The supplied drivers, while not the
most recent, should at least be sufficient as WinXP has been out for more
than 2 years now. Under no circumstances should the owner mess with it. The
manufacturer can and will use any excuse to void the warranty. Making them
own up to it and getting it straight is what that warranty is for. Use it,
there is no reason anyone should have to muck about on their own with a new
system.
--
Best of Luck,
Rick Rogers aka "Nutcase" MS-MVP - Windows
Windows isn't rocket science! That's my other hobby!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org
"The Unknown P" <mikisiw@msn.com> wrote in message
news:14E50061-0557-4084-A77D-76E5B70EA25C@microsoft.com...
> Using Nutcases method is rather drastic in my opinion. Freezing up or
> locking up is very rarely a result of defective hardware. In most cases
> it's a matter of the individual not having the latest drivers for XP from
> the hardware manufacturer and the system is trying to initiate a higher
> function that is called for and not finding it in the driver program so
> goes into a locked or loop state. This is where the event viewer comes
> into play. go>start\control panel\administrative tools\event viewer and
> double click the system or software log on the left to open it in the
> right panel. Now look for any red X's that correspond to the time of you
> lockup. Double click them to open a details window. Now this may or may
> not help you as most of it you won't be able to understand. If you post
> back with the event ID and perhaps the applicaton or module that caused
> the problem then we can give you more assistance on what to fix. In the
> mean time spend a day or two getting the latest drivers for your system
> from the manufacturers. This means for everythign from your mouse to your
> monitor. Welcome to the eXPeriance. {:~)
Facebook
Twitter
Instagram