Changed CPU's -> HWINFO64 won't run anymore

maseo

Member
HWINFO64 forces closes itself, no log as it CTD's and logs in Windows 10 eventviewer as "APPCRASH". I've tried various versions, none of them allow the application to start and all of them CTF/Force close before a log can even be procured. Any suggestions? Fwiw, Aida64 and Ryzen Master work fine, but apps like CPU-Z and HWMonitor also have the same problem, pointing at Faulting module name: MSCTF.dll, version: 10.0.18362.387, time stamp: 0x1dc2f89b.

Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: HWiNFO64.EXE
P2: 6.20.4030.0

Faulting application name: HWiNFO64.EXE, version: 6.20.4030.0, time stamp: 0x5de7ab87
Faulting module name: MSCTF.dll, version: 10.0.18362.387, time stamp: 0x1dc2f89b
Exception code: 0xc0000005
Fault offset: 0x000000000000d391
Faulting process id: 0x53dc
Faulting application start time: 0x01d5c16f49785e3a
Faulting application path: C:\Program Files\HWiNFO64\HWiNFO64.EXE
Faulting module path: C:\WINDOWS\System32\MSCTF.dll
Report Id: e15680ed-ca2b-48f0-8538-8842898e90a3
Faulting package full name:
Faulting package-relative application ID:
 

Martin

HWiNFO Author
Staff member
The to completely Reset Preferences in the main settings of HWiNFO. You can reach these options before starting the main scan.
 

maseo

Member
The to completely Reset Preferences in the main settings of HWiNFO. You can reach these options before starting the main scan.
Reset all preferences, enabled debug mode (portable and installer); won't initiate scan at all. Application shows in taskmanager, then CTD's / force closes.
 

Martin

HWiNFO Author
Staff member
After HWiNFO terminates, please attach the HWiNFO64.DBG file it created. That should tell me what exactly happens there.
 

Martin

HWiNFO Author
Staff member
This is very strange. Try to also delete the INI file and check again if there's really no DBG file created in the installation folder.
You might also try the latest Beta build 6.21.
 

Martin

HWiNFO Author
Staff member
I'm afraid I don't know why this is happening, but the fact that other applications are affected in the same way indicates some issue in the system installation, most probably Windows components.
I would suggest to install all Windows updates, if that won't help then run some Windows diagnostics, perhaps try to unintstall/reinstall components.
 

maseo

Member
I'm afraid I don't know why this is happening, but the fact that other applications are affected in the same way indicates some issue in the system installation, most probably Windows components.
I would suggest to install all Windows updates, if that won't help then run some Windows diagnostics, perhaps try to unintstall/reinstall components.
Thanks Martin. The irony is that windows is up to date. CPU-Z, HWMonitor or other application have no specific information why it's crashing. I'll continue digging.
In the meantime, here's the report.wer file:

