HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error ...
Operating System - OpenVMS
1828416
Members
3318
Online
109977
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2007 09:19 PM
06-19-2007 09:19 PM
Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr
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
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
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2007 09:36 PM
06-19-2007 09:36 PM
Re: Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr
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.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2007 08:00 AM
06-20-2007 08:00 AM
Re: Fatal BUG Check v=v5.5-2h4 MSCPSERV, Fatal error - MSCPr
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP