As if it's not enough to chew a crown off on Tuesday, I fired up the main machine this morning and it wouldn't boot. Being Good Friday, I can't get warranty service until at least Wednesday. :( Luckily, my backup regime means that I was able to transfer to the other desktop, after a quick check on the forum via the netbook, with almost everything intact. (I have the data for everything, but in a couple of cases, the app isn't installed - plus there's three shared printers I can't access.)
I want a better week next week. :)
CMOS battery?
The CMOS shouldn't stop it booting. My mums PC had a dead battery in it and you had to go into the bios to set the time on every boot or it wouldn't start. Other than that, it worked fine for months (until I found the key to open the case and replace the battery ;D)
Quote from: DorsetBoy on Apr 02, 2010, 17:38:20
CMOS battery?
Possible, Dorset, though a scrambled CMOS seems more likely. Unfortunately, with my tremors, I can't get to the battery without risking the SATA leads nearby. :(
SATA leads are also good for coming loose :mad:
They seem OK. The initial message was "Initialising USB controller" at which it hung. A reset got no further so I powered down and disconnected all the USB devices. On powering up again, the fans and drives all ran up OK, but no graphic output, no beeps and the drive lights just stayed on. It doesn't respond to the power button or the reset button either.
Can you get to BIOS setup?
No, it's not even entering POST from what I can see - and the graphics card is giving no signal, ie the monitor shuts down into standby.
That could be the power supply failing.
Just as well it's under warranty Rik
It could be a long list of things. This is what irritates me about PCs :D
It could be the graphics card itself, it could even be a soundcard that's died stopping it booting (or any other PCI device for that matter). I doubt it's a power supply issue as it would more likely not even start to boot. The motherboard controllers could have killed themselves though as I saw that happen on my sisters PC, although I forget the exact message the screen showed when booting, or even where it got to.
Quote from: kinmel on Apr 02, 2010, 17:57:22
Just as well it's under warranty Rik
Indeed. :)
http://vip.asus.com/forum/view.aspx?id=20071112150542734&board_id=1&model=P5W+DH+Deluxe&page=1&SLanguage=en-us
Quote from: Niall on Apr 02, 2010, 17:57:51
It could be a long list of things. This is what irritates me about PCs :D
Definitely one to hand off to an engineer with a van load of spares. :)
Fixed my brothers after it wouldn't boot. Corrupt boot-sector. Takes about 5 minutes to fix with the install disk and a commandline. Worth a try.
Quote from: Glenn on Apr 02, 2010, 17:58:45
http://vip.asus.com/forum/view.aspx?id=20071112150542734&board_id=1&model=P5W+DH+Deluxe&page=1&SLanguage=en-us
Lots of possibilities, none that I can do for myself. :(
Quote from: Supanova on Apr 02, 2010, 18:04:01
Fixed my brothers after it wouldn't boot. Corrupt boot-sector. Takes about 5 minutes to fix with the install disk and a commandline. Worth a try.
I don't get a POST screen or any video, though. :(
Follow the flowchart
Go with the flow (http://www.fixingmycomputer.com/)
Sounds like power to me or at worst a motherboard/CPU failure. If it was any other component or a device boot failure you would still have the potential for BIOS entry or the BIOS would be beeping out a merry tune.
Quote from: kinmel on Apr 02, 2010, 18:06:56
Follow the flowchart
Go with the flow (http://www.fixingmycomputer.com/)
Sadly, I can't. :(
Quote from: zappaDPJ on Apr 02, 2010, 18:07:49
Sounds like power to me or at worst a motherboard/CPU failure. If it was any other component or a device boot failure you would still have the potential for BIOS entry or the BIOS would be beeping out a merry tune.
Well, any of them are covered by the warranty. :)
Quote from: zappaDPJ on Apr 02, 2010, 18:07:49
Sounds like power to me or at worst a motherboard/CPU failure. If it was any other component or a device boot failure you would still have the potential for BIOS entry or the BIOS would be beeping out a merry tune.
That is what I thought, I had a power supply that failed on 2 coils so that drives and fans came up but 2 of the ATX leads were dead.
You have several supplies in one,there are 6 different supplies on mine.
Anybody want to pop round with a spare? ;D
Have you tried shouting at it rik?
Quote from: adamr8965 on Apr 02, 2010, 18:28:06
Have you tried shouting at it rik?
Shush,everybody else thought it was thunder in MK. ;D
Nah rik passing wind.
Quote from: adamr8965 on Apr 02, 2010, 18:28:06
Have you tried shouting at it rik?
I've tried that, pleading, Sue's offered to cook it a steak but nada. :'(
neither off them worked? must be proper nacked then
I am. ;D
Have you tried hooking up an external monitor?
The monitor is OK, Drummer, I switched it to this machine.
Have you tried this? (http://xkcd.com/627/)
It's much easier than this one:
(http://gadgets.boingboing.net/repair%20flow.jpg)
About my level, Ben. ;D
can't see the hammer option.
It's on page 2.
Quote from: Rik on Apr 02, 2010, 18:46:25
The monitor is OK, Drummer, I switched it to this machine.
D'oh! I read your first post too quickly and assumed you were talking about a netbook. :blush:
ah hammer will always solve the problem, coz it will be full nacked. Then you'll a new one then :thumb:
Quote from: drummer on Apr 02, 2010, 20:10:44
D'oh! I read your first post too quickly and assumed you were talking about a netbook. :blush:
I do it all the time, Drummer. ;)
Quote from: Glenn on Apr 02, 2010, 17:58:45
http://vip.asus.com/forum/view.aspx?id=20071112150542734&board_id=1&model=P5W+DH+Deluxe&page=1&SLanguage=en-us
The only one there with a solution was due to badly seated ram. I have a machine that ran for a couple of years with 4 sticks of RAM until suddenly it wouldn't post.I removed 2 sticks reset CMOS and it worked until I but the other 2 sticks back in. So now it runs Windows 7 happily with 2 Gb instead of rather slow Vista.
Want to pop round, Steve? ;)
I would but I've got four orders for sausages,bacon,eggs,beans and toast to do before the football kicks off. ;D
;D
I'll get Sue on the job... ;)
Quote from: Rik on Apr 03, 2010, 11:24:27
;D
I'll get Sue on the job... ;)
Its good to see age never effects libido :evil:
;D
no boot at all with no beeps etc.?
first off, id take the power cable out the back, discharge it all by pressing power button a few times and leave it 5 mins, try again
take out anything not needed
if still no, you are looking at component fiddling which as u say with shakey hands its a bit risky - but id take the cmos out and do the above - wait for 30 mins with cmos out.
then id try with bare minimum components - hell take the ram out and see if u get beeps!
then its a case of trying with less and less components till a) you find the culprit or b) its your motherboard fooked!
doubt its shorting somewhere, but possible
I'd basically narrowed it down to scrambled CMOS, power supply, motherboard, graphics card, CPU, RAM or something else, Sam. I think the case is OK though. :)
Quote from: Rik on Apr 06, 2010, 09:37:11
I'd basically narrowed it down to scrambled CMOS, power supply, motherboard, graphics card, CPU, RAM or something else, Sam. I think the case is OK though. :)
Rik, it is much more likely to be that the smoke has escaped (http://www.bbc.co.uk/dna/h2g2/A465310), be sure to point out that possibility to the repairman ;D
:rofl:
I kept the case hermetically sealed, Alan, which also allowed me to fry eggs on the top. ;)
Quote from: Rik on Apr 06, 2010, 12:38:33
:rofl:
I kept the case hermetically sealed, Alan, which also allowed me to fry eggs on the top. ;)
Well at least you know it's not the smoke gone missing then :thumb:
;D
It's a dead mobo. Changing PSU and graphics card didn't work, neither did resetting the CMOS, not singling down to one stick of RAM. No RAM did produce an error beep code, but nothing else helped, so new mobo to be fitted tomorrow or Friday.
Quote from: zappaDPJ on Apr 02, 2010, 18:07:49
Sounds like power to me or at worst a motherboard/CPU failure. If it was any other component or a device boot failure you would still have the potential for BIOS entry or the BIOS would be beeping out a merry tune.
That was my second guess! :laugh:
And you were right. With my luck, they'll replace the mobo and discover it was the CPU after all. :)
I still think the smoke has escaped from a resistor or capacitor.
You may be right, but I think it's trapped in the spigot flange...
There's an ointment for that condition available from all good chemists :laugh:
;D
I've got some, but Sue refuses to rub it on. ;)
Quote from: Rik on Apr 08, 2010, 08:52:20
;D
I've got some, but Sue refuses to rub it on. ;)
Jesus rik, dont really need that information thanks all the same.
I'm a very open person. ;)
Sounds like it. :whistle:
And now one of my external HDs has failed. Do you think it's the Friday jinx?
The drive or the enclosure?
I don't know, tbh, Glenn, and can't take it apart to find out.
Update on this. Getting the new mobo took a week, but the engineer came out and fitted it today. Guess what? It made no difference. So, for the moment, he's saying it's a dead CPU and he'll be back on Friday to change it. We shall see on both counts...
Time to ask for a refund/replacement, it is unreasonable to leave you so long without a working PC.
I'm getting there, Alan. :)
Won't that end up being more work for you, getting it all set up again, Rik?
Quote from: Rik on Apr 14, 2010, 19:37:21
Update on this. Getting the new mobo took a week, but the engineer came out and fitted it today. Guess what? It made no difference. So, for the moment, he's saying it's a dead CPU and he'll be back on Friday to change it. We shall see on both counts...
That was also my second guess. Can I just say that if it does turn out to be a loss of smoke that would have been my third guess? :duck:
;D
I still wonder if the PSU spiked and took out the memory and CPU. Testing after the event with a different PSU doesn't eliminate the possibility.
Quote from: Simon on Apr 15, 2010, 11:59:16
Won't that end up being more work for you, getting it all set up again, Rik?
It would, and it would leave me with a mix of OS on the network, which I'm never keen on.
Quote from: Rik on Apr 15, 2010, 12:07:33
;D
I still wonder if the PSU spiked and took out the memory and CPU. Testing after the event with a different PSU doesn't eliminate the possibility.
It doesn't although there should be some degree of surge protection built into the PSU unless it's really nasty.
Well, if the new CPU doesn't fix it, he'll presumably then try the RAM, but meanwhile there's the, slim, chance that the PSU has knackered the new parts. This could be an expensive repair for them. :)
I would have thought that he would have had one of these (http://www.antec.com/Believe_it/product.php?id=MjA4Mw==) in his tool kit, Rik, to check the psu. :)
Quote from: Rik on Apr 15, 2010, 12:25:20
Well, if the new CPU doesn't fix it, he'll presumably then try the RAM, but meanwhile there's the, slim, chance that the PSU has knackered the new parts. This could be an expensive repair for them. :)
Is it an engineer or someone doing guesswork here?
It's a swapsie man, Dorset.
Surely they know the PC model and the parts that it uses and should bring them all out with them so they don't have to make several trips.
Quote from: Rik on Apr 15, 2010, 12:37:16
It's a swapsie man, Dorset.
Gawd, I could send Patrick to do that.
Quote from: psp83 on Apr 15, 2010, 14:09:36
Surely they know the PC model and the parts that it uses and should bring them all out with them so they don't have to make several trips.
They do, but they go for the cheapest option first, Paul. I gather that if it proves to be the CPU, they will put the old mobo back in to save some money...
That might save you a lot of extra work
I thought so too, Steve. :)
Surprise, surprise, no word from the engineer, so I don't think he's coming back today after all. I can feel myself reaching for my copy of the Sale of Goods Act.