Overclock.net › Forums › AMD › AMD CPUs › "Dead" core in task manager
New Posts  All Forums:Forum Nav:

"Dead" core in task manager - Page 2

post #11 of 41
Check in MS config (type msconfig, boot tab, advanced options) and make sure the core count on boot didn't get set to something, then go into BIOS and make sure that you didn't activate ACC and set it to 3 cores or simply turned off one of the cores in another menu. Also make sure you don't have a core unlocker turned on - it would actually deactivate a core on your CPU. If you haven't played around in BIOS and this randomly happened, first try rebooting to see if it comes up right, then try loading Optimized Defaults. Finally clearing the BIOS as a last resort.
Edited by ALUCARDVPR - 8/19/11 at 1:32pm
post #12 of 41
Thread Starter 
Quote:
Originally Posted by ALUCARDVPR View Post
Check in MS config (type msconfig, boot tab, advanced options) and make sure the core count on boot didn't get set to something, then go into BIOS and make sure that you didn't activate ACC and set it to 3 cores or something. Also make sure you don't have a core unlocker turned on - it would actually deactivate a core on your CPU. If you haven't played around in BIOS and this randomly happened, first try rebooting to see if it comes up right, then try clearing the BIOS as a last resort.
I'm about to reboot, checked msconfig, numproc is set to 4. I haven't touched the ACC or Core Unlocker functions at all, because they stop me getting core temp readings from any program. Guess I'll reboot now.
post #13 of 41
Run Command Prompt with Admin, and type in "sfc /scannow"

It's worth to explore all options, even though SFC will scan through all your Windows files for corrupted garbage and repair it all, it's at least worth a try
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
Ryzen
(8 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 Gigabyte AX370 Gaming K5 Nvidia GTX 770 G.Skill Trident Z 16GB 3000MHz 
Hard DriveCoolingOSPower
Samsung Evo 960 M.2 Stock AMD Windows 10 Pro Superflower 650W 
  hide details  
Reply
post #14 of 41
Try clearing CMOS or reseating the CPU
Needs More Red
(20 items)
 
  
CPUMotherboardGraphicsRAM
i7 3770k Asrock Z77 Extreme4 Gigabyte Windforce 290X OC 4GB Samsung DDR3-1600 Low Voltage 
RAMHard DriveHard DriveHard Drive
4GB Samsung DDR3-1600 Low Voltage 1TB Samsung F3 2TB Samsung F4 OCZ Agility 3 256GB 
Optical DriveOptical DriveCoolingOS
Samsung 24x DVD+-RW Lite-On 12x Bluray Burner Coolermaster Hyper 212 EVO Windows 8.1 Pro x64 
MonitorPowerCaseMouse
Yamakasi Catleap Q270 Antec TruePower 850W Thermaltake V4 Black Logitech G400s 
Mouse PadAudioAudio
Steelseries QCK Ultrasone Pro 900 Fiio E17 
  hide details  
Reply
Needs More Red
(20 items)
 
  
CPUMotherboardGraphicsRAM
i7 3770k Asrock Z77 Extreme4 Gigabyte Windforce 290X OC 4GB Samsung DDR3-1600 Low Voltage 
RAMHard DriveHard DriveHard Drive
4GB Samsung DDR3-1600 Low Voltage 1TB Samsung F3 2TB Samsung F4 OCZ Agility 3 256GB 
Optical DriveOptical DriveCoolingOS
Samsung 24x DVD+-RW Lite-On 12x Bluray Burner Coolermaster Hyper 212 EVO Windows 8.1 Pro x64 
MonitorPowerCaseMouse
Yamakasi Catleap Q270 Antec TruePower 850W Thermaltake V4 Black Logitech G400s 
Mouse PadAudioAudio
Steelseries QCK Ultrasone Pro 900 Fiio E17 
  hide details  
Reply
post #15 of 41
Quote:
Originally Posted by linkin93 View Post
I'm about to reboot, checked msconfig, numproc is set to 4. I haven't touched the ACC or Core Unlocker functions at all, because they stop me getting core temp readings from any program. Guess I'll reboot now.
I'd still poke my head in BIOS just to be be absolutely certain.
post #16 of 41
Thread Starter 
Working fine after a reboot:



I wonder what caused it in the first place?
post #17 of 41
Quote:
Originally Posted by linkin93 View Post
Working fine after a reboot:



I wonder what caused it in the first place?
Glad you got it working. For now I wouldn't worry about it, but if this happens again I would just consider reinstalling the driver's and/or reinstalling Windows.
post #18 of 41
Thread Starter 
Reinstalling windows is probably overdue, though I dread setting it up again. Moving my profile is easy but all the services and crap that need to be disabled or cut out just jaratees me off. I'm a sucker for disabling stuff I never use.
post #19 of 41
Quote:
Originally Posted by linkin93 View Post
Working fine after a reboot:



I wonder what caused it in the first place?
You're on Windows, my friend. Glitches are bound to happen one way or another, which in most cases are almost always solved with a simple restart.
post #20 of 41
Thread Starter 
Okay so it seems it was just a bug with windows. I just hope it doesn't happen again.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › "Dead" core in task manager