BSODs quite regularly. Stop codes: 0x00000124, 0x0000003b

Hi,

I've recently had my PC decide to BSOD every once in a while. Time frame and cause undetermined. Sometimes it's once in every few days after many hours of gaming, others it is several times in a few hours while idle.

So far I've encountered stop codes:
0x00000124
0x0000003b
0x0000001e

and I think there was also a 0x0000005a at some point but I have since wiped my install drive. I think the cause is my graphics card but I'm not certain.
Updated the drivers a few weeks ago and ever since, no matter which drivers I am on. Clean install or no, fresh install of Windows or no, I am getting BSODs.
Perhaps the card has become damaged? I dunno. I just need pointed in the right direction.

Only got 3 dump files at the moment, as all my others were on previous Windows installations and I failed to back them up but rest assured more will come if they are needed to solve this.




OS: Windows 7 Professional x64 - Retail (well, MSDN AA)
Latest install is maybe a week or so old. I can't remember. Wiped so many times.

CPU - i5 2500K
MB: Asus P8P67 Pro 3.0
PSU: Corsair AX850
Install drive: Crucial M4 128GB in AHCI mode
GPU: Palit GTX 460
SPU: Auzentech X-Fi Prelude + whatever onboard the MB has

Everything apart from the GPU and SPU are about two months old.
GPU about 6 months and the SPU, a few years?



Oh, and the attached health report says I don't have any AV/AM/Firewall but I'm on MSE, Search & Destroy, Malwarebytes and Commodoo Firewall and the system is, as far as I know, clean.

Any help will be appreciated.

Hello,

I've tried all of that bar removing components.
Stress tested CPU, GPU and ran through memtests clear, everything seems to be fine and then a day later I'll BSOD while browsing explorer or something equally light.

I'll see if I can grab a GPU from somewhere to replace the 460 in case it's that, that is causing the issue but in the meantime I'll rip out the rest of the components and see what's what.
I've heard a few times that 124 is different from the rest of the stop codes in that it doesn't point to any issue exactly and is more of a 'No, bad! Hardware!' kinda thing. Is this true?
I was hoping someone more knowledgeable about dumpfiles/BSODs would be able to pinpoint the issue but if that's the case then I guess that's out the window.

Not had a BSOD in quite some time now, think the problem is solved. Despite passing numerous stress tests, and being perfectly fine for two months before hand, I found my CPU to be unstable at its (now) previous vcore.
I can understand not being stable at a given voltage but being fine for two months and then all of a sudden not so? Oh well. All good now.