msiexec.exe appcrash

[dovstern]

Any thoughts(?) on dealing with the following:     

Version=1
EventType=APPCRASH
EventTime=131045196240278719
ReportType=2
Consent=1
ReportIdentifier=a111bb7f-fcdc-11e5-8930-e06995905d2c
IntegratorReportIdentifier=a111bb7e-fcdc-11e5-8930-e06995905d2c
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=msiexec.exe
Sig[1].Name=Application Version
Sig[1].Value=5.0.7600.16385
Sig[2].Name=Application Timestamp
Sig[2].Value=4a5bc7bd
Sig[3].Name=Fault Module Name
Sig[3].Value=msvcrt.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.0.7601.17744
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eeb033f
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000035e1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bbcf
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bbcf518a25bc3d575d398561a3a98913
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=6c43
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=6c43c599f20a6028cc7d09a953aa912a
UI[2]=C:\WINDOWS\system32\msiexec.exe
UI[3]=Windows® installer has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Windows® installer stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\WINDOWS\system32\msiexec.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\ADVAPI32.dll
LoadedModule[5]=C:\Windows\system32\msvcrt.dll
LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
LoadedModule[8]=C:\Windows\system32\USER32.dll
LoadedModule[9]=C:\Windows\system32\GDI32.dll
LoadedModule[10]=C:\Windows\system32\LPK.dll
LoadedModule[11]=C:\Windows\system32\USP10.dll
LoadedModule[12]=C:\Windows\system32\ole32.dll
LoadedModule[13]=C:\WINDOWS\system32\msi.dll
LoadedModule[14]=C:\Windows\system32\SHELL32.dll
LoadedModule[15]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[16]=C:\Windows\system32\apphelp.dll
LoadedModule[17]=C:\Windows\AppPatch\AppPatch64\AcLayers.DLL
LoadedModule[18]=C:\WINDOWS\system32\WINSPOOL.DRV
LoadedModule[19]=C:\WINDOWS\system32\MPR.dll
LoadedModule[20]=C:\Windows\AppPatch\AppPatch64\AcGenral.DLL
LoadedModule[21]=C:\WINDOWS\system32\SspiCli.dll
LoadedModule[22]=C:\WINDOWS\system32\sfc.dll
LoadedModule[23]=C:\WINDOWS\system32\sfc_os.DLL
LoadedModule[24]=C:\Windows\system32\USERENV.dll
LoadedModule[25]=C:\Windows\system32\profapi.dll
LoadedModule[26]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[27]=C:\Windows\system32\IMM32.DLL
LoadedModule[28]=C:\Windows\system32\MSCTF.dll
LoadedModule[29]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_fa3b1e3d17594757\COMCTL32.DLL
LoadedModule[30]=C:\WINDOWS\system32\CRYPTBASE.dll
LoadedModule[31]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[32]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[33]=C:\WINDOWS\system32\CRYPTSP.dll
LoadedModule[34]=C:\Windows\system32\rsaenh.dll
LoadedModule[35]=C:\WINDOWS\system32\RpcRtRemote.dll
LoadedModule[36]=C:\Windows\system32\NETAPI32.DLL
LoadedModule[37]=C:\WINDOWS\system32\netutils.dll
LoadedModule[38]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[39]=C:\WINDOWS\system32\wkscli.dll
LoadedModule[40]=C:\Windows\system32\SRCLIENT.DLL
LoadedModule[41]=C:\WINDOWS\system32\SPP.dll
LoadedModule[42]=C:\WINDOWS\system32\VSSAPI.DLL
LoadedModule[43]=C:\WINDOWS\system32\ATL.DLL
LoadedModule[44]=C:\WINDOWS\system32\VssTrace.DLL
LoadedModule[45]=C:\Windows\system32\VERSION.DLL
LoadedModule[46]=C:\Windows\system32\MSCOREE.DLL
LoadedModule[47]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[48]=C:\Windows\System32\drprov.dll
LoadedModule[49]=C:\Windows\System32\WINSTA.dll
LoadedModule[50]=C:\Windows\System32\ntlanman.dll
LoadedModule[51]=C:\Windows\System32\davclnt.dll
LoadedModule[52]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[53]=C:\WINDOWS\system32\browcli.dll
LoadedModule[54]=C:\WINDOWS\system32\cscapi.dll
LoadedModule[55]=C:\Windows\system32\FAULTREP.DLL
File[0].CabName=AppCompat.txt
File[0].Path=WER72AF.tmp.appcompat.txt
File[0].Flags=65538
File[0].Type=5
File[0].Original.Path=C:\Windows\temp\WER72AF.tmp.appcompat.txt
File[1].CabName=WERInternalMetadata.xml
File[1].Path=WER72CF.tmp.WERInternalMetadata.xml
File[1].Flags=65538
File[1].Type=5
File[1].Original.Path=C:\Windows\temp\WER72CF.tmp.WERInternalMetadata.xml
File[2].CabName=memory.hdmp
File[2].Path=WER72D0.tmp.hdmp
File[2].Flags=2097152
File[2].Type=3
File[2].Original.Path=C:\Windows\temp\WER72D0.tmp.hdmp
File[3].CabName=minidump.mdmp
File[3].Path=WER731F.tmp.mdmp
File[3].Flags=2162690
File[3].Type=2
File[3].Original.Path=C:\Windows\temp\WER731F.tmp.mdmp
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Windows® installer
AppPath=C:\WINDOWS\system32\msiexec.exe

