BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 profecional 64 bits
       #1

    BSOD playing bf3, hal.dll hal.dll+12a3b , ntoskrnl.exe ntoskrnl.exe+18


    i am having this problem after i change my video cards i upgraded a 460 SLI to a 680
    i have run 3dmark11 to try to replicate the bsod or something and nothing happends
    i clean my hardware and change the thermal compound then i played some bf3 and paff the same bsod =(

    pd: sorry for my english


    i forgot to say that i have the last beta drivers from nvidia because with the WHQL i was having problems in gw2
    Attachment 231326
    Last edited by Fayer; 11 Sep 2012 at 21:19.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    For the bug check you're getting go through:
    Stop 0x124 - what it means and what to try

    Also get a latest version of your BIOS.

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Yusra\Downloads\Fayer\SF_11-09-2012\091112-23509-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`03667000 PsLoadedModuleList = 0xfffff800`038ab670
    Debug session time: Wed Sep 12 06:29:05.072 2012 (UTC + 6:00)
    System Uptime: 0 days 7:04:57.025
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80086cf028, ba000000, 400405}
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : hardware
     
    Followup: MachineOwner
    ---------
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    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.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80086cf028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`030acb58 fffff800`03630a3b : 00000000`00000124 00000000`00000000 fffffa80`086cf028 00000000`ba000000 : nt!KeBugCheckEx
    fffff880`030acb60 fffff800`037f3b03 : 00000000`00000001 fffffa80`0860b890 00000000`00000000 fffffa80`0860b8e0 : hal!HalBugCheckSystem+0x1e3
    fffff880`030acba0 fffff800`03630700 : 00000000`00000728 fffffa80`0860b890 fffff880`030acf30 fffff880`030acf00 : nt!WheaReportHwError+0x263
    fffff880`030acc00 fffff800`03630052 : fffffa80`0860b890 fffff880`030acf30 fffffa80`0860b890 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`030acd50 fffff800`0362ff0d : 00000000`00000008 00000000`00000001 fffff880`030acfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`030acd90 fffff800`03623e88 : 0000003b`5e9a7a72 fffffa80`0ae15ac8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`030acdc0 fffff800`036e4aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`030acdf0 fffff800`036e4913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`030acf30 fffff800`036e863a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`03ffd890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForMultipleObjects+0x1d2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner
    ---------
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    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.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80086cf028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`030acb58 fffff800`03630a3b : 00000000`00000124 00000000`00000000 fffffa80`086cf028 00000000`ba000000 : nt!KeBugCheckEx
    fffff880`030acb60 fffff800`037f3b03 : 00000000`00000001 fffffa80`0860b890 00000000`00000000 fffffa80`0860b8e0 : hal!HalBugCheckSystem+0x1e3
    fffff880`030acba0 fffff800`03630700 : 00000000`00000728 fffffa80`0860b890 fffff880`030acf30 fffff880`030acf00 : nt!WheaReportHwError+0x263
    fffff880`030acc00 fffff800`03630052 : fffffa80`0860b890 fffff880`030acf30 fffffa80`0860b890 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`030acd50 fffff800`0362ff0d : 00000000`00000008 00000000`00000001 fffff880`030acfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`030acd90 fffff800`03623e88 : 0000003b`5e9a7a72 fffffa80`0ae15ac8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`030acdc0 fffff800`036e4aac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`030acdf0 fffff800`036e4913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`030acf30 fffff800`036e863a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`03ffd890 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForMultipleObjects+0x1d2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner
      My Computer


  3. Posts : 8
    Windows 7 profecional 64 bits
    Thread Starter
       #3

    i have this mb http://www.msi.com/product/mb/Big-Ba...l#/?div=Detail
    and i have the last bios installed
    i will try the stuff on that link and see what happens
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Thanks
    Keep us posted
      My Computer


  5. Posts : 8
    Windows 7 profecional 64 bits
    Thread Starter
       #5

    i run the MDSCHED and got nothing 0 problems
    now i will do the CHKDSK /R and see what happens
    what can i do to stress the vga?
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Video Card - Stress Test with Furmark
    Video Card - Stress Test with Furmark

      My Computer


  7. Posts : 8
    Windows 7 profecional 64 bits
    Thread Starter
       #7

    k i did the CHKDSK /R on C: and i got 0 erros the hdd is all good

    now i will do the furmark
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Will wait for the results
    You may use Speccy to monitor your temps during the test
      My Computer


  9. Posts : 8
    Windows 7 profecional 64 bits
    Thread Starter
       #9

    ok, i will have to do again the video stress then for the temps but the vga temp went from 30° celcius to 85
      My Computer


  10. Posts : 15,026
    Windows 10 Home 64Bit
       #10

    85 is allot.
    Do you have a cooler?
      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 08:16.
Find Us