[wolf]

MasterBit
Ты посмотри, что пишет в шапке..., т.е. EventID, Source... (и скажи нам)

[MasterBit]

Ну вроде про это меня спросили:?

тип-уведомление,
источник- Save Dump

Добавлено:

Ну вроде про это меня спросили:?

тип-уведомление,
источник- Save Dump
категория - отсутсвует
событие-1001

[wolf]

Ответы здесь: http://www.eventid.net/display.asp?a...p;eventid=1001

Если что-то непонятно, пиши...

[MasterBit]

Ну если честно, то мне ничего не понятно. Что делать то...?

Почти сразу после установки вин2к сп2 ушел в синий экран

STOP:0x00000050 (0xEB630018,0x00000000,0xA0011E48,0x00000000)
PAGE_FAULT_IN_NON_PAGED_AREA
Address A0011E48 base at A0000000, DateStamp 3aa010b4 win32k.sys

может подскажете в чем тут может быть дело?

Конфигурация Athlon 1700+, Shuttle AK32 (VIA xxx), 256x2 DDR, HDD IBM (с ним проблем нет), не разогнан.

Да и вин98се подвисает иногда, понимаю что проблема в где-то в железе, но где именно ?

[wolf]

MasterBit
Вот статьи на эту тему, которые упоминаются по данной теме:
PSS ID Number: Q192463
Article last modified on 01-17-2000

WINDOWS:2000; winnt:4.0

WINDOWS winnt


======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows NT Server version 4.0
- Microsoft Windows NT Workstation version 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
-------------------------------------------------------------------------------

SUMMARY
=======

The information below covers some steps you can take to gather more information
about a blue screen error message. These steps will not always provide
conclusive answers and may only be a symptom of another problem.

Event Log Messages
------------------

- Set up your system to write an event log message with bugcheck information.

  Windows NT Server 4.0 is set to write event log messages by default. Windows
 NT Workstation is not set by default. To set your system to write an event
 log message, click to select the "Write an event to the system log" check box
 located in the Recovery section of the Startup/Shutdown tab in System
 Properties. This will cause an event log message to be written to the system
 log.

- Data contained in the event log message.

  The description and format of the event log differs from the format displayed
 when the computer is writing the Memory.dmp file, but the majority of the
 information is the same. Below is an example of the event log.

     Event ID: 1001
    Source: Save Dump
    Description:
      The computer has rebooted from a bugcheck. The bugcheck was :
      0xc000021a (0xe1270188, 0x00000001, 0x00000000, 0x00000000).
      Microsoft Windows NT (v15.1381). A dump was saved in:
      C:\WINNT\MEMORY.DMP.

  This information contains the stop code 0xc000021a and the four parameters.
 These can be very useful when troubleshooting certain types of stop codes.
 The parameters will mean different things depending on what type of stop code
 it is. For information on what the parameters represent, search the Knowledge
 Base for the specific STOP code. Not all STOP code parameters are covered in
 the Knowledge Base.

Using Dumpchk.exe to Determine Memory Dump Information
------------------------------------------------------

If you use Dumpchk.exe from the Service Pack 3 CD, you can determine all of the
above information as well as the address of the driver that generated the stop
message. This information can often give you a direction to begin
troubleshooting. Before you run Dumpchk.exe, be sure to adjust the properties of
the command prompt so that the screen buffer size height is set to 999. This
height will allow you to scroll back to see the output. Run Dumpchk.exe from the
command prompt with the following syntax:

dumpchk.exe Memory.dmp

The following is an example of the portions of the output that are most useful.

  MachineImageType   i386
 NumberProcessors   1
 BugCheckCode      0xc000021a
 BugCheckParameter1   0xe1270188
 BugCheckParameter2   0x00000001
 BugCheckParameter3   0x00000000
 BugCheckParameter4   0x00000000

  ExceptionCode      0x80000003
 ExceptionFlags      0x00000001
 ExceptionAddress   0x8014fb84

As previously mentioned, not all sections will give the same information. This
will depend on the type of STOP code. The information above tells us the STOP
code (0xc000021a) and the parameters (0xe1270188, 0x00000001, 0x00000000,
0x00000000), as well as the address of the driver that called the exception
(0x8014fb84). This address can be used to identify the driver name using the
output from running Pstat.exe, which can be found on the resource kit.

Dumpchk.exe will also verify that the dump is valid.

Using Pstat.exe to Identify Driver Information
----------------------------------------------

Pstat.exe, a resource kit utility, will give you a picture of the processes and
drivers currently running on your system. For these purposes, the most useful
information will be the list of loaded drivers that appears at the end of the
output. All you need to do is run Pstat.exe from the command line. The
information given by Pstat.exe can be piped to a file using the following
sytax:

pstat.exe > filename


By using the starting address shown above under the "load addr" column, you can
match the exception address to the driver name. Using 8014fb84 as an example,
you can determine that Ntoskrnl.exe has the nearest load address below the
exception address and is most likely the driver that called the exception. With
this information, you can go to the Knowledge Base to look for known issues that
match your situation.

REFERENCES
==========

For additional information, please see the following article in the Microsoft
Knowledge Base:

  Q129845 Blue Screen Preparation Before Contacting Microsoft

  Q103059 Descriptions of Bug Codes for Windows NT

Additional query words: howto

======================================================================
Keywords          :  
Version           : WINDOWS:2000; winnt:4.0
Platform          : WINDOWS winnt
Issue type        : kbinfo
=============================================================================
Copyright Microsoft Corporation 2000.



Если не понятно, пиши опять...

[MasterBit]

Я попробЫвал переустановить Win 2K но у меня снова та же самая проблема, вот wolf написал что-то по аглицки, я попробЫвал перевести и я понял что там про утилитки писалось типа chkdump dumpexam и т.д. но у win 2K нет этих утилит а от NT они не работают.
Помоги уважаемый
wolf


Добавлено:

Да кстати, я не устанавливал CPU Cool так что дело не в ней. Но снова Поставил DrWeb`а -  может дело внем?????

[MasterBit]

Как показал опытный путь "метод тыка", дело оказалось в DrWeb`овском Spider, я его отключил и перезагузки прекратились.
Теперь думаю какой антивирь использовать в трее

[Guest]