Blue screen of death, 0x124; Memory tests fine with MemDiag. What next

[Steps]

Hi all,

I have recently started seeing my PC crash; it crashed three or four times today.
When it does, the screen just goes black (no blue screen technically appears), or rather, the PC no longer sends the signal to my monitor.

Nothing was ever overclocked.

I was digging through the files and experiences and now I'm wondering about the next step to take.

BlueScreenView doesn't highlight any drivers as faulty.
Dumpchk wasn't of much help (no probable cause listed), although it does list 0x124.
NTOSKRNL.EXE is what's mentioned by WhoCrashed.

I tried Microsoft's memory diagnostic, it told me it's all good, I then booted MemTest, it also tells me no errors with RAM are there after a couple more runs.

What should I try next?


At times something similar happens - at times when I turn the PC on (press the power button), nothing happens (monitor doesn't get the picture, no boot starts), only the first yellow LED on the case lits up and then it stops.
I then turn it off (long press of the Power button) and turn it on again, and it works. This has been going on for years now, but no other issues were there so I ignored it.

When the BSOD crashes me, it seems as if the PC goes right to that state.

I think hardware failure is likely, but I am unsure what is failing.
And, of course, I might be missing something alltogether.

I attached diag files.

 

[axe0]

Hi Steps,

Make sure that Windows is up to date for security, stability and performance reasons.

 

[Steps]

I have installed all "critical" updates now.

I have then ran the diag again and attached the new diagnostics report.

 

[axe0]

You'll want to update completely, including recommended and optional onces.

 

[Steps]

I am now done with that, and with running another diagnostic.

 

[axe0]

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc /scannow" (without quotes) and press enter
• When it is finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

 

[Steps]

Done all, no integrity violations found.

 

[Steps]

Btw, I'm happy to run these various tests, as it feels like I'm getting somewhere.

Initially I figured, it's most likely RAM; but once it was apparent it's not, I was a bit puzzled about how should (could) I continue.

 

[Steps]

My PC has just crashed again.
It was in the middle of some graphics workings; that's the best guess I have now.

The fans are still rolling, but other than that it just dies. Oddly, no dump file was generated this time. I have not changed anything with regards whether PC should dump anything or not when it crashes (again, I never see the actual BSOD; the picture from my monitor just disappears).

Here is the log.

 

[axe0]

That isn't a B(lue)SOD, but a black screen.

Try to update or reinstall the display drivers.