Different BSODs in ntoskrnl.exe, (Codes: 0x3b - 0xc5 - 0x124)

Layback Bear said:

If you are getting more BSOD please post new logs so Archie can have a look.

Alright, sorry. It's always the same 0x124, so i didn't think of posting more Dumps. My bad.

I packed all of the dump files i currently have in a zip archive. They're all the same 0x124 Error over the course of a little over 2 weeks.

Arc said:

How far have you gone through the Stop 0x124 - what it means and what to try guide?

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

That is pretty much the only thing i haven't done yet. I don't have access to parts to do that and i currently don't have the money to buy new parts just for the purpose of testing. I'm currently asking people i know if anyone else has parts that i could use for testing, but so far I've had no Luck.

I was still hoping that it would be possible to determine the faulty piece of hardware another way.

Arc said:

Can you perform a clean reinstall?

First boot into the BIOS and set it to defaults. How To Clear CMOS (Reset BIOS) [Easy, 10 to 15 Min]

Then perform the clean reinstall. When it is a vanilla install, see how it does. If it BSODs in this state, the issue is from the part of hardware components like PSU, CPU, RAM or the motherboard itself. (memtest86+ should minimize the possibility of a failing RAM, with running at least 8 consecutive passes).

Then add the hardware drivers. Not from the driver CD but from GIGABYTE - Motherboard - Socket AM3+ - GA-78LMT-USB3 (rev. 4.1)
Add the drivers one by one ... see at what point the BSODs are coming back.

Then add other hardware (if any) and programs .... one by one. See how it goes.

It will be a time consuming and long process .... but let us expect that it will work.

What does the (rev. 4.1) after the Model number of the Motherboard mean? Last time i did a fresh install, i used the ones from the (rev. 5.0) Page.

I think the reinstall i did was a clean install. I never changed any settings in the BIOS.

The PC runs fine with a clean install, but the crashes only occur while playing games. (Even now it is stable, as long as i don't play anything. It never crashed while being idle.) Mostly newer ones that are more taxing on the Hardware. Older ones crash, too, but not quite as frequently.

The last time i installed only the Drivers and one game, just to see how it goes and the PC crashed without anything except those things installed.

I think i will try it again, though. Maybe the installation wasn't as fresh as i thought or i missed something.

Guess i will do that this weekend, then i should have plenty of time. Until then, thank you again for your time!

Alright, i will do the tests with Furmark and Prime 95 again. This time i will let FurMark run for about an hour or maybe more. Maybe 15 min was just not enough to trigger the error.

Right now i am trying to figure out how to take a damn screenshot with FurMark. Since the F9 key doesn't seem to save them anywhere (or it just isn't working at all) and whenever i use the print-screen key, it takes a screenshot of my desktop beneath FurMark. I will probably end up taking a picture with a camera.

Also, this time i will extract Prime 95 before doing the test, so it can save a log file.

If this fails, i may be able to borrow an old Geforce GTX 275 from a Friend on the Weekend. I don't really know why, but i always suspected the GPU. I hope I am wrong, though, because the GPU doesn't have warranty (I bought it second hand. It was still new when i bought it, but since it was a private transaction, there's no warranty) which means i couldn't do anything about it right now.

I will continue to look for parts for testing and will post back when i have the results of the Furmark and Prime95 tests.

So, after i ran FurMark for an hour and used GPU-Z for logging purposes (in addition to the screenshots) i noticed some very weird voltages values. They sometimes jumped into the negative, which, to me, as a guy who has no real idea of what this could mean, seemed pretty strange and noteworthy.

So, here is the GPU-Z Log File and the 2 Pictures i took of the FurMark Interface after it ran roughly an hour (The values reached these points within minutes and then pretty much stayed constant.)

Will post back once Prime 95 is finished.

(I packed the .txt into a zip because after an hour of logging one line every sec, the file got bigger than 1MB)

While the Prime95 stress test was running, i noticed some really weird voltages values again. I used PC Wizard and Speccy to compare them, since Speccy seemed to give wrong values the last time.

This time, they are pretty far apart so i am beginning to wonder if there is something wrong with the PSU after all. See snapshots of the voltage values. I aborted Prime 95 and will open the PC again. Maybe i overlooked something the last time. If nothing else, i will check the voltage on the CMOS battery itself and confirm that all plugs are sitting tight just where they belong.

At this point, i just want the PC to crash during something specific, to be honest. The not knowing is what's really frustrating.

Just opened it up and posting from my phone right now. First thing i noticed was this. The 12v connector of my PSU has only 4 pins but the MB has 8. Please tell me this isn't it, because if it is, I'll probably cry.