Random BSOD occurrence. Error hal.dll+12a3b and ntoskrnl.exe+18c453

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Home Edition 64bit
       #1

    Random BSOD occurrence. Error hal.dll+12a3b and ntoskrnl.exe+18c453


    Hi all,

    New to the forum and I'm after some help on the random BSOD I keep getting. I have recently updated my motherboard bundle with an i5 4670k (overclocked to 4.4ghz), Gigabyte Z87-HD3.

    Every now and again I get a BSOD and it has happened during gaming and when browsing the net.

    Using BlueScreenView gave me two addresses...

    ntoskrnl.exe ntoskrnl.exe+18c453 fffff800`03819000 fffff800`03dff000 0x005e6000 0x51db806a 09/07/2013 04:15:54 Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.18205 (win7sp1_gdr.130708-1532) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe

    hal.dll hal.dll+12a3b fffff800`03dff000 fffff800`03e48000 0x00049000 0x4ce7c669 20/11/2010 14:00:25

    I read on the web a few things to try. One was the possibility of it to do with Avast Antivirus, so I uninstalled and put on MSE and the other was do with my eSata connection. This is just a port from the back of the PC with a SATA cable running and connecting to my mobo. The eSata drive isn't always on and it still caused a BSOD.

    Attached are the dump files as requested. Anything else please let me know.

    Thanks.
      My Computer

  2.    #2

    Code:
    BugCheck 124, {0, fffffa8007fb0028, bf800000, 124}
    
    Probably caused by : GenuineIntel
    Code:
    3: kd> !errrec fffffa8007fb0028
    ===============================================================================
    Common Platform Error Record @ fffffa8007fb0028
    -------------------------------------------------------------------------------
    Record Id     : 01cead73daec61e2
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 9/9/2013 16:26:47 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007fb00a8
    Section       @ fffffa8007fb0180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000006
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007fb00f0
    Section       @ fffffa8007fb0240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000006
    CPU Id        : c3 06 03 00 00 08 10 06 - bf fb da 7f 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  @ fffffa8007fb0240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8007fb0138
    Section       @ fffffa8007fb02c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL0_WR_ERR (Proc 3 Bank 1)
      Status      : 0xbf80000000000124
      Address     : 0x000000023e5f5200
      Misc.       : 0x0000000000000086
    There seems to be a problem with writing data to the cache, I would suggest running this test:

    Enable "Round off checking" before the test (see first post below tutorial).

    Run the Small FFT's, Large FFT's and Blend Test for a few hours each, do not let the temperature exceed 80*C.
      My Computer


  3. Posts : 10
    Windows 7 Home Edition 64bit
    Thread Starter
       #3

    Thanks for the reply BlueRobot.

    Tried to run the Small FTT's and had another BSOD. Tried a second time and the screen went black and it just rebooted.

    Any other ideas please?

    Also the issue picked up with writing to cache, can this be a fault with the mobo, memory or cpu? If so would it be best I went back to where I purchased it (as this bundle was built and overclocked by them) for support or possible exchange?
      My Computer

  4.    #4

    It's most likely CPU, but I wouldn't want to say for certain without running the test, and a BSOD during a test usually indicates problems with the CPU. Please post the new BSOD with the same SF_Diagnostic Tool.
      My Computer


  5. Posts : 10
    Windows 7 Home Edition 64bit
    Thread Starter
       #5

    New one...
      My Computer

  6.    #6

    It's almost the exact same dump file as before, have you tried the Intel Burn In test?
      My Computer


  7. Posts : 10
    Windows 7 Home Edition 64bit
    Thread Starter
       #7

    Just attempted the Intel test but my temp shot up to 80 degs and recommended max is 72 degs. I had the same happening when running Prime95 (before it BSOD).

    I have a Dark Rock Advanced heatsink and fan and at idle the CPU is 32 degs. Under load around 45 degs. So should the temp be hitting 80 degs under these tests?

    For now I have disabled the write caching on my system drive and so far no Bluescreen and I don't notice any difference in performance.
      My Computer

  8.    #8

    It will be hot, and have you tried the test without the side panel?
      My Computer


  9. Posts : 10
    Windows 7 Home Edition 64bit
    Thread Starter
       #9

    That didn't work. Bluescreen again and with the same errors.
      My Computer

  10.    #10

    I'm quite positive, you most likely have a bad CPU, have you checked the condition of the socket and checked the pins on the CPU?
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
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 18:38.
Find Us