Jump to content

Hey guys,

 

Recently when i turn my computer on, it stayed at the windows loading screen for over 10 - 20 mins, i left it going once and it booted into windows, normally ill just restart the computer and it will just boot up normal, 90% of the time it boots normally, but once and a while it will get stuck for ages..

 

What does this mean? my hard drives (raid 0) are going to die? or something is corrupt on the Operating System files?

 

I know normally when it takes ages to load, it means your hard drive is going, but with mine, it doesnt always happen, so i am thinking more software issue

 

any thoughts??

Link to comment
https://linustechtips.com/topic/14736-windows-xp-loading-slow-sometimes/
Share on other sites

Link to post
Share on other sites

normally cause by a service that has been halted or a startup entry failing to start. this results in application time out. so the app thats trying to load will have to wait a set time before it closes itself and the boot continues. normally this will be around 5000ms or 5 seconds but can be as much as 30 or more. if a file is trying and failing to load an extension it may do so repeatedly up to 30 times in some cases each time taking up to 5 seconds which could be the result your seeing. basically an app wont quit till its finished failing.

 

if you have been disabling unneeded services. its likely that you have stopped a dependency of another service. basically some services need other services to be running before they themselves can run. if this doesnt happen the service will keep trying to load its dependencies for a set amount of times again leading to very slow boot times.

 

start up entries.. did you uninstall some app that used to start up automatically. you may not have gotten everything including its startup call in the registry. this will result in the o.s. trying to find files that dont exist or do exist but only partially. again while its searching your waiting for windows to boot.

 

the good news is most of this can be fixed with a reg cleaner. ccleaner will allow you to clean your registry and clear any startup entries that may be fouling the boot. 

you will also want to look in services along with event logs to see which services may be failing to start. find them in ctrl panel/admin tools.

 

depending on the drive some manufactureres have testing tools available so you can test your drives yourself.

 

http://pcsupport.about.com/od/toolsofthetrade/tp/tophddiag.htm

 pick the 1 you need for the half dozen or so in the above link. only use the 1 for your drive.

Rig: Intel i7 920 D0 @3.5 | gtx970 | 12 gig Balistix 1333 @ 8-8-8-24 | 2x1TB Spinpoint F3 Raid 0 | 1TB Spinpoint F3 |samsung 840 evo|  Thermaltake 850w Tp |

Xfi extreme gamer | Antec 902

Peripherals: Samsung syncmaster 2494hs @1920/1080 - 60Hz | Q-pad MK85 | g502 | Razor Destructor | Logitech G930 | Logitech 3D pro xtreme | 360 pad | Nitro Wheel

Link to post
Share on other sites

use glary utilities to defrag your registry

CPU: i7 3770k 4.5ghz M/Board: Sabertooth Z77 GPU: Asus Gtx 560 Direct CUii OC RAM: 2x4gb Corsair Veangance PSU: Corsair CX600 Cooler: Custome Water Loop With Gentle typhoon 1850rpm fan, Single 120mm Rad, XSPC Raystorm CPU Block

Link to post
Share on other sites

Maybe event viewer will tell you what's happened 

 


How to View Event Logs

To open Event Viewer, follow these steps:

  1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
  2. In the console tree, click Event Viewer

    The Application, Security, and System logs are displayed in the Event Viewer window.

 

Check to see if you have an error logged during the times you've started up your pc. Then you can tell us what it is or google the error yourself in search of the resolution :)

export PS1='\[\033[1;30m\]┌╼ \[\033[1;32m\]\u@\h\[\033[1;30m\] ╾╼ \[\033[0;34m\]\w\[\033[0;36m\]\n\[\033[1;30m\]└╼ \[\033[1;37m\]'


"All your threads are belong to /dev/null"


| 80's Terminal Keyboard Conversion | $5 Graphics Card Silence Mod Tutorial | 485KH/s R9 270X | The Smallest Ethernet Cable | Ass Pennies | My Screenfetch |

Link to post
Share on other sites

somethings not rite with your raid thats for sure. have you ran chkdsk lately?

right click and run the CMD prompt wiith elevated privs (run as admin) and run chksdk from there.

Rig: Intel i7 920 D0 @3.5 | gtx970 | 12 gig Balistix 1333 @ 8-8-8-24 | 2x1TB Spinpoint F3 Raid 0 | 1TB Spinpoint F3 |samsung 840 evo|  Thermaltake 850w Tp |

Xfi extreme gamer | Antec 902

Peripherals: Samsung syncmaster 2494hs @1920/1080 - 60Hz | Q-pad MK85 | g502 | Razor Destructor | Logitech G930 | Logitech 3D pro xtreme | 360 pad | Nitro Wheel

Link to post
Share on other sites

somethings not rite with your raid thats for sure. have you ran chkdsk lately?

right click and run the CMD prompt wiith elevated privs (run as admin) and run chksdk from there.

 

this is the event logs, as you can see every morning it just has that RAID error, also get 2-3 other warnings

 

1fcuhk.jpg

 

first time i ran chkdsk, it just said it cant fix for some reason, so i ran it again and this happened. ill restart and see what happens

30jsd4x.jpg

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×