After the patch this morning every time i pull up certain window like the char' info tab on some one else or zone to another area it causes my client and/or computer itself to reboot. Is this an issue just dealing with me or are there any other people out there having this issue.
After the patch this morning every time i pull up certain window like the char' info tab on some one else or zone to another area it causes my client and/or computer itself to reboot. Is this an issue just dealing with me or are there any other people out there having this issue.
:mad:
Sounds like you have faulty hardware, inadequate heating, faulty PSU or a driver error if your comp is rebooting.
Sounds like you have faulty hardware, inadequate heating, faulty PSU or a driver error if your comp is rebooting.
No, I don't think so, and reading your "one size fits all" explanation is becoming tedious. There is a definite programming issue with the application. It looks like it's overloading co-processors and causing them to miss interrupts. There is no way that 100% of the folks noting this BSOD/restart issue have inadequate hardware, under-powered PSUs, or driver issues.
My box, with 8 cores, 9 GB of RAM, a gaming-rated video card, and a honking huge PSU--not to mention the latest stable drivers for everything--is falling anywhere with range of your "solution."
See, the problem is that the issue mutates every time there's a new patch. It didn't happen at all for me until the last two days of open beta. Then it happened more or less regularly until the patch prior to full retail. It started again after the last patch. That's not consistent with your explanation at all, and 30+ years of computer experience allows me to tell the difference.
No, I don't think so, and reading your "one size fits all" explanation is becoming tedious. There is a definite programming issue with the application. It looks like it's overloading co-processors and causing them to miss interrupts. There is no way that 100% of the folks noting this BSOD/restart issue have inadequate hardware, under-powered PSUs, or driver issues.
My box, with 8 cores, 9 GB of RAM, a gaming-rated video card, and a honking huge PSU--not to mention the latest stable drivers for everything--is falling anywhere with range of your "solution."
See, the problem is that the issue mutates every time there's a new patch. It didn't happen at all for me until the last two days of open beta. Then it happened more or less regularly until the patch prior to full retail. It started again after the last patch. That's not consistent with your explanation at all, and 30+ years of computer experience allows me to tell the difference.
Not to offend you, but if your pc reboots by itself, then you have a hardware or driver problem. If it was th game, then everyone would have the same issue. The sooner you take the advice and get it fixed, the better. If you keep trying to blame everything else, the problem will spread to other components and break the sytem.
There is no way that 100% of the folks noting this BSOD/restart issue have inadequate hardware, under-powered PSUs, or driver issues.
umm, yea I'd willignly place a bet that almost all of them have inadequate hardware, Low rated PSU, and out of date drivers. Have a search of these tech forums. People are trying to play this game on very low spec systems or using badly configured hardware. They then try to use the excuse that because their system can play wow, it should be able to play any other game. Thats just simpy not true.
As for your system, i'd guess that it is down to inadequate cooling, or the system is badly configured. There are plently of players playing this game on similar systems, or systems that are even better than yours, yet they have no problems. Also, by your logic, lower spec systems would be having even worse issues. Again, thats is 100% not true.
My computer restarted too one time right in the middle of a PvP game and it was the Windows Update that without further information did it. At least the new Windows starts lightning quick and I could be on and playing in less that a minute.
No, I don't think so, and reading your "one size fits all" explanation is becoming tedious. There is a definite programming issue with the application. It looks like it's overloading co-processors and causing them to miss interrupts. There is no way that 100% of the folks noting this BSOD/restart issue have inadequate hardware, under-powered PSUs, or driver issues.
My box, with 8 cores, 9 GB of RAM, a gaming-rated video card, and a honking huge PSU--not to mention the latest stable drivers for everything--is falling anywhere with range of your "solution."
See, the problem is that the issue mutates every time there's a new patch. It didn't happen at all for me until the last two days of open beta. Then it happened more or less regularly until the patch prior to full retail. It started again after the last patch. That's not consistent with your explanation at all, and 30+ years of computer experience allows me to tell the difference.
I am SOOOOO glad someone called this out. I've wanted to multiple times and was curious when someone would.
I'm sure with a lot of people these things are the case. Bad instals of drivers will indeed cause reboots but sory that's not the only thing that will. Bad hardware will as well but again not the only thing that will. Windows, forget about it of course a bad Windows install will but again not the only thing that will.
You know what else causes reeboots and BSOD? Do you, for real? For instance you've repeatedly blamed page faults on user hardware failure. Well I have news for you. BAD CODING in the API for GPU sync will as well resulting in "out of sync" errors. It's realy at this level where things go wrong or recover. Dependent on the user environment (the workstations not the ambient lol) those sync issues can be exhasborated. Sometimes or some machines will recover from the stall and some wont.
Don't get me wrong it's awesome that people take their time to help others with technical problems within the community but your canning responses are NOT helpful. In fact you could have PERSONALLY caused people that know no better to spend money on hardware that was not needed and given this circumstance specifically I can guarantee you have.
Now that is again not to say that in some cases it is indeed "user error" but one things for certain there IS a problem in the coding itself. how do I know? I build machines for a living, tested the game on three very different configs and I can reproduce a BSOD on each machine. Granted I have to change the variables (graphic options in game and at driver level) but I can solidly reproduce a BSOD on each of the three machines.
umm, yea I'd willignly place a bet that almost all of them have inadequate hardware, Low rated PSU, and out of date drivers. Have a search of these tech forums. People are trying to play this game on very low spec systems or using badly configured hardware. They then try to use the excuse that because their system can play wow, it should be able to play any other game. Thats just simpy not true.
As for your system, i'd guess that it is down to inadequate cooling, or the system is badly configured. There are plently of players playing this game on similar systems, or systems that are even better than yours, yet they have no problems. Also, by your logic, lower spec systems would be having even worse issues. Again, thats is 100% not true.
I call BS on that. Ambient temp 62 F, Idle 33F, load 54F (that's maxed out and I mean MAXED on one machine I can enable Catalyst AI and enable Wide tent AA filtering that's x32 AA btw) and everything else and game runs smoothe as butter just like every other of the15 games on that machine but enable Dynamic lighting while everything is set to the lowest possible denominator and CRASH. That is a code problem not hardware. Now it wont BSOD because the amount of RAM not being pounded by requests is very low. Max everything out and enable DL and BSOD. That is on THREE machines using the same variable of low/dl, high/dl, low/no dl, high/no dl. On the high settings with DL it BSOD's every single time on three machines. Yeah that's user error LOL!
Ok. lets look at this problem another way, before people start flaming each other.
What is teh error message you get when you get the BSOD? Post the full name and error code if you can.
Let me be VERY clear, I am not flamming you. I am suggesting that before you continue to give canned responses you take into account that just because it's not a "wide spread" issue does not equate to user error or faulty hardware. That's irresponsible.
Let me be VERY clear, I am not flamming you. I am suggesting that before you continue to give canned responses you take into account that just because it's not a "wide spread" issue does not equate to user error or faulty hardware. That's irresponsible.
Ok. let me say this. When a BSOD occurs, 99.9% of the time, it is a hardware or driver fault. That is fact. That is why you see a "generic canned response". If you can reproduce the BSOD repeatedly, then post the full error message here, so you can gain input on whats wrong and how to fix it. Without that message, theres very little anyone can do to help you.
BTW, I should add that I would expect the game to crawl like a baby when maxed with DL but it certainly shouldnt BSOD. Weirder still is that it only crashes with the above formentioned on Ground Combat (lots of DL going on compared to space specifically when theres like 20 characters on screen spaming effects).
Ok. let me say this. When a BSOD occurs, 99.9% of the time, it is a hardware or driver fault. That is fact. That is why you see a "generic canned response". If you can reproduce the BSOD repeatedly, then post the full error message here, so you can gain input on whats wrong and how to fix it. Without that message, theres very little anyone can do to help you.
Unless you can recode the game there is nothing you can do to stop the DL from crashing the game. Plain and simply. The BSOD codes are irrelevant as they vary dependent on the "state" your at when the error reports itself. Besides, and this will sound like a flame but it's not intended to be it's just the truth. I can again guarantee I have more experience troubleshooting both hardware and software environments than you could imagine ( I own and operate a data center and am it's chief engineer) .
I get that your trying to help people but realy Cryptic will get around to recoding the API that's an eventaullity and I will just have to do without DL for now until they do. I'm just suggesting that you do yourself a favour and look beyond your narrow vision to the possibility that it is indeed software related not just hardware or user related.
Unless you can recode the game there is nothing you can do to stop the DL from crashing the game. Plain and simply. The BSOD codes are irrelevant as they vary dependent on the "state" your at when the error reports itself. Besides, and this will sound like a flame but it's not intended to be it's just the truth. I can again guarantee I have more experience troubleshooting both hardware and software environments than you could imagine ( I own and operate a data center and am it's chief engineer) .
I get that your trying to help people but realy Cryptic will get around to recoding the API that's an eventaullity and I will just have to do without DL for now until they do. I'm just suggesting that you do yourself a favour and look beyond your narrow vision to the possibility that it is indeed software related not just hardware or user related.
The BSOD errors will tell you what the problem is or related to. From those error codes we can work on a solution. As you keep insisting on trolling and refusing to provide the error codes, and will not even consider the possibility of any other source of the problem , then im sorry, but nobody including official tech support will be able to help you. Good luck in trying to resolve your problem.[/B]
I read somewhere the game does not play nice with overclocked pc's. Like mine. So after getting tired of the rebooting, I reset my pc back to factory defaults and the game has not caused any issues, over heating or rebooting.
I dont get a BSOD, the screen usually just goes black or brown and the sound loops continuously and i have to manually power off my system.. It's not inadequate hardware.. This is the ONLY game that does this out of all the new ones that have come out recently, such as dragon age and mass effect 2.. so its just not the OP who is having this problem..
Ok. lets look at this problem another way, before people start flaming each other.
What is teh error message you get when you get the BSOD? Post the full name and error code if you can.
if you can tell me how to record the message I could tell you its not even popping up blue screen.
for the record i updated all my drivers and bio's yesterday and it is still rebooting, tried it in windowed mode and again it is still rebooting, and i even lowerd all the graphics and it still reboots .
i know the easy response is "replace hardware" but not everyone can at a drop of a hat.
After applying the lastest patch on STO and being told to install the latest Nvidia driver (196.21) for a GTX295 , My computer has become unstable when playing the STO game.
The computer is performing a BSOD crashes regularly which is so quick the machine reboots before I can see what the error message is.
I work in IT so have used the normal process of elimination to find root cause.
Power problem? I know it is not a power issue as the computer would shut down immediately as if the power chord was pulled out - it's a safety feature of the PSU if components draw to much power that the psu can provide.
This leads to either a virus , overheating issue of the graphics card , a bad graphics driver , a bugged STO patch or a combination of updated graphics driver and STO patch.
I did a full virus scan of the PC , including boot records etc. No Virus found.
As far as overheating of the GPU goes, I am running a monitoring tool called Techpowerup GPU-Z, it is a light weight utility that can monitor the temperature and clock frequencies of most modern graphics cards, it can also write a log file of results. Basically after the reboot (from a crash), my GTX295 had a temperature rating of around 47c , when idle the GPU temperature is around 41c so this slight increase is quite normal temperature under load and indicates the card is not really being pushed while playing STO.
As far as the graphics driver causing a problem and \or STO patch combination causing the BSOD - I really don't know.
My next test is to disable the multi core GPU operation, this is a option in the nividia contol panel. Multi GPU's are used to increase 3d rendering so are normally a good thing but it will be interesting to see if this makes any diference.
If the PC BSOD again, I will revert back to a earlier graphics driver and see what that does,
Have you tried changing your system failure setting to not automatically restart in startup and recovey?
Thats a good point, It was set to restart, I've changed it now.
The latest is that with the following configuration of :
1. Disabled the multi core GPU operation
2. configured to Single Monitor (instead of Dual)
3. Monitored Temperature and GPU Load whilst playing game at 1920x1200 The temperature of the card hit a max of 60c.
I've just played the game for 2 hours straight , a couple of Fleet missions in both space and ground assualts and my system has worked fine with no crashes etc.
I'lll be on later so will continue monitoring, not sure what to make of these findings so far but I would speculate that the earlier crashes may be something to do with less load on the card (e.g. disabling dual monitor configuration) and the way in which the game code is using the GPU may have contributed to the crashes.
I have had the same problem. My computer seems to reboot itself once in a while when i play the game, and i have thought it was hardware related (not that my processor or hardware was getting too hot, i have a quite elaborate cooling systems with many fans).
But i'm starting to think that this might instead be driver related (maybe the game working bad with the latest ATI driver).
I have a ATI Radeon HD 4870 1gb ddr5, with a AMD dual core 6000+ and 3gb ddr2 RAM.
Thats a good point, It was set to restart, I've changed it now.
The latest is that with the following configuration of :
1. Disabled the multi core GPU operation
2. configured to Single Monitor (instead of Dual)
3. Monitored Temperature and GPU Load whilst playing game at 1920x1200 The temperature of the card hit a max of 60c.
I've just played the game for 2 hours straight , a couple of Fleet missions in both space and ground assualts and my system has worked fine with no crashes etc.
I'lll be on later so will continue monitoring, not sure what to make of these findings so far but I would speculate that the earlier crashes may be something to do with less load on the card (e.g. disabling dual monitor configuration) and the way in which the game code is using the GPU may have contributed to the crashes.
Ok. been playing the game for most of the day now and have had no problems whats so ever.
I can only assume that either the game or graphics Driver code does not like having Nividia Dual monitor setup and multi GPU configuration. At least I am able to play now - so happy for the time being
I don't recall, did you try the latest beta NVidia driver? One or two others reported it solved some issues for them in STO but I haven't tried it yet.
Comments
No, I don't think so, and reading your "one size fits all" explanation is becoming tedious. There is a definite programming issue with the application. It looks like it's overloading co-processors and causing them to miss interrupts. There is no way that 100% of the folks noting this BSOD/restart issue have inadequate hardware, under-powered PSUs, or driver issues.
My box, with 8 cores, 9 GB of RAM, a gaming-rated video card, and a honking huge PSU--not to mention the latest stable drivers for everything--is falling anywhere with range of your "solution."
See, the problem is that the issue mutates every time there's a new patch. It didn't happen at all for me until the last two days of open beta. Then it happened more or less regularly until the patch prior to full retail. It started again after the last patch. That's not consistent with your explanation at all, and 30+ years of computer experience allows me to tell the difference.
umm, yea I'd willignly place a bet that almost all of them have inadequate hardware, Low rated PSU, and out of date drivers. Have a search of these tech forums. People are trying to play this game on very low spec systems or using badly configured hardware. They then try to use the excuse that because their system can play wow, it should be able to play any other game. Thats just simpy not true.
As for your system, i'd guess that it is down to inadequate cooling, or the system is badly configured. There are plently of players playing this game on similar systems, or systems that are even better than yours, yet they have no problems. Also, by your logic, lower spec systems would be having even worse issues. Again, thats is 100% not true.
I am SOOOOO glad someone called this out. I've wanted to multiple times and was curious when someone would.
I'm sure with a lot of people these things are the case. Bad instals of drivers will indeed cause reboots but sory that's not the only thing that will. Bad hardware will as well but again not the only thing that will. Windows, forget about it of course a bad Windows install will but again not the only thing that will.
You know what else causes reeboots and BSOD? Do you, for real? For instance you've repeatedly blamed page faults on user hardware failure. Well I have news for you. BAD CODING in the API for GPU sync will as well resulting in "out of sync" errors. It's realy at this level where things go wrong or recover. Dependent on the user environment (the workstations not the ambient lol) those sync issues can be exhasborated. Sometimes or some machines will recover from the stall and some wont.
Don't get me wrong it's awesome that people take their time to help others with technical problems within the community but your canning responses are NOT helpful. In fact you could have PERSONALLY caused people that know no better to spend money on hardware that was not needed and given this circumstance specifically I can guarantee you have.
Now that is again not to say that in some cases it is indeed "user error" but one things for certain there IS a problem in the coding itself. how do I know? I build machines for a living, tested the game on three very different configs and I can reproduce a BSOD on each machine. Granted I have to change the variables (graphic options in game and at driver level) but I can solidly reproduce a BSOD on each of the three machines.
What is teh error message you get when you get the BSOD? Post the full name and error code if you can.
I call BS on that. Ambient temp 62 F, Idle 33F, load 54F (that's maxed out and I mean MAXED on one machine I can enable Catalyst AI and enable Wide tent AA filtering that's x32 AA btw) and everything else and game runs smoothe as butter just like every other of the15 games on that machine but enable Dynamic lighting while everything is set to the lowest possible denominator and CRASH. That is a code problem not hardware. Now it wont BSOD because the amount of RAM not being pounded by requests is very low. Max everything out and enable DL and BSOD. That is on THREE machines using the same variable of low/dl, high/dl, low/no dl, high/no dl. On the high settings with DL it BSOD's every single time on three machines. Yeah that's user error LOL!
Let me be VERY clear, I am not flamming you. I am suggesting that before you continue to give canned responses you take into account that just because it's not a "wide spread" issue does not equate to user error or faulty hardware. That's irresponsible.
Ok. let me say this. When a BSOD occurs, 99.9% of the time, it is a hardware or driver fault. That is fact. That is why you see a "generic canned response". If you can reproduce the BSOD repeatedly, then post the full error message here, so you can gain input on whats wrong and how to fix it. Without that message, theres very little anyone can do to help you.
Unless you can recode the game there is nothing you can do to stop the DL from crashing the game. Plain and simply. The BSOD codes are irrelevant as they vary dependent on the "state" your at when the error reports itself. Besides, and this will sound like a flame but it's not intended to be it's just the truth. I can again guarantee I have more experience troubleshooting both hardware and software environments than you could imagine ( I own and operate a data center and am it's chief engineer) .
I get that your trying to help people but realy Cryptic will get around to recoding the API that's an eventaullity and I will just have to do without DL for now until they do. I'm just suggesting that you do yourself a favour and look beyond your narrow vision to the possibility that it is indeed software related not just hardware or user related.
The BSOD errors will tell you what the problem is or related to. From those error codes we can work on a solution. As you keep insisting on trolling and refusing to provide the error codes, and will not even consider the possibility of any other source of the problem , then im sorry, but nobody including official tech support will be able to help you. Good luck in trying to resolve your problem.[/B]
if you can tell me how to record the message I could tell you its not even popping up blue screen.
for the record i updated all my drivers and bio's yesterday and it is still rebooting, tried it in windowed mode and again it is still rebooting, and i even lowerd all the graphics and it still reboots
i know the easy response is "replace hardware" but not everyone can at a drop of a hat.
Your system is overheating then or you have a faulty piece of hardware. have you tried running a proram called memtest?
Does your system make any beeping sound, on startup or shutdown?
After applying the lastest patch on STO and being told to install the latest Nvidia driver (196.21) for a GTX295 , My computer has become unstable when playing the STO game.
The computer is performing a BSOD crashes regularly which is so quick the machine reboots before I can see what the error message is.
I work in IT so have used the normal process of elimination to find root cause.
Power problem? I know it is not a power issue as the computer would shut down immediately as if the power chord was pulled out - it's a safety feature of the PSU if components draw to much power that the psu can provide.
This leads to either a virus , overheating issue of the graphics card , a bad graphics driver , a bugged STO patch or a combination of updated graphics driver and STO patch.
I did a full virus scan of the PC , including boot records etc. No Virus found.
As far as overheating of the GPU goes, I am running a monitoring tool called Techpowerup GPU-Z, it is a light weight utility that can monitor the temperature and clock frequencies of most modern graphics cards, it can also write a log file of results. Basically after the reboot (from a crash), my GTX295 had a temperature rating of around 47c , when idle the GPU temperature is around 41c so this slight increase is quite normal temperature under load and indicates the card is not really being pushed while playing STO.
As far as the graphics driver causing a problem and \or STO patch combination causing the BSOD - I really don't know.
My next test is to disable the multi core GPU operation, this is a option in the nividia contol panel. Multi GPU's are used to increase 3d rendering so are normally a good thing but it will be interesting to see if this makes any diference.
If the PC BSOD again, I will revert back to a earlier graphics driver and see what that does,
I'll keep you posted.
Have you tried changing your system failure setting to not automatically restart in startup and recovey?
Thats a good point, It was set to restart, I've changed it now.
The latest is that with the following configuration of :
1. Disabled the multi core GPU operation
2. configured to Single Monitor (instead of Dual)
3. Monitored Temperature and GPU Load whilst playing game at 1920x1200 The temperature of the card hit a max of 60c.
I've just played the game for 2 hours straight , a couple of Fleet missions in both space and ground assualts and my system has worked fine with no crashes etc.
I'lll be on later so will continue monitoring, not sure what to make of these findings so far but I would speculate that the earlier crashes may be something to do with less load on the card (e.g. disabling dual monitor configuration) and the way in which the game code is using the GPU may have contributed to the crashes.
There were reports of ATI Eyefinity with multiple monitors crashing STO in earlier posts.
But i'm starting to think that this might instead be driver related (maybe the game working bad with the latest ATI driver).
I have a ATI Radeon HD 4870 1gb ddr5, with a AMD dual core 6000+ and 3gb ddr2 RAM.
My graphics driver is Catalyst 10.2
Ok. been playing the game for most of the day now and have had no problems whats so ever.
I can only assume that either the game or graphics Driver code does not like having Nividia Dual monitor setup and multi GPU configuration. At least I am able to play now - so happy for the time being