Possible motherboard failure? Replace or attempt to fix?

mustang-wolf · Jun 30, 2016

Okay, so I have been having problems for a while now.

When gaming, I would get a short beep. Lower tone than the startup beep, little longer I think. Shortly after the beep, the game then freezes. Audio, however, continues. Eventually, I started getting BSODs.

Now this happened a lot, and given the fact that loaded assets were still working (a loading circle would still spin, or the audio would continue to play) and my RAM meter was almost entirely empty, I figured I was just running out of RAM. So I bought more.

I installed it yesterday and it registered fine. Except now the beeps and freezes were more frequent. And I was getting BSODs at the slightest bit of stress. Even when only booting.

STOP: 0x0000001e 0x00000000 0x00000000 0x00000000

Booting also now took at least fifteen minutes. The splash screens would beep and freeze and everything.

So I decided I probably had outdated drivers. I downloaded a driver for my motherboard (MSi 760GM-P34 FX). Well, I tried to. I was downloading through Firefox and the computer froze. Like old XP style mouse won't even move frozen. I didn't realize until 20 minutes later that the clock on the monitor still said 7:58:02 even though the laptop was at 8:15.

I decided to try again, this time in safe mode with networking. However, after selecting that it starts loading drivers. This is normal. What's not normal is that it stops loading at CLASSPNP.SYS and the screen starts... Bleeding? From the top down, it starts turning to black static.

I did this three times. Same result.

So, deciding I was going to simply try downloading the update again in normal mode, I rebooted again.

Well, I tried to. The first time it went to the motherboard splash screen, then checkdisk (which I skipped because it always does this, even after letting it do it's thing), then nothing. Display switched to the main TV, I know because it woke up and the boot screen is the left TV for some reason, but there was nothing. A black screen.

I rebooted again. Nothing. No power to the USB ports, no display output, not even a beep to show that it's booting.

So that's where I'm at. A computer that's pretty much dead, I have no idea what could have caused it, and I don't even have a way to check. The only thing I can think of is that my motherboard just kinda kicked it, but I don't exactly want to spend the only bit of change I have on a motherboard that might not work if it turns out to not be a problem with the mobo at all.

So, advice?

cin19 · Jun 30, 2016

0x0000001e is the hardware problem, and from what you said, like CLASSPNP.SYS --damaged registry system files, like checkdisk when boot up---hard drive problem. And I guess your hard drive may have problem.

So try the Bench it - Troubleshooting http://www.tomshardware.com/faq/id-1753671/bench-troubleshooting.html to see you can boot the PC without the hard drive or not.

mustang-wolf · Jul 1, 2016

cin19 :

No need to bench. I know what the problem is now.

Question is... How the hell do I fix it?

Right, so it's my harddrive. Severe corruption. This explains a lot. Even my left monitor no longer displaying even though it's fully hooked up and detected. Some Nvidia files were also corrupted, as practically yelled at me by error boxes on boot. I ran a CHKDSK and was able to find the corrupted sectors. This is great, as it means I should be able to fix it without losing everything.

Or so I hoped. Obviously it can't fix it while the harddrive is being used, this is fine. I set it to check and repair on reboot.

I rebooted. Nothing happened. Same problem as before, except it loads Windows fine. You know, except for all the error messages and blue screens.

But no motherboard splash screen, no DSKCHK, nothing. This is a HUGE problem, as the only way to fix this is to let DSKCHK do it's thing on boot. Unfortunately, I can't let it do it's thing anymore. Or at least if it is doing it's thing, I can't see it because my damn monitor won't work.

I'm going to try unplugging said monitor and see if it defaults to the DVI one on the right. Actually, I've just unplugged it and set CHKDSK to run on boot as typed this. Restarting as soon as I post this.

Oh, and it didn't bluescreen while I did all that and typed this out. That's a plus. Maybe it can hold out until I fix this. and I won't have to lose.. Four years of work...

You know, you'd think having this much stuff, and being so afraid to lose it, I'd have a drive to back it all up to by now. Guess that shows how smart I am. I have a 250GB drive I can try to slave in if all else fails. Back my FL Studio folder onto that and still have a little bit of space left.

Wish me luck.

-----------------------------------------------------------------------------------

I was right, it was trying to display on the left monitor, even though the left monitor apparently doesn't exist. Oh well.

Anyway, I got the "Chkdsk could not be performed due to a recently installed software package" bit. Unspecified error with a code too long for me to memorize. I'll look it up.

mustang-wolf · Jul 1, 2016

Update: I was going to do a repair through USB when it suddenly froze. Now it won't boot.

I finally got it to boot after leaving it for a half hour, and it was showing an option for windows repair. So I did it. It blue screened. I got a 0x50 code and it referenced wimFsf.sys. Now it no longer boots. Instead it beeps three times. Long higher pitched beeps. Nothing after that. From what I know, this is a RAM issue. But it shouldn't a RAM issue. The stick in there is brand new, and I've had no problems with it.

So so far I've gotten a 0x1e BSOD, a 0xe7 BSOD, a 0x50 BSOD, and a RAM failure beep code.

Ugh. I'm starting to hate computers.

johnbl · Jul 1, 2016

a failure in wimFsf.sys would mean a corrupted or unreadable windows image file.
if the usb image is being corrupted then the problem will not be your hard drive itself.

I would start with the basics,remove any hardware you do not need to boot. reset the BIOS to defaults and reconfigure, get the machine to boot correctly into bios.
check the systems voltages. Then boot and run memtest86 on its own boot image.
(make sure your BIOS sata mode is set correctly)

mustang-wolf :

mustang-wolf · Jul 8, 2016

Okay, so it was harddrive failure. I found out when the drive finally kicked it.

Well I decided to use the harddrive from my laptop so I could play simple games like RWBY: Grimm Eclipse until my new harddrive arrives. However, something strange happened.

I can use this harddrive fine on the laptop it came from, as I'm typing this post on it now. But when plugging it into my desktop, it gets to the "starting Windows" screen, then suddenly bluescreens. It flashes so fast that I can't get the code. It didn't put a file in C:/Windows/Minidump either so I can't even find out what caused it.

And idea what could cause that? This harddrive has Windows 7 Home Premium 64 bit on it.

Search

Possible motherboard failure? Replace or attempt to fix?

mustang-wolf

Reputable

johnbl

cin19

Titan

mustang-wolf

Reputable

mustang-wolf

Reputable

johnbl

Polypheme

mustang-wolf

Reputable

TRENDING THREADS

Latest posts

Moderators online

Share this page