Jump to content

Build Theme!
  •  
  • Infected?

WE'RE SURE THAT YOU'LL LOVE US!

Hey there! :wub: Looks like you're enjoying the discussion, but you're not signed up for an account. When you create an account, we remember exactly what you've read, so you always come right back where you left off. You also get notifications, here and via email, whenever new posts are made. You can like posts to share the love. :D Join 91867 other members! Anybody can ask, anybody can answer. Consistently helpful members may be invited to become staff. Here's how it works. Virus cleanup? Start here -> Malware Removal Forum.

Try What the Tech -- It's free!


Photo

Computer Freeze


  • Please log in to reply
8 replies to this topic

#1 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 02 June 2007 - 08:28 AM

This isnt my problem....its a friends....their computer freezes on the log in screen.... it is a family who all have their own user log ins... Im not a computer expert by any means...the computer will run in safe mode but only as the administrator not the family members logs.... there is no checking their problems because it wont let you in.... is there a back door to checking the problem??

    Advertisements

Register to Remove


#2 Doug

Doug

    Retired Administrator -Tech Team

  • Tech Team
  • 10,057 posts

Posted 02 June 2007 - 09:18 AM

Ability to log into SAFE Mode, but failure to log into Normal Mode with the Welcome Displaying the User Accounts,
Suggests
1. a missing or corrupted Windows Operating System file(s).
2. possibly (not likely) a bit of malware corrupting the system

