Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESXi host PSOD : PF exception 14 at address 0x0 running on Nvidia M10 GPU with older 390.* vib (78081)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 8660Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

The VMs which has dedicated vGPU fails with crash dump.

The end users notice they got disconnected while using the VM.

ESXi Host may PSOD  when deploying vSGA enabled linked clones desktop pool in Horizon View

The backtrace will be similar to below
2019-10-07T18:05:12.458Z cpu1:2101958)@BlueScreen: #PF Exception 14 in world 2101958:hostd-IO IP 0x4180284fa6de addr 0x45026c716000
PTEs:0x9040057023;0x8031176063;0x8048a0f063;0x0;
2019-10-07T18:05:12.458Z cpu1:2101958)Code start: 0x418027800000 VMK uptime: 60:16:15:47.722
2019-10-07T18:05:12.459Z cpu1:2101958)0x451b3431b9e0:[0x4180284fa6de]_nv010143rm@(nvidia)#<None>+0xb2 stack: 0x451b3431ba60
2019-10-07T18:05:12.459Z cpu1:2101958)0x451b3431ba30:[0x4180285abca6]_nv012468rm@(nvidia)#<None>+0xcf stack: 0x451b3431bc20
2019-10-07T18:05:12.459Z cpu1:2101958)0x451b3431ba70:[0x4180286b97d7]_nv017782rm@(nvidia)#<None>+0x4d0 stack: 0x451b3431ba98
2019-10-07T18:05:12.459Z cpu1:2101958)0x451b3431bae0:[0x418028944be4]_nv021250rm@(nvidia)#<None>+0x365 stack: 0x451b3431bb3c
2019-10-07T18:05:12.460Z cpu1:2101958)0x451b3431bd20:[0x41802894505d]_nv021218rm@(nvidia)#<None>+0x8a stack: 0x0
2019-10-07T18:05:12.460Z cpu1:2101958)0x451b3431bd60:[0x41802894ba86]rm_isr@(nvidia)#<None>+0x4b stack: 0x451b3431bdb0
2019-10-07T18:05:12.460Z cpu1:2101958)0x451b3431bd80:[0x4180289af0c0]nv_interrupt_handler@(nvidia)#<None>+0xdd stack: 0x8a
2019-10-07T18:05:12.460Z cpu1:2101958)0x451b3431bdc0:[0x4180278ef47b]IntrCookieBH@vmkernel#nover+0x1e0 stack: 0x0
2019-10-07T18:05:12.461Z cpu1:2101958)0x451b3431be60:[0x4180278cd4ef]BH_DrainAndDisableInterrupts@vmkernel#nover+0x100 stack: 0x451b3431bf30
2019-10-07T18:05:12.461Z cpu1:2101958)0x451b3431bef0:[0x4180278f0e7a]IntrCookie_VmkernelInterrupt@vmkernel#nover+0xb3 stack: 0x44
2019-10-07T18:05:12.461Z cpu1:2101958)0x451b3431bf10:[0x41802794731c]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0
2019-10-07T18:05:12.461Z cpu1:2101958)0x451b3431bf30:[0x418027963066]gate_entry@vmkernel#nover+0x67 stack: 0x0

Logging leading up to crash in the vmkernel.log will be similar to below

2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000e0 count was zero (count=0)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000e1 count was zero (count=1)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000e2 count was zero (count=2)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000e3 count was zero (count=3)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000e9 count was zero (count=9)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000f3 count was zero (count=19)
2019-10-07T18:05:11.980Z cpu73:2097567)WARNING: VmMemPin: 333: vm 3591873: bpn 0x1000000fd count was zero (count=29)
2019-10-07T18:05:12.084Z cpu73:2097567)WARNING: PFrame: vm 3591873: 2489: Deallocating pinned bpn 0x1001dafab, pinCount 1 throttle 0.

Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment.
Disclaimer:VMware is not responsiblee for the reliability of any data,opinions,advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses,recommends or accepts any

Purpose

To resolve the PSOD.

Cause

This is caused due to a heap corruption in driver.

Impact / Risks

None

Resolution

This is a known issue with Nvidia driver  and fixed in version 390.93 vib.

To check the current version installed run command esxcli software vib list

For more information refer to :Nvidia Grid release notes

Nvidia reports this issue is fixed in vib 390.93 or later.
Nvidia recommends to update to Grid 8.3, or 10.0 to resolve this issue.

Workaround

None

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
NSX-T Edge の不完全な削除 (77305)

KB
•
NVMe Inbox ドライバによって報告された NVME_STATUS_UNDERRUN によって発生した VMK_SCSI_HOST_ERROR が原因の「ストレージ イニシエータ エラー」により vSAN ディスクグループがオフラインになる (78258)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant