locked
BSOD after power on and first startup (every time), then no problem? RRS feed

  • Question

  • Hi all.

    I have a problem with my computer, maybe you can give me some pointers or tips.

    When I flick the power swith and start the computer, I get a BSOD every time (from about 7-8 minutes to up to half an hour after start. It reboots, and then the computer runs smoothly for how many hours I like. I can´t seem to find a pattern when it comes to which programs I use. Sometimes it crashes right after I start Spotify, sometimes during image editing or regular browsing. Sometimes during a game. 
    According to BlueScreenView it´s the famous (from forums that I read) driver ntoskrnl.exe that is the reason every time. The Check code is 0x00000124, and the address is: ntoskrnl.exe+4adb3c. Every time.

    I have run memtest86 for 15 hours, no problem, and the memory test that comes with win 7, also without any problem.

    If anyone has any tips of what to look for next, I would be appreciate it very much, because I´m at a loss here...!

    Have a great day!

    Below is the latest 8 BSOD incidents if you want more detailed info:==================================================
    Dump File         : 011815-23899-01.dmp
    Crash Time        : 2015-01-18 10:48:10
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`0744b748
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\011815-23899-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2015-01-18 10:48:26
    ==================================================

    ==================================================
    Dump File         : 011315-23212-01.dmp
    Crash Time        : 2015-01-13 19:30:36
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`071d38f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\011315-23212-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2015-01-13 19:30:48
    ==================================================

    ==================================================
    Dump File         : 122214-22698-01.dmp
    Crash Time        : 2014-12-22 19:11:11
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`071a08f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\122214-22698-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-12-22 19:11:24
    ==================================================

    ==================================================
    Dump File         : 121514-23337-01.dmp
    Crash Time        : 2014-12-15 18:52:18
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`071918f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\121514-23337-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-12-15 18:52:31
    ==================================================

    ==================================================
    Dump File         : 121414-22557-01.dmp
    Crash Time        : 2014-12-14 20:55:06
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`0718f8f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\121414-22557-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-12-14 20:55:18
    ==================================================

    ==================================================
    Dump File         : 120814-29468-01.dmp
    Crash Time        : 2014-12-08 21:22:51
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`071998f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\120814-29468-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-12-08 21:23:05
    ==================================================

    ==================================================
    Dump File         : 110214-21762-01.dmp
    Crash Time        : 2014-11-02 09:59:44
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`071718f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\110214-21762-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-11-02 09:59:58
    ==================================================

    ==================================================
    Dump File         : 110114-24195-01.dmp
    Crash Time        : 2014-11-01 12:05:42
    Bug Check String  : 
    Bug Check Code    : 0x00000124
    Parameter 1       : 00000000`00000000
    Parameter 2       : fffffa80`0717d8f8
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+4adb3c
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+4adb3c
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\110114-24195-01.dmp
    Processors Count  : 4
    Major Version     : 15
    Minor Version     : 7601
    Dump File Size    : 262 144
    Dump File Time    : 2014-11-01 12:05:56
    ==================================================

    Monday, January 19, 2015 10:40 AM

All replies

  •  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Monday, January 19, 2015 11:07 AM
  • Hi, very sorry about that. 

    I hope this works, I put the last 10 BSOD from the Minidump folder in the compressed file on this link: 

    http://1drv.ms/1wlkW1f

    If I missed something, please let me know, thanks for looking into this!
    /Niclas

    Monday, January 19, 2015 12:58 PM
  • Niclas

    These were called BCC124 and are related to hardware.  Since yours mentions Authentic AMD I would start by running a CPU stress test

    Try this free stress test:  http://www.mersenne.org/freesoft/

    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.

    Stop 0x124 is a hardware error
    If you are overclocking try resetting your processor to standard settings and see if that helps.
    If you continue to get BSODs here are some more things you may want to consider.
    This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

    Stop 0x124 - what it means and what to try

    Synopsis:
    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
    Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


     Generic "Stop 0x124" Troubleshooting Strategy:

    1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.
    2) Ensure that the machine is adequately cooled.
     If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
    3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
    It is good practice to run the latest drivers anyway.
    4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
    Their website should provide detailed instructions as to the brand and model-specific procedure.
    5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
    At the time of writing, Windows 7 (or 8) is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
    6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
    The most obvious examples are the RAM and HDD(s).
    For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
    Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.
    7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
    Should that fail to mitigate the 0x124 problem, jump to the next steps.
    If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
    Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
    If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
    Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
    8) Clean and carefully remove any dust from the inside of the machine.
    Reseat all connectors and memory modules.
    Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
    9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
    Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

    Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

    More advanced reading can be found here from a MS MVP IT PRO

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\New folder\011315-23212-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*h:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`03258000 PsLoadedModuleList = 0xfffff800`0349b890
    Debug session time: Tue Jan 13 13:30:36.024 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:06.257
    Loading Kernel Symbols
    ....................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80071d38f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffffa80071d38f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    STACK_TEXT:  
    fffff880`031a16f0 fffff800`03518cb9 : fffffa80`071d38d0 fffffa80`06ab2040 fffffa80`00000011 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031a1c10 fffff800`033f9ea7 : fffffa80`071d38d0 fffff800`034732d8 fffffa80`06ab2040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031a1c40 fffff800`03361275 : fffff800`034d4d00 00000000`00000001 fffffa80`07181d00 fffffa80`06ab2040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031a1c80 fffff800`032d7261 : fffff880`010a1e00 fffff800`03361250 fffffa80`06ab2000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031a1cb0 fffff800`0356973a : 00000000`00000000 fffffa80`06ab2040 00000000`00000080 fffffa80`06a25ae0 : nt!ExpWorkerThread+0x111
    fffff880`031a1d40 fffff800`032be8e6 : fffff880`02f64180 fffffa80`06ab2040 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`037ac730 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus_prv
    
    FAILURE_ID_HASH:  {78c2f422-5335-4ef3-5cef-a28518da5023}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Tuesday, January 20, 2015 12:10 PM
  • Hello Niclas_47,

    What is your current situation?

    Have you tried the solution as MVP Zigzag mentioned?

    Best regards,
    Fangzhou CHEN


    Fangzhou CHEN
    TechNet Community Support

    Friday, January 23, 2015 2:57 AM
  • Hi both, and thanks for your help, it is very appreciated!

    Sadly, I havn´t had time to try the Prime95 test, but I will run a test on tomorrow, if all goes well.
    I did try one thing, though. I upgraded my BIOS (since the one I had was from 2009), so now it´s from 2011 instead. The change is that I don´t get any BSOD´s (with mandatory reboot.) Now the computer just freezes instead, and I need to restart it by holding down the power button. 

    These freezes doesn´t show in the BlueScreenView, either, and I can´t find a *.dmp file of the incident. The patterns are the same, though. After I switch the power on and start the computer for the first time, the freeze appears after 5-20 minutes. After the reboot, the computer can run for hours and hours with no incidents at all, which really is strange (for me, anyway). Was it a bad idea to update the BIOS?

    I read somewhere that it could be a memory issue, that the timings for the memory sticks is not correct. I tried to find the option to adjust them in BIOS (version 02.61, American Megatrends), but could only find the option to change the frequency. Could this be something to examine further?

    Another thing has also appeared in the last couple of days. One of my hard drives seems to be nearing the end. The system tells me during startup, that one drive has a bad sector , and needs to be replaced. It also says (in Windows) that I should backup the HDD and replace it. When I did Check Drive (in Windows) on the HDD, however, it came out fine, with no issues. Could this be a reason for my start up BSOD´s?

    Again, more questions...
    I whish you a great day, and thanks again for taking the time to help me. I will get back to you with the result from Prime95.
    /Niclas

    Sunday, January 25, 2015 8:47 PM
  • Hi Fangzhou CHEN, thanks for asking. 
    As I stated in the reply to MVP ZigZag above inte the thread, I will try Prime95 tomorrow. There has been some develpments (see reply), but if they are a step forward or a step backwards, I am not the right guy for judging that :-)
    Sunday, January 25, 2015 8:52 PM
  • Hello Niclas,

    What is your current situation?

    As you receive error message about Drive bad sector, please contact the manufacturer to check if there are hardware issues.

    Please remember to create a system image backup in case of the hardware crash.
    http://windows.microsoft.com/en-hk/windows/back-up-programs-system-settings-files#1TC=windows-7
     
    About the Windows freezing issue, please use the Task Manager to check which program or process is occupying large amount of system resource.

    Best regards,
    Fangzhou CHEN


    Fangzhou CHEN
    TechNet Community Support


    Tuesday, February 3, 2015 5:52 AM