[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Server 2003 System Error Event ID:1003

Posted on 2008-11-06
9
Medium Priority
?
2,555 Views
Last Modified: 2012-05-05
Hi
I am running a windows server 2003 standart x86.  The server rebooted itself 3 times today.  I can seem to find what is causing the issue.  I have searched up and down for the problem.  I have attached the minidump file, i have renamed the .dmp to .dmp.txt so that i can upload the file.  

Any and all help is greatly appreciated
DumpFile.zip
0
Comment
Question by:netsmart1
  • 5
  • 4
9 Comments
 
LVL 29

Expert Comment

by:Michael Worsham
ID: 22900550
Event ID 1003 is usually in some relation to a driver that has been installed or updated and is causing conflicting issues with the Windows OS kernel.

How to read the small memory dump files that Windows creates for debugging
http://support.microsoft.com/kb/315263

Also, does your EventLog show any errors or warnings? If so, post them here as well.

0
 

Author Comment

by:netsmart1
ID: 22900591
I got a system error

Source: System Error
Category (102)
Even ID: 1003
Type: Error

Error code 00000050, parameter1 fffffff3, parameter2 00000000, parameter3 8089b738, parameter4 00000000.

The shutdown event tracker also showed this.
Source: USER32
Category: None
Event ID: 1076
Type: Warning

The reason supplied by user CAI\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
 Reason Code: 0x805000f
 Bug ID:
 Bugcheck String: 0x00000050 (0xfffffff3, 0x00000000, 0x8089b738, 0x00000000)
 Comment: 0x00000050 (0xfffffff3, 0x00000000, 0x8089b738, 0x00000000)
0
 
LVL 29

Expert Comment

by:Michael Worsham
ID: 22904341
There is a Microsoft Hotfix available for this issue...

You may receive various Stop error messages on a computer that is running Windows Server 2003
http://support.microsoft.com/kb/937455
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:netsmart1
ID: 22909454
mwecomputers, thank you for the suggestion.  I have applied the hotfix, i will let you know how it turns out.
0
 

Author Comment

by:netsmart1
ID: 22912954
Nope did not work, the server still shutsdown unexpected.  I cant seem to figure out from the dump file what the problem is.
0
 

Author Comment

by:netsmart1
ID: 22916252
Here is what my dump file is telling me.. any and all help is appreciated..

System Uptime: 0 days 3:48:18.812
Loading Kernel Symbols
....................................................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 8082c64e, f714fbd8, f714f8d4}

Probably caused by : srv.sys ( srv!SrvTerminateWorkerThread+57 )

Followup: MachineOwner
---------

3: kd> -v
       ^ Syntax error in '-v'
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8082c64e, The address that the exception occurred at
Arg3: f714fbd8, Exception Record Address
Arg4: f714f8d4, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx".
 The memory could not be "%s".

FAULTING_IP:
nt!MmDeleteTeb+54
8082c64e f6432702        test    byte ptr [ebx+27h],2

EXCEPTION_RECORD:  f714fbd8 -- (.exr 0xfffffffff714fbd8)
ExceptionAddress: 8082c64e (nt!MmDeleteTeb+0x00000054)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000027
Attempt to read from address 00000027

CONTEXT:  f714f8d4 -- (.cxr 0xfffffffff714f8d4)
eax=00000000 ebx=00000000 ecx=8a375358 edx=f714fc94 esi=8a39a648 edi=886f6a40
eip=8082c64e esp=f714fca0 ebp=f714fcb8 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!MmDeleteTeb+0x54:
8082c64e f6432702        test    byte ptr [ebx+27h],2       ds:0023:00000027=00
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The
 memory could not be "%s".

READ_ADDRESS:  00000027

BUGCHECK_STR:  0x7E

EXCEPTION_STR:  0x0

LAST_CONTROL_TRANSFER:  from 8091f8d6 to 8082c64e

STACK_TEXT:
f714fcb8 8091f8d6 8a39a728 887ae68c 886f6a40 nt!MmDeleteTeb+0x54
f714fd44 809206e4 00000000 00000102 00000000 nt!PspExitThread+0x4ea
f714fd5c 808feaa7 886f6a40 00000000 00000001 nt!PspTerminateThreadByPointer+0x4b
f714fd70 b6c8491d 00000000 89f730e0 00000010 nt!PsTerminateSystemThread+0x26
f714fd84 b6c9f245 00000000 886f6a40 00000000 srv!SrvTerminateWorkerThread+0x57
f714fdac 80920833 00f730e0 00000000 00000000 srv!WorkerThread+0xa1
f714fddc 8083fe9f b6c98602 89f730e0 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
srv!SrvTerminateWorkerThread+57
b6c8491d 5e              pop     esi

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  srv!SrvTerminateWorkerThread+57

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: srv

IMAGE_NAME:  srv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48b558b6

STACK_COMMAND:  .cxr 0xfffffffff714f8d4 ; kb

FAILURE_BUCKET_ID:  0x7E_srv!SrvTerminateWorkerThread+57

BUCKET_ID:  0x7E_srv!SrvTerminateWorkerThread+57

Followup: MachineOwner
---------
0
 
LVL 29

Expert Comment

by:Michael Worsham
ID: 22918845
You could possibly have a bad memory stick or one that might be going bad. I recommend downloading the MemTest (www.memtest.org) ISO, burning to CD then running it on the server to rule out that possibility.

0
 
LVL 29

Accepted Solution

by:
Michael Worsham earned 2000 total points
ID: 22918861
Your problem seems to be an error related to -- SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed on the Microsoft Windows Hardware Compatibility List (HCL).

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

---

Another possible hotfix that might work...

"STOP 0xA in srv.sys" error message during Windows Server 2003 startup
http://support.microsoft.com/kb/841475
0
 

Author Closing Comment

by:netsmart1
ID: 31514165
Thank you that did the trick
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
Ready to get certified? Check out some courses that help you prepare for third-party exams.
This video will show you how to get GIT to work in Eclipse.   It will walk you through how to install the EGit plugin in eclipse and how to checkout an existing repository.
Despite its rising prevalence in the business world, "the cloud" is still misunderstood. Some companies still believe common misconceptions about lack of security in cloud solutions and many misuses of cloud storage options still occur every day. …

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question