Vous êtes confronté à un problème matériel persistant. Comment naviguez-vous dans le processus de dépannage ?

"Persistent hardware problem" is a very general description. To come to this conclusion, there are initial steps to take first: Observe the computer behavior when being turned on up to the point of its failure. A normal computer startup will conduct its own hardware check upon UEFI/BIOS loading (CPU, RAM, DISKS, etc). If successful, it will continue to load the OS. 1. IN THE EVENT OF A BLANK SCREEN, DARK SCREEN 2. IN THE EVENT IT CAN NOT LOAD OS 3. IN THE EVENT IT KEEPS SHUTTING DOWN. I wrote a comment here detailing the 3 scenarios but apparently LinkedIn only provide me with 750 characters.

1st: When/(How long) did this start happening? 2nd: Were there any software upgrades during the same time as 1? 3rd: What has changed (environment, new worker, etc.) in that time period? 4th: Are any other machines having similar problems. 5th: Any history of this in the past? 6th: Now I would start the initial checks.

ManagedPrintServices.ca : Ensure all cables, power sources, and connections are secure. A loose or faulty connection can often be the root cause of hardware issues.

Estoy de acuerdo, como todo equipo electrónico se debe empezar revisando voltajes y verificar que el equipo no tenga defectos físicos, algunas veces al desconectar el dispositivo de la energia electrica (10 minutos) este se descarga de estática por lo que algunas veces esta puede ser la solución.

To troubleshoot a persistent hardware problem, I first identify the symptoms and isolate the issue by testing different components. I check for obvious causes, such as loose connections or faulty power supplies, and consult error logs or diagnostic tools. If the issue persists, I systematically eliminate possible causes by swapping out or testing individual hardware components. I research known issues for the hardware in question and consult manufacturer documentation or support if needed. If all else fails, I consider a repair or replacement based on the cost and impact of the issue.

The single most important initial check if assisting an end-user, especially one without advanced technical knowledge, is to verify the issue. Observe the issue firsthand if possible, otherwise gather as much relevant data as possible. Often users may describe a problem one way, but it ends up being a completely different issue than described as they do not possess the correct expertise to give a detailed initial description.

The first thing I want to know is what is the symptom that is being presented. “Persistent hardware problem” does not give me enough information to even begin solving the problem. Does the computer power on? Is the monitor not showing all colors? Does the computer shut down unexpectedly? Are some of the characters on the keyboard not working? There is not enough information here to even begin troubleshooting the problem.

Who is saying that there is a "persistent problem" is it the client? Have I seen this client and hardware before or is this the first time and THEY are saying this? It could just be human error and people have been giving them wrong information the whole time. I'm sure everyone has come across the "Well my cousin said.." or "I read on the internet that ..." So the first thing would be to ask more questions about this "persistent problem." Find out about the hardware's environment. The "persistent problem" could be caused by where the hardware is kept.

Principalmente cuando el equipo con sistema operativo Windows nos de una pantalla azul y se reinicie el equipo es un problema de controladores o drivers, se recomienda tener el equipo con actualizaciones al día y reiniciar al menos una vez a la semana ya que en este proceso termina de instalar actualizaciones o drivers, es indicado realizar al menos un punto de restauración mensual en el caso de ser un equipo con funciones delicadas, cuando el equipo presenta muchos problemas lo indicado es restaurar a un punto de restauración anterior tomando en cuenta el respaldo de información.

Often with business-grade machines (Dell, HP, Lenovo, and others) there will be a vendor supplied program which assists in updating drivers and firmware. Checking this program for updates (for example, Dell Command Update) can resolve many driver related problems and ensure you get the correct drivers installed.

Due to the amount of RAM that is standard in computers these days (typically no less than 16GB, often times up to 32 or 64GB) it's important to note these memory tests can take several hours to run, especially if they are running multiple passes for thoroughness. It's critical to be aware of this as starting a RAM test can take a user out of productive work for an extended period of time.

Una manera de mantener estable la temperatura es realizar un mantenimiento preventivo al menos una vez al año para evitar acumulación de polvo, este puede ser la causa de problemas en ventiladores y partes de la placa electrónica, si el equipo se reinicia es recomendable revisar las configuraciones de la BIOS y realizar un monitoreo de temperatura para descartar calentamiento en el procesador en el caso de detectar sobrecalentamiento cambiar la pasta térmica y verificar el estado de los ventiladores.

There are purpose-built programs intended for stress testing systems, but in a pinch you can also launch Google Chrome playing 4K video on YouTube or another site and open 50, 100, or more tabs to stress the CPU, RAM, and network adapter.