Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

windows 7 64bit freeze up


  • Please log in to reply
19 replies to this topic

#1 mcb99

mcb99

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 21 January 2010 - 01:06 AM

Hi I also have been getting win7 64bit freeze ups. Not BSOD, just a freeze requiring me to reset the puter.
I have checked windows update. I have checked to see if I needed any new drivers. I flashed the latest MOBO bios .
I have not found a pattern to when the freeze happens. I have tried running a process monitor and seeing what was the last
process logged b4 the screen freeze.

The last 5 freezes had these as the last process:

MOM.exe (PID) 3728
Firefox.exe (pid)184
wmptvetwk.exe (pid) 4700
teatimer.exe (pid_3468 WOW6432NODE
teatimer.exe (pid)2640 WOW6432NODE

Puter is a new build. Fresh install of win7 64
AMD phenom II 94
Asus M4a79t deluxe
Mushkin 4gb
Seasonic gold 650x
ATI raadeon 5700
Velociraptor 150 gb
Western Digital Mybook Home 500gb

I run AVG anti virus, Spybot, Mozilla , CCleaner, Comodo Firewall

I think thats enough info.

Is there anything that can run in the backround and tell me what caused the freeze?

vew results:


Report run at 21/01/2010 12:23:40 AM

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 04/12/2009 11:35:45 PM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Acronis Disk Director 10, from vendor Acronis) was hard-blocked and raised the following: Acronis Disk Director 10 is incompatible with this version of Windows. For more information, contact Acronis.

Log: 'Application' Date/Time: 04/12/2009 10:48:30 PM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Acronis Disk Director 10, from vendor Acronis) was hard-blocked and raised the following: Acronis Disk Director 10 is incompatible with this version of Windows. For more information, contact Acronis.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 21/01/2010 6:13:52 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program VEW.exe version 1.0.0.4 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: cdc Start Time: 01ca9a60dac0ce53 Termination Time: 1 Application Path: C:\Users\mark\Desktop\VEW.exe Report Id: 236087b2-0654-11df-bc82-002618417e3e

Log: 'Application' Date/Time: 21/01/2010 6:13:26 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program VEW.exe version 1.0.0.4 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: 524 Start Time: 01ca9a60bba6a5ee Termination Time: 2 Application Path: C:\Users\mark\Desktop\VEW.exe Report Id: 135baaf7-0654-11df-bc82-002618417e3e

Log: 'Application' Date/Time: 21/01/2010 6:12:10 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program VEW.exe version 1.0.0.4 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: 610 Start Time: 01ca9a60645182a2 Termination Time: 3 Application Path: C:\Users\mark\Downloads\VEW.exe Report Id: e2d42746-0653-11df-bc82-002618417e3e

Log: 'Application' Date/Time: 20/01/2010 1:34:44 PM
Type: Error Category: 0
Event: 63 Source: SideBySide
Activation context generation failed for "e:\program files (x86)\spybot - search & destroy\DelZip179.dll".Error in manifest or policy file "e:\program files (x86)\spybot - search & destroy\DelZip179.dll" on line 8. The value "*" of attribute "language" in element "assemblyIdentity" is invalid.

Log: 'Application' Date/Time: 20/01/2010 8:08:32 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007041d, The service did not respond to the start or control request in a timely fashion. .

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 8:08:32 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x8007041d, The service did not respond to the start or control request in a timely fashion. ]

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 8:01:45 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007041d, The service did not respond to the start or control request in a timely fashion. .

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 8:01:45 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x8007041d, The service did not respond to the start or control request in a timely fashion. ]

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 7:55:05 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007041d, The service did not respond to the start or control request in a timely fashion. .

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 7:55:05 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x8007041d, The service did not respond to the start or control request in a timely fashion. ]

Operation:
Instantiating VSS server

Log: 'Application' Date/Time: 20/01/2010 7:37:01 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: Procmon64.exe, version: 2.8.0.0, time stamp: 0x4aef9a4d Faulting module name: guard64.dll, version: 3.13.55704.574, time stamp: 0x4b0b9962 Exception code: 0xc0000005 Fault offset: 0x00000000000022e0 Faulting process id: 0x650 Faulting application start time: 0x01ca999faae49848 Faulting application path: C:\Users\mark\Downloads\Procmon64.exe Faulting module path: C:\Windows\system32\guard64.dll Report Id: 982505d1-0596-11df-a42e-002618417e3e

Log: 'Application' Date/Time: 20/01/2010 5:30:16 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program regedit.exe version 6.1.7600.16385 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: 6b4 Start Time: 01ca99913ab9e85a Termination Time: 2 Application Path: C:\Windows\regedit.exe Report Id: e01b9cd9-0584-11df-a42e-002618417e3e

Log: 'Application' Date/Time: 20/01/2010 5:19:21 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Procmon64.exe version 2.8.0.0 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: 125c Start Time: 01ca999002eb36d5 Termination Time: 3 Application Path: C:\Users\mark\Downloads\Procmon64.exe Report Id: 555a004a-0583-11df-a42e-002618417e3e

