From: relayPoint 

On Wed, 12 Mar 2003 11:43:11 +0000, Chris Robinson
 said all this:

>When you say you've gone over the hardware and found nothing wrong does
>this mean you've swapped out various hardware for other hardware?

Among other things.

> It could well be that any part of your hardware is on the way out but you
>just can't detect it.  Wear and tear could be the cause here?  In this
>case there's not much you can do other than swap out each and every bit of
>your PC to see which bit's causing the problem.

The only parts not swapped are board and CPU. I'm running FreeBSD
-CURRENT on another drive (SCSI) I have plugged into this system, and
if there was anything wrong, believe me, I would know IMMEDIATELY.

>You could run diagnostics tools first I guess but you may have already done
this?
>That said, does it only happen when you CTRL-ALT-DEL and lock?  If so, there
>are some tools from Sysinternals that could be of use here.  They're called
>procmonand regmon (www.sysinternals.com).  Run both on a healy PC to see
>what happens when you lock and then unlock your PC (it'll show you which files
>are accessed/ which parts of the reg are accessed).  Also run this on your
>faulty system and see if there're any major differences (e.g. hangs occur
>when accessing a particular part of the registry or a particular file).  I
>find these tools very useful for odd Windows problems.

The "Unknown Hard Error" *ONLY* occurs when I use Ctrl-Alt-Del.
Otherwise, Explorer will sit there dumbfounded for hours if I let it. I've
actually used procmon and regmon, and it's not showing anything abnormal
when I get the Unknown Hard Error. There's absolutely no difference from a
normal lock and one that produces that. :(  I'm really and truly stumped..
time to build a new system, I guess.. no choice really. ;P
_rP
INSERT INTO news.barkto(post) VALUES ("above::post");

--- BBBS/NT v4.01 Flag-4