Windows Explorer has stopped working.

You may have corrupted files on your disk. Please try running the following.
First close ALL Applications as this routine will automatically restart your computer.
Click on START - RUN and copy / paste the following entry into the box and click OK



Post Event Logs:

• Please download VEW by Vino Rosso from here and save it to your desktop
  
• Double click it to start it Note: If running Windows Vista or Windows 7 you will need to right click the file and select Run as administrator and click Continue or Allow at the User Account Control Prompt.
  
• Click the check boxes next to Application and System located under Select log to query on the upper left
  
• Under Select type to list on the right click the boxes next to Error and Warning Note: If running Windows Vista or Windows 7 also click the box next to Critical (not XP).
  
• Under Number or date of events select Number of events and type 20 in the box next to 1 to 20 and click Run
  
• Once it finishes it will display a log file in notepad
  
• Please copy and paste its entire contents into your next reply
  

Once the program has completed, it says "Cannot find the C:\VEW.txt file. Do you want to create a new file?"

I must have a virus because every time I log on to the computer, norton and windows defender is saying they need updating but will not allow me to do so.

Hello.
Right click Vew.exe and select run as administrator, does it give you any log this time?

Yes, Sorry.

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 07/07/2010 14:13:25

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\dwmcore.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 Desktop Window Manager because of this error. Program: Desktop Window Manager File: C:\Windows\System32\dwmcore.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\localspl.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 Spooler SubSystem App because of this error. Program: Spooler SubSystem App File: C:\Windows\System32\localspl.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\diagperf.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\diagperf.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_DPS, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000006 Fault offset: 0x0000000000015a45 Faulting process id: 0x450 Faulting application start time: 0x01cb1d08c6de9bf4 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 69d7e927-88fc-11df-a860-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541 Faulting module name: d3d10_1core.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdeb6 Exception code: 0xc0000006 Fault offset: 0x00000000000308fa Faulting process id: 0x8cc Faulting application start time: 0x01cb1d08d7dfe4d1 Faulting application path: C:\Windows\system32\Dwm.exe Faulting module path: C:\Windows\system32\d3d10_1core.dll Report Id: 69d7c216-88fc-11df-a860-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 12:45:56
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: spoolsv.exe, version: 6.1.7600.16385, time stamp: 0x4a5bd3d1 Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000006 Fault offset: 0x00000000000351df Faulting process id: 0x430 Faulting application start time: 0x01cb1d08c6d777d3 Faulting application path: C:\Windows\System32\spoolsv.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 69d81037-88fc-11df-a860-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 02:02:39
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{237567A3-5589-4CA1-B68A-B533E9BFFE30}\mpengine.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:\ProgramData\Microsoft\Windows Defender\Definition Updates\{237567A3-5589-4CA1-B68A-B533E9BFFE30}\mpengine.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 02:02:39
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_WinDefend, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000006 Fault offset: 0x00000000000351df Faulting process id: 0x64c Faulting application start time: 0x01cb1ca2b4148782 Faulting application path: C:\Windows\System32\svchost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8d3e1faf-88a2-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 02:02:35
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\ntdll.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\ntdll.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 02:02:35
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\System32\shell32.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\shell32.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 02:02:35
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: explorer.exe, version: 6.1.7600.16450, time stamp: 0x4aebab8d Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000006 Fault offset: 0x00000000000351df Faulting process id: 0xd54 Faulting application start time: 0x01cb1ca44af24173 Faulting application path: C:\Windows\explorer.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8b217953-88a2-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 02:02:35
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: svchost.exe_DPS, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1 Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802 Exception code: 0xc0000006 Fault offset: 0x0000000000015a26 Faulting process id: 0x4e8 Faulting application start time: 0x01cb1ca2b2356717 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8b215243-88a2-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 02:02:33
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Users\Jake\AppData\Local\Google\Chrome\Application\5.0.375.99\chrome.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 Google Chrome because of this error. Program: Google Chrome File: C:\Users\Jake\AppData\Local\Google\Chrome\Application\5.0.375.99\chrome.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 02:02:33
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: chrome.exe, version: 0.0.0.0, time stamp: 0x4c2943a6 Faulting module name: chrome.dll, version: 5.0.375.99, time stamp: 0x4c294377 Exception code: 0xc0000006 Fault offset: 0x004f0458 Faulting process id: 0x9a0 Faulting application start time: 0x01cb1cab195576d1 Faulting application path: C:\Users\Jake\AppData\Local\Google\Chrome\Application\chrome.exe Faulting module path: C:\Users\Jake\AppData\Local\Google\Chrome\Application\5.0.375.99\chrome.dll Report Id: 8a1a65ba-88a2-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 00:46:47
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.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 Notepad because of this error. Program: Notepad File: C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.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: C0000010 Disk type: 3

Log: 'Application' Date/Time: 06/07/2010 00:46:47
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: notepad.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc60f Faulting module name: COMCTL32.dll, version: 6.10.7600.16385, time stamp: 0x4a5bd976 Exception code: 0xc0000006 Fault offset: 0x000c3a19 Faulting process id: 0xf2c Faulting application start time: 0x01cb1ca45336ec61 Faulting application path: C:\Windows\SysWOW64\notepad.exe Faulting module path: C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\COMCTL32.dll Report Id: f41aedd3-8897-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 00:43:47
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program explorer.exe version 6.1.7600.16450 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: c88 Start Time: 01cb1ca41e0162de Termination Time: 0 Application Path: C:\Windows\explorer.exe Report Id: 8356b361-8897-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 00:42:31
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program explorer.exe version 6.1.7600.16450 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: b60 Start Time: 01cb1ca39e1bf354 Termination Time: 0 Application Path: C:\Windows\explorer.exe Report Id: 56ad6628-8897-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 00:41:28
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: notepad.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc60f Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29c Exception code: 0xc0000005 Fault offset: 0x00084347 Faulting process id: 0xdd8 Faulting application start time: 0x01cb1ca3e6f341df Faulting application path: C:\Windows\SysWOW64\notepad.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 361fcae1-8897-11df-91e9-001f16caeab5

