Turn does not work into an observable situation
My computer is slow can mean many things. An application takes time to open, a webpage fails to load, or the pointer stutters during an export. Begin with the specific action and visible result, then state what you expected instead. Another person can then understand the situation without first guessing what slow means in this case.
A useful opening might be: after connecting the external monitor, its screen stays black while the laptop display works normally. That already identifies the equipment, trigger and a working comparison. Saying the graphics card is broken would instead direct attention towards a cause that has not yet been established.
Describe the relevant environment
Record the exact computer model, Windows version and affected application. For accessories, include their models and connection path. A monitor connected directly to a laptop is a different setup from the same monitor connected through a dock and adapter. Write that chain in its actual order. Supply serial numbers privately only when the responsible support provider needs them.
Preserve the complete wording of an error message. A screenshot can help, but should not unnecessarily expose personal information. Explain when the message appears: during startup, after sign-in or following a particular click. That timing can be more useful than an indiscriminate list of every application installed on the computer.
Pair each attempt with its result
Avoid writing that you tried everything. State the few steps actually taken and what happened after each. For example: another cable made no difference; the same monitor works on a second computer. This avoids repetitive suggestions and identifies components that remain untested. If something is uncertain, say so instead of filling the gap with a guess.
Mention a relevant recent change, such as an update or newly connected accessory, without immediately treating it as the cause. Timing is a clue. For intermittent faults, note frequency and any recognisable conditions. Three times after waking while docked is more useful than always when the problem does not really happen every time.
Passwords, recovery keys and complete confidential documents do not belong in public forums. Diagnostic logs can contain personal paths and names too, so inspect them before sharing. End with a clear question, such as which comparison to try next. A manageable, accurate account is more likely to receive a useful answer than a long collection of theories attempting to anticipate every possible cause before the evidence has been examined.
