HELP! Computer wont start...

bass_junkie83

bass_junkie83

Suspended / Banned
Messages
4,367
Name
Dave
Edit My Images
Yes
...and I have photos from two weddings and a music festival to edit yet!

A couple of days ago my computer decided that it wouldn't let google chrome work any more, after a couple of years of working fine. Since then, it has started getting a bit buggy, locking up on simple low CPU intensive programs.

Now this morning it wont turn off after crashing last night. It wants to run startup repair tool, which seems to sit for hours and not actually do anything, or if I tell it to start normally, it hangs on the start up screen.

I assume it's likely to be a software issue, and not hardware? In which case maybe it's just time for a fresh windows install, what do you reckon?

If that is what it needs, I have no idea how to do that. I have a 30GB or 60GB SSD for the OS, and two 1TB drives set up in RAID as general storage. I have no clue how to set that all back up again after, the computer was put together by a mate who can do it all with his eyes closed, but not me.
 
does it start up in safe mode?
 
as it's booting up , just keep pressing F8
 
It's now working, kinda.
Could not get it to open in safe mode, so left the startup repair tool running for ~3 hours and it fired up once that finished.

But as soon as you log in it comes up saying that a couple of programs have stopped working, the desktop gadgets and something to do with my Nas drive.
Opening IE and that does the same thing, dialogue box opens saying that it has stopped working.
Chrome still isn't working and have no way of accessing the web on it.
 
The chrome issue may relate to the recent update to the inbuilt Flash Player (there are now 2 versions built in, the one named PepperFlash seems to be causing some issues).

Guide of how to disable it here:
http://www.youtube.com/watch?v=QZW6o0jgcY8
 
Turn PC on, log in to windows, click on start button, then click either in the search area at the bottom of the list OR if you have the "Run" command available click on that.