Log: 'Application' Date/Time: 06/07/2010 00:39:28
Type: Error Category: 100
Event: 1005 Source: Application Error
Windows cannot access the file C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.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 Notepad because of this error. Program: Notepad File: C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.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: C0000010 Disk type: 3

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/07/2010 13:09:33
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/07/2010 12:55:30
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/07/2010 12:42:41
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/07/2010 00:20:57
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/07/2010 00:18:22
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 06/07/2010 00:15:25
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/07/2010 23:59:12
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/07/2010 23:49:57
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/07/2010 23:43:24
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/07/2010 23:31:03
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/07/2010 12:26:05
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 04/07/2010 23:15:27
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 04/07/2010 21:54:23
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 04/07/2010 15:16:23
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 04/07/2010 13:57:42
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 04/07/2010 11:55:08
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 03/07/2010 17:22:05
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 03/07/2010 15:50:04
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 03/07/2010 12:50:29
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 02/07/2010 18:04:28
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The HomeGroup Provider service terminated with service-specific error %%-2146959355.

Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the netprofm service.

Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The DHCP Client service terminated with the following error: There are no more endpoints available from the endpoint mapper.

Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 4
Event: 1004 Source: Microsoft-Windows-Dhcp-Client
Error occurred in stopping the Dhcpv4 Client service. Error code is 0x6D9. ShutDown Flag value is 0

Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 4
Event: 1004 Source: Microsoft-Windows-DHCPv6-Client
Error occurred in stopping the Dhcpv6 client service. ErrorCode is 0x6D9.ShutDown Flag value is 0.

Log: 'System' Date/Time: 07/07/2010 13:13:53
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 07/07/2010 13:13:52
Type: Error Category: 0
Event: 7024 Source: Service Control Manager
The Windows Firewall service terminated with service-specific error The parameter is incorrect..

Log: 'System' Date/Time: 07/07/2010 13:13:19
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the EventSystem service.

Log: 'System' Date/Time: 07/07/2010 13:13:19
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1BE1F766-5536-11D1-B726-00C04FB926AF} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The TCP/IP NetBIOS Helper service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The HomeGroup Provider service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Event Log service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The DHCP Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Audio service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Peer Name Resolution Protocol service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Peer Networking Grouping service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:53
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Peer Networking Identity Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:52
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Windows Firewall service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:52
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Diagnostic Policy Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Log: 'System' Date/Time: 07/07/2010 13:11:52
Type: Error Category: 0
Event: 7031 Source: Service Control Manager
The Base Filtering Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.

Try this.

To get to Device Manager click Start>>Run type devmgmt.msc click OK Look down the list for Display Adapters
Click on the + sign to expand
Double click on your video card
Click on the Driver tab

Uninstall the driver

Restart the PC

No Improvement, it also seems as though i cannot update any software that I currently have on the computer, and Norton antivirus asks me to activate it everytime i turn the computer on.

bump

I aren't too sure what is causing it, while I work with the other techs, run these quick scans for me.

Click Start > In the little search box, type in cmd, then when it find the command prompt, right click it > Run as administrator.

When the command prompt opens, type in the following:

sfc /scannow

Hit enter, this will run the system file checker.

---

Then do the same again for this command:

chkdsk /f

Report back on any fixes.

Last edited by Belahzur on 11th July 2010, 8:55 pm; edited 1 time in total

Im not currently near the laptop, but whenever i go on it, every firewall i have is down, and when I turn them back on the computer crashes, could this be a virus?

Possibly.

Run ESET Online Scan
Please do an online scan with ESET Online Scanner. Please use Internet Explorer as it uses ActiveX.

• Check (tick) this box: YES, I accept the Terms of Use.
  
• Click on the Start button next to it.
  
• When prompted to run ActiveX. click Yes.
  
• You will be asked to install an ActiveX. Click Install.
  
• Once installed, the scanner will be initialized.
  
• After the scanner is initialized, click Start.
  
• Check (tick) Remove found threats box.
  
• Check (tick) Scan unwanted applications.
  
• Click on Scan.
  
• It will start scanning. Please be patient.
  
• Once the scan is done, the log will be saved here: C:\Program Files\esetonlinescanner\log.txt.
  

when doing the scannow, it gets to 96 percent and then comes up with the message "Windows resource protection could not perform the requested operation" and it doesn't recognise the other command, this is the ESET log:

ESETSmartInstaller@High as CAB hook log:
OnlineScanner64.ocx - registred OK
OnlineScanner.ocx - registred OK

Hello.

Please re-open Malwarebytes, click the Update tab, and click Check for Updates. Then, click the Scanner tab, select Perform Quick Scan, and press Scan.

Post the new log when done.

Malwarebytes' Anti-Malware 1.46
www.malwarebytes.org

Database version: 4304

Windows 6.1.7600
Internet Explorer 8.0.7600.16385

11/07/2010 23:16:17
mbam-log-2010-07-11 (23-16-17).txt

Scan type: Quick scan
Objects scanned: 128334
Time elapsed: 4 minute(s), 51 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

Any Ideas?

As far as I can see, it's not malware related.

You could try opening a topic in the operating systems forum, see if any other techs have any ideas.

On a related note, please uninstall Frostwire, P2P is dangerous.

Thanks for all your help, not many would have persisted with this for this long.