Discussion Locked

NT 4.0 Workstation Blue Screen

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a NT 4.0 Workstation that keeps blue screening on me. The STOP message that I am getting is:
STOP: 0x000000IE (0xC000005, 0xFC453977, 0x00000000, 0x03663000)
KMODE_EXCEPTION_NOT_HANDLED xxx ADRRESS FC4539477 has base at Fc453000 - atirage.dll

CPUID: GENuinINTEL 6.5.2 irqli if sysver 0xF0000565

I am not sure if it has something to do with my video driver. I do have a ATI card in the system. Do I need a different driver? Any help will be appreciated.

3 replies

by afonger

What I would try is to start the PC using The Last Known Good configuration or VGA mode, get an upgraded video driver, and install it. If that doesn't work try and apply the lastest Service Pack (6a). If it's a PCI card move it to another slot. There's a remote chance that it could be an application that's giving you the BSOD.

Good Luck!

by bwgerho

I have worked with a similar problem and my system operates better, but I cannot pinpoint a particular cure. Check your driver version in your machine (control panel, display, settings, display type). Next, go to www.atitech.ca (the Canada site) and look for a later driver. They are good about updating and recommending what to use.

Finally, try different display properties - I have best luck with 1024 x 768 at 100 Hz. When I was set at 75 Hz, I had more blue screens - go figgure.

regards Bruce

by joseph.leon

Have received blue screen on a IBM T20 and Dell CSx Latitude. Happend when client's are getting out of PAL which is software to allow them to get to the server. Blue screen appears when disconnecting from PAL and locks system up. Do not remember the address but the name of the file which cause the error. It was MRXWDNP.SYS which after looking at the properties of this file denoted this was Walldata (allows access to a AS400) problem. Renamed the extension and it hasn't happened again, Yet. This is a temporary fix until it happens again. If it does, also delete it from REGEDIT.

This discussion is closed to new replies.