PDA

View Full Version : PC not booting up and BSOD.



Tsavong
01-11-2010, 19:36
I've recently been having two technical problems with my PC I do not know if they are related or just a coincidence.

Firstly have had a BSOD twice recently with a 0x0000008E error one referenced fltmgr.sys or something.

The other problem I've had is my computer not booting up just given a series or repeated long beeps. After googling my motherboard, FOXCONN, beep codes it says that this this code means a memory error could someone tell me what that is probably going to mean?

I should probably also say that I opened it up and put the hover in to blow out the dust just incise I could see something not that I know what to look for and now its booting up again and ive been able to make this post.

TinCow
01-11-2010, 19:51
Sounds to me like a corrupted system sector on your HDD. How old is the HDD and when was the last time you wiped it and installed a fresh OS?

That said, it could be a lot of stuff. Usually repeated BSODs require some process of elimination. If it is indeed dying RAM, then it shouldn't be too expensive. Depending on what your mobo uses, you can buy new RAM for $50-100 USD.

Tsavong
01-11-2010, 19:56
Thanks for the reply

Two and a half years and never as I have an OEM version of vista and no CD to install it from.

If its any use the beeping would start as soon as I hit the power button nothing would come up on screen. Also I do not know if the two things are related they have just happened at about the same time.

TinCow
01-11-2010, 20:04
Thanks for the reply

Two and a half years and never as I have an OEM version of vista and no CD to install it from.

If its any use the beeping would start as soon as I hit the power button nothing would come up on screen. Also I do not know if the two things are related they have just happened at about the same time.

Has the computer been acting funny in any way prior to this? Booting slower, programs crashing more often?

If you can post the model mobo you have, I can also give you a precise estimate on RAM if that indeed turns out to be the problem. Also, the number and size of your RAM sticks would be useful.

Tsavong
01-11-2010, 20:25
No I can't think of any problems be for now really it boots quite fast still.

My mobo is a FOXCONN 946GZ7MA-1.18KRS2H. It looks like I have two sticks of 1 gig ram as I have 2 gig total.

TinCow
01-11-2010, 20:46
No I can't think of any problems be for now really it boots quite fast still.

Hrmm... might not be HDD then. In my experience, those tend to start going gradually before popping, though a sudden problem isn't unheard of. Plus, 2.5 years is still a bit young for a HDD to die.


My mobo is a FOXCONN 946GZ7MA-1.18KRS2H. It looks like I have two sticks of 1 gig ram as I have 2 gig total.

That mobo (http://www.foxconnchannel.com/product/Motherboards/detail_spec.aspx?ID=en-us0000301) takes DDR2 533/667, in either 1gb or 2gb strips. That stuff is relatively cheap these days. If it's just one of your RAM strips that is going bad, you can replace it for about $25 USD. 533 prices (http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=2010170147%201052408147&name=DDR2%20533%20%28PC2%204200%29)/667 prices (http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=2010170147%201052408745&name=DDR2%20667%20%28PC2%205300%29). If you wanted to upgrade to 4gb total, you'd have to swap out both strips, for a general cost of about $100 USD.

However, before you spend any money, you should check to be sure that's the actual problem. I would recommend running Memtest86+ (http://www.memtest.org/) or a similar memory checker to confirm that you've got a bad stick.

Tsavong
01-11-2010, 21:33
Thanks for the help ill see about testing it. :book:

Tellos Athenaios
01-12-2010, 05:56
You know; the power of search enginges such as Google is marvellous, it really is:

“0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED”

IOW: some software component in kernel space crapped itself. There are many possibilities but since your error messages clearly references a .sys file; a faulty driver is among the more likely of candidates. So you may want to research that .sys file first; and see if you can fix your problems via a relatively simple update or roll-back of that driver.