Log: 'Application' Date/Time: 19/01/2010 6:19:48 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program CCC.exe version 2.0.0.0 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: d94 Start Time: 01ca99337d6aad55 Termination Time: 10 Application Path: C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe Report Id: 2f9c3aad-0527-11df-86c1-002618417e3e

Log: 'Application' Date/Time: 18/01/2010 7:18:38 PM
Type: Error Category: 3
Event: 1019 Source: Microsoft-Windows-Search
Windows Search Service failed to process the list of included and excluded locations with the error <30, 0x80040d07, "iehistory://{S-1-5-21-3706090690-2790638088-1762892125-1000}/">.


Log: 'Application' Date/Time: 18/01/2010 7:02:49 PM
Type: Error Category: 3
Event: 1019 Source: Microsoft-Windows-Search
Windows Search Service failed to process the list of included and excluded locations with the error <30, 0x80040d07, "iehistory://{S-1-5-21-3706090690-2790638088-1762892125-1000}/">.


Log: 'Application' Date/Time: 18/01/2010 7:01:18 PM
Type: Error Category: 3
Event: 1019 Source: Microsoft-Windows-Search
Windows Search Service failed to process the list of included and excluded locations with the error <30, 0x80040d07, "iehistory://{S-1-5-21-3706090690-2790638088-1762892125-1000}/">.


Log: 'Application' Date/Time: 18/01/2010 6:58:58 PM
Type: Error Category: 3
Event: 1019 Source: Microsoft-Windows-Search
Windows Search Service failed to process the list of included and excluded locations with the error <30, 0x80040d07, "iehistory://{S-1-5-21-3706090690-2790638088-1762892125-1000}/">.


Log: 'Application' Date/Time: 18/01/2010 5:31:36 AM
Type: Error Category: 0
Event: 11935 Source: MsiInstaller
Product: Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148 -- Error 1935.An error occurred during the installation of assembly 'Microsoft.VC90.MFC,version="9.0.30729.4148",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070091. assembly interface: IAssemblyCacheItem, function: Commit, component: {03A12C9D-C56A-3F97-8530-0643D6391970}

Log: 'Application' Date/Time: 18/01/2010 4:00:01 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: IObit SmartDefrag.exe, version: 1.4.0.0, time stamp: 0x4b443b5e Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf Exception code: 0x0eedfade Fault offset: 0x0000b727 Faulting process id: 0x1e0dc Faulting application start time: 0x01ca97f2b487c78e Faulting application path: C:\Program Files (x86)\IObit\IObit SmartDefrag\IObit SmartDefrag.exe Faulting module path: C:\Windows\syswow64\KERNELBASE.dll Report Id: f328c19d-03e5-11df-88cd-002618417e3e

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 21/01/2010 6:21:34 AM
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: 21/01/2010 5:27:13 AM
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: 20/01/2010 5:16:51 AM
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: 20/01/2010 5:13:26 AM
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: 19/01/2010 9:29:57 PM
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: 19/01/2010 9:26:42 PM
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: 19/01/2010 8:39:53 PM
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: 19/01/2010 7:13:09 PM
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: 19/01/2010 6:43:56 PM
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: 19/01/2010 6:35:08 PM
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: 19/01/2010 6:27:20 PM
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: 19/01/2010 6:15:51 PM
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: 19/01/2010 7:57:27 AM
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: 19/01/2010 7:44:53 AM
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: 19/01/2010 2:21:36 AM
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: 19/01/2010 2:17:39 AM
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: 19/01/2010 1:50:16 AM
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: 18/01/2010 6:40:37 PM
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: 18/01/2010 5:53:47 AM
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: 18/01/2010 5:52:37 AM
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: 21/01/2010 6:21:42 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The ASInsHelp service failed to start due to the following error: The system cannot find the file specified.

Log: 'System' Date/Time: 21/01/2010 6:21:41 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 21/01/2010 6:21:41 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 12:20:13 AM on ?1/?21/?2010 was unexpected.

Log: 'System' Date/Time: 21/01/2010 6:21:31 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 21/01/2010 5:27:21 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The ASInsHelp service failed to start due to the following error: The system cannot find the file specified.

Log: 'System' Date/Time: 21/01/2010 5:27:19 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 21/01/2010 5:27:20 AM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 9:14:51 AM on ?1/?20/?2010 was unexpected.

Log: 'System' Date/Time: 21/01/2010 5:27:10 AM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 20/01/2010 8:08:13 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:08:13 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Log: 'System' Date/Time: 20/01/2010 8:07:26 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:07:26 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Log: 'System' Date/Time: 20/01/2010 8:06:41 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:06:41 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Log: 'System' Date/Time: 20/01/2010 8:05:58 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:05:58 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Log: 'System' Date/Time: 20/01/2010 8:05:17 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:05:17 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Log: 'System' Date/Time: 20/01/2010 8:04:38 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Volume Shadow Copy service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Log: 'System' Date/Time: 20/01/2010 8:04:38 AM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Volume Shadow Copy service to connect.

