[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:Windows NT
Notice:See note 15.0 for HCL location
Moderator:TARKIN::LIN.com::FOLEY
Created:Thu Oct 31 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6086
Total number of notes:31449

5724.0. "Win NT v4 freeze/hang" by NETRIX::"[email protected]" (Steve Bevis) Thu Feb 20 1997 04:37

Hi,
Can anyone out there help us. We have the following scenario:-
Hardware:   Alphastation 600
            128 meg (64 meg in 2 Banks)
            ZLXP-L1 graphics controller
            Storage on the standard I/O card.
            ARC V4.49

Software:   Windows NT V.4.0 & Service pack 2
            Windows 3D Image ?

Problem:    Windows NT freezes and can is cleared by power cycle. 

            Customer has 3 of the above systems identically
            configured. Only one has the problem. It started since
            the system was upgraded to V4.0. The failing system was
            upgraded and run without service pack 2 for two weeks.
            The good systems were upgraded and the service pack 
            installed at the same time.

            On the face of it, it appears to be a hardware problem
            and the system module was changed to no avail.

Does anyone know of a technique or tool that will better help us
understand or assist in deciding if it hardware or software and
if it decided it is hardware, identifying a failing area, i.e. cache,
memory, io etc.

thanks in anticipation
   
Steve Bevis

            
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
5724.1Debug Mode ?MSE1::mse-tatenger.mse.tay.dec.com::ChenisKenneth ChenisFri Feb 21 1997 13:4811
If you boot into debug mode, and set up a debug
console machine, you should be able to ctrl-c 
into the kernel when it is hung.  This would let
you poke around and see what it was doing, or at
least crash it, and get a dump for someone else
to take a gander at.

Hope this helps a little (probably very little eh?)

Ken Chenis
Multivendor Systems Engineering