Windows 10: How do I read or understand dump file?

OldMike65 · Sep 10, 2015

Windows 10 created a new crashdump file called ShellExperienceHost.exe.3708 in my AppData/local/Crashdumps folder, does anyone know how to read one of these dump files or what this one means to me??? Thanks.

:)

pcp7 · Sep 10, 2015

BSOD and understanding dump files

Thanks for replying. So I did a memory Diagnostic Test and found no errors. I have uploaded all the reports/files you mentioned above to one drive and links have been posted below.

BSOD items 8-25-2016 (1)

One thing i forgot to mention is that most of the time these crashes happen is while I am running x264 encoding. I dont always get BSOD , sometimes all files get encoded without any problem while others
not even reach 10%. CPU has been overclocked to 4.4Ghz , but temperatures stay well under 78-80 C all the time. I am using water cooling btw.

Gerry C J Cornell · Sep 10, 2015

BSOD and understanding dump files

Please run the Windows Memory Diagnostic tool:

Windows 10 - How to Detect RAM Issues with Windows Memory Diagnostic Tool

Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please.

DriverView: Loaded Windows Drivers List

Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut Win+R, type msinfo32 and press the ENTER key. Select File, Export and give the file a name noting where it is located.
Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting
a copy. Please upload the file to your OneDrive, share with everyone and post a link here.

Please upload to your OneDrive and share with everyone a copy of your
System log file from your Event Viewer and post a link here. Please remove any earlier copies of the logs from your OneDrive.

To access the System log select the keyboard shortcut Win+R, type
eventvwr.msc and press the ENTER key. From the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and
Save All Events as (the default evtx file type) and give the file a name. Do
not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do
not clear logs whilst you have a continuing problem.

dalchina · Sep 10, 2015

Hi, besides the event viewer, and freeware Event Log Explorer, the easiest is probably Nirsoft's AppCrashView.

It certainly shows that process crashing many times, and I've noted a similar comment elsewhere.