Edited by mcb99, 21 January 2010 - 01:25 AM.


BC AdBot (Login to Remove)

 


#2 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:01 AM

Posted 21 January 2010 - 01:50 AM

It's going to be a long shot, but to eliminate software issue, I'd....

Go Start>Run (Start Search in Vista), type in:
msconfig
Click OK (hit Enter in Vista).

Click on Startup tab.
Click Disable all
IMPORTANT! In case of laptop, make sure, you do NOT disable any keyboard, or touchpad entries.

Click Services tab.
Put checkmark in Hide all Microsoft services
Click Disable all.

Click OK.
Restart computer in Normal Mode.

NOTE. If you use different firewall, than Windows firewall, turn Windows firewall on, just for this test, since your regular firewall won't be running.
If you use Windows firewall, you're fine.

Run it for while and see, if it works OK.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#3 rusjkit

rusjkit

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:10:01 PM

Posted 21 January 2010 - 08:12 AM

I have read elsewhere that Spybot Tea timer is not the best with Windows 7. could be the problem

#4 mcb99

mcb99
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 22 January 2010 - 01:10 AM

Spybot Teatimer is an integral part of Spybot? or is this part of the application that can be turned off?
Any suggestions for other good spyware freeware?

#5 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:01 AM

Posted 22 January 2010 - 01:15 AM

Yes, TeaTimer is a part of Spybot. Spybot itself is rather tool of the past.
Your current best choices:
- SUPERAntiSpyware Free Edition: http://www.superantispyware.com/download.html
- Malwarebytes' Anti-Malware (trial version is fully functionable): http://www.malwarebytes.org/mbam.php

Did you try my advice?

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#6 mcb99

mcb99
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 23 January 2010 - 12:51 PM

Ok, i did what Broni suggested and disabled thru msconfig all the MS stuff and ran widows firewall and windows antivirus...etc.
havent had a freeze up for 1.5 days. so great! But now what? how do I let my computer run normally again and how do I choose what to allow
to run in the background? thanks

#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:01 AM

Posted 23 January 2010 - 12:56 PM

Good :huh:

Now, you need a lot of time and a lot of patience.

Go back to "msconfig" and re-enable ONE of the services, you disabled before.
Restart computer.
Use it for a while.
No freezing?
Go back to "msconfig", re-enable next service.
Restart computer and so on.....

If services checks out, proceed with re-enabling startups, also one at a time.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#8 Jacee

Jacee

    Bleeping around


  • Malware Response Team
  • 3,716 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:07:01 AM

Posted 23 January 2010 - 06:17 PM

It looks like Comodo Firewall could be causing a few problems. Disable Comodo, in Services and use Windows 7 Firewall while you're adding programs back (one at a time) using msconfig.

MS_MVP.gif
MS MVP Windows-Security 2006-2016
Member of UNITE, the Unified Network of Instructors and Trusted Eliminators

Admin PC Pitstop


#9 plaztikrhino

plaztikrhino

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:09:01 AM

Posted 23 January 2010 - 08:45 PM

I would remove spybot S&D, seems like that program is a waste of time and causes issues. Install superantispyware, malwarebytes and be done with it.

#10 mcb99

mcb99
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 25 January 2010 - 10:43 PM

problem solved, its software related. no freezes for 3 days now.
Removed spybot. but kept comodo. also stopped a western digital
program and a couple others i didnt need or know whzt they did.
Thank you

#11 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,699 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:07:01 AM

Posted 25 January 2010 - 10:47 PM

Nice job :huh:

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#12 jstoutjr

jstoutjr

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:08:01 AM

Posted 03 February 2010 - 12:46 PM

I've had issues like this when Norton Internet Security 9.0 starts up. Had to uninstall and reinstall the product to resolve the issue.

#13 busybeaver

busybeaver

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 03 February 2010 - 08:52 PM

Ok, my daughter has been having same problem with her 64-bit Windows 7 Upgrade package. It seems her laptop will freeze up on her after about an hour or so of use. To the person who removed Spybot, did you just eliminate that program and turn all the other programs back on in the config?

Let me know so that I can make my daughter realize that going back to Vista is just SOOOOO wrong.

Thanks in advance,

BB

#14 mcb99

mcb99
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:10:01 AM

Posted 02 March 2010 - 02:14 PM

well , problem evidently is not solved. I have turned off most programs, eliminated spybot, comodo.
I have avg as my spyware.
Any other ideas? Is there anyway to find out what program or driver actually caused the freeze?
I tried scanning with a program called VEW.
Thanks

#15 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:02:01 PM

Posted 02 March 2010 - 02:25 PM

With that many errors I would be guessing bad memory.

Spybot is still a valuable tool. Its immunizer is very good. I use it just for that.

Edited by cryptodan, 02 March 2010 - 02:25 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users