HX520 possible problem

[Uriel]

I have a HX520, just over a year 1/2 old and I suspect it may be causing me problems. Just wondering if the best cause of action would be to buy a new PSU to test and if it turns out the old one is faulty to RMA it?

The problem I have happens intermittently. The computer will occasionally reset itself, or give a 0x00000124 BSOD. Sometimes the BSOD is reset before the memory dump has time to complete itself. The resets don't always result in a boot and sometimes the PC will just sit there with fans spinning but fail to post. The same thing sometimes happens if the PC has been off for a while.

The problem seems worst after a cold boot and starting up can be problematic. Crashing after a cold start sometimes happens frequently. It can take 3 or 4 attempts to get everything up and running, sometimes making it into Windows, sometimes not. Once the PC is up and running it can usually keep going for hours. It's usually completely stable at this point and I can game or benchmark for hours without a problem. If crashes happen after the PC has been on a while it's usually during less intensive tasks or while the PC is idle.

The problem is certainly intermittent. It's been happening on and off since last summer. Sometimes it won't happen for weeks and then I'll get several crashes in a day or two. This happens in both my Windows XP and Vista installations.

So far have reseated most components (and given things a bit of a dust out with compressed air), changed RAM (the old RAM has been running problem-free in a friend's PC since). Additionally the graphics card and soundcard have both been upgraded since the problems started with no change in results.

Along with the PSU, the prime suspects are now the motherboard and CPU. Also considering the possibility of a hard drive problem. Prior to the start of these problems the PC had run with 100% stability, problem free, through several upgrades and including the Vista installation.

[Yellowbeard]

I Googled the error and most of the solutions point to a sound card related issue. You may want to study the posts related to that error code and see if any of it applies to your machine.

[Uriel]

It's possible. That was one reason I changed soundcards. I've used a Creative Xtreme Music, an Asus Xonar and an Auzentech X-Fi Prelude since the problem started. All had the same results. Used different PCI slots too.

Drivers have been thoroughly cleaned etc.

Soundcard isn't the only potential issue though. Googling points to any number of potential problems. There's a lot of people that think they've solved it, only to continue to have problems later.

I've even convinced myself that the problem was solved a couple of times, only for it to happen again eventually.

Edit: as for graphics cards - I read somewhere it was an nVIDIA issue so I swapped out my 8800GT for a HD4850. Same results.

Further Edit: Oh yes, and hours and have hours looking up the offending error code.

[Yellowbeard]

In general, it does not sound power related based on your description. But, if you have access to another PSU it would be a logical move to test the PSU to eliminate it as a suspect.

[Cyber-Mav]

my creative labs sound card gave me those issues but then i took it out and used the onboard realtek sound and all my issues went away. as mentioned above it would be best to check on the sound drivers first.

[Uriel]

As stated, I don't think it's a sound issue. Have been through 2 different X-Fi Xtreme Musics, 2 X-Fi Preludes (currently using the second) and a Xonar D2 all with same issue (I enjoy messing with soundcards...). Drivers thoroughly uninstalled and cleaned between card changes.

However, I don't think it's the PSU either now. I think it's down to some sort of problem with my weird 939motherboard / AM2 daughterbord setup. After recognising that moving the machine can both cause and allievieate the issues, I had a gentle wiggle of a few components and found I could replicate the crashing when disturbing the daughterboard. Best case scenario - it needs reseating. Next best case would be a damaged daughterboard as I have a spare. Hoping it's not damage to the slot on the motherboard because replacing that will be more of a pain.

Funny, I used to expect the odd crash but after, first building this current setup, I was BSOD free for the best part of 2 years (including the first few months after the AM2 upgrade). It kind of lowered my tolerance level to that sort of thing.

Edit: Swapped out AM2CPU expansion board for the spare. Looks thermal paste spread may not have been my best effort last time. Fingers crossed...

[Uriel]

Swapping out the AM2CPU board for the spare and reseating the CPU seems to have solved it. At least 3 weeks since my last BSOD or reset.

[12GaugeShotty]

A PSU will never cause a BSOD. Those are mostly driver problems.

[GoNz0]

the 124 error is the "im not really sure but its hardware related"

i get it when im overclocking a little to much.

[Uriel]

Timely response guys .

As stated the problem was solved. Never had another BSOD on that rig until one of the lugs was snapped off my my Arctic Cooler Freezer 64 Pro's excessive clamping a few months later (inside the case, unbeknownst to me...). Those BSODs were definitely hardware related though - just not the PSU