VMware Cloud Community
oasisinin
Enthusiast
Enthusiast

WinBSOD Code decipher

A VM (File Server) crashed with following in vmware.log; appreciate if someone can help decipher the codes or direct me to right place

VM: Window 2008 R2

vSphere: 6.5 , 7388607

vmware.log contents :

2018-02-20T23:09:58.735Z| vcpu-6| W115: WinBSOD: Synthetic MSR[0x40000100] 0x9e

2018-02-20T23:09:58.735Z| vcpu-6| W115:

2018-02-20T23:09:58.736Z| vcpu-6| W115: WinBSOD: Synthetic MSR[0x40000101] 0xffffad8072929840

2018-02-20T23:09:58.736Z| vcpu-6| W115:

2018-02-20T23:09:58.736Z| vcpu-6| W115: WinBSOD: Synthetic MSR[0x40000102] 0x4b0

2018-02-20T23:09:58.736Z| vcpu-6| W115:

2018-02-20T23:09:58.736Z| vcpu-6| W115: WinBSOD: Synthetic MSR[0x40000103] 0x65

2018-02-20T23:09:58.736Z| vcpu-6| W115:

2018-02-20T23:09:58.736Z| vcpu-6| W115: WinBSOD: Synthetic MSR[0x40000104] 0x0

2018-02-20T23:09:58.736Z| vcpu-6| W115:

2018-02-20T23:09:59.739Z| svga| I125: SVGA-ScreenMgr: Screen type changed to RegisterMode

2018-02-20T23:10:00.796Z| vcpu-6| I125: LSI: Invalid PageType [21] pageNo 0 Action 0

2018-02-20T23:10:06.016Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2018-02-20T23:10:12.366Z| vcpu-0| I125: SCSIFilterESXAttachCBRCInt: CBRC not enabled or opened without filters,skipping CBRC           filter attach.

2018-02-20T23:10:12.366Z| vcpu-0| I125: SCSIFilterSBDAttachCBRC: device scsi0:0 is not SBD. Skipping CBRC attach SBD way.

2018-02-20T23:10:12.387Z| vcpu-0| I125: PCIBridge4: ISA/VGA decoding enabled (ctrl 0004)

2018-02-20T23:10:12.387Z| vcpu-0| I125: pciBridge4:1: ISA/VGA decoding enabled (ctrl 0004)

2018-02-20T23:10:12.632Z| vcpu-0| I125: SVGA: Registering MemSpace at 0xe8000000(0xe8000000) and 0xfe000000(0xfe000000)

2018-02-20T23:10:12.636Z| vcpu-0| I125: SVGA: Unregistering MemSpace at 0xe8000000(0xe8000000) and 0xfe000000(0xfe000000)

2018-02-20T23:10:12.762Z| vcpu-0| I125: SVGA: Registering MemSpace at 0xe8000000(0xe8000000) and 0xfe000000(0xfe000000)

2018-02-20T23:10:12.770Z| vcpu-0| I125: SVGA: Unregistering MemSpace at 0xe8000000(0xe8000000) and 0xfe000000(0xfe000000)

2018-02-20T23:10:12.771Z| vcpu-0| I125: SVGA: Registering IOSpace at 0x1070

2018-02-20T23:10:12.771Z| vcpu-0| I125: SVGA: Registering MemSpace at 0xe8000000(0xe8000000) and 0xfe000000(0xfe000000)

2018-02-20T23:10:12.776Z| vcpu-0| I125: PCIBridge4: ISA/VGA decoding enabled (ctrl 0004)

2018-02-20T23:10:12.777Z| vcpu-0| I125: pciBridge4:1: ISA/VGA decoding enabled (ctrl 0004)

2018-02-20T23:10:37.640Z| vcpu-0| W115: CPU microcode update available.

2018-02-20T23:10:37.640Z| vcpu-0| W115+ The guest OS tried to update the microcode from patch level 1063 (427h) to patch level 1064 (428h), but VMware ESX does not allow microcode patches to be applied from within a virtual machine.

2018-02-20T23:10:37.640Z| vcpu-0| W115+ Microcode patches are used to correct CPU errata. You may be able to obtain a BIOS/firmware update which includes this microcode patch from your system vendor, or your host OS may provide a facility for loading microcode patches.APIC CMCI LVT write: 0x100d8

I can provide full logs if needed

Thank You

Tags (1)
Reply
0 Kudos
3 Replies
msripada
Virtuoso
Virtuoso

Have you performed any recent changes in the environment like windows updates on the guest os?

can you login to safe mode?

can you try chkdsk from safemode to check if it boots?

Thanks,

MS

Reply
0 Kudos
oasisinin
Enthusiast
Enthusiast

we had some new network connection added to guest connecting to equalogic. Guest was using OS iSCSI connection for that though, not Host iSCSI

