VMware Cloud Community
SeanathanHadley
Contributor
Contributor

6.7.0 build-13006603 - PSOD - PF Exception 14 in world 2097785:Tcpip4 wtask

Greetings,

I hit a PSOD on my homelab (non enterprise/home desktop components), and was hoping someone could clarify if this is hardware/software related. I didn't have much success finding information related to "Tcpip4 wtask", so any additional information would be great.

2019-11-02T07:53:00.402Z cpu0:2097785)World: 3015: PRDA 0x418040000000 ss 0x0 ds 0xfd0 es 0xfd0 fs 0xfd0 gs 0xfd0

2019-11-02T07:53:00.402Z cpu0:2097785)World: 3017: TR 0xfd8 GDT 0x450984200000 (0xfe7) IDT 0x41803b564000 (0xfff)

2019-11-02T07:53:00.402Z cpu0:2097785)World: 3018: CR0 0x8001003d CR3 0x79e93000 CR4 0x10016c

2019-11-02T07:53:00.408Z cpu0:2097785)Backtrace for current CPU #0, worldID=2097785, fp=0x206

2019-11-02T07:53:00.408Z cpu0:2097785)0x451a0e41bbb8:[0x41803b707d2f]CpuSchedIdleLoopInt@vmkernel#nover+0x20b stack: 0x4180400007c0, 0x0, 0x7fffffff00000000, 0x1, 0x418040000000

2019-11-02T07:53:00.410Z cpu0:2097785) [45m [33;1mVMware ESXi 6.7.0 [Releasebuild-13006603 x86_64] [0m

#PF Exception 14 in world 2097785:Tcpip4 wtask IP 0x41803b707d2f addr 0x81

PTEs:0x0;

2019-11-02T07:53:00.411Z cpu0:2097785)cr0=0x8001003d cr2=0x81 cr3=0x79e93000 cr4=0x10016c

2019-11-02T07:53:00.411Z cpu0:2097785)frame=0x451a0e41baf0 ip=0x41803b707d2f err=0 rflags=0x10206

2019-11-02T07:53:00.411Z cpu0:2097785)rax=0x0 rbx=0x1 rcx=0x0

2019-11-02T07:53:00.411Z cpu0:2097785)rdx=0x4180400007c0 rbp=0x206 rsi=0x1

2019-11-02T07:53:00.411Z cpu0:2097785)rdi=0x206 r8=0x430076a7f230 r9=0x450185246000

2019-11-02T07:53:00.412Z cpu0:2097785)r10=0x0 r11=0x1 r12=0x1

2019-11-02T07:53:00.412Z cpu0:2097785)r13=0x1 r14=0x418040000000 r15=0x1f34ee7a8882ba

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:0 world:2097785 name:"Tcpip4 wtask" (S)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:1 world:2099562 name:"vmx" (U)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:2 world:2098399 name:"ntpd" (U)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:3 world:2100018 name:"vmm0:servie2019" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:4 world:2099869 name:"vmm5:server2" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:5 world:2100169 name:"vmm2:server1" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:6 world:2099867 name:"vmm3:server2" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:7 world:2097180 name:"netCoalesce2World" (S)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:8 world:2097316 name:"CpuSchedAgingVtimes" (S)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:9 world:2100165 name:"vmm0:server1" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:10 world:2100171 name:"vmm4:server1" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:11 world:2097163 name:"idle11" (IS)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:12 world:2099865 name:"vmm1:server2" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:13 world:2100172 name:"vmm5:server1" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:14 world:2099862 name:"vmm0:server2" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)pcpu:15 world:2100170 name:"vmm3:server1" (V)

2019-11-02T07:53:00.412Z cpu0:2097785)@BlueScreen: #PF Exception 14 in world 2097785:Tcpip4 wtask IP 0x41803b707d2f addr 0x81

PTEs:0x0;

No new BIOS available for my motherboard, and I do plan to upgrade to 6.7 U3 soon.

Reply
0 Kudos
1 Reply
KocPawel
Hot Shot
Hot Shot

Usually PSOD is caused by firmware issue.

Check your hardware and firmware with actual compatibility matrix.

Reply
0 Kudos