Here's what appcrashview shows for one such:
Version=1
EventType=MoAppCrash
EventTime=130860191445246881
ReportType=2
Consent=1
UploadTime=130860191446006883
ReportIdentifier=d78cce0b-5499-11e5-b1f9-00242b20ef59
IntegratorReportIdentifier=dc8c8b79-7ddc-4832-bdab-71106bbf3bf4
NsAppName=praid:App
Response.BucketId=c9102f8d89d3422e9d2ea5d8e16aef86
Response.BucketTable=5
Response.LegacyBucketId=133180623931
Response.type=4
Sig[0].Name=Package Full Name
Sig[0].Value=Microsoft.Windows.ShellExperienceHost_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy
Sig[1].Name=Application Name
Sig[1].Value=praid:App
Sig[2].Name=Application Version
Sig[2].Value=10.0.10240.16425
Sig[3].Name=Application Timestamp
Sig[3].Value=55bec2bc
Sig[4].Name=Fault Module Name
Sig[4].Value=Windows.UI.Xaml.dll
Sig[5].Name=Fault Module Version
Sig[5].Value=10.0.10240.16431
Sig[6].Name=Fault Module Timestamp
Sig[6].Value=55c9b90a
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Offset
Sig[8].Value=0051fb4a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10240.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bdcb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=15ec
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=15ec6bdb19118e8d31d380ac8ee3b4ab
UI[2]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
LoadedModule[0]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\combase.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\system32\RPCRT4.dll
LoadedModule[7]=C:\Windows\system32\ole32.dll
LoadedModule[8]=C:\Windows\system32\sechost.dll
LoadedModule[9]=C:\Windows\system32\GDI32.dll
LoadedModule[10]=C:\Windows\system32\USER32.dll
LoadedModule[11]=C:\Windows\SYSTEM32\wincorlib.DLL
LoadedModule[12]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[13]=C:\Windows\system32\IMM32.DLL
LoadedModule[14]=C:\Windows\system32\MSCTF.dll
LoadedModule[15]=C:\Windows\system32\kernel.appcore.dll
LoadedModule[16]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[17]=C:\Windows\SYSTEM32\cryptsp.dll
LoadedModule[18]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[19]=C:\Windows\System32\Windows.UI.Xaml.dll
LoadedModule[20]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[21]=C:\Windows\SYSTEM32\CoreMessaging.dll
LoadedModule[22]=C:\Windows\SYSTEM32\Bcp47Langs.dll
LoadedModule[23]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[24]=C:\Windows\system32\advapi32.dll
LoadedModule[25]=C:\Windows\SYSTEM32\NInput.dll
LoadedModule[26]=C:\Windows\system32\shcore.dll
LoadedModule[27]=C:\Windows\system32\rsaenh.dll
LoadedModule[28]=C:\Windows\System32\twinapi.appcore.dll
LoadedModule[29]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[32]=C:\Windows\System32\ActXPrxy.dll
LoadedModule[33]=C:\Windows\system32\uxtheme.dll
LoadedModule[34]=C:\Windows\system32\CoreUIComponents.dll
LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[37]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[38]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\StartUI.dll
LoadedModule[39]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[40]=C:\Windows\SYSTEM32\VEEventDispatcher.dll
LoadedModule[41]=C:\Windows\SYSTEM32\nvwgf2um.dll
LoadedModule[42]=C:\Windows\system32\PSAPI.DLL
LoadedModule[43]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[44]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\QuickActions.dll
LoadedModule[45]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Windows.UI.ActionCenter.dll
LoadedModule[46]=C:\Windows\SYSTEM32\QuickActionsDataModel.dll
LoadedModule[47]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[48]=C:\Windows\System32\MrmCoreR.dll
LoadedModule[49]=C:\Windows\System32\Windows.UI.dll
LoadedModule[50]=C:\Windows\SYSTEM32\d2d1.dll
LoadedModule[51]=C:\Windows\system32\DataExchange.dll
LoadedModule[52]=C:\Windows\SYSTEM32\dcomp.dll
LoadedModule[53]=C:\Windows\System32\NotificationObjFactory.dll
LoadedModule[54]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[55]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[56]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[57]=C:\Windows\System32\Windows.Globalization.Fontgroups.dll
LoadedModule[58]=C:\Windows\SYSTEM32\fontgroupsoverride.dll
LoadedModule[59]=C:\Windows\System32\Windows.Storage.ApplicationData.dll
LoadedModule[60]=C:\Windows\system32\windows.storage.dll
LoadedModule[61]=C:\Windows\system32\powrprof.dll
LoadedModule[62]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[63]=C:\Windows\System32\Windows.Graphics.dll
LoadedModule[64]=C:\Windows\System32\threadpoolwinrt.dll
LoadedModule[65]=C:\Windows\SYSTEM32\policymanager.dll
LoadedModule[66]=C:\Windows\SYSTEM32\msvcp110_win.dll
LoadedModule[67]=C:\Windows\System32\Windows.StateRepository.dll
LoadedModule[68]=C:\Windows\SYSTEM32\StateRepository.Core.dll
LoadedModule[69]=C:\Windows\system32\windowscodecs.dll
LoadedModule[70]=C:\Windows\system32\directmanipulation.dll
LoadedModule[71]=C:\Windows\system32\shell32.dll
LoadedModule[72]=C:\Windows\SYSTEM32\winsta.dll
LoadedModule[73]=C:\Windows\System32\RTMediaFrame.dll
LoadedModule[74]=C:\Windows\system32\twinui.dll
LoadedModule[75]=C:\Windows\SYSTEM32\Windows.UI.Immersive.dll
LoadedModule[76]=C:\Windows\System32\Windows.Shell.ServiceHostBuilder.dll
LoadedModule[77]=C:\Windows\system32\NotificationControllerPS.dll
LoadedModule[78]=C:\Windows\System32\twinapi.dll
LoadedModule[79]=C:\Windows\System32\SystemSettings.DataModel.dll
LoadedModule[80]=C:\Windows\System32\msxml6.dll
LoadedModule[81]=C:\Windows\SYSTEM32\PhotoMetadataHandler.dll
LoadedModule[82]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\XamlTileRendering.dll
LoadedModule[83]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\DevicesFlowUI.dll
LoadedModule[84]=C:\Windows\system32\cfgmgr32.dll
LoadedModule[85]=C:\Windows\System32\DevicesFlowBroker.dll
LoadedModule[86]=C:\Windows\System32\DevDispItemProvider.dll
LoadedModule[87]=C:\Windows\System32\DeviceDisplayStatusManager.dll
LoadedModule[88]=C:\Windows\System32\FunDisc.dll
LoadedModule[89]=C:\Windows\System32\FdDevQuery.dll
LoadedModule[90]=C:\Windows\system32\fdprint.dll
LoadedModule[91]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[92]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[93]=C:\Windows\system32\usbui.dll
LoadedModule[94]=C:\Windows\SYSTEM32\DEVOBJ.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=MoAppCrash
AppName=Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App
AppPath=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=E73CDAA8B985F648D05673F0AFF76A31

