topic Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr in Operating System - OpenVMS

Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr

Bo Alexander — Wed, 20 Jun 2007 04:19:56 GMT

I am getting this on a "brick" VAX 4000 model 50. The machine go into a continual reboot. The next message I get is Fatal BUG Check version = V5.5-2h4 INVEXCEPTN, Exception while above ASTDEL or on interrupt stack.

No changes have been made to the software in years. I suspect a memory or some other type of hardware problem.

Any help will be appreciated.

Thank you

Re: Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr

Volker Halle — Wed, 20 Jun 2007 04:36:07 GMT

Hi,

welcome to the OpenVMS ITRC forum.

If you can get some more information about the crash footprint, we may be able to find out what's wrong.

Does the MSCPSERV crash happen after you power-on and boot the machine ? Then it reboots after writing the crash and gets an INVEXCEPTN crash and so on.

Can you do a conversational boot (>> B/n0000001) and set STARTUP_P1 "MIN" ? Does the system boot, can you look at the crash and the errorlog ?

If the system even can't boot with minimum startup, you can set DUMPFLAGS bit 1 (full console output) and capture the console output. Then post the output as an attached .TXT file to your next reply.

Volker.

Re: Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr

Dean McGorrill — Wed, 20 Jun 2007 15:00:23 GMT

hi,
you could also set MSCP_LOAD = 0 and
skip loading it. check the errorlog, I think
mscp tu/dudriver posts to it. then again if
its hardware, disabling mscp might just move
the crash somewhere else at bootup. see what can see from the console, mem devices etc.