Win2003 Server random restarts Event ID:1003

Status
Not open for further replies.
Hello,
My server Win2003 OS randomly restarts (1-2 times a day)
I get following error message in Event Viewer:

Source: System Error
Category: (102)
Event ID: 1003

Error code 00000050, parameter1 a2f517fc, parameter2 00000001, parameter3 f61b4fe9, parameter4 00000000.

Can't find any issues with configuration, and I suspect that the reason is a hardware (possibly RAM)

Since I do not know how to read the minidumps - maybe some kind soul will help me figure out the culprit.

Pyotrek
 

Attachments

cpc2004

Posts: 1,994   +0
Hi,

One of the minidumps has code memory which is the symptom of faulty memory. It coulbd be caused by faulty ram or PSU.

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f3665a48 80828c95 86145378 00ebea48 85ebea48 0x85a01848
f3665a5c 80907bfa f3665c04 86145360 00000000 nt!IofCallDriver+0x45
f3665b44 80902fad 86145378 00000000 85e4ce08 nt!IopParseDevice+0xa35
f3665bc4 80906a15 00000000 f3665c04 00000040 nt!ObpLookupObjectName+0x5a9
f3665c18 8090613b 00000000 00000000 00000801 nt!ObOpenObjectByName+0xea
f3665c94 8092b2c2 00bfdbb4 c0100080 00bfdb50 nt!IopCreateFile+0x447
f3665cf0 8092ca4c 00bfdbb4 c0100080 00bfdb50 nt!IoCreateFile+0xa3
f3665d30 8082337b 00bfdbb4 c0100080 00bfdb50 nt!NtCreateFile+0x30
f3665d30 7c82ed54 00bfdbb4 c0100080 00bfdb50 nt!KiFastCallEntry+0xf8
00bfdb0c 00000000 00000000 00000000 00000000 0x7c82ed54

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
!chkimg -lo 50 -d !nt
80828c9d-80828ca0 4 bytes - nt!IofCompleteRequest

[ ff 25 e4 e7:01 00 00 00 ]
4 errors : !nt (80828c9d-80828ca0)

MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .trap fffffffff366599c ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
Followup: memory_corruption

The culprit is faulty memory. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot. Reseat video card as well.
3. Downclock the ram. Check to default setting if you video card is overclocked.
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
For example : DIMM1 and DIMM2 do not have the same timing.
DIMM1: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (2.5-3-3-8 @ 200 MHz) (2.0-3-3-7 @ 166 MHz)
DIMM2: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
DIMM3: Corsair CMX512-3200C2 512 MB PC3200 DDR SDRAM (3.0-3-3-8 @ 200 MHz)
7. Make sure that your PSU have adequate power to drive all the hardware including USB devices
8. Run chkdsk /r at command prompt

If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
 
  • Thread Starter Thread Starter
  • #3
Thanks for quick reply,
I will remove one of the DIMM's and see what will happen.

I have yet another server that reboots now every 5-6 hours and I get EventID: 1003 as well.

Checked for viruses etc. with no results. This server was in service for quite some time, and had no problems until recently. Is it memmory again?

Attached are minidumps from this one - by the way - how do you view minidumps?
 

cpc2004

Posts: 1,994   +0
Hi,

The priblem may be related to software error at b57xp32.sys (ethernet card driver) or faulty hardware. Upgrade b57xp32.sys. Repost if your windows still crashes.

Mini120105-01.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : b57xp32.sys ( b57xp32+35e5 )

Mini120105-02.dmp BugCheck 24, {19033c, f5b52db8, f5b52ab4, f7384f20}
Probably caused by : atapi.sys ( atapi!IdeReadWriteExt+204 )

Mini120105-03.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : b57xp32.sys ( b57xp32+34cf )

Mini120105-04.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : b57xp32.sys ( b57xp32+35e5 )

Mini120105-05.dmp BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : b57xp32.sys ( b57xp32+35e5 )

Mini120105-06.dmp BugCheck 50, {9804008f, 1, bf87f28d, 0}
Probably caused by : win32k.sys ( win32k!HANDLELOCK::bLockHobj+a )
 
Status
Not open for further replies.