OldMike65 · Sep 10, 2015

Thanks for the reply, I don't understand what this dump file is trying to tell me at the moment. I have restarted and that file that crashed and made that dump file didn't give me any errors after a restart, and my OS is running fine. I'm just trying to figure out what the heck happened to create that crash dump.

WhyMe · Sep 10, 2015

@OldMike65

I have not read this tutorial, although I did quickly scan. It appears, at first, glance, to use the same MS debugging tools/software and method that I have always used. Hope it helps.

http://www.instructables.com/id/How-...Dump/?ALLSTEPS

dalchina · Sep 10, 2015

FWIW, my folder as per your initial post is empty..

axe0 · Sep 10, 2015

Windows 10 created a new crashdump file called ShellExperienceHost.exe.3708 in my AppData/local/Crashdumps folder, does anyone know how to read one of these dump files or what this one means to me??? Thanks.
Click to expand...

Hi @OldMike65,

When a program crashes, it saves a dump file in the Crashdumps folder.
This dump file simply means that a program has crashed.
I believe this program 'ShellExperienceHost' is a part of windows self, but you shouldn't worry about it too much.

The dumps in this folder are usually pointing to files like .dll that couldn't be loaded or something.
I've read 1 once, it was pointing to a dll file, saying it couldn't load it, but the program worked just fine after the program crashed.

axe0 · Sep 10, 2015

Hi, besides the event viewer, and freeware Event Log Explorer, the easiest is probably Nirsoft's AppCrashView.

It certainly shows that process crashing many times, and I've noted a similar comment elsewhere.

