I'm having really weird blue screens and random restarts, think it may be PSU

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
Hi there.

First of all, based on my research, I'm thinking that this is possibly a PSU issue. However, I have no experience with a failing PSU.

Windows 7 Ultimate
AMD Phenom II X4 965 BE (3.4 standard)
NVIDIA 750 ti
8gb Kingston Ram (4,4) (or 8 gig Gskill ripjaws (2,2, 4), depends on if I'm blaming Ram that day, or 12 if I feel like mixing the sets)
2 WDs 500gb
1 Kingston SSD (has the OS on it)
I don't even know the PSU
Asus M4A79XTD EVO Mobo

Here is a lengthy description of everything that is happening.
My problem is that I'm getting blue screens/complete system freezes/freezes with buzzing whenever I play a game. These have been increasing in frequency. I downloaded some stress testers (Prime95 and Fur), but I cannot even get them going before I randomly restart/blue screen. The computer seems to operate fairly fine under normal conditions though. I can also highly suggest that it isn't a heat problem.

Most of the blue screens are ntoskrnl related (general memory or PSU based on research). I've recently had a CLASSPNP and an NTFS. Sometimes after a hard crash, the computer will fail to bootup beyond the 'starting windows screen.' It will then need manually reset. Sometimes, my computer will then bootup with the MOBO screen saying 'New CPU installed! press X for y and Z for A' Even though my CPU never moved (as far as I know). I've been needing to manually restart quite often recently.

A few weeks ago I decided that it may be dust and fully cleaned everything. Then blue screens were happening often. So after troubleshooting, I just re-seated my RAM and that took care of things for a while. Now... they're back with a vengeance.

This computer is probably about 7 years old. During that time, I've replaced literally everything except the PSU and the MOBO. I also recently clean reinstalled my GPU drivers.


It's because of the random restarts/freezes/age that I am thinking it is the PSU. However, I have NO experience in troubleshooting one. The fact that I can't even initiate stress tests makes me also lean towards it.


For the love of all, does anyone have some insight on this?

Thanks
 
For a 7 year old machine, there's no point in wasting time figuring out the issue. It seems to be a general motherboard failure, but what failure is hard to tell (since it could be memory related as well, due to degraded paths in the mobo... which again is mobo related). You can get a better PC for only a bit more than it would cost to try to replace failed components, so why not start saving a bit of cash and just replacing the whole thing?
 

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
Well I want to troubleshoot it for a couple reasons. Mostly, I can't afford to get a whole new computer at this point and I shouldn't need to get a whole new system either. Everything except the PSU and the MOBO is pretty new. Aside from the money aspect, I'm an extremely.... 'dedicated' Mr. Fixit. I really want to figure out what specifically is causing the problem. I see no point in buying a new system if only the PSU or the MOBO needs replaced.
 

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
Well I've replaced my PSU and I think that has solved most of my crashing. I can run the stress tests without any crashing. I can also play my games without any problems.

But now I'm getting different BSODs.


Since my last post, I have had:

NTFS_FILE_SYSTEM due to Ntfs.sys
DRIVER_IRQL_NOT_LESS_OR_EQUAL due to tcpip.sys
CRITICAL_OBJECT_TERMINATION due to ntoskrnl.exe

I ran a chkdsk on my C drive, and nothing really appeared out of place.

 

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
Look, I appreciate that you're responding, but that would be like getting a new car when all you need to do is change a spark plug. As I said, everything in this machine, aside from the mobo, is less than two years old and hasn't been stressed much at all. It isn't a waste of time or money (in my opinion, that is). By troubleshooting this, I am learning more about how my PC components work together. And spending 6-$700 on brand new everything, when all I really needed was one thing... THAT would be a waste of money.

That being said, I've run into a new slurry of problems. I'm beginning to lean on the idea that my RAM slots on my mobo are bad/going bad. It's dual channel capable and has the order being A1A2 B1B2 (A is one color, B is another). Having played around with slot placement, everything I used to do worked. But, after the nightmare of trying to reinstall windows (described in the rant below), I've discovered that my RAM is only operating when placed in A1 B1 or B1 B2 (I didn't try A1 B2 because that is quite tacky). If I have anything else in any other place, regardless of kit, it will freeze or not boot past the mobo screen (it will freeze before I even get the chance to enter bios). I'm currently running a Kingston kit in A1B1. I'll mention the RAM that I have to test all this with consists of 1 Kingston kit with specs all it's own (2x4gb). Then I have a 2nd kit of 2x2gb Gskill. I have an additional stick of Gskill, from a different kit however, but with the exact same specs as the kit, but is 1x4gb. I know RAM can be picky, but as I mentioned, I've tested all sorts of combinations over the past year, and haven't seen anything like what I've been dealing with over the past 2 days. What has been working, isn't now, which has me thinking RAM slots instead of RAM. Since reinstalling windows, I haven't had any blue screen issues YET, but I also haven't tested much out yet that usually caused them in the past.


*Unrelated rant of frustration below*
I struggled REALLY hard getting windows installed, but that is unrelated. I just want to complain that I tried 4 different programs to make a bootable flash drive (Which I've done multiple times in the past), but they all were read as 'USB hard drives' in the bios menu, instead of removable drives. This resulted in a 1am trip to Walmart to buy DVDrs, and they only had 2 self checkout lines open (no other lines open), there was 12 person line where half did late night grocery shopping. Finally got home, burned that disk at max speed, and the stupid disc was apparently burned too fast because it wouldn't expand the files. Burned a second one at half speed, managed to install windows, then immediately was forced to troubleshoot RAM freezes. This has been the worst chain of 'one thing after anothers' that I've experienced in a very long time.
 

It could be the spark plug change helps, but the actual issue is the timing controller, but that is really because the power cable is having a partial short, but that's because the radiator is broken, etc. The issues you describe are very similar to that, where you could spend months fixing each problem as it crops up.




I did say motherboard failure was likely (check first post), but it'll be hard to pinpoint why the mobo is failing. There's a good chance the root cause was a bad PSU slowly killing your mobo, but who knows how far the damage went.
Here's a few more things you can try:
Reseating the CPU cooler
Underclocking CPU/Memory



And no, new system is only ~$250 considering you have the PSU, case, disks, and OS, since by "new system" it's only PSU+mobo+cpu+memory+case+hdd+os (but you have more than half already, $300 including tier 1 psu)
 

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
I agree that it could be a chain of events that has led to the current situation. However, I still have needed to troubleshoot other issues in order to further pinpoint that it is likely the motherboard. I needed to start somewhere and the PSU was cheapest. Next step in this process is indeed the motherboard. I never ruled out the motherboard, I just want to make that the last option since it will end up being expensive and time consuming. I've never bought a motherboard on my own, so there is a learning curve with specs and stuff.

Do you suggest the reseating and the underclocking because of heat issues? I actively monitor heat and fan speed constantly. Right now I've undone every overclock as well, so I'm fully stock.
 


No, reseating is because AMD chips are notoriously susceptible to pressure induced memory controller issues. Underclocking is to test the VRM on the motherboard
 

gopherkiler9

Reputable
Feb 17, 2015
30
0
4,530
Sorry I just sort of left this hanging, however, the time was not in vain.

Thanks for the input and I will consider doing those when problems arise again. As for the moment I seem to be doing entirely okay. The last thing I did was reinstalled windows and troubleshot the RAM problems. Having not touched anything since then, I haven't bluescreened out or even froze up in any way. If anything happens again I'll attempt the underclocking and see how that goes. Honestly though, if I'm going to reseat my CPU, I'm just going to seat it into a new MOBO. I'm pretty sure one (or possibly two) of my RAM slots are bad/going bad. So even if the underclocking finds something, I'll still have those issues to deal with. For now though, I'm going with the 20 year old car philosophy. I'm just going to drive this MOBO until it dies.

Anyway, thanks for the input. As for now I'll put this thread on dormant for a bit to see if I trigger anymore BSODs.
 

TRENDING THREADS