Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I think these are related with BSOD.
---------------------------------------------
Hatalı uygulama adı: wallpaper32.exe, sürüm: 1.0.0.0, zaman damgası: 0x592812b8
Hatalı modül adı: wallpaper32.exe, sürüm: 1.0.0.0, zaman damgası: 0x592812b8
Özel durum kodu: 0xc0000005
Hata uzaklığı 0x00032437
Hatalı işlem kimliği: 0x1278
Uygulama başlangıç zamanı: 0x01d2ee8206d970a4
Hatalı uygulama yolu: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\wallpaper32.exe
Hatalı modül yolu: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\wallpaper32.exe
Rapor kimliği: c28974f7-5a80-11e7-a887-20cf30947f85
-------------------------------------------------
Hata demeti , tür 0
Olay Adı: APPCRASH
Yanıt: Kullanılamıyor
Cab Id: 0
Sorun imzası:
P1: wallpaper32.exe
P2: 1.0.0.0
P3: 592812b8
P4: wallpaper32.exe
P5: 1.0.0.0
P6: 592812b8
P7: c0000005
P8: 00032437
P9:
P10:
İliştirilmiş dosyalar:
Bu dosyalar burada bulunabilir:
C:\Users\Administrator\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_wallpaper32.exe_1bf2adb11969a667dc24a43b411d9381fe752f3_0c8e03a9
Çözümleme simgesi:
Çözüm için yeniden denetleme: 0
Rapor Kimliği: c28974f7-5a80-11e7-a887-20cf30947f85
Rapor Durumu: 0
-----------------------------------------------------------------------------------------------------
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
---------------------------------------------------------------------------------------------------------------------
I don't know about last if related with BSOD but it seems as Error.
But this one looks like a normal crash, so are there any mini dumps here: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine ?
http://www.mediafire. com/file/obyduhtii1h7i4w/Criticals.evtx
And here are the 2 mini dumps as you said:
http://www.mediafire. com/file/p7hde7ix21n24py/wallpaper_engine.rar
Edit: Steam doesn't allow links, please delete the space.
I think the mdmp and the BSOD doesn't coincide, the mdmp seems to have happened 30 minutes before the BSOD.
However the mdmp shows a graphics driver crash (probably recovered by Windows afterwards). Which graphics card do you have and is it possibly overclocked?
The BSOD events show a memory issue (PINBALL_FILE_SYSTEM, 0x00000059) which apparently can happen if there is just not enough memory available, so were you perhaps using a large wallpaper or even multiple? Was it happening while playing a game?
I was using this wallpaper while playing game:
http://steamcommunity.com/sharedfiles/filedetails/?id=850972127
BUT
I have thought like you and changed to another wallpaper, this without playing a game:
https://steamcommunity.com/sharedfiles/filedetails/?id=926250820&searchtext=
and it gave another BSOD still, I'm so scared to use Wallpaper Engine, it's so bad and sad. BSODs happened when I clicked somewhere.
Also, I was using "completely turn off when enter a game" option in Wallpaper Engine.
https://i.hizliresim. com/5Q7DGR.png
Do you mean like clicking on the desktop?
But since it even happens with scene wallpapers and not only videos, I don't know, scenes are exactly built like games are (just using DirectX to display 3D graphics).
The only foreign module that hooked into the program is Fraps, but I haven't heard of that causing issues.
You should probably consider refunding it while you are still in the 2h window because there is nothing I could change on my end. You can still test it as long as you don't run it through Steam so it won't increase the time, but other than Fraps I cannot think of what is causing it (could just be some driver feature or GameDVR or such though).
I will continue to testing, program is awesome.
I've sent request for refund.