It would be using a bunch of memory and then stop and then use a bunch and then stop until windows finally switched my computer to windows 7 basic mode. #5 Interesting update: I ran xsplit and unchecked the screen region I was capturing so it wasn't capturing anything and I was able to keep it open for a couple of minutes.ĭuring this time, I noticed that the dwm.exe (desktop window manager) process was going crazy. Sorry for the novel, what do you guys think the problem is? And is anyone else having xsplit crash their computer? I think it might still be under warranty, should I try to send it in? It seems to be running a couple of degrees cooler, but still getting up to 65-66° C and xsplit is still crashing. After seeing this, I cleaned out the processor heatsink (it was super dusty), cleaned off the thermal paste and added some new paste and put it all back together. I think the box that it came in said it shouldn't get above 62° C. After my comp crashed a few times, I checked the processor temperature and it gets up to 65-69° C. If it's not xsplit's fault, I think my processor have a problem.
I haven't streamed or used xsplit in about a month, so it's possible that some newer version is the cause of the problem, is there anyway to download an old version from a month ago? I thought this might be because of the new "tier3" update with gamesource, so I uninstalled that reinstalled the current non-tier3 version, but it still crashes me. By wigging out, I mean having messed up graphics/artifacts when I minimize and maximize a window (like google chrome), as well as the screen going black and then things slowly reappearing (such as the taskbar) but then the computer crashes before they all come back. So I can't even have xsplit open for more than a couple of minutes before my computer starts wigging out and then eventually crashes. I'm trying to figure out if xsplit is crashing my computer or if my processor is bad.
#1 Thought I'd ask some tech gurus for help.
0 kommentar(er)
