none
Minidump of BSOD After fresh installation of windows RRS feed

  • Question

  • Hello

    After downgrading from windows 8.1 to windows 7, right after fresh install of win7, BSOD happens. no weird application installed...

    Here is the minidump file:

    https://www.dropbox.com/s/3qlrn6fpaslv3ud/070114-8408-01.dmp

    Can anyone help me?

    Saturday, July 5, 2014 1:26 PM

Answers

  • Disable the Turbo Mode for your CPU and undo any overclocking if you've done.

    check if machine is adequately cooled and fan is working.

    load the bios with default settings.

    post back if the problem persist.

    • Marked as answer by I.Mir Saturday, July 5, 2014 3:00 PM
    Saturday, July 5, 2014 1:39 PM

All replies

  • Disable the Turbo Mode for your CPU and undo any overclocking if you've done.

    check if machine is adequately cooled and fan is working.

    load the bios with default settings.

    post back if the problem persist.

    • Marked as answer by I.Mir Saturday, July 5, 2014 3:00 PM
    Saturday, July 5, 2014 1:39 PM
  • Thanks for your reply

    I haven't done any overclocking.

    Computer chassis has 5 fans that all work fine.

    I have installed Speedfan application and monitored the temperatures and there are all below 50 degree Celsius.

    Bios is in its default settings.

    Any other Idea? 

    Saturday, July 5, 2014 1:49 PM
  • Visit this Link :Try This.
    Saturday, July 5, 2014 1:59 PM
  • Hello

    After downgrading from windows 8.1 to windows 7, right after fresh install of win7, BSOD happens. no weird application installed...

    Here is the minidump file:

    https://www.dropbox.com/s/3qlrn6fpaslv3ud/070114-8408-01.dmp

    Can anyone help me?

    lM

    This crash is called a BCC124 and is almost always related to hardware.  In your case it refers to genuine Intel so I would run the cpu stress test first

    *

    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 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

    http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\070114-8408-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    OK                                             C:\Users\Ken\Desktop
    
    ************* 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: C:\Users\Ken\Desktop
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02a66000 PsLoadedModuleList = 0xfffff800`02cabe90
    Debug session time: Tue Jul  1 08:57:44.510 2014 (UTC - 4:00)
    System Uptime: 0 days 0:00:04.322
    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, fffffa801c0f78f8, 0, 0}
    
    Probably caused by : GenuineIntel
    
    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: fffffa801c0f78f8, 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_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    STACK_TEXT:  
    fffff880`03da85b0 fffff800`02d29d29 : fffffa80`1c0f78d0 fffffa80`18849040 fffff8a0`001c5b10 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03da8ad0 fffff800`02c09217 : fffffa80`1c0f78d0 fffff800`02c83658 fffffa80`18849040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03da8b00 fffff800`02b70865 : fffff800`02ce53a0 00000000`00000001 fffff8a0`001c5a88 fffffa80`18849040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03da8b40 fffff800`02af0a21 : fffff800`02f08100 fffff800`02b70840 fffffa80`18849000 fffffa80`18849040 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03da8b70 fffff800`02d83cce : 00000000`00000000 fffffa80`18849040 00000000`00000080 fffffa80`187c5380 : nt!ExpWorkerThread+0x111
    fffff880`03da8c00 fffff800`02ad7fe6 : fffff880`03b74180 fffffa80`18849040 fffff880`03b7f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03da8c40 00000000`00000000 : fffff880`03da9000 fffff880`03da3000 fffff880`049c9400 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE_PRV
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache_prv
    
    FAILURE_ID_HASH:  {81541344-bc50-ac27-6893-a85ccb2f6d33}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Saturday, July 5, 2014 2:41 PM
    Moderator