• Computer taking a half an hour to POST? Motherboard fucked?
    19 replies, posted
So I lightly dusted the fans and dust filters of my computer today and the I turned it on and started using it. Then I attempted to put it to sleep, and it just sat there at the blue hummingbird Windows 7 screen. I turned it off by holding down the power button. I turned it back on and it didn't POST at all for five minutes. After five minutes of waiting, the MSI splash screen finally displayed. Windows asked to please be booted in safe mode, so I did and system restored to earlier today. I did some homework and tried to print it. Printer wasn't recognized in any way, shape, or form, so I try to shut down, but it doesn't so I turn it off by holding the power button. Then I turn it back on. Nothing is displayed for half an hour (which I passed weeping softly at my desk). Windows asks to be kindly booted in safe mode, but hell with that and I start it up normally. It works fine now that it's on, but a window appeared saying Windows has recovered from an unexpected shutdown and this is the error it dumped. [QUOTE]Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 1000009f BCP1: 0000000000000004 BCP2: 0000000000000258 BCP3: FFFFFA80066CC660 BCP4: FFFFF80000B9C3D0 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Files that help describe the problem: C:\Windows\Minidump\051213-12916-01.dmp C:\Users\Xander\AppData\Local\Temp\WER-87142-0.sysdata.xml Read our privacy statement online: [url]http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409[/url] If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt[/QUOTE] Speccy. [IMG]http://puu.sh/2NOLq[/IMG] oh god help, if I need to replace the motherboard it's not too much of a hardship because it was like 75 USD.
Try unplugging everything besides monitor & power. Then try booting. If it doesn't POST almost immediatly you have a problem.
Mind uploading the .dmp? It holds some useful information about the crash. Also it's a driver error that caused it, iirc the .dmp usually explains which driver.
MAYBE your hard drive is at the point of failing, I have a HP computer which had a failing hard drive. It took a lot of effort for it to read the damn thing :C Maybe your system has a hard time to detect & boot the hard drive? Try completely unplugging it, and see if your system still takes such a long time to go through the POST.
Definitely sounds like the beginning stages of a hard drive failure. If I was you, I would find a secondary drive that you can use to pull as much data to as you can before the hard drive stops being able to be read.
If it is your hard drive failing, did you give it a lot of hard-shut downs or whatever else is bad to it?
I'm afraid to turn the computer off in case it never turns back on. Also, I got this computer like a month and a half ago so I'd be pretty pissed if the hard drive failed. Here's the .dmp (sorry for Dropbox) [URL="https://www.dropbox.com/s/wjpnxafepjxulhu/051213-12916-01.dmp"]https://www.dropbox.com/s/wjpnxafepjxulhu/051213-12916-01.dmp[/URL] [editline]13th May 2013[/editline] I'd also like to emphasize that once it's started up, everything works exactly the same. I've run Portal 2 maxed at the same performance it had before, and the maps load just as quickly. [editline]13th May 2013[/editline] Should I check motherboard headers?
Maybe you knocked something loose. Check all your connections.
I would go with HD failure. You should run HD Tune and look at the S.M.A.R.T. data on the drive to see if there are any reallocated sectors or other problems.
The problem has disappeared, I changed the boot order to having the HDD first. It was booting from USB first and I think it was trying to boot from my printer. I'll look at my hard drive data though [editline]14th May 2013[/editline] I don't really know what I'm supposed to be looking for, so here's screenshots from all four tabs. [IMG]http://puu.sh/2TEFp.png[/IMG] [IMG]http://puu.sh/2TEFK.png[/IMG] [IMG]http://puu.sh/2TEGn.png[/IMG] [IMG]http://puu.sh/2TEIK.png[/IMG]
Well, that looks perfectly fine, no need to get a new one.
Try to run some diagnostic tools from Western Digital, you never know what different tools show up. You really need to be sure if it is the hard drive at failure here, OR your SATA controller is in a bad condition.
[QUOTE=Merijnwitje;40650598]Try to run some diagnostic tools from Western Digital, you never know what different tools show up. You really need to be sure if it is the hard drive at failure here, OR your SATA controller is in a bad condition.[/QUOTE] Really doesnt sound like a drive/controller issue if switching the boot priority fixed it. The absolute best test of course, would be to return the boot order to USB first and unplug your printers USB cable. If that fixes it you know for definite it's the printer causing it.
What do you mean by didn't POST for 5 mins? Did not start POST for 5 mins or it took 5 mins to finish? I would reseat memory/CPU. If POST started, but took 5 mins to run, I would look at where it seems to be hanging up for a clue, i.e. if it is looking at the hard drive, go there.
[QUOTE=metallics;40650624]Really doesnt sound like a drive/controller issue if switching the boot priority fixed it. The absolute best test of course, would be to return the boot order to USB first and unplug your printers USB cable. If that fixes it you know for definite it's the printer causing it.[/QUOTE] Uhm, what printer? I don't have one. [editline]15th May 2013[/editline] Oh wait that printer, I missed that he had the printer messing it up.
[QUOTE=tina the baker;40651822]What do you mean by didn't POST for 5 mins? Did not start POST for 5 mins or it took 5 mins to finish? I would reseat memory/CPU. If POST started, but took 5 mins to run, I would look at where it seems to be hanging up for a clue, i.e. if it is looking at the hard drive, go there.[/QUOTE]It was completely blank for half an hour before anything was displayed onscreen.
it could just be a USB drive that you had plugged in, sometimes they can delay startup by a ton of time
This issue is pretty common IMO, I've fixed it multiple times by disabling USB legacy support on Asus Mobos. Changing boot order is a pretty lucky fix though didn't work for me.
This hasn't recurred, I'll say solved
Sorry, you need to Log In to post a reply to this thread.