Windows 7 Constantly Freezing - Lots of Errors in Event Viewer

[stephm]

My Acer Aspire 5253 running on Windows Home 64bit keeps freezing up every 10 seconds. It's been happening for three days. I found a lot of errors in the Event Viewer but I'm not sure what to do with them. They are listed below with a row of pound signs between errors in chronological order, with the most recent errors on the bottom. Can anyone advise?

Faulting application name: svchost.exe_EapHost, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: eapsvc.dll, version: 6.1.7600.16385, time stamp: 0x4a5bded5
Exception code: 0xc0000006
Fault offset: 0x0000000000011100
Faulting process id: 0x1ac
Faulting application start time: 0x01ce816e397b561e
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\eapsvc.dll
Report Id: c67e7693-ed62-11e2-9f5b-1c7508ab500d

#####################################

Windows cannot access the file C:\Windows\System32\eapsvc.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\eapsvc.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#############################3

Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: DeviceIoControl(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2 - 00000000000000FC,0x00560038,000000000027FFD0,0,000000000015E960,4096,[0]).

Operation:
Processing PostFinalCommitSnapshots

Context:
Execution Context: System Provider

##############################

Faulting application name: wmiprvse.exe, version: 6.1.7601.17514, time stamp: 0x4ce79d42
Faulting module name: framedynos.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c64e
Exception code: 0xc0000006
Fault offset: 0x000000000000f126
Faulting process id: 0xa74
Faulting application start time: 0x01ce8171dbc131bd
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\framedynos.dll
Report Id: f2ddbc46-ed65-11e2-88c9-1c7508ab500d

####################################

Faulting application name: SearchIndexer.exe, version: 7.0.7601.17610, time stamp: 0x4dc0d019
Faulting module name: MSSRCH.DLL, version: 7.0.7601.17610, time stamp: 0x4dc0e0c8
Exception code: 0xc0000006
Fault offset: 0x000000000008fea7
Faulting process id: 0xd3c
Faulting application start time: 0x01ce8171de45f37b
Faulting application path: C:\Windows\system32\SearchIndexer.exe
Faulting module path: C:\Windows\system32\MSSRCH.DLL
Report Id: f32aa4e6-ed65-11e2-88c9-1c7508ab500d

################################33

Windows cannot access the file C:\Windows\System32\mssrch.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Windows Search Indexer because of this error.

Program: Microsoft Windows Search Indexer
File: C:\Windows\System32\mssrch.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#####################################

Windows cannot access the file C:\Windows\System32\framedynos.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program WMI Provider Host because of this error.

Program: WMI Provider Host
File: C:\Windows\System32\framedynos.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#########################################

Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: sysmain.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c9db
Exception code: 0xc0000006
Fault offset: 0x00000000000a3020
Faulting process id: 0x3f4
Faulting application start time: 0x01ce8171ab3b0ef2
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: 7b119786-ee30-11e2-88c9-1c7508ab500d

##################################

Windows cannot access the file C:\Windows\System32\sysmain.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\sysmain.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#############################

The program Explorer.EXE version 6.1.7601.17567 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: b1c
Start Time: 01ce8171d880101d
Termination Time: 0
Application Path: C:\Windows\Explorer.EXE
Report Id:


#################################

Faulting application name: PmmUpdate.exe, version: 1.1.36.0, time stamp: 0x4c932097
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96f
Exception code: 0xc0000005
Fault offset: 0x0013d169
Faulting process id: 0xa2c
Faulting application start time: 0x01ce8171db3be4ad
Faulting application path: C:\Program Files (x86)\EgisTec IPS\PmmUpdate.exe
Faulting module path: C:\Windows\syswow64\ole32.dll
Report Id: b6a81915-eefb-11e2-88c9-1c7508ab500d

############################

The search service has detected corrupted data files in the index {id=3800}. The service will attempt to automatically correct this problem by rebuilding the index.

Context: Windows Application, SystemIndex Catalog

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)


###############################3

The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Context: Windows Application, SystemIndex Catalog

Details:
The content index catalog is corrupt. (HRESULT : 0xc0041801) (0xc0041801)


############################################################

Faulting application name: services.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc10e
Faulting module name: WTSAPI32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be09c
Exception code: 0xc0000006
Fault offset: 0x0000000000001995
Faulting process id: 0x1e8
Faulting application start time: 0x01ce83193dc675be
Faulting application path: C:\Windows\system32\services.exe
Faulting module path: C:\Windows\system32\WTSAPI32.dll
Report Id: 91f4c7e5-ef0e-11e2-bdeb-1c7508ab500d

