As soon as you notice the intermittent error, try to probe test points, examine status words, and record as much as possible about all the signals on the system. Work out possibilities in your head later.
For example after how many tries I should declare the defect is not reproducible. But there are mysteries. Some mysteries we never solve. Atul, I think that depends on process. Probably the best way with that kind of bug problems is statistical approach. If you want to describe the process statistically then you should collect some basic features of the process.
The features are: minimum values, maximum values, range of the values, standard deviation. Going back to the root of your question: If in the same conditions every single time results are different then you know that the bug is not easy to reproduce.
We have a solution and tool for these problems. The method is based on execution differences, when we compare the exdecutions, I mean the failed and the passed one, ane based on the differences we usually can find the fault. More information on jidebug. Lots of generic advice. Wish each point had real life examples as opposed to just a few.
Maybe you could write a book or suggest one? But perhaps I have a blind spot. Can you suggest three or four that seem overly generic to you? Your email address will not be published. Some Principles of Intermittent Problems: Be comforted: the cause is probably not evil spirits. If it happened once, it will probably happen again. Be wary of any fix made to an intermittent bug.
Any software state that takes a long time to occur, under normal circumstances, can also be reached instantly, by unforeseen circumstances. Complex and baffling behavior often has a simple underlying cause.
Complex and baffling behavior sometimes has a complex set of causes. Intermittent problems often teach you something profound about your product. An intermittent problem in the lab might be easily reproducible in the field. The problem may be intermittent, but the risk of that problem is ever present. The more testability is designed into a product, the easier it is to investigate and solve intermittent problems.
When you have eliminated the impossible, whatever remains, however improbable, could have done a lot of damage by then! If you ever get in trouble an intermittent problem that you could not lock down before release, you will fare a lot better if you made a faithful, thoughtful, vigorous effort to find and fix it. The journey can be the reward, you might say. Some General Suggestions for Investigating Intermittent Problems: Recheck your most basic assumptions: are you using the computer you think you are using?
Eyewitness reports leave out a lot of potentially vital information. Invite more observers and minds into the investigation. Create incentives for people to report intermittent problems. Check tech support websites for each third party component you use. Maybe the problem is listed. Seek tools that could help you observe and control the system. Improve communication among observers especially with observers who are users in the field. Establish a central clearinghouse for mystery bugs, so that patterns among them might be easier to spot.
Look through the bug list for any other bug that seems like the intermittent problem. Make more precise observations consider using measuring instruments. Improve testability: Add more logging and scriptable interfaces. Control inputs more precisely including sequences, timing, types, sizes, sources, iterations, combinations. In Windows:. You can also download the Wushowhide troubleshooter to hide the problematic updates.
Check whether the internet connection stabilizes after uninstalling the update. A network reset uninstalls and removes network adapters you may have installed, plus their settings. Once you restart your PC, the network adapters will be reinstalled, and their settings set back to default.
Note : You need Windows 10 version or later to use network reset. Elsie is a technology writer and editor with a special focus on Windows, Android and iOS. She writes about software, electronics and other tech subjects, her ultimate goal being to help people out with useful solutions to their daily tech issues in a simple, straightforward and unbiased style.
Read Elsie's Full Bio. We hate spam too, unsubscribe at any time. Thanks for your feedback. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 9. Report abuse.
Details required :. I should also mention that sometimes the problem goes away on its own. I'll start my computer in the morning and there will be no stuttering. Rather it starts after some time using the computer. Additionally, the problem persists after restarting my computer. Thanks again for the suggestion to do a clean boot. I just tried doing that when the stuttering started but even after a restart into clean boot the problem persisted.
Tanner Bobak. So far I have tried the following to fix the problem to no avail: Update Windows fully now Windows 10 Home, version , OS build System is dual boot with Ubuntu Any ideas on how to further diagnose or address this issue? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
0コメント