Repara tus cosas Comunidad Tienda

iMac Intel 27 "EMC 2309 (Finales de 2009, Core 2 Duo 3.06 o 3.33 GHz) ID iMac10,1, EMC 2374 (Finales de 2009, Core i5 2.66 GHz o Core i7 2.8 GHz) ID iMac11,1

Preguntas 467 Ver todo

Opciones

Can start in Safe Boot only

iMac Intel 27" Late 2009

Hello there,

My iMac is having serious freezing issues.

When I was watching a YouTube video, my iMac completely froze. I could only move the cursor. I had to shut it down using the power button. It froze a few more times before it started freezing when starting. It would freeze at the Apple logo and the progress bar.

I tried resetting the NVRAM. Started in Safe Boot to close all the programs that hadn't closed properly.

Next I reinstalled macOS Sierra from recovery. That didn't work.

Then I took it to the apple Genius Bar where they did some heath checks and it passed all of them. Next they reinstalled a fresh copy of macOS directly from their servers. It started up fine. I set up an account whilst there and I brought it home.

I tried customizing my Mac and it started freezing again.

Before taking it to Genius Bar, I even swapped the rams to see if they corrupt. But they weren't. I still had the same problem with the other rams.

I don't know what is wrong with this machine. 2.5 years ago I also had the logic board relaxed through Apple.

I can start the Mac in Safe Boot only.

Please help!

Cheers!

Abhishek

Contesta esta pregunta Yo también tengo este problema

Es esta una buena pregunta?

Sí No
Puntuación 0
1 comentario

What virus protection program are you using? How many programs of the (Clean my Mac, MacKeeper, Fix my Mac) type have you downloaded and installed?

- de

Agregar un comentario

1 Respuesta

Filtrar por:
Mas Útiles Más Reciente Más antiguo
Respuesta Más Útil

Opciones

When you reinstalled Sierra from the recovery partition, I'm betting that you did NOT do a clean install but instead just replaced the in-place operating system. That would be why your installation failed but Apple's succeeded.

The key -- obviously, I think -- is the "customizing" you're doing to your Mac. Something that you're doing or installing is creating an OS-level problem.

Clean-reinstall the OS and use it for a day or two like that. Don't add any software or anything like that. If it's still working, then add ONE thing and use it for a day or two. Repeat until your computer fails. The last thing you installed is the culprit.

Fue útil esta respuesta?

Sí No
Puntuación 1

3 comentarios:

I agree with Steve. It ran fine until you started customizing. Just exact what did you do to customize it?

- de

By customizing I mean adjusting the size of the dock. Enabling right click on the mouse. Increasing the track speed of the mouse. Adding sound to the menu bar. Changing the time to 24 hour format. Just basic things.

If I were to install any apps they would be chrome, VPN, daisy disk, etc. nothing very powerful.

Apple did a clean reinstall of the OS at the store from their servers. I think it's the ram slot or the logic board that is failing. When the computer freezes, the cursor still moves and the computer goes to sleep and all. I can even wake it up by hitting a key on the keyboard or by clicking the mouse.

Don't know what the issue is. This is really strange.

- de

If a clean/untouched OS is able to run without crashing, it's not the logic board.

It MIGHT be memory-related. If your memory module has a defect in an area of high memory, it wouldn't affect the performance of the computer until/unless the OS went to access that memory. If it did so by putting a critical bit of data in that bad spot, it could crash the system. With a clean OS install you may not be "touching" that bad spot, but once you start using the system the OS's memory footprint would expand a bit and perhaps touch that bad spot.

If you have two memory modules installed, remove one and try the system. If the problem persists, remove the second one and put the first one in the slot where the second one was and try the system again. If the problem STILL persists, try another memory module. If the problem goes away during any of the swaps, the last module you removed is the culprit.

- de

Agregar un comentario

Añadir tu respuesta

Abhishek estará eternamente agradecido.
Ver Estadísticas:

Ultimas 24 horas: 0

Ultimos 7 días: 0

Ultimos 30 días: 0

Todo El Tiempo: 70