Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

blue screen


  • Please log in to reply

#61
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
its not on desk top
  • 0

Advertisements


#62
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Let's try it again. I suspect that you didn't check the box beside Use Safelist in the Extra Registry section.

Please read the directions carefully.

Posted Image OTL Scan

Please re-open OTL
  • Right click the OTL icon and click Run as Administrator. Make sure all other windows are closed .
  • You will see a console like the one below:

    Posted Image
  • Click the greyed out None at the top of the console.
  • At the top of the console, click the box beside Include 64bit Scans
  • Make sure the Output box at the top is set to Standard Output.
  • VERY IMPORTANT: In the Extra Registry section click the circle beside Use Safelist.<---Important
  • Click the Posted Image button. Do not change any settings unless otherwise told to do so.
  • Let the scan run uninterrupted.
  • When the scan completes, it will open OTL.txt on the desktop. Extras.txt will be minimized. These are saved in the same location as OTL.
  • I Do Not need the OTL.txt log. Please close it and open the Extras.txt file and copy the contents of that file and paste it into your reply. To do that:
  • On the .txt file Menu Bar click Edit then click Select All. This will highlight the contents of the file. Then click Copy.
  • Right-click inside the forum post window then click Paste. This will paste the contents of the .txt file in the in the post window.

  • 0

#63
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
I did it again and it has not produced an extras file I cant see it on desk top
  • 0

#64
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
I tried it again ..it stops responding then lap top freezes again and I have to switch it all off to start it up...blue screen again no writing in it
  • 0

#65
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Well I'm at a loss. I'm trying to see if this is still in the error logs:

Error - 12/17/2012 9:54:07 AM | Computer Name = amanda-TOSH | Source = atapi | ID = 262155
Description = The driver detected a controller error on \Device\Ide\IdePort0.


I'm gonna need to get with some colleagues and maybe the tool developer. I've never seen an instance when clicking the Use Safelist button wouldn't include the Extras.txt file...


  • Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
  • Right click VEW.exe and click Run as Administrator to run the program.
  • Under 'Select log to query', select:
    • System
  • Under 'Select type to list', select:
    • Error
    • Warning
    Then use the 'Number of events' as follows:
  • Click the radio button for 'Number of events'
  • Type 20 in the 1 to 20 box
  • Then click the Run button.
Notepad will open with the output log. Post it in your next reply.
  • 0

#66
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
I tried it again . the OTL it scans then stops for a while then only reports the OTL and not the extras

Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 29/12/2012 23:49:47

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/12/2012 20:05: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.

Log: 'System' Date/Time: 29/12/2012 19:56:21
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: 29/12/2012 17:50:07
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: 29/12/2012 15:20:21
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: 27/12/2012 19:47: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: 26/12/2012 00:25:32
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: 22/12/2012 16:50:26
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/12/2012 20:34:39
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: 17/12/2012 14:08: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: 16/12/2012 14:33:19
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: 15/12/2012 14:13: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: 13/12/2012 14:52: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: 13/12/2012 09:05: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: 13/12/2012 08:54:13
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: 13/12/2012 08:14: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: 12/12/2012 17:56:49
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: 12/12/2012 17:23: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: 12/12/2012 16:08:31
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: 12/12/2012 15:55: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: 12/12/2012 15:40: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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/12/2012 23:37:59
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 23:37:59
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:07:42
Type: Error Category: 0
Event: 10 Source: Microsoft-Windows-CorruptedFileRecovery-Server
The system file C:\Windows\System32\en-US\taskcomp.dll.mui may be corrupted, but Windows could not determine if the file was actually damaged (error code 2147943517). No repair action was taken. Run the command "sfc /scannow" at an administrative command prompt to check for errors and to repair the file if necessary.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:05:08
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 21:00:48
Type: Error Category: 0
Event: 14 Source: volsnap
The shadow copies of volume C: were aborted because of an IO failure on volume C:.

