New Desktop PC Problems

[The_Reaper]

So, anyone who followed my last thread, knows I've had some recent trouble with my PC.

Well, after doing a complete Windows restore and reinstalling my drivers, I'm having some more issues.

When using Civilization IV, or watching a video in Windows Media Player 11, the PC is likely to freeze for a second, then cut to a blue screen (detailing the problem/error) which only stays for a second, so I can't even view it before it disappears...

And then the computer either remains on while the screen stays black, or else it actually restarts itself without getting caught up on anything.

I tried to go into BIOS earlier, but it even froze there.

This computer isn't even a year old, so the fact that these problems are occurring is worrisome to me. I thought it had to do with the Catalyst Control Center "Mom*****" (FYI, I double checked the program files and there wasn't a separate spyware folder for this program) as I managed to fix the computer slightly when I removed that software.

But now...I'm not sure what the problem is. The boyfriend is concerned that perhaps the intergrated video card on the motherboard may be going; and I'm curious to see whether or not the rest of you agree.

Again, I can usually run the computer fine with programs like Mozilla and iTunes and anything that doesn't seem to be 'graphic intensive'. But the minute I try to watch a video in WMP11 or play Civilization IV (which is fully patched btw), the computer experiences a massive problem.

Thoughts?

 

[T-Rexx]

In the other thread, cityboy-stl recommended you try Puppy Linux, just to prove whether or not this is a hardware vs. software issue. If Puppy (or any Linux distro, for that matter) runs okay, then you can be sure it is a software issue. If it does not, then you can be sure some piece of hardware is failing. I take it you have not taken his advice? I think it is still worth trying.

But, as I said in the other thread, I suspect you are having hardware trouble with some component of the motherboard. It may be the integrated video, but there are many things that could be failing on the mobo.

I don't suppose your computer science bf has a spare video card? The easy way to test his theory would be to disable onboard video and use a plugin video card instead. But I wouldn't go out and buy a video card just to test it - too expensive and too likely that it's some other hardware component.

It may be time for a new mobo. But I wouldn't go out and buy one of those, either, until you have proven the problem is hardware.

 

[The_Reaper]

^

It sounds like good advice, but here's the problem.

Of course, after I posted this, the computer seemed to know I was soliciting advice and proceeded to return to the world of "I'll run perfect for about 2 minutes, then either restart myself or just go to a black screen."

I'm lucky that most of my files are still on the external hard drive I use, as I don't have time to even copy and paste files onto that. (Although there is some data, non-essentially thankfully but still painful to part with that will be lost if I can't fix this and it's a hard drive issue.) As such, I don't think the computer would even allow me to attempt to install Linux.

If it got going, it would likely just freeze or reboot itself mid-way through the process. I can't even get the damned thing to boot into safe mode! I hold down F8 from the beginning of pressing the power button, and instead of getting the Windows boot options, I'm prompted to select what device I'd like to boot first.

After selecting that (usually the hard drive), I continue to hold down F8 but windows just boots normally to my desktop and then proceeds to either freeze or black screen or restart itself.

As for the video card; the boyfriend just replaced his own video card, as the one he was using fried. So, unfortunately, he doesn't have a functioning replacement. Thankfully, all of his friends are computer people, and tend to have parts just lying about; so we're going to start testing the hardware devices on Tuesday...

If we find out it is a hardware issue, I'll be going back to the store where we purchased everything to find out what we can do about it, and whether or not they'll even attempt to fix it under warranty or not (keep in mind, we did put the computer together ourselves from parts we bought from them).

Either way, it looks like I might end up having to replace something...Even though I already did that less than six months ago.

 

[T-Rexx]

As such, I don't think the computer would even allow me to attempt to install Linux.

You don't need to install Linux, just to test the hardware.

You boot (from a DVD or usb drive) and run it "live" - that means it runs from the CD or USB drive only, not your hard drive. Running an OS from a CD drive is a lot slower than running it from a hard drive, but this is just for testing purposes.