Although the Guest came back alright after the crash and we removed OS iSCSI connections after that.

Reply
0 Kudos
Sandeshp
Contributor
Contributor

We had also faced almost same issue on our production setup below are the logs

2018-04-04T11:09:21.662Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2018-04-04T11:09:21.662Z| vmx|

I125: GuestRpc: app toolbox-dnd's second ping timeout; assuming app is down

2018-04-04T11:09:21.662Z| vmx| I125: GuestRpc:

Reinitializing Channel 2(toolbox-dnd)

2018-04-04T11:09:21.663Z| vmx|

I125: GuestMsg: Channel 2, Cannot unpost because the previous post is already completed

2018-04-04T11:09:22.238Z| vcpu-0|

W115: GuestRpc: application toolbox-dnd, changing channel 65535 -> 2

2018-04-04T11:09:22.238Z| vcpu-0| I125: GuestRpc:

Channel 2, guest application toolbox-dnd.

2018-04-04T11:18:51.735Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox-dnd

timed out.

2018-04-04T11:19:00.010Z| vcpu-0| I125: Tools: Tools heartbeat timeout.

2018-04-04T11:19:06.739Z| vmx| I125:

GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2018-04-04T11:19:06.739Z| vmx| I125: GuestRpc: app toolbox-dnd's

second ping timeout; assuming app is down

2018-04-04T11:19:06.739Z| vmx| I125: GuestRpc: Reinitializing Channel 2(toolbox-dnd)

2018-04-04T11:19:06.739Z| vmx| I125: GuestMsg: Channel 2, Cannot unpost because the previous post is already completed

2018-04-04T21:02:02.766Z| mks| I125: SOCKET 6229867 (135) Creating VNC remote connection.

2018-04-04T21:02:02.856Z| mks|

W115: VNCENCODE 6229867 failed to allocate VNCBlitDetect

2018-04-04T21:02:02.856Z| mks| W115: VNCENCODE 6229867 failed to

allocate VNCBackBuffer

2018-04-04T21:02:04.911Z| vmx| I125: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1280

825

2018-04-04T21:02:07.024Z| vcpu-1|

W115: WinBSOD: Synthetic MSR[0x40000100] 0xd1

2018-04-04T21:02:07.024Z| vcpu-1|

W115: 2018-04-04T21:02:07.024Z| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000101] 0x3f8ddfbc

2018-04-04T21:02:07.024Z| vcpu-1|

2018-04-04T21:02:07.024Z| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000101] 0x3f8ddfbc

2018-04-04T21:02:07.024Z| vcpu-1| 

W115:

2018-04-04T21:02:07.024Z| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000102] 0x2

2018-04-04T21:02:07.024Z| vcpu-1|

W115:

2018-04-04T21:02:07.024Z| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000103] 0x1

2018-04-04T21:02:07.024Z| vcpu-1|

W115:

2018-04-04T21:02:07.024Z| vcpu-1| W115: WinBSOD: Synthetic MSR[0x40000104] 0x5edc82e2

2018-04-04T21:02:07.024Z| vcpu-1|

W115:

2018-04-04T21:02:07.024Z| vcpu-1| W115: Guest operating system crash detected.

2018-04-04T21:02:08.026Z| mks| I125: VNCENCODE 6229867 encoding desktop size: (1024x768x24depth,32bpp)

2018-04-04T21:02:08.071Z| mks| W115: VNCENCODE 6229867 failed to allocate VNCBlitDetect

2018-04-04T21:02:08.071Z| mks| W115: VNCENCODE 6229867 failed to allocate VNCBackBuffer

2018-04-04T21:02:08.161Z| mks| I125: VNCENCODE 6229867 encoding desktop size: (1164x768x24depth,32bpp)

2018-04-04T21:02:08.201Z| mks| I125: VNCENCODE 6229867 encoding desktop size: (1164x714x24depth,32bpp)

2018-04-04T21:02:08.245Z| mks| W115: VNCENCODE 6229867 failed to allocate VNCBlitDetect

2018-04-04T21:02:08.245Z| mks| W115: VNCENCODE 6229867 failed to allocate VNCBackBuffer

2018-04-04T21:02:09.498Z| vcpu-1| I125: LSI: Invalid PageType [21] pageNo 0 Action 0

2018-04-04T21:03:04.913Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.

2018-04-04T21:03:27.945Z| vcpu-0| I125: CPU reset: hard (mode 2)

2018-04-04T21:03:27.946Z| vcpu-1| I125: CPU reset: hard (mode 1)

2018-04-04T21:03:27.946Z| vcpu-0| I125: Destroying virtual dev for scsi0:0 vscsi=8391

2018-04-04T21:03:27.946Z| vcpu-0|

kindly confirm if u have any suggestions on same

with regards

Aniket

vmware.support@idfcbank.com/aniket.parab@wipro.com

Reply
0 Kudos