Then type "command" (without the " marks) and press enter, this should open a black box on screen.

Then when the black box is open, type "chkdsk /r" (without the " marks) which basically tells the computer to CHecK DiSK and Repair - this will take at least an hour to run, maybe two so best to do it just as you are going to bed.

It will tell you that the drive is in use and will ask you if you want to schedule it for next startup - tell it Yes or OK or Accept - I forget the exact wording.

BACKUP YOUR ESSENTIAL DATA / PICTURES ETC BEFORE RESTARTING.

Then restart the computer and walk away - you will see it gives you a blue screen with a countdown to checking the disk - do not interrupt it otherwise it will not run.

In my experience, this will extend the life of the hard drive for a short while, but I would recommend saving for a new hard drive NOW.

Cheers,

Ste
 
if its windows 7 youll need to run command prompt in an elevated permission.

so type command into search, right click command prompt and "run as admin".

it wont extend any "life" of the drive, it will however correct any errors. if the drive is failing however the drive will continue to cause errors and the problems will come back. it should not have any destructive effect.

if chkdsk takes more than 10 mins to run (either just slow or repairing lots of errors) then throw the disk away asap.
 
neil_g said:
if its windows 7 youll need to run command prompt in an elevated permission.

so type command into search, right click command prompt and "run as admin".

it wont extend any "life" of the drive, it will however correct any errors. if the drive is failing however the drive will continue to cause errors and the problems will come back. it should not have any destructive effect.

if chkdsk takes more than 10 mins to run (either just slow or repairing lots of errors) then throw the disk away asap.
Click to expand...

When I say "extend the life" to clarify - the chkdsk marks any bad partitions as bad so the computer does not use them any longer, and the time for chkdsk - I have known a chkdsk /f run for an hour on an older system and a chkdsk /r run for a couple of hours. The same drive(s) have lasted a while longer - however hard drives are very fickle and may die at a day old or may last years - this is why the recommendation is always to backup.

Agreed it does not have any destructive effect, but if the drive is already failing then I always backup before running chkdsk.

If the drive does appear to fail then one other temporary "fix" I have used previously is to remove the hard drive from the computer, double wrap it in plastic so it is watertight and dry and put it in the freezer for an hour before trying to use it again.

This is a last resort "fix" and should only be used for getting data off a failing drive and the drive is likely to be dead very shortly afterwards if you do NEED to do this.

Cheers,

Ste
 
correct it does mark those sectors however the underlying reason for those issues may still be present. any disk with bad sectors, especially that reoccur, should be binned asap.

if the disk takes an hour to check then something serious is up.

the freezer trick wont help a drive that is failing with bad sectors, normally thats for stuck platters/heads.
 
Everything I desperately need is regularly backed up, so no real concerns there. I will do the checks tonight.

With the two drives being in raid, will the check disk check both? How about the SSD, should I check that too?

Thanks for the help so far!
 
your OS is on an SSD though not the RAID?

you should specify the C: drive on the chkdsk, thatll probably be the one with the issue if your OS and programs are failing.
 
Last edited:
Yeah that is right, I have;

C: SSD, OS only
D: 2x1TB, general storage and all other software.

I assumed that because I was getting a few other small programs giving it, it would be one of the hard drives failing affecting windows in some way.

Not sure if it would be related, but if it is the SSD, I have always had a problem with it where it was always close to being full. And 30GB of just a windows 7 install seems a bit much!
 
30 is a bit small for an OS. might be worth swapping windows onto the 60 and using the 30 (if not faulty) as a swap/cache/scratch disk. presumably the SSD was set up correctly within windows? trim enabled etc? might just need the manufacturer wipe tool to bring it back to life.

as per my last, find out the make of the SSD and download diag tools also.
 
Last edited:
I have no idea to be honest, someone else built the pc for me. Will run the checks tonight and let you know what it throws up.

I think it may be worth a fresh install of windows once I get to the bottom of all this anyway, as it's been going 3+ years already. Is there any benefit in waiting for windows 8?
 
It gets better. :(

Got home yesterday evening to do the check disc.

Turned on the computer and just got a series of beeps and nowt else. Turned it off, unplugged and re plugged in the SSD and it fired up. Scheduled the SSD to run the check on the next restart. Restarted the computer and was greeted with the beeping again. Many restart attempts later and I still can't get the thing to fire up. :(

So, new SSD time it seems. The one I have at the moment is an OCZ, so looking at something different, this should be suitable right?
http://www.ebuyer.com/288065-sandisk-120gb-ultra-ssd-sdssdh-120g-g25
 
one repetitive long beep?

POST Error Beep Codes
This section lists POST (Power On Self Test) error beep codes for the Phoenix BIOS.
POST error beep codes are divided into two categories: recoverable and terminal.
This section lists Beep Codes for recoverable POST errors.
Recoverable POST Error Beep Codes
When a recoverable type of error occurs during POST, BIOS will display a POST
code that describes the problem. BIOS may also issue one of the following beep
codes:
1 long and two short beeps - video confi guration error
1 repetitive long beep - no memory detected
1 continuous beep (with the front panel OH LED on) - system overheat
Click to expand...
 
I would say they are just short beeps.

More of a beep....beep....beep....beep

rather than a beeeeeeeeep....beeeeeeeeep....beeeeeeeeep....beeeeeeeeep....beeeeeeeeep

Can't see it being an overheating issue, it's been off for a full day and the beeps start the moment the power button is pressed. Can't see how anything can get that hot instantly.
 
if a heatsink isnt on secure then it will pretty instantly. would be worth a check. might also be worth reseating memory while youre in there.

it does mention terminal beep codes but doesnt list them.. do you have the paper manual?
 
No unfortunately not. The computer was built for me years ago by a mate who works in a data center. I just asked for a kick ass photo editing machine and this is what he cobbled together with parts he had kicking around.

I found this full list, but nothing sticks out.

http://www.bioscentral.com/beepcodes/phoenixbeep.htm#

I shall have to try it again tonight and listen properly I think, Admittedly as soon as it started beeping wildly at me I shut it off in fear of something getting damaged.
 
Will do, thanks for your help!

I'm still inclined to get a new larger SSD and copy of windows anyway. Hopefully I can get it running again as is to get this last lot of jobs done, then have the parts ready to hand to give if a squeeky clean fresh install.
 
I wouldnt rule out a memory (hardware) problem causing the initial crash. Obviously the memory could have been damaged by a surge of electricity.

You've got to start with the software though. Do a spyware scan. Better still, take the hard drive out and put it in another computer as a slave. Scan it for errors and issues i.e spyware / viruses. Then make it the slave to see if it runs. that way your confirming where the issue is.
 
Just got home and opened her up. Was going to go through a process of unseating and reseating one component at a time followed by powering up to try and find exactly what may have caused it.

Started off taking the ram out and putting it back in, fired up fine first time, with no error beeps.

So now going through the checks. SSD has a load of 'bad cluster' in loads of files which apparently it has sorted. Going through the other hard drives and they appear to be fine.
Still have issues with a few programs not working, but other than that seems ok at this moment in time.
 
bass_junkie83 said:
Just got home and opened her up. Was going to go through a process of unseating and reseating one component at a time followed by powering up to try and find exactly what may have caused it.

Started off taking the ram out and putting it back in, fired up fine first time, with no error beeps.

So now going through the checks. SSD has a load of 'bad cluster' in loads of files which apparently it has sorted. Going through the other hard drives and they appear to be fine.
Still have issues with a few programs not working, but other than that seems ok at this moment in time.
Click to expand...

Sounding a little more promising..... Still suspicious of the SSD though.... Backup time!
 
You must log in or register to reply here.
Back
Top