Question Locked

My system Restarts every 5min and event log shows Event id 1001 ...pls help

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Dear Friends,

My system Restarts every 5min and event log shows Event id 1001,to stop restart i diclicked Auto restart from system properties but i m getting continous error for "system recover from serious error" .event viewer shows dump file was created. I downloaded WinDBG tool but dont know how to use it so request you to help me

I have uploaded dump file on below link :-
http://www.easy-share.com/1904802705/Mini dump and error 0x1000000a.rar

pls help

4 replies

by oh smeg

This will be useful to you.

http://support.microsoft.com/kb/271213

the main part of the text though is this

[i]SYMPTOMS Event ID 1000 and 1001 may be repeatedly be logged in the Application log every...Event ID 1000 and 1001 may be repeatedly be logged in the Application log every five minutes with the following information:
Event Type: Error
Event Source: SceCli
Event Category: None
Event ID: 1001
Date: 4/7/2000
Time: 4:30:46 AM
User: N/A
Computer: MYCOMPUTER
Description: Security policy cannot be propagated. Cannot access the template. Error code = 3. \\mydomain.com\sysvol\mydomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 4/7/2000
Time: 4:30:46 AM
User: NT AUTHORITY\SYSTEM
Computer: MYCOMPUTER
Description: The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (3).
Back to the top
CAUSEThis issue can occur if the %SystemRoot%\SYSVOL\Domain\Policies Group Policy dir...This issue can occur if the %SystemRoot%\SYSVOL\Domain\Policies Group Policy directory structure is missing or is incorrect. The Replication service is trying to replicate the directory but cannot locate it.
Back to the top
RESOLUTIONTo resolve this issue, the directory must be restored to allow replication betwe...To resolve this issue, the directory must be restored to allow replication between domain controllers. This directory can either be restored from a backup or it can be recreated. For additional information about how to recreate the policy directory, click the article numbers below to view the articles in the Microsoft Knowledge Base:
253268 (http://support.microsoft.com/kb/253268/EN-US/ ) Group Policy Error Message Without Appropriate Sysvol Contents
257338 (http://support.microsoft.com/kb/257338/EN-US/ ) Troubleshooting Missing SYSVOL and NETLOGON Shares[/i]

by rob miners

Boot into your BIOS and enable Plug and Play (PNP OS).
Either uninstall or update Kaspersky Antivirus drivers.
Update to the latest Chipset drivers for your Motherboard.

If that doesn't get you going run these tests.

You can test the memory by running Windows Memory Diagnostic that can be downloaded from http://oca.microsoft.com/en/windiag.asp. If memory problems are found, try re-seating the RAM. If it doesn't work, replace the defective RAM.

You can use the Hard Drive Makers Testing Utility to Test the Drive which can be downloaded from below.
Hitachi / IBM
Western Digital
Fujitsu
Seagate
Samsung

Let us know how you get on.

by rob miners

Click Start, right mouse click Computer and select Properties. Select Advanced System Properties, continue. Select Settings for Startup and Recovery. Untick Automatically Restart.

Minidump Files can be found here. C:\WINDOWS\Minidump\Mini******-**.dmp

How to read the small memory dump files that Windows creates for debugging

http://support.microsoft.com/kb/315263

To download and install the Windows debugging tools, visit the following Microsoft Web site:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

Instructions on using Windbg.

Open Windbg and select file, Symbol file path and brows to the Symbol folder that you have downloaded and installed Symbols to, select OK.

Close the workpage and save the Workspace information. This should lock in the Symbol path.

Open Windbg and select file and select Open Crash Dump then navigate to the minidump, highlight it and select Open.

There are two ways to use !analyze -v the easiest is to click on !analyze -v under Bugcheck Analysis.

When you have ran the initial dump if you look to the bottom of the screen you will see kd> to the right of that type in !analyze -v and press the Enter key.

Ctrl + a will let you copy the information and paste it into notepad.

Look to the bottom of the page for information like this. This was fixed by updating the Graphics Drivers.

FAULTING_THREAD: 864f6a98

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

PROCESS_NAME: logon.scr

LAST_CONTROL_TRANSFER: from 00000000 to bfef0fea

STACK_TEXT: f6434e6c 00000000 00000000 00000000 00000000 sgiul50!DrvBitBlt+0x585

STACK_COMMAND: .thread 0xffffffff864f6a98 ; kb

FOLLOWUP_IP: sgiul50!DrvBitBlt+585 bfef0fea 75f9 jne sgiul50!DrvBitBlt+0x580 (bfef0fe5)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: sgiul50!DrvBitBlt+585

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: sgiul50

IMAGE_NAME: sgiul50.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 3b7dfec7

FAILURE_BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

BUCKET_ID: 0xEA_IMAGE_sgiul50.dll_DATE_2001_08_18

This discussion is closed to new replies.