- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Faulting Application cpqnimgt.exe
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
03-15-2011 08:20 AM
03-15-2011 08:20 AM
Faulting Application cpqnimgt.exe
The server is a ML370 G4 running WK23 R2
Hi have made sure the Insight Agents are up to date.
The error below is logged.
Source: Application Error Event ID: 1004
Description:
Reporting queued error: faulting application cpqnimgt.exe, version 8.60.0.0, faulting module unknown, version 0.0.0.0, fault address 0x0073e336.
I also ran the windbg on the dump file that was created, the output is below. Can anyone make any sense of it?
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
***** OS symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kernel32.dll -
*** ERROR: Module load completed but symbols could not be loaded for cpqnimgt.exe
*** ERROR: Module load completed but symbols could not be loaded for xpsp2res.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for w2kmgdll.dll -
*** ERROR: Module load completed but symbols could not be loaded for MFC90ENU.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for uxtheme.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ws2help.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ws2_32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for netapi32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for snmpapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for wsnmp32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for mgmtapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msasn1.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for crypt32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msimg32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for imm32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for atl.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for psapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for credui.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for wintrust.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for imagehlp.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for mprapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for iphlpapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for adsldpc.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for activeds.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for rtutils.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for wldap32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for secur32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for comres.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for setupapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for user32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for comctl32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for comctl32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ole32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for clbcatq.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for version.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msvcrt.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for gdi32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for rpcrt4.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for oleaut32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msvcp90.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msvcr90.dll -
*** ERROR: Module load completed but symbols could not be loaded for mfc90u.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for shell32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for shlwapi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for advapi32.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for samlib.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: IMAGE_NT_HEADERS32 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
FAULTING_IP:
+e8
0073e336 ?? ???
EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0073e336
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 0073e336
Attempt to read from address 0073e336
PROCESS_NAME: cpqnimgt.exe
FAULTING_MODULE: 7c800000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 4c51e135
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 0073e336
READ_ADDRESS: 0073e336
FOLLOWUP_IP:
+e8
0073e336 ?? ???
FAILED_INSTRUCTION_ADDRESS:
+e8
0073e336 ?? ???
IP_ON_HEAP: 0073e336
STACK_ADDR_RAW_STACK_SYMBOL: 13affe8
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[ffffffff]
LAST_CONTROL_TRANSFER: from 013affec to 0073e336
FAULTING_THREAD: ffffffff
BUGCHECK_STR: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_WRONG_SYMBOLS_STACKIMMUNE
PRIMARY_PROBLEM_CLASS: BAD_INSTRUCTION_PTR_STACKIMMUNE
DEFAULT_BUCKET_ID: BAD_INSTRUCTION_PTR_STACKIMMUNE
IP_ON_STACK:
+189952f00e1df78
013affec 0000 add byte ptr [eax],al
FRAME_ONE_INVALID: 1
STACK_TEXT:
00000000 cpqnimgt+0x0
SYMBOL_NAME: cpqnimgt
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cpqnimgt
IMAGE_NAME: cpqnimgt.exe
STACK_COMMAND: ** Pseudo Context ** ; kb
FAILURE_BUCKET_ID: BAD_INSTRUCTION_PTR_STACKIMMUNE_c0000005_cpqnimgt.exe!Unknown
BUCKET_ID: APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ_WRONG_SYMBOLS_STACKIMMUNE_BAD_IP_cpqnimgt
WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne/cpqnimgt_exe/8_60_0_0/4c51e135/unknown/0_0_0_0/bbbbbbb4/c0000005/0073e336.htm?Retriage=1
Followup: MachineOwner
---------
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-05-2011 11:37 AM
04-05-2011 11:37 AM
Re: Faulting Application cpqnimgt.exe
I've recently updated all HP drivers/software to the latest available versions.
Now we have the same problem here.
Fehlgeschlagene Anwendung cpqnimgt.exe, Version 8.60.0.0, fehlgeschlagenes Modul unknown, Version 0.0.0.0, Fehleradresse 0x0077e3d0.
Crashing 1-2 times per day.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2011 09:00 AM
04-07-2011 09:00 AM
Re: Faulting Application cpqnimgt.exe
Faulting application name: cpqnimgt.exe, version: 8.70.0.0, time stamp: 0x4d375c9b Faulting module name: bmapia.dll_unloaded, version: 0.0.0.0, time stamp: 0x4c8047e4 Exception code: 0xc000041d Fault offset: 0x0000000010040450 Faulting process id: 0x1b18 Faulting application start time: 0x01cbf4ace340f0b8 Faulting application path: C:\Windows\system32\CPQNiMgt\cpqnimgt.exe
Faulting module path: bmapia.dll
Report Id: 0af72c82-6136-11e0-b770-001e0b924b90
The HP Insight NIC Agents service terminated unexpectedly. It has done this 5 time(s).
Has anyone opened a case with HP yet?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2011 09:04 AM
04-07-2011 09:04 AM
Re: Faulting Application cpqnimgt.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-07-2011 11:32 AM
04-07-2011 11:32 AM
Re: Faulting Application cpqnimgt.exe
HP ProLiant BL460c G1 Blade Server
with 2x E5345 2.33GHz Quad-Core Procs
and 16GB of RAM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
04-09-2011 08:23 AM
04-09-2011 08:23 AM
Re: Faulting Application cpqnimgt.exe
The clean install windows 2003 occur the following fault
Faulting Application cpqnimgt.exe
Event ID:1000 Faulting application cpqnimgt.exe, version 8.60.0.0, faulting module unknow, version 0.0.0.0, fault address 0x00d9e36b.
any suggest?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-20-2011 02:35 PM
07-20-2011 02:35 PM
Re: Faulting Application cpqnimgt.exe
Hi Guys,
Has anyone been able to work around this problem?
The things that I can suggest are, uninstalling the agents, making sure that this folders is gone :
C:\PROGRAM FILES\HPWBEM\NETWORK\DLL\BMAPI.DLL
Since my errro points to cpqnimgt.exe using the BMAPI.dll (Broadcom Management Application Programming Interface). Then reinstall the agents.
This because the error seems to be APPLICATION_FAULT_BAD_INSTRUCTION_PTR_INVALID_POINTER_READ
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
09-02-2011 12:05 AM
09-02-2011 12:05 AM
Re: Faulting Application cpqnimgt.exe
Hello All,
I have a same issue.
Server is DL380 G7 and OS is Win2003 R3 Enterprise SP2.
PSP version is 8.70.0.0.
I got the below message
"Evant ID : 1000 , Faulting application name: cpqnimgt.exe, version 8.70.0.0.,
faulting module unknown, version 0.0.0.0 fault address 0x007f42f0."
2 servers are configured by cluster and 2 servers has same error message.
I know that PSP 8.70.0.0 is the latest version.
How can I solve this issue?
Best reagrds
Chul-Ho/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-15-2011 11:36 PM
11-15-2011 11:36 PM
Re: Faulting Application cpqnimgt.exe
Multiple DL380 G5's with various specs but all just taken to PSP 8.70
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-18-2012 06:56 AM
01-18-2012 06:56 AM
Re: Faulting Application cpqnimgt.exe
Does anyone solve this problem yet?
I have the same issues on 3 servers recently upgraded with PSP 8.70.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP