Good afternoon! WhatsApp.exe Crash

FacundoPacheco Sosa · Dec 7, 2023

I've been having problems with my PC for several weeks. Many blue screens, for various reasons. I've done EVERYTHING (it's incredible that there were so many things to correct and it still doesn't work as it should).

After finding and repairing the integrity of some corrupted files, I thought it was fixed. But a few minutes ago I was about to play a game of Team Fight Tactics to relax a bit and the PC stopped. This time it was not a blue screen, because after a few minutes everything returned to normal, with the difference that WhatsApp was closed; It obviously crashed.

From WinDBG and I opened a dumb file that was generated. I copy it below:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.078 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Facundo\AppData\Local\CrashDumps\WhatsApp.exe.15516.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19045 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Tue Dec 5 19:09:42.000 2023 (UTC - 3:00)
System Uptime: not available
Process Uptime: 0 days 6:37:52.000
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...............................................................
................................................................
................................................................
....
Loading unloaded module list
................................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3c9c.2a08): Unknown exception - code c000027b (first/second chance not available)
For analysis of this file, run !analyze -v
KERNELBASE!RaiseFailFastException+0x152:
00007ff8`8f84db22 0f1f440000 nop dword ptr [rax+rax]
0:002> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9843

Key : Analysis.Elapsed.mSec
Value: 12102

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 4796

Key : Analysis.Init.Elapsed.mSec
Value: 9679

Key : Analysis.Memory.CommitPeak.Mb
Value: 431

Key : Failure.Bucket
Value: STOWED_EXCEPTION_c000027b_Windows.UI.Xaml.dll!ImageSurfaceWrapper::AllocateHardwareResources

Key : Failure.Hash
Value: {09765531-5ffd-45b1-cc6c-bc5a1fb5b731}

Key : Timeline.Process.Start.DeltaSec
Value: 23872

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: WhatsApp.exe.15516.dmp

NTGLOBALFLAG: 40000000

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000b3b8fe130 rbx=0000000b3b8fe740 rcx=0000000b3b8fe130
rdx=0000000000000000 rsi=00000111198c0460 rdi=0000000b3b8fe130
rip=00007ff88f84db22 rsp=0000000b3b8fe050 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000b3b8fe740 r12=0000000000000000 r13=0000000080070057
r14=0000000000000002 r15=0000400000000000
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000200
KERNELBASE!RaiseFailFastException+0x152:
00007ff8`8f84db22 0f1f440000 nop dword ptr [rax+rax]
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff88f84db22 (KERNELBASE!RaiseFailFastException+0x0000000000000152)
ExceptionCode: c000027b
ExceptionFlags: 00000001
NumberParameters: 2
Parameter[0]: 00000111198c0460
Parameter[1]: 0000000000000005

PROCESS_NAME: WhatsApp.exe

ERROR_CODE: (NTSTATUS) 0xc000027b - An application-internal exception has occurred.

EXCEPTION_CODE_STR: c000027b

EXCEPTION_PARAMETER1: 00000111198c0460

EXCEPTION_PARAMETER2: 0000000000000005

