XP is being gay on my old computer. It will start up, and go to the desktop. As soon as I click a program to open it, or just a folder, it freezes. Everything freezes, won't even open task manager. Tried system restore, freezes during that, but everything works in safe mode. Im on it now, but in safe mode.
XP locks up once started
Collapse
X
-
Tags: None
-
Re: XP locks up once started
Did you change, update or install something in last week? If so, try uninstalling it.
Next move is disabling most programs loaded at boot and check for malware too: post the log generated by Hijackthis and try to clean it ith Spybot S&D.
ZandraxHave an happy life. -
Re: XP locks up once started
I got it fixed, finally got it to do a system restore. I think it didn't like the AMD power watch thing.
Also ran a full maleware scan with malwarebytes fully updates as soon as I got it running (nothing), already have malwarebytes startup lite too, only have my sound card software and nvidia thing enable on startup.Comment
-
Re: XP locks up once started
Luckily you restored a previous restore point: loaded programs are not only the one with a tray bar icon, drivers and services are loaded too on normal boot and not loaded on safe mode.
The culprit is AMD Power Monitor? Try RMClock instead: it's a more complete monitor and can change settings on some cpus (vcore and energy saving C-States on most, multiplier on mobile and recent desktop cpus). Since a too low voltage or a bad setting can freeze the machine, I suggest do not loading RMClock at boot unless you double checked all settings under load with Prime95.
ZandraxHave an happy life.Comment
Related Topics
Collapse
-
by Flasman90I have a 2020 Macbook Pro A2289 and after many attempts managed to get it into DFU mode, using my older 2017 A1706 Macbook Pro (Running Ventura 13.7.8). However, when attempting 'Restore', it fails at step 4 of 4, showing the following error:
- "The operation couldn’t be completed. (AMRestoreErrorDomain error -1 - Failed to handle message type StatusMsg (Generic error)) [AMRestoreErrorDomain – 0xA (10)]
- "The system cannot be restored on this device. Failed to create new state machine for restore [com.apple.MobileDevice.MobileRestore - 0xFB1 (4017)]
...08-30-2025, 10:27 AM -
by grosseaderHello everyone, i got this mobo for long time, now i decided to rearrange some hardware and build a office pc, but 1 week so far, this motherboard drives me crazy.
What is the issue:
PC freezes randomly. While loading win, while installing win, while in windows , and just once did it while in bios.
Hardware:
MSI B450 Gaming Plus Max , MSI A320m A-pro
BIOS : 7B86vHG - latest
CPU: Ryzen 3 1200, 3200G , Ryzen 5 3500x, Ryzen 5 5500
GPU: Vega 7 in 3200g and MSI 1060 6GB
RAM: 2x8 ADATA spectrix 3000 , 2x8 SiliconePower 3200
...01-30-2023, 03:24 PM -
by iMuhtasebA2338 - Pristine condition.. I took out of the board and inspected it.. nothing.. as if the computer is barely used even.
Anyway, customer said they tried erasing/formatting it and it got stuck on Apple logo preventing to go further.. I asked them why they tried to erase it from the first place? They said it turned off randomly once.. then they erased it and it worked out for a few days then it shut off again..
I put the computer in DFU; I downloaded the latest Ventura IPSW and restored it.. during the "Installing.." it restarts then it shows the exclamation...09-11-2023, 08:43 AM -
by lab10.haifaGood day, friends. Got this problem with M1 macbook - it starts, chimes, tries to boot and stuck with a message "support.apple.com/mac/restore"
It works with DFU mode, but it's cannot be restored. With "revive" function - same problem. Internal restore mode doesn't work, as well as Internet Recovery.
There is no damage on the motherboard. No short circuits.
Could it be a NAND problem? (but usually, if NAND is dead - mac simply wouldn't turn on)
Thanks....10-08-2025, 02:55 AM -
by yheriatovychHi. I need some help troubleshooting the issue (which is a bit odd to my limited experience) with the A2338 Macbook.
Initial symptoms:
One day the laptop refused to wake up (as it seemed at first), spinning the fan on full blast, with no picture on the screen.
Force rebooting didn't help. To check if it boots at all I connected the external display and surprisingly it booted to the system, and I was able to log in to the system.
However, I noticed that it was in some weird state:- The fan was still blasting at full speed. It's blasting even when the system
- Loading...
- No more items.
Comment