Here's what appcrashview shows for one such:
Code: Version=1 EventType=MoAppCrash EventTime=130860191445246881 ReportType=2 Consent=1 UploadTime=130860191446006883 ReportIdentifier=d78cce0b-5499-11e5-b1f9-00242b20ef59 IntegratorReportIdentifier=dc8c8b79-7ddc-4832-bdab-71106bbf3bf4 NsAppName=praid:App Response.BucketId=c9102f8d89d3422e9d2ea5d8e16aef86 Response.BucketTable=5 Response.LegacyBucketId=133180623931 Response.type=4 Sig[0].Name=Package Full Name Sig[0].Value=Microsoft.Windows.ShellExperienceHost_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy Sig[1].Name=Application Name Sig[1].Value=praid:App Sig[2].Name=Application Version Sig[2].Value=10.0.10240.16425 Sig[3].Name=Application Timestamp Sig[3].Value=55bec2bc Sig[4].Name=Fault Module Name Sig[4].Value=Windows.UI.Xaml.dll Sig[5].Name=Fault Module Version Sig[5].Value=10.0.10240.16431 Sig[6].Name=Fault Module Timestamp Sig[6].Value=55c9b90a Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Offset Sig[8].Value=0051fb4a DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.10240.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=bdcb DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=15ec DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=15ec6bdb19118e8d31d380ac8ee3b4ab UI[2]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe LoadedModule[0]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\combase.dll LoadedModule[5]=C:\Windows\system32\msvcrt.dll LoadedModule[6]=C:\Windows\system32\RPCRT4.dll LoadedModule[7]=C:\Windows\system32\ole32.dll LoadedModule[8]=C:\Windows\system32\sechost.dll LoadedModule[9]=C:\Windows\system32\GDI32.dll LoadedModule[10]=C:\Windows\system32\USER32.dll LoadedModule[11]=C:\Windows\SYSTEM32\wincorlib.DLL LoadedModule[12]=C:\Windows\system32\OLEAUT32.dll LoadedModule[13]=C:\Windows\system32\IMM32.DLL LoadedModule[14]=C:\Windows\system32\MSCTF.dll LoadedModule[15]=C:\Windows\system32\kernel.appcore.dll LoadedModule[16]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[17]=C:\Windows\SYSTEM32\cryptsp.dll LoadedModule[18]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[19]=C:\Windows\System32\Windows.UI.Xaml.dll LoadedModule[20]=C:\Windows\SYSTEM32\wintypes.dll LoadedModule[21]=C:\Windows\SYSTEM32\CoreMessaging.dll LoadedModule[22]=C:\Windows\SYSTEM32\Bcp47Langs.dll LoadedModule[23]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[24]=C:\Windows\system32\advapi32.dll LoadedModule[25]=C:\Windows\SYSTEM32\NInput.dll LoadedModule[26]=C:\Windows\system32\shcore.dll LoadedModule[27]=C:\Windows\system32\rsaenh.dll LoadedModule[28]=C:\Windows\System32\twinapi.appcore.dll LoadedModule[29]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\SYSTEM32\CRYPTBASE.dll LoadedModule[32]=C:\Windows\System32\ActXPrxy.dll LoadedModule[33]=C:\Windows\system32\uxtheme.dll LoadedModule[34]=C:\Windows\system32\CoreUIComponents.dll LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll LoadedModule[36]=C:\Windows\SYSTEM32\dxgi.dll LoadedModule[37]=C:\Windows\SYSTEM32\d3d11.dll LoadedModule[38]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\StartUI.dll LoadedModule[39]=C:\Windows\system32\SHLWAPI.dll LoadedModule[40]=C:\Windows\SYSTEM32\VEEventDispatcher.dll LoadedModule[41]=C:\Windows\SYSTEM32\nvwgf2um.dll LoadedModule[42]=C:\Windows\system32\PSAPI.DLL LoadedModule[43]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[44]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\QuickActions.dll LoadedModule[45]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\Windows.UI.ActionCenter.dll LoadedModule[46]=C:\Windows\SYSTEM32\QuickActionsDataModel.dll LoadedModule[47]=C:\Windows\SYSTEM32\XmlLite.dll LoadedModule[48]=C:\Windows\System32\MrmCoreR.dll LoadedModule[49]=C:\Windows\System32\Windows.UI.dll LoadedModule[50]=C:\Windows\SYSTEM32\d2d1.dll LoadedModule[51]=C:\Windows\system32\DataExchange.dll LoadedModule[52]=C:\Windows\SYSTEM32\dcomp.dll LoadedModule[53]=C:\Windows\System32\NotificationObjFactory.dll LoadedModule[54]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[55]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[56]=C:\Windows\SYSTEM32\dwrite.dll LoadedModule[57]=C:\Windows\System32\Windows.Globalization.Fontgroups.dll LoadedModule[58]=C:\Windows\SYSTEM32\fontgroupsoverride.dll LoadedModule[59]=C:\Windows\System32\Windows.Storage.ApplicationData.dll LoadedModule[60]=C:\Windows\system32\windows.storage.dll LoadedModule[61]=C:\Windows\system32\powrprof.dll LoadedModule[62]=C:\Windows\SYSTEM32\PROPSYS.dll LoadedModule[63]=C:\Windows\System32\Windows.Graphics.dll LoadedModule[64]=C:\Windows\System32\threadpoolwinrt.dll LoadedModule[65]=C:\Windows\SYSTEM32\policymanager.dll LoadedModule[66]=C:\Windows\SYSTEM32\msvcp110_win.dll LoadedModule[67]=C:\Windows\System32\Windows.StateRepository.dll LoadedModule[68]=C:\Windows\SYSTEM32\StateRepository.Core.dll LoadedModule[69]=C:\Windows\system32\windowscodecs.dll LoadedModule[70]=C:\Windows\system32\directmanipulation.dll LoadedModule[71]=C:\Windows\system32\shell32.dll LoadedModule[72]=C:\Windows\SYSTEM32\winsta.dll LoadedModule[73]=C:\Windows\System32\RTMediaFrame.dll LoadedModule[74]=C:\Windows\system32\twinui.dll LoadedModule[75]=C:\Windows\SYSTEM32\Windows.UI.Immersive.dll LoadedModule[76]=C:\Windows\System32\Windows.Shell.ServiceHostBuilder.dll LoadedModule[77]=C:\Windows\system32\NotificationControllerPS.dll LoadedModule[78]=C:\Windows\System32\twinapi.dll LoadedModule[79]=C:\Windows\System32\SystemSettings.DataModel.dll LoadedModule[80]=C:\Windows\System32\msxml6.dll LoadedModule[81]=C:\Windows\SYSTEM32\PhotoMetadataHandler.dll LoadedModule[82]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\XamlTileRendering.dll LoadedModule[83]=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\DevicesFlowUI.dll LoadedModule[84]=C:\Windows\system32\cfgmgr32.dll LoadedModule[85]=C:\Windows\System32\DevicesFlowBroker.dll LoadedModule[86]=C:\Windows\System32\DevDispItemProvider.dll LoadedModule[87]=C:\Windows\System32\DeviceDisplayStatusManager.dll LoadedModule[88]=C:\Windows\System32\FunDisc.dll LoadedModule[89]=C:\Windows\System32\FdDevQuery.dll LoadedModule[90]=C:\Windows\system32\fdprint.dll LoadedModule[91]=C:\Windows\system32\SETUPAPI.dll LoadedModule[92]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[93]=C:\Windows\system32\usbui.dll LoadedModule[94]=C:\Windows\SYSTEM32\DEVOBJ.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=MoAppCrash AppName=Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy!App AppPath=C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=E73CDAA8B985F648D05673F0AFF76A31
Click to expand...