##########################3

Faulting application name: SynTPHelper.exe, version: 15.1.6.0, time stamp: 0x4c524f47
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000006
Fault offset: 0x0000000000027506
Faulting process id: 0xdec
Faulting application start time: 0x01ce8319567e47db
Faulting application path: C:\Program Files\Synaptics\SynTP\SynTPHelper.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 92187d0a-ef0e-11e2-bdeb-1c7508ab500d

################################3

Windows cannot access the file C:\Windows\System32\advapi32.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Synaptics Pointing Device Helper because of this error.

Program: Synaptics Pointing Device Helper
File: C:\Windows\System32\advapi32.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

################################

Windows cannot access the file C:\Windows\System32\wtsapi32.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Services and Controller app because of this error.

Program: Services and Controller app
File: C:\Windows\System32\wtsapi32.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#########################

Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4
Faulting module name: UxTheme.dll, version: 6.1.7600.16385, time stamp: 0x4a5be093
Exception code: 0xc0000006
Fault offset: 0x000000000001f101
Faulting process id: 0x81c
Faulting application start time: 0x01ce831951f49e3b
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\UxTheme.dll
Report Id: 9280b641-ef0e-11e2-bdeb-1c7508ab500d

########################

Windows cannot access the file C:\Windows\System32\uxtheme.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Windows Explorer because of this error.

Program: Windows Explorer
File: C:\Windows\System32\uxtheme.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#############################

Faulting application name: SynTPHelper.exe, version: 15.1.6.0, time stamp: 0x4c524f47
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc000041d
Fault offset: 0x0000000000027506
Faulting process id: 0xdec
Faulting application start time: 0x01ce8319567e47db
Faulting application path: C:\Program Files\Synaptics\SynTP\SynTPHelper.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9a4c37c9-ef0e-11e2-bdeb-1c7508ab500d

#############################

The description for Event ID 1 from source Chrome cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Chrome has encountered a fatal error.
ver=28.0.1500.72;lang=;id=;is_machine=0;upload=1;minidump=C:\Users\April Wolcott\AppData\Local\Google\CrashReports\6b9351d9-339d-4cb8-afb2-9bc69b47265b.dmp

#############################

Faulting application name: NisSrv.exe, version: 4.2.223.0, time stamp: 0x51023aa3
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000006
Fault offset: 0x0000000000052fd5
Faulting process id: 0x96c
Faulting application start time: 0x01ce831badd8be7b
Faulting application path: c:\Program Files\Microsoft Security Client\NisSrv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 76bbf832-efc7-11e2-b120-929ffa5fdaf2

###########################

Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Microsoft Network Realtime Inspection Service because of this error.

Program: Microsoft Network Realtime Inspection Service
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 0



###ERRORS CONTINUED IN COMMENTS###

 

[stephm]

########################

Faulting application name: WLIDSvcM.exe, version: 7.250.4225.0, time stamp: 0x4c99277f
Faulting module name: WLIDSvcM.exe, version: 7.250.4225.0, time stamp: 0x4c99277f
Exception code: 0xc0000006
Fault offset: 0x000000000000b0fc
Faulting process id: 0x7e0
Faulting application start time: 0x01ce831babf0c463
Faulting application path: C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSvcM.exe
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSvcM.exe
Report Id: 582265a9-efc8-11e2-b120-929ffa5fdaf2

############################3

Windows cannot access the file C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVCM.EXE for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program MicrosoftÆ Windows Live ID Service Monitor because of this error.

Program: MicrosoftÆ Windows Live ID Service Monitor
File: C:\Program Files\Common Files\Microsoft Shared\Windows Live\WLIDSVCM.EXE

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

#########################3

Faulting application name: svchost.exe_wuauserv, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
Faulting module name: ESENT.dll, version: 6.1.7601.17577, time stamp: 0x4d79bfba
Exception code: 0xc0000006
Fault offset: 0x00000000000cc510
Faulting process id: 0x154
Faulting application start time: 0x01ce83d8aee82a93
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\ESENT.dll
Report Id: 3ff83e66-efcd-11e2-8784-1c7508ab500d

##########################

Windows cannot access the file C:\Windows\System32\esent.dll for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Host Process for Windows Services because of this error.

Program: Host Process for Windows Services
File: C:\Windows\System32\esent.dll

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: C0000185
Disk type: 3

###################################

