Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: DREDIOCK on July 22, 2007, 08:10:22 PM
-
As some of you are aware I have been having issues with my machine suddenly shutting down during gameplay.
Long story short.
I decided to replace my power supply. No big deal right...No.
Hooking everything up went without incident.
Upon booting I was getting a warning beep. Looked it up and info I got stated MB PS or keyboard probs.
So I shut down and recheck everything.
Next come a long nonstop beep unlike the typical warning beeps.
But. windows loaded.
I shut down and rechecked a couple more times. and each time windows started normally except for the beep
Eventually I figured out that it was because I didnt have my system case fan hooked up. This is the fan that is attached to the panel that comes off when I need to do something to the innards. Replace graphic card etc.
So I disable the warning buzzer in BIOS and the sound goes away. BUT
Now windows wont load.
I get a
"DISK BOOT FAILOUR insert system disk etc" message.
Went back into BIOS. it doesnt recognise my hard drive.
Tried inserting the windows disk. that doesnt see it either.
Tried everything I can think of including turning the bios back to where it was.
Thoughts? Solutions?
Also. could it be it was my hard drive on its way out all along that was the cause of my system shutdowns?
If I get a new hard drive. will I somehow be able to retrieve the data on the old one?
-
reseat your ram . you may have bumpitied it or poped one of the locks on it.
(just some stupid thing ive done befor )
-
I've gotten this on my old computer, your motherboard may be going bad. This is one problem.
-
Originally posted by SpikesX
I've gotten this on my old computer, your motherboard may be going bad. This is one problem.
oh dont tell me that. its less then a year old
-
Originally posted by DREDIOCK
oh dont tell me that. its less then a year old
The long beep is ram as roo said... :D
-
Ram checks out as fine in the Bios
Tried reseating it anyway to no avail.
Tried hooking up a different hard drive but that doesnt work either.
BUT. the HD was from my old P500 and wasnt working right when I still had that machine up and running.
Next question.
Would I be able to tell if its the motherboard by switching IDE slots? Meaning hooking up the CDROM where the HD is normally plugged into the board?
-
Your RAM can't be tested from the BIOS; Make a MemTestx86 boot CD to correctly test memory. (http://www.memtest86.com/) However, this is not your problem.
"DISK BOOT FAILOUR insert system disk etc" message.
If you can get Windows to load the Recovery Console from the CD, run CHKDSK /R and if it can see your disk, it will run a check and attempt to repair data damage on the drive.
Would I be able to tell if its the motherboard by switching IDE slots? Meaning hooking up the CDROM where the HD is normally plugged into the board?
This is an excellent way to determine if you have a bad IDE channel on the motherboard; if the BIOS doesn't see it or you can't see the drive in Windows (i.e., if your boot hard drive is attached to the secondary channel and set to boot in the BIOS, for example) then you'd know that the primary channel was dead. It happens.
-
Originally posted by 0thehero
If you can get Windows to load the Recovery Console from the CD, run CHKDSK /R and if it can see your disk, it will run a check and attempt to repair data damage on the drive.
Volume has one or more unrecoverable problems
But it seems it may let me do a fresh install of windows. which I am assuming will also end up wiping my HD clean?
Which is something I'd prefer to avoid if possible
-
Assuming that only the hard drive is the issue.
If you buy a second hard drive, install windows, and boot from said drive, you can then look at the "dead" drive and retrieve any information that hasn't been destroyed.
-
trying to install windows (on same drive) I get this message
*** stop: 0x0000008e(0cx0000005,0xf77c0cad,0xf732a7e4,0x00000000)
-
You might just have a motherboard problem. (http://support.microsoft.com/kb/315335)
That's a RAM-based STOP error, but if your drive is having corruption issues, your motherboard could be on the way out.
Test your RAM using the MemTestX86 boot CD, to rule it out.
Good luck.
-
Im lleaning towerd the motherboard as suggested.
Unfortunately its a socket 939 with an AGP slot which is next to impossible to find anymore.
I got the 939 a year or so ago when it looked like that was going to be the way AMD was going to go. unfortunately a couple months later that changed.
Problem now is this may mean building an entire new system as my Video card, and memory will be next to useless which is something I definately wanted to avoid doing just yet.
It also means a less then $100 purchise will balloon up to a $400 purchice
Which right after buying my new plasma. paying property,sales and income taxes I just dont have this very moment and wont have extra funds for a couple weeks till I get paid from my next job
So for now Im stuck using my wifes machine
AMD Anthon 2400 (socket A) with 512 ram
Which for her purposes is just fine.
Sucks for my gameplay though
Only other thought I have is in grasping at straws and throwing the old PSU back in and seeing if maybe the new unit is bad.
But as I have said. Thats grasping at straws
I may do it though as I have nothing better to do
-
Originally posted by 0thehero
This is an excellent way to determine if you have a bad IDE channel on the motherboard; if the BIOS doesn't see it or you can't see the drive in Windows (i.e., if your boot hard drive is attached to the secondary channel and set to boot in the BIOS, for example) then you'd know that the primary channel was dead. It happens.
Ok just farting around and noticed I overlooked this.
Switched IDE slots. system still wont boot but the in the bios it clearly and correctly sees both the master and slave CD drives reguardless of which IDE I hook them up to.
And doesnt see thr HD in either
Is there any meaning to this?
Or is it still the mainboard is bad?
-
That proves that the motherboard IDE ports are both working. Either your HD has gone to the angels or the cable to it went bad. Try swapping drive cables and see what happens. You may also want to try a different power cable to the HD too.
-
Originally posted by Auger
That proves that the motherboard IDE ports are both working. Either your HD has gone to the angels or the cable to it went bad. Try swapping drive cables and see what happens. You may also want to try a different power cable to the HD too.
Had tried different cables previously including a brand new set I never used when getting the motherboard option to go with the higher quality ASUS cables I already had instead.
Also tried just about every power connector that the PSU has attached to it.
Back to an old question.
Could a dieing hard drive have been causing the sudden occasional shutdowns I was experiencing as well?
BTW Thank you to everyone for the help
-
I don't think a HD would cause shutdowns... Once the OS is loaded it's in memory. If the HD is bad it will give errors, be unable to read data, unable to write, missing, nonresponsive, but the HD going bad while in-use will not shut the system down. That points to a different HD problem.
I say if you can't upgrade just get an older motherboard.
Check this out, on newegg:
http://www.newegg.com/Product/Product.aspx?Item=N82E16813157097
I've got the socket775 (Intel) version of this. You can use your old ram and old video card and upgrade later.
On mine I get the option of DDR1 or DDR2, but that one only seems to have DDR1 (DDR 400).
It's only $67 USD, as well.
That should keep you going for a while.
-
Once the OS is loaded it's in memory. If the HD is bad it will give errors, be unable to read data, unable to write, missing, nonresponsive, but the HD going bad while in-use will not shut the system down. That points to a different HD problem.
Well, actually it can; just try killing the power to your main drive(s) and see how Windows likes that. :) You can look in the Event Viewer of a system, and quite frequently trace spontaneous shutdowns or reboots to ATAPI errors or DEV errors where the system times out trying to access the hard drive. And as soon as it needs to page something to or from a location where there is no longer access, BOOM!
That said, the idea of swapping cables is a good one, frequently overlooked. I mean, really, how often do cables go bad, right?
-
Picked up a new hard drive and am going to give that a shot. as oppised to an IDE I picked up a SATA. (which my MB supports) figuring when it comes time to a new build. which may be comming sooner rather then later anyway, This way I can just drag it along to my next build.
-
Well Im up and running.
Just installed windows (acck) I hate installing windows.
Now just gotta install the proper drivers for everything else.
So far so good
upgraded from a 60 Gig IDE hard drive to a 160 gig WD SATA 300 Caviar SE
Took me 5 years to nearly fill the 60 gig.
I figure at the rate I fill hard drives I should be ready for retirement bout the time this one is full LOL