Normal you would see something like this in the log:
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [VkLayer_swapchain.dll+0xb817]
C [VkLayer_swapchain.dll+0xcda5]
C [VkLayer_object_tracker.dll+0x1b801]
C [VkLayer_core_validation.dll+0xa223f]
C 0x0000000002375e34
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.lwjgl.system.JNI.callPPPPI(JJJJJ)I+0
j org.lwjgl.vulkan.KHRSwapchain.nvkCreateSwapchainKHR(Lorg/lwjgl/vulkan/VkDevice;JJJ)I+41
j org.lwjgl.demo.vulkan.HelloVulkan.demo_prepare_buffers()V+323
j org.lwjgl.demo.vulkan.HelloVulkan.demo_prepare()V+149
j org.lwjgl.demo.vulkan.HelloVulkan.run()V+13
j org.lwjgl.demo.vulkan.HelloVulkan.main([Ljava/lang/String;)V+7
This is a crash inside a Vulkan SDK validation layer. I don't think the validation layers are supposed to ever crash, but they're still being worked on and may improve in the future. Anyway, in order to get something useful out of the crash, you should use debug builds of the validation layers.
The Vulkan SDK comes with debug builds, in the <sdk path>/Source/lib directory. You can set the VK_LAYER_PATH environment variable to that directory and they will be used automatically. The output would change to:
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [VkLayer_swapchain.dll+0x15fbf] validateCreateSwapchainKHR+0x49f
C [VkLayer_swapchain.dll+0x11665] vkCreateSwapchainKHR+0x85
C [VkLayer_object_tracker.dll+0x14d82] vkCreateSwapchainKHR+0x102
C [VkLayer_core_validation.dll+0x43a2e] vkCreateSwapchainKHR+0x6e
C 0x00000000023f5e34
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.lwjgl.system.JNI.callPPPPI(JJJJJ)I+0
j org.lwjgl.vulkan.KHRSwapchain.nvkCreateSwapchainKHR(Lorg/lwjgl/vulkan/VkDevice;JJJ)I+41
j org.lwjgl.demo.vulkan.HelloVulkan.demo_prepare_buffers()V+323
j org.lwjgl.demo.vulkan.HelloVulkan.demo_prepare()V+149
j org.lwjgl.demo.vulkan.HelloVulkan.run()V+13
j org.lwjgl.demo.vulkan.HelloVulkan.main([Ljava/lang/String;)V+7
This should help a bit with identifying the issue. You can also use a native debugger to step into the validation layers.
Disclaimer: The pre-built debug layers did not work for me (SDK 1.0.8, on Windows). I had to clone
Vulkan-LoaderAndValidationLayers and build them manually.