BSOD playing Path of Exile Stop: 0x124

Page 1 of 2 12 LastLast

  1. lukloko
    Posts : 11
    Windows 7 Ultimate x64
       New #1

    BSOD playing Path of Exile Stop: 0x124


    I've recently installed a new Motherboard (Asus Z97), cpu (i7 4770-k) and 1 dimm (Corsair vengeance 8Gb 1600Mhz) to my previously broken PC. I had to install windows on my HD, since my previous one is not compatible with my new motherboard.

    I have since received several (4?) BSOD over a few days, mostly while playing PoE, but also in one other game if I remember correctly.

    I know for a fat the problem is not overheating, since after the first BSOD I replaced my thermal paste and monitored temps and the temperature at the crash was at about 45C.
    On another note, my temperature during games hovers around 65C--is that a problem?

    Help? D::
      My Computer
    Quote Quote

  3. Brink
    Posts : 72,041
    64-bit Windows 11 Pro for Workstations
       New #2

    Hello lukloko, and welcome to Seven Forums.

    Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help. :)
      My Computer
    Quote Quote

  4. lukloko
    Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       New #3

    Hmmm. I did, and I thought I'd uploaded the file, but apparently .zipx files can't be uploaded. Here's the .zip version.
      My Computer
    Quote Quote

  6. carwiz
    Posts : 4,161
    Windows 7 Pro-x64
       New #4

    Update to SP1. It contains many critical updates to hardware drivers including HAL and DX.
      My Computer
    Quote Quote

  7. lukloko
    Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       New #5

    Thanks! If I have any more problems, I'll post here again.
      My Computer
    Quote Quote

  8. lukloko
    Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       New #6

    I'm afraid that didn't work.


    Edit: also, I just installed a new gtx 760. Is that relevant?

    Also, it seems windows repair does not seem to work. It says something about the disk not being compatible with my version of windows, but that is plain untrue. I installed windows with the very same disk.
    Last edited by lukloko; 05 Jul 2014 at 12:19. Reason: wrong zip
      My Computer
    Quote Quote

  10. carwiz
    Posts : 4,161
    Windows 7 Pro-x64
       New #7

    Apparently, neither did your update. (See below) I'll see if one of our update gurus can take a look and verify.

    The Bug Check Code you're getting is 0x124 which is a hardware error. The dump is indicating an L0 Cache error on the CPU. However, I don't read Spanish so I couldn't review the logs to determine if this is being caused by elevated temperatures or perhaps errors on your memory modules or disk(s).

    You might run Memtest86+ for a minimum of seven passes, eight preferred, to eliminate the memory.
    Also check for dust accumulation on the CPU cooler and fan.

    Code:
     