Version=1
EventType=APPCRASH
EventTime=132224523594339392
ReportType=2
Consent=1
UploadTime=132224523595999761
ReportStatus=268435456
ReportIdentifier=a00f7740-659e-42bd-95ce-8c9bb2d84d3a
IntegratorReportIdentifier=b79e6000-bf95-409a-a7f5-1a91d8719eb5
Wow64Host=34404
NsAppName=HWiNFO64.EXE
OriginalFilename=HWiNFO64.EXE
AppSessionGuid=00003ca4-0001-0104-c3e6-90ee80c1d501
TargetAppId=W:00004f62bf5ecfbe45d6cb39ca0aa20852340000ffff!00004efe9fe8f5c6bb2201460bf9556ac30da43a6417!HWiNFO64.EXE
TargetAppVer=2019//12//04:12:50:15!4490c5!HWiNFO64.EXE
BootId=4294967295
ServiceSplit=2564096
TargetAsId=468
UserImpactVector=808452096
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=dfdd7e4c4d9d1bc5fa496afae0334302
Response.BucketTable=4
Response.LegacyBucketId=1894162744021828354
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=HWiNFO64.EXE
Sig[1].Name=Application Version
Sig[1].Value=6.20.4030.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5de7ab87
Sig[3].Name=Fault Module Name
Sig[3].Value=MSCTF.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.18362.387
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=1dc2f89b
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000000000000d391
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.18362.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3072
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=099c
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=099c7c87f1504e12143db9e4ead393c0
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8f49
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8f49dc10927c41951c29040530833358
UI[2]=C:\Program Files\HWiNFO64\HWiNFO64.EXE
LoadedModule[0]=C:\Program Files\HWiNFO64\HWiNFO64.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:\Program Files\Bitdefender\Bitdefender Security\atcuf\264422702906632813\atcuf64.dll
LoadedModule[5]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\sechost.dll
LoadedModule[8]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[10]=C:\WINDOWS\System32\combase.dll
LoadedModule[11]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[12]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\WINDOWS\System32\shcore.dll
LoadedModule[14]=C:\WINDOWS\System32\USER32.dll
LoadedModule[15]=C:\WINDOWS\System32\win32u.dll
LoadedModule[16]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[17]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[18]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[19]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[20]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[21]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[22]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[23]=C:\WINDOWS\System32\profapi.dll
LoadedModule[24]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[25]=C:\WINDOWS\System32\UMPDC.dll
LoadedModule[26]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[27]=C:\WINDOWS\System32\cryptsp.dll
LoadedModule[28]=C:\WINDOWS\System32\ole32.dll
LoadedModule[29]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[30]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[31]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.18362.476_none_e6c4b11b130f2595\COMCTL32.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[36]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[39]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[40]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[41]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[42]=C:\WINDOWS\System32\setupapi.dll
LoadedModule[43]=C:\WINDOWS\system32\hid.dll
LoadedModule[44]=C:\WINDOWS\system32\nvapi64.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\dxcore.dll
LoadedModule[48]=C:\Program Files\NVIDIA Corporation\NVSMI\nvml.dll
LoadedModule[49]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[50]=C:\WINDOWS\system32\msimg32.dll
LoadedModule[51]=C:\WINDOWS\system32\opencl.dll
LoadedModule[52]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[53]=C:\WINDOWS\system32\wevtapi.dll
LoadedModule[54]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[55]=C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks64.dll
LoadedModule[56]=C:\WINDOWS\System32\TextInputFramework.dll
LoadedModule[57]=C:\WINDOWS\System32\CoreUIComponents.dll
LoadedModule[58]=C:\WINDOWS\System32\CoreMessaging.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[60]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[61]=C:\WINDOWS\System32\iertutil.dll
LoadedModule[62]=C:\WINDOWS\System32\clbcatq.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=18362
OsInfo[3].Key=ubr
OsInfo[3].Value=476
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1043
OsInfo[7].Key=geoid
OsInfo[7].Value=176
OsInfo[8].Key=sku
OsInfo[8].Value=48
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=297591
OsInfo[15].Key=osinsty
OsInfo[15].Value=3
OsInfo[16].Key=iever
OsInfo[16].Value=11.476.18362.0-11.0.160
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32696
OsInfo[19].Key=svolsz
OsInfo[19].Value=236
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=190318
OsInfo[22].Key=bldtm
OsInfo[22].Value=1202
OsInfo[23].Key=bldbrch
OsInfo[23].Value=19h1_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.18362.476.amd64fre.19h1_release.190318-1202
OsInfo[30].Key=buildflightid
OsInfo[30].Value=ea937804-0215-4b41-999f-1485e788551d
OsInfo[31].Key=edition
OsInfo[31].Value=Professional
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=HWiNFO64
AppPath=C:\Program Files\HWiNFO64\HWiNFO64.EXE
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=FB2A37A30E20652D5679AEB33E0A80F7
MetadataHash=786862670
 

maseo

Member
I'm afraid I don't know why this is happening, but the fact that other applications are affected in the same way indicates some issue in the system installation, most probably Windows components.
I would suggest to install all Windows updates, if that won't help then run some Windows diagnostics, perhaps try to unintstall/reinstall components.
Martin, changing the settings in hwinfo64.ini to:

DebugMode=1
SensorsOnly=1
ShowWelcomeAndProgress=0
Autorun=1
Starts the application and shows all the sensor information. DBG file is now also created. I can share this if that helps?
 

Martin

HWiNFO Author
Staff member
Interesting.. But that's most probably just some coincidence that avoids exposing the problem in Windows system components.
I guess the culprit was disabling the ShowWelcomeAndProgress option.
 

loftygoals

New Member
I have been experiencing this exact same problem with HWINFO64 since I upgraded my CPU-- a AMD Ryzen 2700X to a 3800X. Just like @maseo, HWINFO64 crashes with event log information indicating an APPCRASH with faulting module MSCTF.dll. Also like the OP, I also experience this when I try to run CPU-Z.

As @Martin suggested, I set ShowWelcomeAndProgress=0 and this allowed HWINFO64 to successfully run.

Again just as the OP, Windows 10 is 100% updated. I also ran sfc /scannow to ensure the system was healthy.
 

SteverinoLA

New Member
I found this post as I just started having this same issue with msctf.dll gpf when trying to run HWInfo, CPU-Z or HWMonitor. Setting ShowWelcomeAndProgress=0 and SensorsOnly=1 in ini file does let HWInfo come up w/sensors.

But why? MSCTF is part of text services which I don't use or change. And this just started a couple days ago. Only thing I've changed is updating Realtek audio drivers. Could that matter?

It can't get to the debug logging without these 2 options set, but we want the debug output for when it fails. Unfortuantely, it fails before ever starting debug log.
 
Top