Log: 'System' Date/Time: 29/12/2012 20:59:29
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:59:29
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:59:29
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:59:29
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 29/12/2012 20:09:09
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 29/12/2012 20:05:57
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 29/12/2012 19:56:50
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 29/12/2012 17:50:52
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 29/12/2012 15:22:04
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name download736.avast.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 29/12/2012 15:20:57
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 29/12/2012 15:00:22
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name dns.msftncsi.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 29/12/2012 12:42:12
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 28/12/2012 18:47:11
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name c.betrad.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/12/2012 06:11:45
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name talk.google.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/12/2012 06:11:41
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name teredo.ipv6.microsoft.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 28/12/2012 06:10:59
Type: Warning Category: 0
Event: 1006 Source: Microsoft-Windows-DNS-Client
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. 192.168.0.1

Log: 'System' Date/Time: 27/12/2012 19:48:06
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 27/12/2012 11:44:07
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 27/12/2012 11:42:04
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 26/12/2012 00:26:47
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 24/12/2012 21:38:51
Type: Warning Category: 0
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name labs.popcap.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 24/12/2012 19:59:07
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 24/12/2012 19:57:10
Type: Warning Category: 0
Event: 4001 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN AutoConfig service has successfully stopped.

Log: 'System' Date/Time: 24/12/2012 19:37:44
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Log: 'System' Date/Time: 24/12/2012 19:25:54
Type: Warning Category: 0
Event: 11 Source: Microsoft-Windows-Wininit
Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

Edited by dustypink, 29 December 2012 - 05:50 PM.

  • 0

#67
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Hi dustypink,

I want to check the system files just to be on the safe side, but I think we are dealing with more serious problems.

From the Event Viewer log:

Log: 'System' Date/Time: 29/12/2012 21:00:48
Type: Error Category: 0
Event: 14 Source: volsnap
The shadow copies of volume C: were aborted because of an IO failure on volume C:.

Research indicates that this is sometime the precursor to a hard drive failure.

Log: 'System' Date/Time: 29/12/2012 20:59:29
Type: Error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Research shows this can be anything from a bad or loose cable to a failing hard disk, to a motherboard problem, or it could be just a driver problem.


Step-1.

Run SFC from Safe Mode

Warning!
Be aware that if you have modified your system files as in theming explorer/system files, running sfc/scannow will revert the system files such as explorer.exe back to it's default state. Make the appropriate backups of your system files that you have modified if you wish to save them before running sfc/scannow.


Boot into Safe Mode

  • Start, or Restart the computer and as soon as it starts booting up (you might see the Mfg. logo) start tapping the F8 key.
  • An Advanced Boot Options screen will come up where you will be given the option to enter Safe Mode.
    NOTE: If you miss the Boot menu, continue to let the machine boot up. Then restart the machine and start tapping the F8 key.
    Very Important: Never restart the computer while it is booting up. Bad things, including the computer not being able to load Windows, can occur!
  • Use the down arrow key to highlight Safe Mode and push the ENTER key.
    Windows 7
    Posted Image
  • After the system files load the Windows welcome screen will come up.
  • Click your user name and type in the password (if you have one) and click OK or press Enter. The Safe Mode desktop will come up.

Rename the old SFC log

Open an elevated command prompt. To do that:
  • Click the Start Orb and in the Search box type cmd.exe.
  • In the list of files that comes up above the Search box find the cmd.exe file, right click it and click Run as Administrator
  • Click Continue on the UAC window.
    A command window will open like the image below:
    Posted Image
  • Type the following and press ENTER after each line
  • cd C:\windows\Logs\cbs
  • copy cbs.log cbs.old
  • del cbs.log
  • cd C:\Windows\System32

Now run System File Checker

The System File Checker scans all protected system files and can replace incorrect versions with correct Microsoft versions. This process will take some time.
  • At the blinking cursor type or Copy and Paste the following and press the Enter key:
    sfc /scannow
    (notice the space between the c and the /...it needs to be there)

    Posted Image
    Scans the integrity of all protected system files and repairs the system files if needed. (See screenshot above)
  • When the scan is complete, hopefully you will see all is ok like the screenshot below.

    Posted Image

    NOTE: If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 2 or 3 more times to completely fix everything that it's able to.
  • When the process has finished, write down the results of the scan so you can post them in your next reply.
  • Type exit and press the ENTER key to close the command window.
