Windows Forum

Ask something
Discussion Locked

Blue Screen of Death

0 helpful
12 replies

by lcave

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

Event Type: Error
Event Source: cpqasm
Event Category: None
Event ID: 4188
Date: 3/30/2001
Time: 6:09:34 PM
User: N/A
Computer: MOTT-TS3
Description:
The Compaq System Management Driver has detected that the system encountered an NT bugcheck prior to this boot. The bugcheck data was: STOP: 0x0000001E (0xC0000005, 0xA00FDAD6, 0x00000000, 0x0000000C).
Data:
0000: 00 00 00 00 09 00 4e 00 ......N.
0008: 00 00 00 00 5c 10 35 c4 ....\.5?
0010: 00 00 00 00 00 00 00 00 ........0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........

This is the error which stops two of our terminal servers. We have replaced misaligned cpus, changed the motherboard, updated firmware to no avail. What's next?

12 replies

by russ werner

Go to Microsoft.com, Support, and search for STOP: 0x0000001E under Window 2000. There are 21 articles listed that will give you some direction. Too many to list here, and too many questions as to what you are running.
But hope it helps.

by vagab0nd

Not too many details on config of your servers but you may try the following articles form Microsoft KnowledgeBase:
Q261322 and Q273632

by pbgerrard

O.K. you can replace hardware all you want, and it will probably not slve the problem. We all know how bug-laden windows is, and especially Windows 2000. The blue screen and the stop message is a bug check code, that can help you fix the problem.This is usually a problem with a driver or operation windows tried to use. On an AMD machine, this is caused by a parity error, but as AMD makes no server chips, I assume you are not using an AMD machine, if you are, that might be your problem. However, I would suggest you look throught the all hardware drivers, and check the IRQ's to make sure everything is configured properly. If everything is, then most likely you are using a thid-party driver that Windows not handle well.

The other problem may be that there is a memory or disk space error, but since you replaced the hard drive and motherboard, I am assuming you thought of this problem and tried to fix it.

The last possibility is that when a program runs, it opens a registry key but does not close it when it is finished. If this is the case, it will be neccessary to modify the program to do that.

I hope this helps, if it does not, you may want to contact Microsoft Tech support. I am not sure if Windows 2000 automatically saves the blue screen in a dump file, but if it does not, you can probably find out how to with little trouble. Call tech support, and they will probably be able to debug the dump file.

by pbgerrard

Oh yeah, and I forgot to mantion that to find out if it is a registry problem, you can download for free software that monitors the registry. It will tell everytime a registry key is opened or closed. If you have a virus scan, beware, the screen will quickly fill up.

by dcyr

The stop code that you see is for a KMODE_EXCEPTION _NOT_HANDLED error. Usually at the end of the stop code, there is a listing for the bad driver. Unfortunately, the Compaq ASM doesn't usually catch this. I would suggest that you apply the latest Compaq SSD (2.20 I think). THis contains all of the newest system Management drivers for Compaq hardware. Otherwise you are going to have to actually see the server bluescreen in order to find out what the offending driver is. Hope this helps.

by lanwanman352

You wrote: "We have replaced misaligned cpus, changed the motherboard, updated firmware to no avail. What's next?" Initially, I would have suspected that the CPQASM.SYS driver was not loading, corrupt, or actually the wrong driver for the originalhardware. Introducing replacement hardware may have complicated the problem.

When selecting motherboards and firmware we must take into account that only one of the three Compaq drivers listed below is typically installed on a server. The type of management controller used in the server determines which driver is applied. Here's where changing the motherboard and firmaware may have complicated the problem if the driver was not properly updated.

Assuming the replacement hardware is indeed Compaq compatible, the Compaq Drivers invloved are:

Compaq Integrated System Management Controller driver, CPQCSM.SYS
Compaq System Management Controller driver, CPQSS.SYS
Compaq Advanced System Management Controller driver, CPQASM.SYS
These drivers may fail to load in the following cases:

The system firmware does not support Microsoft Windows 2000.
The server boot drive was built on another system and was then installed in the server.
The servers boot drive was restored from a backup copy, such as a tape backup.

When the driver fails to load, even Compaq Insight Manager will not be able to display or set any data related to this problem. To work around this issue, consider upgrading to the latest system ROM (tosupport Microsoft Windows 2000) and reinstall the system management component. This is required in order for the drivers to load properly and re-enable system management support.

Go to the following URL to find the latest firmware updates:
http://www.compaq.com/support/files/server/us/index.html

This discussion is closed to new replies.