[/quote] Hi @dalchina,

Programs that are saying to help you solve a crash are not worth it.
They only show the basic. Windows files are blamed a lot, that's the only thing that those programs will give you, but when looking deeper into a dump file you'll see that 3rd party drivers are actually causing it.
(Talking about BSOD dump files, but its almost the same with program dump files)

OldMike65 · Sep 10, 2015

FWIW, my folder as per your initial post is empty..
Click to expand...

Sorry but this post does not make any sense to me sir. Just what are you asking me??? I didn't send anything to you, or know you wanted me too? So I am confused to say the least.

axe0 · Sep 10, 2015

Sorry but this post does not make any sense to me sir. Just what are you asking me??? I didn't send anything to you, or know you wanted me too? So I am confused to say the least.
Click to expand...

It only means he/she has had no progam crashes, or has deleted the files. Removing the files is usually done via a program like Ccleaner

OldMike65 · Sep 10, 2015

Hi @,

When a program crashes, it saves a dump file in the Crashdumps folder.
This dump file simply means that a program has crashed.
I believe this program 'ShellExperienceHost' is a part of windows self, but you shouldn't worry about it too much.

The dumps in this folder are usually pointing to files like .dll that couldn't be loaded or something.
I've read 1 once, it was pointing to a dll file, saying it couldn't load it, but the program worked just fine after the program crashed.
Click to expand...

Yeah axe0 I was thinking the same thing, because even thou I got the crash dump file, this morning, my OS never crashed, or rebooted. Everything was running ok, but I did manually reboot anyways just to make sure. I was just trying to figure out what Windows 10 did, or what happened to make the crash dump file. As you can tell, I don't know much at all about trying to understand or read the crash dump info. But......my OS is running fine, everything is working.

OldMike65 · Sep 10, 2015

It only means he/she has had no progam crashes, or has deleted the files. Removing the files is usually done via a program like Ccleaner
Click to expand...

Ok I guess....lol in my case I actually moved the dump file to another drive just to save it, incase someone needed to see it. Because, CCleaner would have deleted it quickly, just like you said. I will end up deleting it soon thou. Thanks axe0

axe0 · Apr 5, 2018

You're welcome *Smile
You can usually delete those files immediately, pretty much nobody will ever ask you for one of those files.

Windows 10: How do I read or understand dump file?

How do I read or understand dump file?

How do I read or understand dump file?

How do I read or understand dump file?

How do I read or understand dump file?

How do I read or understand dump file?

How do I read or understand dump file? - Similar Threads - read understand dump

Read a dump file.

Read a dump file.

Help understanding this dump file

Help understanding this dump file

Help understanding this dump file

I keep having bluescreens but can't quite understand how to read the dump file. What is the...

I keep having bluescreens but can't quite understand how to read the dump file. What is the...

I keep having bluescreens but can't quite understand how to read the dump file. What is the...

How to read dump files?