Use this when: The screen turns blue (or black) with a sad face and a “stop code”, and the PC restarts itself.
Steps
|
Do this |
What should happen |
|
1. Read and note the stop code — the text after “stop code:”, for example CRITICAL_PROCESS_DIED. |
This is the single most useful thing for us. Photograph the screen if you can. |
|
2. Let it restart on its own. |
A one-off blue screen after which everything is fine is usually nothing to chase. |
|
3. Note what you were doing and whether anything changed recently — a new app, a new device, an update. |
Blue screens usually trace to a driver, a device, or an update. |
|
4. If it happens once and does not return, carry on and keep an eye on it. |
Isolated blue screens happen. A pattern is what matters. |
|
5. If it recurs, unplug recently added devices (a new dock, adapter, or USB device) and see if it stops. |
Isolates a faulty peripheral or its driver. |
If that did not work
It blue-screens repeatedly or in a loop. Log a HIGH ticket with the stop code. If it will not stay up, see “Windows Will Not Start”.
It started right after a new device or update. Say so in the ticket — that usually names the cause.
The same stop code appears each time. Include it exactly; it points straight at the fault.
Log a ticket
MEDIUM — Same day — Blue screens more than once. HIGH if it is looping or will not stay running. Always include the stop code.