First:
While in SAFE Mode, run the various AntiVirus and AntiSpyware utilities that the family may have installed.
(if there seem to be "weird" or "unfamiliar" antivirus or antispyware utilities - Don't run them.)
(for instance Spyaxe, Spyfalcon, WinFixer, Wareout, etc. --- are all malware and shouldn't be run)
So just run the ones you are familiar with (AVG, Norton, McAfee, TrendMicro, AVAST, Spybot Search & Destroy, etc. Allow those familiar utilities to "fix" anything they find.
_________

Next:
Run the Disk Cleanup
Start - All Applications - Accessories - System Tools - Disk Clean Up
This will clean up all the "junk files" and may remove a few bad-guys that could be interferring.
_________

Next:
You can safely run CHECKDISK from SAFE Mode.

Run CHECKDISK
Start - Run - (type)chkdsk /f /r - Enter <-- notice the required space before "/f" and "/r"
You will receive a warning that CHECKDISK cannot be run due to inability to lock files or files in use.
You will be invited to allow CHECKDISK to run next time you reboot your machine.
Allow this to be scheduled by typing "Y" and pressing Enter.
Reboot your machine.

CHECKDISK will open during the boot-up cycle, before opening Windows
It will run a series of 5 scans.
CHECKDISK does not create a log, but if you follow along with the Scan, it alerts when it finds a "bad-cluster" and
announces that it is moving the file contents to a safe known-good location on the Hard Drive disk surface.
CHECKDISK scans take between 30 - 40 minutes depending upon the size of your Hard Drive.
Note: CHECKDISK should be run multiple times if it does detect any "bad-sectors".
Please Run CHECKDISK a second and even third time until no errors/bad-sectors are identified.

Running CHECKDISK "may" get the hard drive repaired enough to boot into Normal Mode.
_______

Next you should Run Windows File Protection - System File Checker <-- only Runs in Normal Boot Mode

(if you still can't boot Normally, we'll have to take some additional steps to Repair the Boot Sector)
(let us know if you still can't boot Normally)

If you can boot normally, move on to running System File Checker:

Run Windows File Protection System File Checker
Start - Run - (type)sfc /scannow - Enter

A block DOS type box will open briefly and then disappear before you can read its contents. That's OK.
Then the Windows File Protection progress bar will display to track progress as SFC scans.
If SFC identifies any missing or corrupted operating system files, it will alert you to insert your XP installation CD.
SFC will then copy a known good version of the missing/corrupted file from the CD and into the correct location in
files.

SFC scans take about 20 to 30 minutes.
One full scan should be sufficient. But with a badly corrupted operating system, multiple scans with SFC may be required.
If SFC terminates within 2 or 3 minutes, then it did not complete its scan.
Please alert us to the fact, if this happens.

Please let us know if you do not have XP (or other Windows) installation CD, as we will have to describe additional steps for a workaround.
___________

Reboot your machine after SFC completes.

Let us know if that takes care of the problem.
We can research and suggest additional steps if not.

Edited by dough, 02 June 2007 - 09:26 AM.

The help you receive here is free.
If you wish, you may Donate to help keep us online.

#3 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 04 June 2007 - 05:06 AM

We followed the instructions as much as we could..... the computer froze in safe mode as well.... we couldnt complete check disk fully....it kept freezing at stage 4...but we could get into normal mode... so we did sfc scan now and it asked for the Windows disk straight away... it reinstalled Windows XP and the computer has not frozen yet...we also ran check disk to see if it would freeze....at the last stage the computer restarted itself....and continues to restart itself almost as soon as you choose to run in safe mode/normal mode etc.... it comes up with a warning when it boots up....it says that the CPU has been changed and to re enter the settings.... what can i do about this.

#4 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 04 June 2007 - 05:07 AM

now it is restarting as soon as it displays the warning

#5 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 04 June 2007 - 05:34 AM

we were able to get in normally again.....however the computer restarted again and again....

#6 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 04 June 2007 - 09:03 AM

computer seems to be ok right now...we ran sfc /scannow again....no problems yet....

#7 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 05 June 2007 - 04:23 AM

computer seems ok but will restart itself still....on initial startup....is this unusual? it eventually goes into windows and works ok...but the little turn itself off thing is a little weird... could u tell me what this could be??

#8 Doug

Doug

    Retired Administrator -Tech Team

  • Tech Team
  • 10,057 posts

Posted 05 June 2007 - 10:15 AM

Automatic Restart How to disable in XP

You may be encountering a feature of Windows XP's Startup and Recovery system.
By default, this system specifically configures Windows XP to automatically restart itself after encountering a system failure error.

These system failure errors are usually isolated and occur randomly.
As such, the best way for the operating system to deal with them is to automatically restart.

However, you can disable the automatic restart behavior. Follow these steps:
1. Go to Start, right-click My Computer and choose Properties
2. Click the Advanced tab
3. In the Startup and Recovery section, click Settings
4. In the System failure section, uncheck "Automatically restart"
5. Click OK twice
Now, your system will not automatically restart when the error occurs.
***This does not mean the issue is resolved, it just means you will be able to see the error encountered.

You will start seeing the Windows Stop Error screen, also known as the "Blue Screen of Death" (BSOD). Encountering this screen means that Windows can no longer continue operating normally and needs to be restarted.
---What is important is that, although daunting, this screen will tell you the error name and number that made your computer unhappy.
Please write down this error name and number the next time you receive it and post it here.
__________

The other option you have to get the error code is through the Event Viewer. Using this method, you won't have to wait for the system to encounter another error.:
1. Go to Start - Run, (type)eventvwr.msc, and press Enter.
2. When the Event Viewer opens, there will be two panes. The left pane is for event categories (Application, Security, and System). The right pane is for event messages (Information, Warning, and Error). We want to find errors.
3. Left-click the Application category in the left pane and check for any error messages in the right pane. You want one that occurred the same time your system encountered the error.
4. Repeat the previous step for each category, or until you find an appropriate error.
5. Double-click the error message to bring up the information.
6. Click the third button on the right side of the information window (copies information)
7. Paste the information here
The help you receive here is free.
If you wish, you may Donate to help keep us online.

#9 Sianaba

Sianaba

    Authentic Member

  • Authentic Member
  • PipPip
  • 22 posts

Posted 05 June 2007 - 11:33 PM

We were told to uncheck the box for automatically shut down by a friend...
the computer still did it afterward....there was no blue screen of death...
error as follows:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 5/06/2007
Time: 6:38:54 PM
User: HOMEATCHLEY\David
Computer: HOMEATCHLEY
Description:
Product: Microsoft Office Professional Edition 2003 -- Error 25090. Office Setup encountered a problem with the Office Source Engine, system error: -2147023179. Please open C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM and look for "Office Source Engine" for information on how to resolve this problem.

For more information, see Help and Support Center at http://go.microsoft....link/events.asp.
Data:
0000: 3130397b 30343031 30362d39 312d3030
0010: 2d334431 45464338 3531302d 38343030
0020: 43333833 7d39


It hasnt restarted itself the last few times we turned it on....

Related Topics



0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users