- Jun 15, 2013
- 33
- 0
- 10,540
Guys, my problem is the same as in THIS LINK.
I have done every thing, including reinstall my OS. I'm running Windows 8 Pro x64. The only recent hardware change is that I have hooked up a GTX 650( a new one).Even the Sevice Host: Local etc.. are consuming a lot of RAM.
I tried going to the file location of that TiWorker. It is
(C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16384_none_622908ad510eb05b)
It has an AMDx64 on the name of the folder. But I'm running on an Intel CPU.Don't know whether this will help, but my OS is in a SSD. None of my components are from AMD. Will post full details of my system and etc.. tommrow morning.(I'm in India).
THANKS IN ADVANCE!
UPDATE 1- I found that my new 1 TB HDD (bought yesterday) was hooked up. I already had a problem with it. It was detected in the bios but not in the OS and not even in the Disk Management. Well that's a different issue, and I will create some other thread or find a similar one.Now that I have disconnected it, the TiWorker's resource usage has gone down to normal (~0%). But still the Service Host : Local Service is consuming up a lot of RAM (sometimes around 500MB, that's halg a gig of RAM).
My Current Idle Resource values - CPU 1%, Memory 70%, Disk 1%.
I have done every thing, including reinstall my OS. I'm running Windows 8 Pro x64. The only recent hardware change is that I have hooked up a GTX 650( a new one).Even the Sevice Host: Local etc.. are consuming a lot of RAM.
I tried going to the file location of that TiWorker. It is
(C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16384_none_622908ad510eb05b)
It has an AMDx64 on the name of the folder. But I'm running on an Intel CPU.Don't know whether this will help, but my OS is in a SSD. None of my components are from AMD. Will post full details of my system and etc.. tommrow morning.(I'm in India).
THANKS IN ADVANCE!
UPDATE 1- I found that my new 1 TB HDD (bought yesterday) was hooked up. I already had a problem with it. It was detected in the bios but not in the OS and not even in the Disk Management. Well that's a different issue, and I will create some other thread or find a similar one.Now that I have disconnected it, the TiWorker's resource usage has gone down to normal (~0%). But still the Service Host : Local Service is consuming up a lot of RAM (sometimes around 500MB, that's halg a gig of RAM).
My Current Idle Resource values - CPU 1%, Memory 70%, Disk 1%.
Facebook
Twitter
Instagram