Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Guides - Privacy & Security Tips
BSOD- How I Try To Find The Cause
Message
<blockquote data-quote="donetao" data-source="post: 319681" data-attributes="member: 27614"><p><strong> Defining a strategy and getting the right attitude </strong></p><p></p><p>You should think about a good strategy for troubleshooting system crashes and adapt a good attitude before starting out. Randomly trying this or that in combination with frustration and making the wrong assumptions will end you up drawing the wrong conclusions. Make sure that you write down all steps that you take down your path. Recognize and identify which are the hard facts and which have been your assumptions. For example, if a bug check occurs, you have a hard fact. As long as a problem does NOT occur, you still have no proof that the problem is solved because the problem not occurring might just be a temporary side effect or artifact of one of the actions that you have taken. Provoking a problem in order to find its root case is often a better strategy than "trying to solve" a problem without adequate information or knowledge. </p><p>The above is a quote from Who Crashed!</p><p><a href="http://www.resplendence.com/whocrashed_troubleshooting" target="_blank">http://www.resplendence.com/whocrashed_troubleshooting</a></p></blockquote><p></p>
[QUOTE="donetao, post: 319681, member: 27614"] [B] Defining a strategy and getting the right attitude [/B] You should think about a good strategy for troubleshooting system crashes and adapt a good attitude before starting out. Randomly trying this or that in combination with frustration and making the wrong assumptions will end you up drawing the wrong conclusions. Make sure that you write down all steps that you take down your path. Recognize and identify which are the hard facts and which have been your assumptions. For example, if a bug check occurs, you have a hard fact. As long as a problem does NOT occur, you still have no proof that the problem is solved because the problem not occurring might just be a temporary side effect or artifact of one of the actions that you have taken. Provoking a problem in order to find its root case is often a better strategy than "trying to solve" a problem without adequate information or knowledge. The above is a quote from Who Crashed! [url]http://www.resplendence.com/whocrashed_troubleshooting[/url] [/QUOTE]
Insert quotes…
Verification
Post reply
Top