Every few updates I get a plethora of BSod's. eventually things smooth back out. But what is really frustrating is that I get an AFK penalty when I get a BSoD in the middle of team play. I didn't leave because I was a jerk. I got kicked out by your game bugs. Maybe you could come up with a way for the system to tell a difference? I know team speak can tell me when a user has left because they left, or because the lost signal. So it must be possible.
This happens to me a lot, but most of the time, if I'm fast enough, the game doesn't even know I've gone anywhere, and I can pop right back into the map.
Nitpicking is a time-honored tradition of science fiction. Asking your readers not to worry about the "little things" is like asking a dog not to sniff at people's crotches. If there's something that appears to violate natural laws, then you can expect someone's going to point it out. That's just the way things are.
BSoD's are usually caused by drivers or hardware, like RAM, CPU or Hard drive.
If you want recommendations for testing applications, let me know.
Star Trek Battles Channel - Play Star Trek like they did in the series!Avatar: pinterest-com/pin/14003448816884219Are you sure it isn't time for a "colorful metaphor"? --Spock in 'The Voyage Home' SCE ADVISORY NOTICE: Improper Impulse Engine maintenance can result in REAR THRUSTER LEAKAGE. ALWAYS have your work inspected by another qualified officer.
Nitpicking is a time-honored tradition of science fiction. Asking your readers not to worry about the "little things" is like asking a dog not to sniff at people's crotches. If there's something that appears to violate natural laws, then you can expect someone's going to point it out. That's just the way things are.
Every few updates I get a plethora of BSod's. eventually things smooth back out. But what is really frustrating is that I get an AFK penalty when I get a BSoD in the middle of team play. I didn't leave because I was a jerk. I got kicked out by your game bugs. Maybe you could come up with a way for the system to tell a difference? I know team speak can tell me when a user has left because they left, or because the lost signal. So it must be possible.
an application is not going to cause a BSOD, BSOD would be caused by a system level failure (OS files issue, registry issue, driver issue, hardware issue).
To put in perspective so that even non-computerists can understand;
- STO is a house, made of stone, concrete, etc. Pretty large, awesome features (and therefor quite heavy.)
- Every house needs a foundation to stand on; In this case you might have chosen for Wood (Win98), Stones and marter (Win2000), Slabs of concrete (Winxp), Strengthened concrete (Vista and up).
Every type of foundation can only carry x much weight. As I mentioned; your house is pretty darn heavy... You might see where I'm going.
Even if your foundation would be one of the best, your foundation will be dependant of the ground it sits on.
A new, good maintained computer is like a stone-like underground; you won't have to worry.
But... If you have an older computer, never cleaned it, driver problems, overheating issues and stuff.. Then your underground is like mud (or softer). Your computer WILL crack and slide (BSOD).
That's quite the paradox, how could you nerf nerf when the nerf is nerfed. But how would the nerf be nerfed when the nerf is nerfed? This allows the nerf not to be nerfed since the nerf is nerfed? But if the nerf isn't nerfed, it could still nerf nerfs. But as soon as the nerf is nerfed, the nerf power is lost. So paradoxally it the nerf nerf lost its nerf, while it's still nerfed, which cannot be because the nerf was unable to nerf.
Regardless, the OPs initial concern, that the AFK penalty is being dished out to people who are not purposely going AFK but have encountered an error is still a valid concern.
Also, even though BSOD's are generally due to hardware, hardware driver or other operating system level hardware<->software interactions, they do give the appearance of being caused by an application since frequently the user is in that application whenever they see BSOD's due to specific drivers and hardware used by that particular application or a scenario specific to that application, so its quite understandable that a user would feel like the application is causing the error because from their perspective it seems to be occurring because of their use of that application.
And no, please don't ask me to repeat that sentence, its early and I haven't had my tea yet....
Comments
Joined January 2009
If you want recommendations for testing applications, let me know.
SCE ADVISORY NOTICE: Improper Impulse Engine maintenance can result in REAR THRUSTER LEAKAGE. ALWAYS have your work inspected by another qualified officer.
BlueScreenOfDeath is something different entirely, and that is hardware failure.
BSoDs can be caused by poorly written device drivers or malfunctioning hardware, such as faulty memory, power supply issues, overheating of components, or hardware running beyond its specification limits. In the Windows 9x era, incompatible DLLs or bugs in the operating system kernel could also cause BSoDs.
Joined January 2009
an application is not going to cause a BSOD, BSOD would be caused by a system level failure (OS files issue, registry issue, driver issue, hardware issue).
- STO is a house, made of stone, concrete, etc. Pretty large, awesome features (and therefor quite heavy.)
- Every house needs a foundation to stand on; In this case you might have chosen for Wood (Win98), Stones and marter (Win2000), Slabs of concrete (Winxp), Strengthened concrete (Vista and up).
Every type of foundation can only carry x much weight. As I mentioned; your house is pretty darn heavy... You might see where I'm going.
Even if your foundation would be one of the best, your foundation will be dependant of the ground it sits on.
A new, good maintained computer is like a stone-like underground; you won't have to worry.
But... If you have an older computer, never cleaned it, driver problems, overheating issues and stuff.. Then your underground is like mud (or softer). Your computer WILL crack and slide (BSOD).
I call it, the Stoutes paradox.
Also, even though BSOD's are generally due to hardware, hardware driver or other operating system level hardware<->software interactions, they do give the appearance of being caused by an application since frequently the user is in that application whenever they see BSOD's due to specific drivers and hardware used by that particular application or a scenario specific to that application, so its quite understandable that a user would feel like the application is causing the error because from their perspective it seems to be occurring because of their use of that application.
And no, please don't ask me to repeat that sentence, its early and I haven't had my tea yet....