Open GoogleCodeExporter opened 9 years ago
I can confirm this only occurs while Prismatik is open. Closing the
application, the issue disappears.
Almost every time I can recreate the crash by opening Prismatik, going into the
nVidia Control Panel, then Checking for Updates from the menu. If you'd like me
to include a crash log from that event as well I can do so.
Original comment by ke...@delaroche.me
on 30 Apr 2013 at 1:11
I too see constant iexplorer crashes when prismatic is open.
It appears to open an instance of IE in the background (there is a process
running but no IE window is displayed) and this process keeps crashing and
restarting. Killing the process manually seems to stop it however.
I am running Windows 7 64 bit.
Original comment by computer...@gmail.com
on 30 Apr 2013 at 11:02
will be fixed in the next release
Original comment by tim.hell...@gmail.com
on 1 May 2013 at 4:28
I have a similar Problem with a game called "Beat Hazard". Die problem is not
DirectX related - with hooking disabled, lights off and only the software
running it still crashes the game.
Is that the same Issue?
Original comment by andreas....@googlemail.com
on 11 May 2013 at 1:19
[deleted comment]
Heh I wanted to report this for months. This bug was in there from 5.9.x or
something like that. But For some reason I was just too lazy and there was very
little activity here or anywhere else, plus I tried to google the issue couple
times with no real results, so I just turned off the app every time after boot
and silently cursed devs for breaking something that worked before ;)
In any way, it crashes 99% of DX10/11 apps and pretty much any DX9 app that has
it's own overlay or has MSI afterburner hooked into. Which in turn mean every
game for me.
Also it does capture screen even if the constant light mode selected, causing
the usual lag with aero enabled.
There are also some stuff with experimental features that either does not do
anything or crashes the app immediately. I'll provide some data on it if needed.
P.S. If not for me noticing the Kickstarter campaign, I would not probably come
here for couple months more lol. I really hope Kickstarter stuff gives this
project a major boost since it was stagnant for a long time software wise if
not degrading. (Sure you add support for more stuff e.t.c. but core features
work much worse than they did when software was called Lightpack).
Original comment by Hc.Hot.C...@gmail.com
on 13 May 2013 at 6:15
andreas.depold:
Hardly. Please report new issue.
hc.hot.cooler:
Yes, the problem is in Dx9 hooking, we are looking forward for any details from
you.
Original comment by tim.hell...@gmail.com
on 15 May 2013 at 9:15
I'll test it out in couple days time and report what crashes and with what
stuff running in background. (Msi afterburner/steam overlay e.t.c.)
Original comment by Hc.Hot.C...@gmail.com
on 29 May 2013 at 3:13
Did you solve this?
I am still having this problem.
Original comment by tony.gu...@gmail.com
on 26 Jan 2014 at 2:10
prismatik-hooks.dll is causing damn near everything to crash when I exit out of
any application. The cause is prismatik-hooks.dll. VLC, Logitec Updater, Adobe
X, PhotoShop CS8, Outlook 2013, everything... Win7x64Ultimate.
Original comment by marwri...@gmail.com
on 8 Feb 2014 at 6:58
possibility to add exclusions will be added.
Original comment by tim.hell...@gmail.com
on 10 Feb 2014 at 8:06
For what it's worth, I don't want to exclude the apps that crash, I want them
to work with Prismatik but not to crash. VLC for instance captures fine, but it
crashes on exit. The Silverlight plugin for Firefox crashes as soon as it start
playing video, so you can't watch Netflix in Firefox - but it works in Chrome.
Anything that has an overlay also seems susceptible, like FRAPS.
Being able to watch videos/netflix and run games without disabling FRAPS seems
like a pretty expected usecases for Prismatik, so I'm not sure adding
exclusions is helping much. I don't really want Prismatik if I'm just reading
static websites and managing files.
Original comment by salman.h...@gmail.com
on 13 Feb 2014 at 7:26
Original issue reported on code.google.com by
ke...@delaroche.me
on 28 Apr 2013 at 12:19