Failed to create restore point (Process = C:\Windows\system32\svchost.exe -k netsvcs; Description = Windows Update; Error = 0x81000101).

 

[MilesAhead]

eapsvc.dll as example... is the file actually there in System32 folder? If not you may have to do a repair install. Do you have a UPS on the system? If not it's easy to get corrupted system files. This particular dll is a system service. If a few of those won't load then your system won't run right.

 

[gregrocker]

The problem could be inferior Factory Preinstalled Win7 with all of the bloatware and duplicate utiltiies which have better versions built into Win7. These throttle Win7 from its native performance and can cause problems.

That's why most tech enthusiasts will not run such an install but instead Clean Reinstall - Factory OEM Windows 7. Everything is provided in the blue link tutorial.

At the minimum I'd Clean Up Factory Bloatware.

If this doesn't resolve performance problems, work through these Troubleshooting Steps for Windows 7.

 

[stephm]

What's the difference between that and this, because I'm halfway through this:

http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[gregrocker]

It's doing an in-place reinstall of the OS while keeping all of the programs, files and settings in place. This means it's parsing a huge corrupt load of Acer bloatware and useless duplicate utilities that interfere and conflict with Win7.

So while it may actually resolve your problem, you'll still have one of the worst possible installs of Win7 one can have, one which no tech enthusiasts would allow. Why not trade that for the best possible install of Win7 which you'd have if you stick with the tools and methods in Clean Reinstall - Factory OEM Windows 7

 

[stephm]

Ok, is this the same thing? How to Use Windows Boot, Repair, Rescue and Startup CDs and USB Flash Drives

 

[gregrocker]

Yes, it looks the same as the links in Step 1 of Clean Reinstall - Factory OEM Windows 7.

So create the bootable installer using the tool in Step 2 and proceed with the other steps.

To repeat, you will get and keep a perfect install to the exact extent you stick with only the tools and methods in the tutorial. So get it right this one time then save a Win7 backup image and you'll never have to do it again.

 

[stephm]

Ok this is going to delete all of my programs, correct? What do I do about getting Microsoft Office back? I'm not sure what my product ID is for that

 

[gregrocker]

Do you have an installation disk or download and Product Key from when you purchased MS office?

Did you install it separately or buy the one which comes preinstalled on the Acer?

It shows how in the steps to audit all of your software and any Product keys using Belarc Advisor

 

[stephm]

Ok I'm at the step where I need to " Delete all partitions not needed, repartition and format" and I am so confused. There are three partitions:

• Disk 0 Partition 1: PQ SERVICE, 15GB, OEM (Reserved)
• Disk 0 Partition 2: SYSTEM RESERVED E:, 100 MB, System
• Disk 0 Partition 3: Acer C:, 217.8 GB, Primary

What do you advise me to do?

 

[stephm]

Actually it wont let me delete any... and I can only install on C... So do that?

 

[gregrocker]

Use the Drive Options shown in Step 8 of Clean Install Windows 7.

   Tip

Drive options (advanced)

• If you have more than one partition for a disk # (hard drive) and want to get rid of them to make that disk # one partition drive again, then select a partition with that disk # and click on the Delete option for each partition with the same disk # until there is only one "unallocated space" with that disk # left as in the screenshot below.
• To shrink an existing partition to create another partition to install Windows 7 on instead, select the partition you want shrink and click on the Extend option. Type in how much in MB (1 GB = 1024 MB) that you want to shrink it by. Now select the new extended partition.

Highlight each partition by clicking on it, then select Delete for each, until you have only Unallocated space.

Then click New to create any new partitions you want, Format to install to the first partition (ignoring the small boot partition it creates in the first partition). As it says in the tutorial for that step, if you have no scheme you can just click Next and the installer will do this for you and commence install.

 

[stephm]

It had me delete ATI Catalyst when I was trying the repair install before I aborted that. Now even after clean install my screen resolution is wonky, like its wide screen and terrible looking. What can I do?

 

[gregrocker]

What display driver has Windows Update delivered after running all rounds of Important and Optional Updates to completion. First enable Option 3 in http://www.sevenforums.com/tutorials/2803-device-installation-settings.html. Keep going back to Check for Updates after requested reboots.

If this driver cannot give you a decent resolution in Control Panel>Display>Screen Res, then import the Display driver from the Acer Support Downloads webpage for your bit version.

Even if you installed the Catalyst Bloatware it should not be starting with WIndows if you've followed all of the steps in http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164