servicesakp.blogg.se

LoadedModule=C:\Windows\system32\MSCTF.dll

LoadedModule=C:\Windows\system32\IMM32.DLL LoadedModule=C:\Windows\system32\WINSPOOL.DRV LoadedModule=C:\Windows\system32\USP10.dll LoadedModule=C:\Windows\system32\GDI32.dll LoadedModule=C:\Windows\system32\USER32.dll LoadedModule=C:\Windows\system32\RPCRT4.dll LoadedModule=C:\Windows\SYSTEM32\sechost.dll LoadedModule=C:\Windows\system32\msvcrt.dll LoadedModule=C:\Windows\system32\ADVAPI32.dll LoadedModule=C:\Windows\system32\KERNELBASE.dll LoadedModule=C:\Windows\system32\kernel32.dll LoadedModule=C:\Windows\SYSTEM32\ntdll.dll UI=Check online for a solution later and close the program UI=Check online for a solution and close the program UI=Windows can check online for a solution to the problem. UI=Print driver host for 32bit applications has stopped working IntegratorReportIdentifier=8a3117ad-bb80-11e5-b9e4-a0369f654611ĭynamicSig.Name=Additional Information 1ĭynamicSig.Name=Additional Information 2ĭynamicSig.Value=d40771d80355fad1dd5e50ce7ddbf91fĭynamicSig.Name=Additional Information 3ĭynamicSig.Name=Additional Information 4ĭynamicSig.Value=155d9ab26763fc3a6686fb802ec195d8 The printer is a Varioprint 135 on the network directly mapped to the computer. No updates accept the KB I listed above since the computer was new. dll file that is part of the print driver) to acrobat.dll, to StackHash_d05a. The faulting module varies from the one listed below (a. The WER report from one of the crashes is below. The problem) and a hotfix (KB2815716) to no avail. I've tried many things, including Print Conductor (thinking maybe Acrobat was Using the batch processing function in Acrobat Pro 9, and a program called Print Conductor, both programs give an splwow64.exe crash about 15-20 minutes after printing starts. Manually doing anything is not an option. My customers are very cranky and not very tech savvy. The only answers I've found either don't work, are from back in 2011 - 12 (therefore, I can't imagine they're up to date), or they involve "just bring up a command promptĪnd type." No. I've been dealing with this issue on a 2 month old computer for almost a month now.