[PCD_Channing]

Hello dovstern,

Can you provide me with some additional detail about what you are doing on the machine when you experience this crash? Which PC-Doctor product are you using? What is the version number? Please let me know.

Thanks,
Channing

[dovstern]

I was running Stress Diagnostics under PC-Doctor Toolbox for Windows, Version: 6.3.6554.49

[PCD_Channing]

Hello dovstern,

In order to look further into this can you please follow the process below to obtain some additional debugging logs for us to examine:

1. Open Run
     a. Move the mouse cursor to the lower left corner of the desktop
     b. Right click on the Windows button to bring up menu options
     c. Click on Run
2. Type "%programfiles%" (Including the % and without the quotes)
3. Open the "PC-Doctor Toolbox for Windows" folder
4. Right click on an empty space and select "New" and then "Folder
5. Name the folder you created "logs"(without quotes)(Leave this window open, we will have to come back to it)

1. Open a Command prompt as Admin (In the same location as Run)
2. Navigate to the installed directory (by typing "cd" followed by the location where PC-Doctor Toolbox for Windows is installed. Make certain to put a space after "cd".) (cd C:\Program Files\PC-Doctor Toolbox for Windows)
3. Enter the command "pcdrcui.exe -enabledebuglogs" (without quotes)(Note: Leave the Command Prompt open, we will need it later)

Once you have done this go ahead and try to use the software just as you had before, this will create the logs that we need.

After you have experienced the issue again, prepare the logs that we just
created:

1. Bring up the "PC-Doctor Toolbox for Windows" window that we left open
2. Right click on the "logs" folder that we created
3. Select "Send To"
4. Select "Compressed(zipped) folder" (Be sure to delete this folder after you are done)

Then please follow these steps to obtain the program logs:

1. Open Run (Same as before)
2. Type "%programdata%" (Including the % and without the quotes)
3. Open the "PCDr" folder
4. Open the folder "6554"
5. Right click on the "logs" folder
6. Select "Send To"
7. Select "Compressed(zipped) folder"(Please name the zipped file "programdata_logs.zip" to avoid confusion)

Once all of these folders have been compressed, you can upload them here or send them in to us via email (support[at]pc-doctor.com). We will take a look at these files and attempt to find out why you are having this problem.

Thanks,
Channing

[dovstern]

Thanks for the direction and sorry for not getting back sooner. I got up to the pcdrcui.exe -enabledebuglog command and got a response that pcdrcui.exe is not recognized as an internal or external command, operable program or batch file. See attached snip.  Any thoughts? I was very careful to follow the instructions.

Dov

[PCD_Channing]

Hi Dov,

It looks like you are running the command in the wrong directory. Please make sure you are running the pcdrcui.exe -enabledebuglogs command from the C:\Program Files\PC-Doctor Toolbox for Windows directory.

Please let me know if you are still seeing issues.

Thanks,
Channing

[dovstern]

Sorry about that....I guess it's time for new glasses...will get right on it...Thanks!

Dov

[dovstern]

Channing,

I have sent you a link to download the log files.

I was able to run the pcdrcui.exe -enabledebuglogs command and started to run 50 stress tests. I happened to be sitting next to the machine when it restarted itself, despite the fact that I had unchecked the "Automatically Restart" box in the Startup and Recovery tab of the Advanced System Properties dialog (snip sent). I also sent  the two zips of compressed log files specified.

I hope this gives you enough to work with.

Thanks for your assistance.

Dov

[dovstern]

Got two unattended critical motherboard errors Friday night on the internal send and receive test (see snip attached). What does the code WSP05-J6X mean?

BTW, while originally trying to do this post 5 minutes ago the PC restarted itself, despite the fact that Automatically Restart is not checked on the Startup and Recovery advanced system properties window. Machine had restarted twice over the weekend due to unexpected shutdowns.

What would be the best way to proceed? Replace motherboard?

Dov Stern

[PCD_Channing]

Hi Dov,

Thank you for the logs. Please allow me to do some further research on my findings. I will get back to you once I have some additional information.

Thanks,
Channing

[dovstern]

Thanks Channing!