All you need is a Linux CD. I bet your bf has one lying about. If not, all you need is access to an internet-connected computer for about 15 minutes, to download an iso and burn it to a blank disk.

 

[The_Reaper]

^

I may very well give that a shot...

Anyways, some updates.

After leaving the Desktop alone for more or less 2 weeks, I turned it on today and it froze shortly after being loaded normally. I was actually able to get into safe mode today, which allowed me to back up some files that hadn't been backed up yet.

It ran in safe mode for what has to be about 5 - 6 hours, before it went to a black screen the tower beeped slightly, but the lights remained on. After attempting to restart, I get a message that I am all too accustomed to seeing on my Dell Laptop:

A problem has been detected and windows has shut down to prevent damage to your computer.

DRIVER_IRQL_NOT_LESS_OT_EQUAL

Technical:
***STOP: 0x000000D1 (0x006E6DEE, 0x00000002, 0x00000008, 0x006E6DEE)

So, before I go through the trouble of installing Linux onto my computer, or rather finding a copy, can anyone tell me just what the hell this means?

 

[T-Rexx]

^ It means Windows has crashed for some reason no one will ever know.

It is either a hardware or a software problem. Since you don't want to test the hardware by running Linux live, I would just reformat and reinstall Windows if I were you. You're probably going to end up doing that anyway.

If it's a hardware problem, you'll continue having the same problem after the reformat and reinstallation. If it's software, the reformat/reinstallation will almost surely fix it.

 

[maxpowr9]

It's a hardware/driver problem. if you post the ".sys" file system error that is in the BSOD, I could figure out which driver. I would just check to make sure all your drivers are updated on your PC. Many times, they don't auto-update. My dad (who is basically computer illiterate) had problems with his graphics card this past weekend and a simple update solved the problem.

You can go into device manager and check everything. Shot in the dark tells me it is the graphics card since it usually crashes when you try to overload it (like people who use two monitors but don't SLI).

I wouldn't dare try to dabble with the windows folder unless you know what you're doing.

 

[Ambrocious]

If your computer is beeping, it could very well be your hard drive. Stop Errors are common with that. It could be your video card too but this sounds like your hard drive.


When all else fails, make sure to install SUPERAntiSpyware and MalwareBytes and do some scans in safemode. This really does sound like a hardware issue though.

 

[Corny]

If your computer is beeping, it could very well be your hard drive. Stop Errors are common with that. It could be your video card too but this sounds like your hard drive.

no it doesn't, and the rest is also not really applicable here. go with maxpowr9's advice please.

boot into safe mode and, if you are lucky it's just a faulty driver and an update will fix it, if you have bad luck the HAL (hardware abstraction layer) is fucked up and you need to reinstall. but I would try a restore point first (programs -> extras -> system something, system restore). if you have very bad luck, it's a piece of hardware - then you need to start singling out what exactly it is. but more about that when you are at this point
since it seems running fine for now .. it could be bad RAM .. it would be weird to result in this bluescreen though .. but if you have some time: www.memtest86.com

 

[rotary]

After reinstalling windows, its important to install the chipset drivers (motherboard) prior to installing anything else. Loading them after installing display drivers for example can cause a lot of hangs.

If its hardware related, Id go with what corny said. Possibly bad ram. Some motherboards sound specific beeps for hardware failures when it cant turn on properly to tell you exactly whats wrong. Check the manual to see what type of failure the beep you heard indicates.

 

[maxpowr9]

If your computer is beeping, it could very well be your hard drive. Stop Errors are common with that. It could be your video card too but this sounds like your hard drive.


When all else fails, make sure to install SUPERAntiSpyware and MalwareBytes and do some scans in safemode. This really does sound like a hardware issue though.

If the motherboard was beeping (usually two short and one long) when he started it up, it would indicate a hardware failure or a bad PCI slot. If it was a HD failure, he wouldn't even get to the bios (assuming he has only 1 HD).

Again, the stop error he posted is related to driver issues 90% of the time. It occasionally is bad RAM but most likely that is not the case.