(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
Please remember, this is not just happening to me, but a group of us using the same program that it seems to be the Only program this problem shows up in.
Also it doesn't matter which version of the program we use.I have tried at least 3 different versions of the program and 3 different versions of java which makes this even more mysterious.
Not everyone is running Win10, at least one of us is running Win7.
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
Please remember, this is not just happening to me, but a group of us using the same program that it seems to be the Only program this problem shows up in.
Also it doesn't matter which version of the program we use.I have tried at least 3 different versions of the program and 3 different versions of java which makes this even more mysterious.
Not everyone is running Win10, at least one of us is running Win7.
Okay, do you know a version of windows that runs the program with no problems
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
Please remember, this is not just happening to me, but a group of us using the same program that it seems to be the Only program this problem shows up in.
Also it doesn't matter which version of the program we use.I have tried at least 3 different versions of the program and 3 different versions of java which makes this even more mysterious.
Not everyone is running Win10, at least one of us is running Win7.
Okay, do you know a version of windows that runs the program with no problems
There are many others who are running the program with Win10 and Win7 and Mac and Linux, all with no problem. Then there are a few with Win10 and Win7 that are having the problem, so it doesn't seem to be specific to Windows.
I have asked if anyone has a different graphics card other than AMD, but from the ones that have answered, they have AMD cards.
I keep trying to get answers, but this group are not that forthcoming with answers!
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
Please remember, this is not just happening to me, but a group of us using the same program that it seems to be the Only program this problem shows up in.
Also it doesn't matter which version of the program we use.I have tried at least 3 different versions of the program and 3 different versions of java which makes this even more mysterious.
Not everyone is running Win10, at least one of us is running Win7.
Okay, do you know a version of windows that runs the program with no problems
There are many others who are running the program with Win10 and Win7 and Mac and Linux, all with no problem. Then there are a few with Win10 and Win7 that are having the problem, so it doesn't seem to be specific to Windows.
I have asked if anyone has a different graphics card other than AMD, but from the ones that have answered, they have AMD cards.
I keep trying to get answers, but this group are not that forthcoming with answers!
We are trying our best to help you and give you an answer. But with this case, we need to check every possibility, so, please give us chance to figure out a solution, it doesn't just come in one day.
I really appreciate every bit of help you try to give me, I am just trying to supply enough info for you guys to try and figure it out. Please let me know if you need any other info, as I cannot think of anything more to tell you which may help. Cheers.
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
The picture tells us what his temps are
It's better if you get the temps while the software is running and the problem occurs.
I didn't think of it that way, thank for the suggestion Double Clutch, Craig run JWildFire with CrystalDiskInfo open and then when the problem happens, have a look at the temperature and tell us what it is
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
The picture tells us what his temps are
It's better if you get the temps while the software is running and the problem occurs.
I didn't think of it that way, thank for the suggestion Double Clutch, Craig run JWildFire with CrystalDiskInfo open and then when the problem happens, have a look at the temperature and tell us what it is
(08-25-2016, 10:25 AM)Double clutch Wrote: I wonder what his temps are. what about a stress test on GPU
The picture tells us what his temps are
It's better if you get the temps while the software is running and the problem occurs.
I didn't think of it that way, thank for the suggestion Double Clutch, Craig run JWildFire with CrystalDiskInfo open and then when the problem happens, have a look at the temperature and tell us what it is
(08-25-2016, 10:33 AM)REC560 Wrote: The picture tells us what his temps are
It's better if you get the temps while the software is running and the problem occurs.
I didn't think of it that way, thank for the suggestion Double Clutch, Craig run JWildFire with CrystalDiskInfo open and then when the problem happens, have a look at the temperature and tell us what it is
OK, doing that now.
Great!
It took a while longer this time, almost thought the problem was gone... No!
