Re: Newly setup W2K3 rebooting and error event ID 1003
From: ITJRW (justice_at_community.nospam)
Date: 01/29/05
- Next message: Roger Abell: "Re: Windows 2003 DNS Setup for Sub-Domain off of Root"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: \\domainname.com\SYSVOL\ is not browseable"
- In reply to: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Next in thread: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Reply: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 29 Jan 2005 16:35:37 -0600
Thanks for the suggestion and the reference. I missed that one because I
didn't search on the hex value of the error code, I guess. So I may have
learned two things.
I'll have to travel an hour each way to test this next week. Is there a
routine to examine the interrupt values of all devices so I could narrow
this down without having to look at each hardware device?
Thanks again. I should be able to find the problem with this information.
By the way what is a BSOD?
Justice
"lazyadmin" <admin@lazyadmin.com.nospam> wrote in message
news:uBUUreiBFHA.4008@tk2msftngp13.phx.gbl...
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w2kmsgs/1147.asp
>
> Have you seen it do this? I think it is a hardware related BSOD, and you
> have the system set to reboot upon BSOD. I would disable the automatic
> restart on BSOD and see if it gives you anymore information.
>
> My Computer properties | Advanced | Startup and Recovery Settings under
> system failure uncheck "Automatically restart" When the system crashes
> next time you will have to restart it manually, but the BSOD may give you
> more information like KERNEL_APC_PENDING_DURING_EXIT
>
>
>
> --
> Rod
> http://www.thelazyadmin.com
>
>
> "ITJRW" <justice@community.nospam> wrote in message
> news:%23T94dqbBFHA.3976@tk2msftngp13.phx.gbl...
>>I have recently set up AD, DNS, and SUS server and installed Symantec AV
>> Corporarte 9.0 on a new server which has W2K3 installed.
>>
>> The server is rebooting from 1 to three times a day and disconnecting
>> users
>> at that time (of course). I get Error message upon the restart that
>> appears when logging back in which contains this information:
>>
>> Event type: Error
>> Event Source: System Error
>> Event Catagory: (102)
>> Event ID: 1003
>> Then the date, time, Computer (server) name, and a Description:
>>
>> Error code 00000020,
>> parameter1 00000000,
>> parameter2 0000ffb,
>> parameter3 00000000,
>> parameter4 00000001.
>>
>> All hardware and the OS came installed (from Dell) and I added the Anti
>> Virus software and set up SUS server to synchronize with Microsoft. I
>> indicates synchronization.
>>
>> I created a new domain on the same subnet as the old domain (NT 4.0)
>> based
>> and made it a mixed domain until I joined all XP Professional clients and
>> disconnected the NT 4.0 machine. I had installed Terminal Services on
>> the
>> Server so that I could contact it from another workstation to make
>> necessary
>> changes. I have stopped that service to try to eliminate the reboot
>> problem
>> and nothing changed.
>>
>> I have searched the knowledge base on MSDN and found nothing to help. I
>> need help understanding what is happening. Thanks.
>>
>> Justice
>>
>
>
- Next message: Roger Abell: "Re: Windows 2003 DNS Setup for Sub-Domain off of Root"
- Previous message: Kevin D. Goodknecht Sr. [MVP]: "Re: \\domainname.com\SYSVOL\ is not browseable"
- In reply to: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Next in thread: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Reply: lazyadmin: "Re: Newly setup W2K3 rebooting and error event ID 1003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
