Bloqueo Constante de PC

Archivado
Muy buenas chicos pues vereis tengo un buen problema y es que ultimamente se me bloquea el pc todo el rato, por ejemplo cuando juego a battlefield 3 bloqueo, cuando juego al fifa world bloqueo, cuando juego minecraft bloqueo, cuando renderizo un video bloqueo, incluso ayer tras reiniciar llame a un amigo por skype y bloqueo.

Cuando se bloquea y tengo que reiniciar me sale esta pantalla Es una imagen de google
http://www.sysadmintutorials.com/images ... estore.jpg

Y Ahora se me ha bloqueado me acabo levantar lo encendi puse un video a renderizar y se me bloque a me sale la imagen de arriba y luego al reiniciarlo me sale esto
http://www.subirimagenes.net/i/140606105228476698.png

Voy a intentar descartar que sea sobrecalentamiento ya que si lo acabo de encender no creo que sea eso.

MI PC ES:

Procesador AM8-6600K:
La grafica la incorpora el procesador ese
RAM: 6GB
Uso windows 7

Si alguien me puede ayudar :(, últimamente me pasa todo el rato...
Intenta poner el resto de información de la ventana (2o pantallazo). El 124 es un error de hardware del que no se ha recuperado Windows. Hay una miniguía sobre pasos a seguir, qué tal vas de inglés?

Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSOD here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.


Si sigue igual tras limpiar y actualizar tocará abrir y tratar de descartar componentes, testear memorias y esperar que no sea cosa de la cpu, placa o fuente, que son cosas más complicadas de probar.
remyeol escribió:Intenta poner el resto de información de la ventana (2o pantallazo). El 124 es un error de hardware del que no se ha recuperado Windows. Hay una miniguía sobre pasos a seguir, qué tal vas de inglés?

Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSOD here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.


Si sigue igual tras limpiar y actualizar tocará abrir y tratar de descartar componentes, testear memorias y esperar que no sea cosa de la cpu, placa o fuente, que son cosas más complicadas de probar.



Buah mi ingles es bastante malo xD, a ver como te pongo el resto de la info del segundo pantallazo T.T que me sale una vez cada 4 o 5 veces que se reinicia T.T.
Bueno, te hago resumen. No creo que el resto de la información del error sirva porque es algo muy genérico pero no está de más poner todo.

1) Asegúrate de no tener ningún componente con overclock.

2) Asegúrate de que el ordenador esta bien refrigerado.

3) Actualizar drivers de todo.

4) Actualizar BIOS de la placa.

5) Falso positivo por bugs en Windows, no hay ninguno conocido. (que va a decir un mvp de microsoft...)

6) Testeo/estrés de componentes (ram, memtest86, hdd, chkdsk /R en una ventana de comandos)

7) Reinstalación de Windows sin añadir nada (actualizaciones, programas, periféricos no indispensables). Puede ser peligroso andar por Internet con el PC sin actualizar así que cuidado con las páginas que visitas. Aquí yo añado algo, puedes probar un liveCD de linux y trastear a ver si se bloquea, descartarías problema del sistema operativo.

8) Limpiar bien el pc (por dentro XD), polvo y pelusa de ventiladores, ranuras (las ocupadas tb), entradas/salidas de aire.

8.5) Suerte

9) Si todo esto falla, a probar componente por componente.

10) Más suerte XD
remyeol escribió:Bueno, te hago resumen. No creo que el resto de la información del error sirva porque es algo muy genérico pero no está de más poner todo.

1) Asegúrate de no tener ningún componente con overclock.

2) Asegúrate de que el ordenador esta bien refrigerado.

3) Actualizar drivers de todo.

4) Actualizar BIOS de la placa.

5) Falso positivo por bugs en Windows, no hay ninguno conocido. (que va a decir un mvp de microsoft...)

6) Testeo/estrés de componentes (ram, memtest86, hdd, chkdsk /R en una ventana de comandos)

7) Reinstalación de Windows sin añadir nada (actualizaciones, programas, periféricos no indispensables). Puede ser peligroso andar por Internet con el PC sin actualizar así que cuidado con las páginas que visitas. Aquí yo añado algo, puedes probar un liveCD de linux y trastear a ver si se bloquea, descartarías problema del sistema operativo.

8) Limpiar bien el pc (por dentro XD), polvo y pelusa de ventiladores, ranuras (las ocupadas tb), entradas/salidas de aire.

8.5) Suerte

9) Si todo esto falla, a probar componente por componente.

10) Más suerte XD


Wuoooooooo muchas gracias tio termino de verme la temporada de juego de tronos y empiezo con todo poco a poco muchas gracias en serio por la ayuda te amo, NO HOMO, jaja a ver si tengo suerte ! ya contare que tal
Hola.
Se reinicia después de dar pantallazo azul no ?
Puede ser de la fuente que esté apunto de morir.Si algún amigo puede dejarte una para probar y descartar.
También del disco duro que tenga las conexiónes flojas,placa madre con condensadores defectuosos o también de drivers, aunque es mas raro.
Si puedes abre la caja y mira a ver como está el disipador/ventilador de la cpu.

Un saludo.
5 respuestas
Archivado
Volver a Hardware