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

[Slyve]

I apologize, i actually did the Memory testing with Memtest86+ - i wasn't aware that there were different ones.

The Power supply calculator says i need a minimum of 338 Watts and recommends a 388 Watt PSU. I am currently using a 750W bequite PSU (because it was on sale and cost just as much as a 500W PSU, so i bought it. Heard good things about bequite and i am using it for a couple of years now, not sure how long exactly.

I ran Furmark for 15 Minutes and it pushed the GPU quite a bit harder than the Valley Benchmark. Temperature rose up to 68°C after a couple of minutes and stayed there for the duration of the test (again, i googled and people said that 15 min are fine for a stability test) If you think a longer test could yield better results, let me know and i will torture the GPU a little more.

When i took the Screenshot (i ran it in FullScreen), Closed Furmark and pasted the Screen into Paint, it actually showed Chrome beneath the actual Test. Not sure what that is about.

I am running Prime95 right now (can you hear the CPU screaming in the background?) and the Temperature just passed 40°C and is climbing rather slow from there on. I will let it run for the 2 hours stated in the Tutorial and then I'll try FurMark again. Maybe in windowed mode, so i can get the Screenshot.

Edit: Here is the Speccy Snapshot ( http://speccy.piriform.com/results/dvdXTeAFEON7enZUsKuRAnR )

Keep in Mind that the Snapshot was taken while Prime95 was running, the idle Temperature of the CPU is pretty much at room temperature. Never really paid attention to it when it wasn't being stressed, but i think it usually hovers around 15-20°C.

Edit2: I just ran Prime 95 for about 2 hours and it failed to produce the requested log file because i'm an Idiot and ran it straight out of the archive without extracting it first.

It's past midnight and i am tired, i will run it again tomorrow. In those 2 Hours, the CPU performed perfectly and the Temp never rose above 43°C.

Could it be that it is somehow the Game itself that causes the Error? (EU4 causes the Crash way more often than other games, i just assumed it's because it's a lot heavier on the CPU than other games.)

 

[Arc]

If you havent got any error/crash/BSOD etc during all those tests, then tests are all ok.

About the game, yes, it is possible that a poorly coded game can cause a stop 0x124 BSOD.

 

[Slyve]

If you havent got any error/crash/BSOD etc during all those tests, then tests are all ok.

About the game, yes, it is possible that a poorly coded game can cause a stop 0x124 BSOD.

I guess i will just try it out by playing something else for a while. Maybe i can even find something that is equally demanding on the CPU and see if the crashes happen again.

One last question, is there any kind of tool that i could use while the game is running to figure out if it actually is the game itself? Some sort of real time logging tool or something similar?

In any case, thank you very much for your help and all the time you spent helping me! I really appreciate it. I don't think I'd have gotten this far without your help!

 

[Arc]

One last question, is there any kind of tool that i could use while the game is running to figure out if it actually is the game itself? Some sort of real time logging tool or something similar?

I am not aware of, but I will see if anybody else can tell anything about it.

 

[Layback Bear]

What I have noticed.

Looking at Speccy.
It shows very low 12V (9.864V) and very low vbat at 1.6V

Check the voltages in Bios.
Check your motherboaed bios battery. I should be 3.0V or very close. (Cmos battery)

Voltage
CPU CORE:
1,188 V

DRAM:
1,500 V

+5V:
5,010 V

+12V:
9,864 V

+3.3V:
3,288 V

CMOS BATTERY:
1,608 V

 

[Slyve]

The MB isn't that Old. About a year ago my old one went belly up, so the MB is 1,5 years old, tops. I never thought about the fact that the BIOS battery may have something to do with it.

Unfortunately i have no idea about the voltages or even where to look for them in the BIOS, so i just went through all the menus and took a picture of every voltage display i could find! (It was never something that came up for me, so I don't really know anything about the voltages)

I hope this is the Info that you were looking for.

 

[Layback Bear]

According to your bios your 12V & 3.3V are good.

Check and see if speccy program is up to date.
Their is a chance it's not working properly with your motherboard.

A motherboard battery can be bad when it new or last for years.

If was me I would just use a DVOM and measure the volts.

 

[Slyve]

I checked with another tool again and it shows the same voltages as my bios. It appears Speccy doesn't like my board all that much.

In any case, all of this seems to point in the direction of the game suffering from crappy coding, which i wouldn't have thought of in 10 more years of error hunting, to be honest.

As long as the error doesn't happen in other applications, i think i found the bad guy.

Thanks again you two!

 

[Slyve]

Well, looks like I'm back where i started. It isn't the game, other games cause the crash as well.

I have no idea what else i could try and am pretty much ready to just give up and deal with the fact that my system just won't be stable. Someone told me that i could try to bump the voltages on the CPU and RAM, but I'm reluctant to mess with that. I have no idea about overclocking or voltages so i don't want to risk frying my system because i screw something up.

Is there anything else i could try?

I just can't afford buying new parts for testing or pay a technician to take a look at it. Also, since the error is random and i haven't been able to reproduce it on purpose, i doubt that would even be an option.

 

[Layback Bear]

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

 

[Slyve]

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]

How far have you gone through the http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 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.

 

[Slyve]

How far have you gone through the http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696 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]

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.

 

[Slyve]

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!

 

[Arc]

The rev. 4.1 is motherboard revision. It can be known from the box of the board, if you are not sure about it.

If stop 0x124 BSODs occur during gaming only, the things you need to check are Graphics card, PSU, CPU and temperatures. But post #21 minimizes them.

May be, in my best guess ... they are failing to take the load of the games, but work fine elsewhere.

Make it sure that there is no dust allocation inside the computer. That may also cause it.

I would suggest you to document the results of Furmark and Prime95 with screenshots and log files, too.

 

[Slyve]

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.

 

[Slyve]

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)

 

[Slyve]

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.

 

[Slyve]

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.