STACK_TEXT:
0000000b`3b8fe050 00007ff8`9126c99a : 00000000`00000000 00000000`8000ffff 00000000`00000000 00000000`00000000 : KERNELBASE!RaiseFailFastException+0x152
0000000b`3b8fe630 00007ff8`603b6f5e : 00000000`0000038f 00000000`00000005 00000111`198c0460 00000000`00000001 : combase!RoFailFastWithErrorContextInternal2+0x43a
0000000b`3b8fe890 00007ff8`6016064e : 00000111`7d2a54f0 0000038f`000001fd 00000111`26619708 00007ff8`8b1ac047 : Windows_UI_Xaml!ImageSurfaceWrapper::AllocateHardwareResources+0x27f15a
0000000b`3b8fe970 00007ff8`60161664 : 000018e9`00000deb 00000000`00000000 00000111`26619cf0 0000038f`000001fd : Windows_UI_Xaml!CLoadedImageSurface::StartDecodingHelper+0xd2
0000000b`3b8fea20 00007ff8`6007eb5e : 0000000b`00000000 00000111`26619cf0 0000000b`3b8fea58 00000111`7d22eb18 : Windows_UI_Xaml!CLoadedImageSurface::StartFinalSizeDecoding+0x3c
0000000b`3b8fea50 00007ff8`6006f506 : 00000000`00000000 00007ff8`6012f901 0000000b`3b8feb00 00007ff8`601c3aef : Windows_UI_Xaml!CLoadedImageSurface::OnDeviceCreated+0x1e
0000000b`3b8fea80 00007ff8`6018be8d : 00000111`7d2a54f0 00000000`00000000 0000000b`3b8feb00 0000000b`3b8feb00 : Windows_UI_Xaml!CCoreServices::BuildDeviceRelatedResources+0xc2
0000000b`3b8fead0 00007ff8`6018bb95 : 00000111`7d289bb0 0000000b`3b8feb70 00000111`7d289bb0 ffffffff`fffffffe : Windows_UI_Xaml!CCoreServices::RecoverFromDeviceLost+0x69
0000000b`3b8feb00 00007ff8`6018bae6 : 00000111`7d289bb0 00000000`00000000 00000000`00000000 00000000`b5e32604 : Windows_UI_Xaml!CWindowRenderTarget:raw+0x45
0000000b`3b8feb40 00007ff8`601731bd : 0000d5c8`e51b8117 00000111`7d2a54f0 00007ff5`986e0000 00007ff8`8f750afd : Windows_UI_Xaml!CXcpBrowserHost::OnTick+0x96
0000000b`3b8feba0 00007ff8`601730c6 : 00000000`a2dea420 00000000`00000000 00000111`180254a0 00000000`00000000 : Windows_UI_Xaml!CXcpDispatcher::Tick+0x8d
0000000b`3b8febe0 00007ff8`600b5909 : 00000111`7d26ce00 00000111`7d2a1a50 00000111`24d79ef8 00000000`00000000 : Windows_UI_Xaml!CXcpDispatcher::OnReentrancyProtectedWindowMessage+0x42
0000000b`3b8fec20 00007ff8`600b797b : 00000111`7d2a1a50 00000111`7d26ce10 0000000b`3b8fecf8 00007ff8`00000000 : Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x119
0000000b`3b8fec70 00007ff8`600b786c : 00000111`7d2a1a50 00000111`7d2a1a50 00000000`00000000 00000000`00000000 : Windows_UI_Xaml!CDeferredInvoke:ispatchQueuedMessage+0xcb
0000000b`3b8fecc0 00007ff8`8c6d529b : 00000111`7d306c00 00000111`7d2a1a00 00000111`7d306cb0 00000111`7d2a1a50 : Windows_UI_Xaml!CXcpDispatcher::MessageTimerCallbackStatic+0x1c
0000000b`3b8fecf0 00007ff8`8c6fc39b : 00000111`7d26cd60 00000111`7d306f00 00000000`000af98f 00000111`7d26cd60 : CoreMessaging!Microsoft__CoreUI__Dispatch__TimeoutHandler$CallbackThunk+0x11b
0000000b`3b8fed70 00007ff8`8c6d9d84 : 00000000`00000000 00000111`7d295a00 00000111`7d295a00 00000000`00000000 : CoreMessaging!Microsoft::CoreUI:ispatch::TimeoutManager::Callback_OnDispatch+0x18b
0000000b`3b8fee00 00007ff8`8c6d8d36 : 00000000`00000000 00000111`2600b828 00000111`7d30bd90 00000111`7d299cb0 : CoreMessaging!Microsoft::CoreUI:ispatch::EventLoop::Callback_RunCoreLoop+0xc04
0000000b`3b8fef20 00007ff8`8c6d6f71 : 00000111`7d299cb0 00000111`7d313230 00000000`00000000 00000111`180465ff : CoreMessaging!Microsoft::CoreUI:ispatch::UserAdapter::OnUserDispatch+0x1d6
0000000b`3b8ff010 00007ff8`8c6d6dd6 : 00000111`7d313230 00000000`00000004 00000111`7d1b0000 00000000`40000c02 : CoreMessaging!Microsoft::CoreUI:ispatch::UserAdapter_DoWork+0xf1
0000000b`3b8ff0f0 00007ff8`902ee858 : 00000111`430f6500 00007ff8`4b790e9c 00000000`00000001 00000000`00000001 : CoreMessaging!Microsoft::CoreUI:ispatch::UserAdapter_WindowProc+0x136
0000000b`3b8ff170 00007ff8`902ee299 : 00000000`00003dff 00007ff8`8c6d6ca0 00000000`00010254 00000111`00000060 : user32!UserCallWinProcCheckWow+0x2f8
0000000b`3b8ff300 00007ff8`8573ef8b : 00007ff8`8c6d6ca0 00000111`7d306840 00000111`7d306800 00000000`00000000 : user32!DispatchMessageWorker+0x249
0000000b`3b8ff380 00007ff8`8573ec80 : 00000000`00000000 0000000b`00000000 00000111`7d306840 00007ff8`85845000 : Windows_UI!Windows::UI::Core::CDispatcher:rocessMessage+0x18b
0000000b`3b8ff430 00007ff8`8573eb0b : 0000000b`3b8ff5e0 00000111`7d306840 0000d5c8`e51b9987 00000000`00000300 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xc0
0000000b`3b8ff540 00007ff8`602f31b0 : 0000000b`3b8ff660 00000000`00000000 00000111`7d289850 00007ff8`89c683d3 : Windows_UI!Windows::UI::Core::CDispatcher:rocessEvents+0x7b
0000000b`3b8ff5f0 00007ff8`602f314f : 00000111`7d306840 00007ff8`601c827f 00000000`00000004 0000000b`3b8ff660 : Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x4c
0000000b`3b8ff620 00007ff8`89c75dca : 0000000b`3b8ff768 00000111`7d289850 00000111`7d27a8a0 00000000`00000004 : Windows_UI_Xaml!DirectUI:XamlCore::RunMessageLoop+0x47
0000000b`3b8ff690 00007ff8`89c2e65f : 00000111`00000000 00000000`80004005 00000111`7d276e40 00007ff8`89c35260 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x3a
0000000b`3b8ff6c0 00007ff8`8ffdbf69 : 00000111`00000000 00000000`00000005 00000000`00000004 00000000`00000000 : twinapi_appcore!<lambda_643db08282a766b00cec20194396f531>:perator()+0x1ef
0000000b`3b8ff760 00007ff8`8fea7344 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : SHCore!_WrapperThreadProc+0xe9
0000000b`3b8ff840 00007ff8`91e826b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000000b`3b8ff870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

STACK_COMMAND: ~2s; .ecxr ; kb

FAULTING_SOURCE_LINE: onecoreuap\windows\dxaml\xcp\core\core\elements\imagesurfacewrapper.cpp

FAULTING_SOURCE_FILE: onecoreuap\windows\dxaml\xcp\core\core\elements\imagesurfacewrapper.cpp

FAULTING_SOURCE_LINE_NUMBER: 723

FAULTING_SOURCE_CODE:
No source found for 'onecoreuap\windows\dxaml\xcp\core\core\elements\imagesurfacewrapper.cpp'

SYMBOL_NAME: windows_ui_xaml!ImageSurfaceWrapper::AllocateHardwareResources+27f15a

MODULE_NAME: Windows_UI_Xaml

IMAGE_NAME: Windows.UI.Xaml.dll

FAILURE_BUCKET_ID: STOWED_EXCEPTION_c000027b_Windows.UI.Xaml.dll!ImageSurfaceWrapper::AllocateHardwareResources

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.3758

FAILURE_ID_HASH: {09765531-5ffd-45b1-cc6c-bc5a1fb5b731}

Followup: MachineOwner
---------

I also opened the Event Viewer and found an event at the time the PC crashed. Says the following:

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 1a1

P2: ffffc98a8af07040

P3: 0

P4: 0

P5: 0

P6: 10_0_19045

P7: 0_0

P8: 256_1

P9:

P10:

Attached files:

\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog\PoW32kWatchdog-20231205-1900.dmp

\\?\C:\WINDOWS\TEMP\WER-114994203-0.sysdata.xml

\\?\C:\WINDOWS\LiveKernelReports\PoW32kWatchdog-20231205-1900.dmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE442.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4EF.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4FD.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE56C.tmp.txt

These files may be available here:

\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a1_18eede0d4e5e3b06799507ebe4e8124c7e22856_00000000_cab_b4c0b7b6-2d2f-40cc-aff2-22064d414e8b

Analysis symbol:

Rechecking for solution: 0

Report Id: b4c0b7b6-2d2f-40cc-aff2-22064d414e8b

Report Status: 2049

Hashed bucket:

Cab Guid: 0

And one more 8 minutes after:

Faulting application name: WhatsApp.exe, version: 0.0.0.0, time stamp: 0x65673cd3

Faulting module name: KERNELBASE.dll, version: 10.0.19041.3758, time stamp: 0xd80f8f12

Exception code: 0xc000027b

Fault offset: 0x000000000012db22

Faulting process id: 0x3c9c

Faulting application start time: 0x01da27902aab5c92

Faulting application path: C:\Program Files\WindowsApps\5319275A.WhatsAppDesktop_2.2347.1.0_x64__cv1g1gvanyjgm\WhatsApp.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 123a360e-543d-4229-8f08-8c6bfc63507a

Faulting package full name: 5319275A.WhatsAppDesktop_2.2347.1.0_x64__cv1g1gvanyjgm

Faulting package-relative application ID: App

I've tried a lot of things. Things that I thought should've worked but didn't.

What else can I try?

Thanks beforehand.

:)

Yuhao Li - MSFT

Hello, FacundoPacheco Sosa

Welcome to Microsoft Community.

It appears that the crash is related to the Windows.UI.Xaml.dll file. However, the provided dump file only records the process and does not indicate the cause. To determine the exact reason, it would be necessary to have a dump file generated by the operating system. You can follow the steps mentioned here to collect the dump file from the Windows system: Windows-based computer freeze troubleshooting - Windows Client | Microsoft Learn. If you encounter the WhatsApp crash again, please share the dump file generated by the system in your reply or upload it to a cloud storage service like OneDrive, Google Drive, Dropbox, Mega, etc. I will try to analyze the crash cause.

Yuhao Li

Microsoft Community Technical Support

TheDrake_

Good afternoon, I've tried many options and they all don't work. The game also crashes. But it began to crash after the last update of Windows 10.

TheDrake_

Good afternoon, I did everything that was suggested, still nothing helps. The game still crashes on these de moments.

JayDelgado

Puedes reiniciar el router e intentar de nuevo. También puedes chequear si los servidores de Xbox live están activos (disponible)

Visitando esta página:

http://xbox.com/status

Otra opción sería obtener un cable lan o ethernet y conectarlo directamente

[Translation - You can restart the router and try again. You can also check if the Xbox live servers are active (available)Visiting this page:http://xbox.com/statusAnother option would be to obtain a lan or ethernet cable and connect it directly]

koezz264

Como dice en los comentarios reinicie el router, luego recomiendo ir a configuración y chequear en redes para conectarte.

-[Translation - As it says in the comments restart the router, then I recommend going to settings and checking on networks to connect.]

Good afternoon! WhatsApp.exe Crash