2014-07-05 13:01:14:533  152 1c4 Shutdwn user declined update at shutdown
2014-07-05 13:01:14:533  152 1c4 AU Successfully wrote event for AU health state:0
2014-07-05 13:01:14:533  152 1c4 AU AU initiates service shutdown
2014-07-05 13:01:14:533  152 1c4 AU ###########  AU: Uninitializing Automatic Updates  ###########
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:533  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:549  152 1c4 DnldMgr FATAL: DM:CBitsJob::SetCallbackHandler: SetNotifyInterface failed with 0x80010108.
2014-07-05 13:01:14:783  152 1c4 Report CWERReporter finishing event handling. (00000000)
2014-07-05 13:01:15:251  152 1c4 Service *********
2014-07-05 13:01:15:251  152 1c4 Service **  END  **  Service: Service exit [Exit code = 0x240001]
2014-07-05 13:01:15:251  152 1c4 Service *************
2014-07-05 13:05:02:657  504 145c Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0300)  ===========
2014-07-05 13:05:02:726  504 145c Misc   = Process: C:\Windows\system32\svchost.exe
2014-07-05 13:05:02:745  504 145c Misc   = Module: c:\windows\system32\wuaueng.dll
2014-07-05 13:05:02:657  504 145c Service *************
2014-07-05 13:05:02:876  504 145c Service ** START **  Service: Service startup
2014-07-05 13:05:02:976  504 145c Service *********
2014-07-05 13:05:04:670  504 145c Agent   * WU client version 7.6.7600.256
2014-07-05 13:05:04:671  504 145c Agent   * Base directory: C:\Windows\SoftwareDistribution
2014-07-05 13:05:04:671  504 145c Agent   * Access type: No proxy
2014-07-05 13:05:04:674  504 145c Agent   * Network state: Connected
2014-07-05 13:05:05:430  504 145c Setup WARNING: SelfUpdate is in an error state
2014-07-05 13:05:53:708  504 145c Report CWERReporter::Init succeeded
2014-07-05 13:05:53:708  504 145c Agent ***********  Agent: Initializing Windows Update Agent  ***********
2014-07-05 13:05:53:761  504 145c Agent ***********  Agent: Initializing global settings cache  ***********
2014-07-05 13:05:53:761  504 145c Agent   * WSUS server: <NULL>
2014-07-05 13:05:53:761  504 145c Agent   * WSUS status server: <NULL>
2014-07-05 13:05:53:761  504 145c Agent   * Target group: (Unassigned Computers)
2014-07-05 13:05:53:761  504 145c Agent   * Windows Update access disabled: No
2014-07-05 13:05:53:919  504 145c Agent   * Found 21 persisted download calls to restore
2014-07-05 13:05:54:868  504 145c DnldMgr Download manager restoring 21 downloads
      My Computer
    Quote Quote

  11. lukloko
    Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       New #8

    I got 2 more BSOD identical to that last one.

    I don't understand. Shoud I try to reinstall the SP1? I just did a windows memory check and no problems it seems.
    It seems the BSOD changed after I updated.

    My temperatures are hovering at 40C, so I doubt that's the issue.

    I'm downloading more updates it seems, so I'll let that finish and then tell you if anything changed.

    Ah, and I'm running 2 x 2Gb memory sticks with frequency 1333 and 1 8Gb with 1600. Is that a problem?
      My Computer
    Quote Quote

  12. carwiz
    Posts : 4,161
    Windows 7 Pro-x64
       New #9

    Window's memory tester doesn't sufficiently test memory. It's more for gross failures. Memtest86+ does a more detailed test over time. The different modules could cause a problem but usually, the memory will just run at the slowest compatible speed. Compatible is the key word and may not even reach the slowest of the modules. This could cause a problem if the memory isn't supplying the cache fast enough because data is spread over different modules. Try running with just the 8GB module.
      My Computer
    Quote Quote

  13. lukloko
    Posts : 11
    Windows 7 Ultimate x64
    Thread Starter
       New #10

    I got this problem several more times, at which point I formatted the hard drive and reinstalled windows, to no avail.

    Even with the sigle 8gb memory, stil getting the BSOD.

    Could this be a hard drive failure? My hd has been making noises for a long time, but I figured it was of no consequence, since I didn't get such problems before.
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
BSOD playing path of exile
in BSOD Help and Support

Recently I have been getting BSOD while playing PoE. It hasn't been an issue before and I can't figure out what is causing it. I've lowered graphics settings and tried other things but I'm not too tech savy myself. Any help would be greatly appreciated!
BSOD playing Path of Exile
in BSOD Help and Support

Hi, I'm getting a BSOD when playing Path of Exile. I've gotten two so far. I am not experiencing BSOD's at random, only in PoE. The BSOD flashes by quicly and I'm unable to give much info about it. I've attached the file generated by the SF Diagnostic Tool. Sorry for the forum clutter. Figured...
Hi, Please see attached for the dump logs. http://farm6.staticflickr.com/5519/10995091273_f54b905470_z.jpg regards, Paul
BSOD playing Path of Exile
in BSOD Help and Support

Hello, Just installed Path of Exile, give me BSOD after 10-20 min.
Hi All, Started playing Path of Exile about a week ago and I am getting habitual BSOD as I enter a few areas in the game. The dump happens every time I try to access a zone more than 1 away area from the Forested Town in Act 2. It is always 0x00000050 Memory Dump I have attached the SF...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 19:06.
Find Us