Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


2nd BSOD in a month

  • Please log in to reply
3 replies to this topic

#1 Zerflamveil


  • Members
  • 35 posts
  • Local time:04:08 PM

Posted 07 March 2018 - 09:45 PM

I was playing League of Legends when my game froze and my computer became on responsive. The audio turned into a loud buzzing noise and I had to hard reboot with the power button the first time. Today it happened again, while playing the same game, but this time I gave the computer time to enter BSOD, but it froze at 100% data collection so I hard rebooted again.


I attached the BSOD file below.

Thank you in advance for the help.


Speccy: http://speccy.piriform.com/results/2qQ7Ugi445iyI0xtMjOOoop

Attached Files

Edited by Zerflamveil, 07 March 2018 - 09:48 PM.

BC AdBot (Login to Remove)


#2 bwv848


    Bleepin' Owl

  • BSOD Kernel Dump Expert
  • 3,029 posts
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:03:08 PM

Posted 07 March 2018 - 10:44 PM

1: kd> !analyze -show 124 0 ffffa688dccea028 be000000 800400
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffa688dccea028, Address of the WHEA_ERROR_RECORD structure.
Arg3: ffffffffbe000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

The very generic 0x124 bugcheck. Dumping the error record architecture we have,

1: kd> !errrec ffffa688dccea028
Common Platform Error Record @ ffffa688dccea028
Record Id     : 01d3ae65d574f8ab
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/8/2018 1:45:07 (UTC)
Flags         : 0x00000000

Section 0     : Processor Generic
Descriptor    @ ffffa688dccea0a8
Section       @ ffffa688dccea180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000001

Section 1     : x86/x64 Processor Specific
Descriptor    @ ffffa688dccea0f0
Section       @ ffffa688dccea240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : a7 06 02 00 00 08 10 01 - bf e3 ba 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ ffffa688dccea240

Section 2     : x86/x64 MCA
Descriptor    @ ffffa688dccea138
Section       @ ffffa688dccea2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 1 Bank 3)
  Status      : 0xbe00000000800400
  Address     : 0x0000380dc9f9215b
  Misc.       : 0x000000000003ffff

which says that there has been an internal timer error on processor three, bank one. You have the most interesting call stack of a 0x124 dump I've ever seen.

1: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff9080`ace2fae8 fffff802`ae71feff nt!KeBugCheckEx
01 ffff9080`ace2faf0 fffff80d`c460148a hal!HalBugCheckSystem+0xcf
02 ffff9080`ace2fb30 fffff802`ae0934b1 PSHED!PshedBugCheckSystem+0xa
03 ffff9080`ace2fb60 fffff802`ae720440 nt!WheaReportHwError+0x261
04 ffff9080`ace2fbc0 fffff802`ae7207a0 hal!HalpMcaReportError+0x50
05 ffff9080`ace2fd10 fffff802`ae72068e hal!HalpMceHandlerCore+0xe0
06 ffff9080`ace2fd60 fffff802`ae7208d2 hal!HalpMceHandler+0xda
07 ffff9080`ace2fda0 fffff802`ae720a60 hal!HalpMceHandlerWithRendezvous+0xce
08 ffff9080`ace2fdd0 fffff802`adf9383b hal!HalHandleMcheck+0x40
09 ffff9080`ace2fe00 fffff802`adf934bd nt!KxMcheckAbort+0x7b
0a ffff9080`ace2ff40 fffff80d`c9f9215b nt!KiMcheckAbort+0x47d
0b fffffe05`daf5cbf0 00000000`00000000 nvlddmkm+0x30215b

Any third-party driver in the stack trace of a 0x124 minidump is a strange occurrence. Here it's your graphics driver (as expected):

1: kd> lm k vm nvlddmkm
Browse full module list
start             end                 module name
fffff80d`c9c90000 fffff80d`cad1f000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvmii.inf_amd64_7805afaeb0300355\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Dec 05 14:28:19 2017 (5A26F353)
    CheckSum:         0103CD2E
    ImageSize:        0108F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I've heard of LoL causing 0x124s before (when the system otherwise runs fine)  so this isn't particularly surprising and is possibly just a bug in the game. I don't have many suggestions here; if it only happens in LoL it must be that bug again. Perhaps uploading the juicy MEMORY.DMP kernel dump file will give us better clues:


• Press and hold the Windows Key + R on your keyboard at the same time.
• In the Run box, type in %WinDir% and hit Enter on your keyboard.
• Find the file MEMORY.DMP and copy/paste it on to your Desktop.
• Zip up MEMORY.DMP (use .ZIP please!!!) and upload it to a trustworthy file-sharing service.

If I do not reply in three days, please message me.
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

#3 Zerflamveil

  • Topic Starter

  • Members
  • 35 posts
  • Local time:04:08 PM

Posted 07 March 2018 - 11:40 PM

I'm curious. What makes my "call stack of a 0x124" interesting?


Link to memory dump: https://drive.google.com/open?id=1ta6QrRnt1qrUGKp_sNbAAPnCXr0IrXfE

Edited by Zerflamveil, 07 March 2018 - 11:43 PM.

#4 bwv848


    Bleepin' Owl

  • BSOD Kernel Dump Expert
  • 3,029 posts
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:03:08 PM

Posted 09 March 2018 - 02:43 PM

This is the first 0x124 minidump I have seen containing a third-party driver in the call stack. :) 0x124s were originally considered "hardware" BSODs, but nowadays I'm see lots of strange things.  A few months ago I was dealing with a system that bugchecked with a 0x124 whenever BlueStacks was run (and only when BlueStacks was run). I found the guilty driver — an AVG driver after a little bit of digging through a kernel dump.

I'm quite lazy to post a full analysis here, but I did notice the following third-party drivers in the "raw stack" of the kernel dump — I would deal with them.

igdkmd64.sys - Intel graphics driver, I'm reluctant to touch graphics drivers unless we really need to
aswHdsKe.sys, aswStm.sys, aswSP.sys, aswbidsdrivera.sys, aswSnx.sys, and aswMonFlt.sys - Avast drivers, get rid of Avast and run their cleaning tool, I'm wondering if their hardware emulation stuff is causing trouble... Windows Defender should kick in automatically
athwnx.sys - wireless card driver
nvlddmkm.sys - your NVIDIA graphics driver, again reluctant to do anything unless we really need to... especially since your machine is a laptop with BOTH NVIDIA and Intel graphics

Edited by bwv848, 09 March 2018 - 02:44 PM.

If I do not reply in three days, please message me.
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users