IF there were errors that SFC couln't fix, complete the directionsbelow to generate and post the sfcdetails.txt log. IF SFC didn't find any errors or fixed all of them, go to Step-2 and just report that in your next reply.

If you need to see the CBS.log

  • Open an elevated command prompt as before. You will see a command window like the screenshot below:
    Posted Image
  • At the blinking cursor type or Copy and Paste the following command and then press ENTER:

    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >%userprofile%\Desktop\sfcdetails.txt

A file named sfcdetails.txt will now be on the desktop. Copy and Paste the contents of this file in your next reply.


Step-2.

Check the Hard Disk drivers

  • Click the Start Orb
  • Right click Computer and in the list in the left column under Tasks, click Device Manager. Click Continue on the UAC window and the Device Manager window will open.
  • Click the + beside IDE ATA/ATAPI controllers
  • Post a screen shot of the Device Manager window in your next reply. To do that:
Capture a Screen Shot

  • When you have the screen up that you want to capture...click on the ALT key + PRT SCR key. This will put the screen shot in the clipboard.
  • Click on Start>> All Programs>> Accessories>> Paint. A Paint window will open up.
  • Left click in the white area and press the CTRL + V keys. This will paste the screen shot from the clipboard into the Paint window.
  • On the Menu bar at the top of the Paint window, click on File, click on Save and save it to your desktop.
  • In the File Name box, name it something related to the screen your capturing. (Like DeviceManager)
  • In the Save as type: box, BE SURE TO SAVE IT AS A .JPG file ...otherwise it may be to big to upload.
To upload the screen shot and put it in a post, click on this link for directions.


Step-3.

Things For Your Next Post:
Please post the logs in the order requested. Do Not attach the logs unless I request it.
1. The results of the SFC scan or the sfcdetails.txt log
2. The screen shot of the Device Manager
  • 0

#68
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
I cannot do this in safe mode as when I do there is no internet connection so I have clicked the one underneath it. Do you want me to carry on?
  • 0

#69
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Yes, please.
  • 0

#70
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
windows resource protection could not perform the requested operation
  • 0

Advertisements


#71
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Did you look at the Device Manager? Were there any red ? question marks or yellow ! exclamation marks or warnings next to any of the devices?

I am going to see if I can get a systems Tech to look at this.
  • 0

#72
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
whats the device manager. I started the next step in safe mode and it wouldnt do it
  • 0

#73
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
did you want me to do step 2? do I do that in safe mode
  • 0

#74
godawgs

godawgs

    Teacher

  • Retired Staff
  • 8,228 posts
Try this:

Log into Normal Mode (boot the computer and log in as you normally would)

THEN:

Delete Old SFC Log

  • Open an elevated command prompt. To do that:
    • Click Start, click on All Programs and Accessories, then right click on Command Prompt and click on Run as administrator. (See screenshot below)

    Posted Image
  • Type the following and press ENTER after each line:
    cd  \windows\Logs\cbs
    
    copy  cbs.log  cbs.old
    
    del  cbs.log
    
    

Now run System File Checker


Run System File Checker

  • Open an elevated command prompt. To do that:
  • Click Start, click All programs and Accessories
  • Right click Command Prompt and select Run as Administrator. (See the screen shot below)

    Posted Image
  • In the black box that opens type or copy and paste the following command and press Enter:

    sfc /scannow

    Posted Image

    The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions.
  • Write down the results of the scan so you can post them in your next reply.
  • Type exit and press the ENTER key to close the command window.

Please post the results of the SFC scan
  • 0

#75
dustypink

dustypink

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 432 posts
on =another lap top now s sick one froze its on desk top nd I click on chrome to launnch and the egg timer sits there for ages the mouse is frozen nothing is working the only way to turn it off is pressing the button
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP