Windows 2003 System Error

bright_genius · 05-13-2008, 12:52 AM

Hi, every week our Server will restart with a stop error. I always encountered these error from the event log i.e.

System Error - Error code 000000fe, parameter1 00000004, parameter2, 88f3ee70, parameter3 894516c8 parameter4

The reason supplied by user Server\Administrator for the last unexpected shutdown of this computer is System failure. stop error. Reason code 0x805000f. Bug ID: Bugcheck String: 0x000000fe ( 0x00000004, 0x88f3ee70, 0x894516c8, 0x00000000)

with a ER_KRNLCRASH_LOG..

I have already done full memory test and test drive it still appears every now and then.

Hope somebody can help me here. Thanks!

MAQ_FR · 05-13-2008, 07:28 AM

Had a similar issue last year, and we finally pin-pointed it to a fault expansion card as well as an "unsigned USB driver".

We updated the driver and changed the card (it was a raid controller) but never did find out the true cause so whether they were linked to cause the failure with us or just coincidence - your guess is as good as mine.

Hope there is a pointer there for you.

bright_genius · 05-14-2008, 02:21 AM

It restarted again today with a different log on the event viewer - application log.

ID : 4124

Component : Application Event Log

Stated : Content index on %1 is corrupt. Please shutdown and restart the indexing service

Message: Database corruption or network issues (restart needed)

Explanation: Index information is corrupt and Indexing Service cannot re-index the content automatically.

Hope somebody finds a solution for this..

Thanks!

MAQ_FR · 05-14-2008, 04:20 AM

HI Bright_genius

I was digging around in our K/base but found nothing except referrals to M/Soft:

In the Application log of the Event Viewer, events 4124 and/or 4126 may occur. The errors in the Event Viewer report that the catalog is corrupt. In the MMC snap-in for Index Server, the statistics for a certain catalog may contain a value of n/a instead of numbers.

http://support.microsoft.com/kb/209304/en-us

Also I found this:

Error 4124 - WINS_EVT_UPD_NTF_NOT_ACCEPTED
The WINS server received an update notification from the non-configured WINS server at the address, %1. The WINS server rejected it. This means the remote WINS server is not in the list of Push partners (WINS servers under the Pull key) and the administrator has prohibited (using the registry) replication with non-configured WINS servers. If you want this WINS server to accept update notifications from non-configured WINS servers then set the Wins\Paramaters\RplOnlyWCnfPnrs value in the registry to 0.

For me it seems your problem is Index Server and if you look in the k/base article there, they offer "some" advice to resolve it.

05-13-2008, 12:52 AM	#1 (permalink)
bright_genius Registered User Join Date: May 2008 Posts: 2 OS: windows xp, windows 2003	Windows 2003 System Error Hi, every week our Server will restart with a stop error. I always encountered these error from the event log i.e. System Error - Error code 000000fe, parameter1 00000004, parameter2, 88f3ee70, parameter3 894516c8 parameter4 The reason supplied by user Server\Administrator for the last unexpected shutdown of this computer is System failure. stop error. Reason code 0x805000f. Bug ID: Bugcheck String: 0x000000fe ( 0x00000004, 0x88f3ee70, 0x894516c8, 0x00000000) with a ER_KRNLCRASH_LOG.. I have already done full memory test and test drive it still appears every now and then. Hope somebody can help me here. Thanks!

05-13-2008, 07:28 AM	#2 (permalink)
MAQ_FR Registered User Join Date: Mar 2005 Location: Switzerland (origin: Scotland) Posts: 131 OS: WinXP pro: 2003 Server: 2008 Server: RHES 4	Re: Windows 2003 System Error Had a similar issue last year, and we finally pin-pointed it to a fault expansion card as well as an "unsigned USB driver". We updated the driver and changed the card (it was a raid controller) but never did find out the true cause so whether they were linked to cause the failure with us or just coincidence - your guess is as good as mine. Hope there is a pointer there for you. __________________ regardz à tous Maq

05-14-2008, 02:21 AM	#3 (permalink)
bright_genius Registered User Join Date: May 2008 Posts: 2 OS: windows xp, windows 2003	Re: Windows 2003 System Error It restarted again today with a different log on the event viewer - application log. ID : 4124 Component : Application Event Log Stated : Content index on %1 is corrupt. Please shutdown and restart the indexing service Message: Database corruption or network issues (restart needed) Explanation: Index information is corrupt and Indexing Service cannot re-index the content automatically. Hope somebody finds a solution for this.. Thanks!

05-14-2008, 04:20 AM	#4 (permalink)
MAQ_FR Registered User Join Date: Mar 2005 Location: Switzerland (origin: Scotland) Posts: 131 OS: WinXP pro: 2003 Server: 2008 Server: RHES 4	Re: Windows 2003 System Error HI Bright_genius I was digging around in our K/base but found nothing except referrals to M/Soft: In the Application log of the Event Viewer, events 4124 and/or 4126 may occur. The errors in the Event Viewer report that the catalog is corrupt. In the MMC snap-in for Index Server, the statistics for a certain catalog may contain a value of n/a instead of numbers. http://support.microsoft.com/kb/209304/en-us Also I found this: Error 4124 - WINS_EVT_UPD_NTF_NOT_ACCEPTED The WINS server received an update notification from the non-configured WINS server at the address, %1. The WINS server rejected it. This means the remote WINS server is not in the list of Push partners (WINS servers under the Pull key) and the administrator has prohibited (using the registry) replication with non-configured WINS servers. If you want this WINS server to accept update notifications from non-configured WINS servers then set the Wins\Paramaters\RplOnlyWCnfPnrs value in the registry to 0. For me it seems your problem is Index Server and if you look in the k/base article there, they offer "some" advice to resolve it. __________________ regardz à tous Maq