Stop Error 1E 1

[deathstar]

I have a Windows 2000 server with Terminal services installed, it has been running well for about a years time before a many more employees has been hired into the company. My terminal server keeps freezing up on me making me reboot the server to flush out any inconsistancies, or it sometimes too jsut crashes on me giving me the Blue Screen of Death with a Stop Error 1E

The exact error I keep getting is

*** STOP: 0x0000001E (0xC0000005, 0X80423438, 0x00000001, 0x00000000)

KMODE_EXCEPTION_NOT_HANDLED

*** Address 80423438 base at 80400000, datestamp 3ad77869 - ntoskrnl.exe

1) I know that the Stop 1E error means that there maybe a driver issue, but I checked my device driver on my device manager and I see no device drivers issues. I have even went to the Microsoft Update site to quey the site to see if any new device drivers are available for my server and all I see are printer drivers that needs updating.

2) I also know that 0xC0000005 means that there was a Access Violation that has caused this Blue Screen of Death

3) I can not seem to find the address 80423438 for the driver that maybe causing this stop error

Can anyone help in this matter, I am hitting a brick wall every road I take. If anyone else has also encountered this problem I would appreciate any input.

Thanking You in advance

 

[markharr]

To get to the bottom of this problem will require, at a minimum, a look at the stack back trace to see if it can be identified where the bad pointer came from.

If this doesn't provide enough information, you will need to get a full memory.dmp and pass that to Microsoft support if you don't have the skills yourself to analyse it. Most people don't so there is no need to feel inadequate which you shouldn't do. You've already done more than most people.

If you can get the stack back trace and post it here, we can at least have a look at that.

 

[Guest_imported]

I think I may have found the source of the problem, I called up our hardware manufacturer, and after several hours of troubleshooting it has been determined that the culprit is a malfunctioned motherboard.

Many thanks Markharr, your reply was much appreciated.