Spotify desktop app crashing

[victorinoaditya]

Windows OS suddenly stops the Spotify App on desktop. No issue occurred before, already updated all audio drivers

[Alex]

Hi there

Sorry to hear that you're having such an experience with the app.

We'd recommend running a clean reinstall of the app. Please follow the steps from this Spotify Guide exactly, as this will assure that all app data is cleared completely, before reinstalling. Corrupted app data can sometimes cause issues like this. 

If that doesn't make a difference, let us know in the app crashes straight after startup or while you're listening to music.

Keep us posted on how you get on with this.

Cheers.

[victorinoaditya]

I already did the clean reinstall of the app using 3rd party software
and or using the remove program feature from windows itself but
Spotify keeps crashing when i log in

[Eni]

Hey there @victorinoaditya,

Thanks for your reply.

We suggest that you head over to the app settings > toggle on Show Local Files > toggle off all the sources that appear there > toggle off Show Local Files. Afterwards, make sure to restart the app. 

If that doesn't change anything, you can turn off the Hardware Acceleration in the app settings. Does that help?

Let us know how it goes.

[Baow1]

Hi

I will hijack this thread as I have the same problem and have had får about a month.
Sometimes I can use Spotify Desktop app for about 10-30 minutes before it crashes and other times it crashes as I start the app and press play.

I've done all your suggestions but non of it work.

I have reinstalled Spotify, Audio Drivers and GPU Drivers and the only thing left for me to do is reinstalling Windows and I will NOT do that drastic measure.

Here is what Windows Event Viewer shows when the app crashes for me:

First this error:

Faulting application name: Spotify.exe, version: 1.1.88.612, time stamp: 0x62adb482
Faulting module name: combase.dll, version: 10.0.19041.1741, time stamp: 0x67ba43f7
Exception code: 0xc000027b
Fault offset: 0x00204261
Faulting process ID: 0x1b14
Faulting application start time: 0x01d88b8af5851680
Faulting application path: C:\Users\PinkDady\AppData\Roaming\Spotify\Spotify.exe
Faulting module path: C:\Windows\System32\combase.dll
Report ID: 0017ff81-edfa-4676-b2b4-0ba068915d03
Faulting package full name:
Faulting package-relative application ID:

After that his info:

Fault bucket 1767401565932456451, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Spotify.exe
P2: 1.1.88.612
P3: 62adb482
P4: combase.dll
P5: 10.0.19041.1741
P6: 67ba43f7
P7: 80070497
P8: 000a68f2
P9:
P10:

Attached files:
\\?\Z:\The Elder Scrolls\The Elder Scrolls III Morrowind Original Game Soundtrack [MP3]\07. Main Theme.mp3
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2D0B.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EC2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EF1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2EEF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F5E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Spotify.exe_5f4459bdcb543516fe2ea8ad9d9b89cf3f297d_32a9bb3c_860c9ad7-1ecd-48c2-902f-95ad5ea096cb

Analysis symbol:
Rechecking for solution: 0
Report Id: 0017ff81-edfa-4676-b2b4-0ba068915d03
Report Status: 268435456
Hashed bucket: bd79d13aff75b3f38887125c30df8a03
Cab Guid: 0

[Jeremy]

Hi there folks,

Thank you for your posts and all the good provided information.

There's actually an ongoing issue about this here that's being investigated. We recommend that you give it a like and subscribe to it so that you don't miss any updates.

Let us know if we can help you with anything else in the meantime.

Take care!

[victorinoaditya]

Hi there,

I am wondering whether other users have similar issue in their desktop
while using the spotify app? or there is a problem in my hardware?
because the app suddenly crashed during my normal routine and i didn't
change anything with my setup.

[Eni]

Hey @victorinoaditya, 

Thanks for getting in touch about this. 

As @Jeremy mentioned above, the right teams are aware of this happening and they're currently looking into it. 

In this case, you can add your vote to the Ongoing Issue mentioned previously, if you haven't already. Also, make sure to leave a comment there providing us with the info we're asking for in the Status update. 

If you need a hand with anything else, the Community is here for you.