Windows 8 Problems

Help. I recently upgraded 3 of my computers to Windows 8. Two worked beautifully and I personally like the operating system. The third, not so good. I have attached a Belarc file describing my machine. A HP 8330f. I have also attached a copy of the Event viewer, showing over 21,000 warnings, criticals, and informtions. I have no idea what is going on. I use the free version of Avast for protection and it has served me well for many years. No evidence of a virus or other malware. I have copied below one of the Error messages. However, no two are alike. They are all over the place. I used CCleaner to analyze and remove all issues, including registry issues. No help. I tried disabling everything in the start menu that was not Microsoft, Avast, APC power software, or HP related. It made no difference. The system is sluggish and slow. My other two computers, although lesser models, are several times faster loading up. I could use some direction on where to start.

Thanks!
David

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

Attachments did not come through on first post. I tried attaching them again with no luck, so I printed out the Belarc base information here. Sorry it is so jumbled. Every time I try to attach a file, MajorGeeks gives me an invalidity screen and kicks me out.

Operating System System Model Windows 8.1 Professional (x64) (build 9600) Install Language: English (United States) System Locale: English (United States) Installed: 10/26/2013 9:57:36 AM Boot Mode: BIOS (Secure Boot not supported) HP-Pavilion GX612AAR-ABA m8330f System Serial Number: MX280506B1 Enclosure Type: Desktop Processor a Main Circuit Board b 2.20 gigahertz AMD Phenom 9500 Quad-Core 128 kilobyte primary memory cache 512 kilobyte secondary memory cache 64-bit ready Multi-core (4 total) Not hyper-threaded Board: ASUSTek Computer INC. NARRA3 3.02 Serial Number: MS1C81R62600713 Bus Clock: 200 megahertz BIOS: Phoenix Technologies, LTD 5.11 04/15/2008 Drives Memory Modules c,d 640.14 Gigabytes Usable Hard Drive Capacity 503.37 Gigabytes Hard Drive Free Space
TSSTcorp CDDVDW TS-H653N SCSI CdRom Device [Optical drive]
Generic- Compact Flash USB Device [Hard drive] -- drive 2 Generic- MS/MS-Pro USB Device [Hard drive] -- drive 5 Generic- SD/MMC USB Device [Hard drive] -- drive 4 Generic- SM/xD-Picture USB Device [Hard drive] -- drive 3 WDC WD3200AAJS-65VWA0 [Hard drive] (320.07 GB) -- drive 0, s/n WD-WMARW0688637, rev 12.01B02, SMART Status: Healthy WDC WD3200AAJS-65VWA0 [Hard drive] (320.07 GB) -- drive 1, s/n WD-WMARW0758053, rev 12.01B02, SMART Status: Healthy
6144 Megabytes Usable Installed Memory
Slot 'A0' has 2048 MB Slot 'A1' has 2048 MB Slot 'A2' has 1024 MB Slot 'A3' has 1024 MB
Local Drive Volumes c: (NTFS on drive 0) * 309.79 GB 182.22 GB free d: (NTFS on drive 1) 320.07 GB 319.81 GB free e: (NTFS on drive 0) 10.28 GB 1.34 GB free
* Operating System is installed on c:
Network Drives

 

I am going to answer my own post. After many hours of reading online forums, I opened up my device driver and noted that it flashed every two or three seconds. I would get the bsod several times a day with notation "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" with some numbers following it. Realized I had some hardware driver that was not compatible with Windows 8, probably due to a Windows optional update, since the system worked fine starting out. I disabled the drivers for one component after the other and my Linksys USB WiFi antenna turned out to be the culprit. removed the driver software and rebooted, it went online to find new drivers, and - Voila! - everything back to normal. Over 21,000 errors and warnings in the Event Viewer in just a few days and Windows Troubleshooter found nothing wrong.