Windows Server 2003 Stop Error Crash

Status
Not open for further replies.

jesse.johnson

Posts: 12   +0
I have 2 Windows servers that have been giving me intermittent stop errors. These servers both are running on Windows Server 2003 and have Microsoft SQL Server 2005 installed. They are in a virtual dasd environment. I feel that these errors are similar to that of a previous post:

techspot.com/vb/all/windows/t-37299-Event-ID-1003.html


Here are a couple samples of the errors I've been getting:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/1/2008
Time: 2:59:56 PM
User: N/A
Computer: NTSMGSS15109G
Description:
Error code 00000050, parameter1 bad0b148, parameter2 00000000, parameter3 809338fc, parameter4 00000000.

For more information, see Help and Support Center at
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 35 0000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 62 61 eters ba
0030: 64 30 62 31 34 38 2c 20 d0b148,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 30 39 33 33 38 , 809338
0048: 66 63 2c 20 30 30 30 30 fc, 0000
0050: 30 30 30 30 0000


Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 4/15/2008
Time: 12:53:29 PM
User: N/A
Computer: NTSMGSS15109G
Description:
Error code 00000050, parameter1 bad0b148, parameter2 00000000, parameter3 809338fc, parameter4 00000000.

For more information, see Help and Support Center at
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 35 0000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 62 61 eters ba
0030: 64 30 62 31 34 38 2c 20 d0b148,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 38 30 39 33 33 38 , 809338
0048: 66 63 2c 20 30 30 30 30 fc, 0000
0050: 30 30 30 30 0000


Please advise any suggestions to what might the culprit.

Thanks-
 
0x50 errors: PAGE_FAULT_IN_NONPAGED_AREA, can be due to a myriad of things such as defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).

Read the sticky here in this particular forum entitled "Before posting your minidumps..." by Julio and follow that advice. It is good.

Personally, I would begin by testing you RAM with MemTest for a minimum of 7 passes. If you have any errors then you need to replace your RAM.
 
Three of your errors were 0x50 and it cited a core Windows driver which is too generic for help but is a good indication of a RAM issue.

The other error was 0x7F: UNEXPECTED_KERNEL_MODE_TRAP

One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause and, of these, memory hardware failures are the most common.

As I suggested earlier, run MemTest on your RAM. It could be something else, but this is where I would begin.
 
One other thing I forgot to mention. Your 0x7F error did cite the driver savrt.sys which belongs to Symantec Anti-virus software.
 
Status
Not open for further replies.
Back