Maingear i7 Windows 7 Professional x64


  1. Posts : 2
    Windows 7 Professional x64
       #1

    Maingear i7 Windows 7 Professional x64


    - x86 x64
    - original installed OS on the system
    - OEM
    - What is the age of system (hardware)? - November 2010
    - What is the age of OS installation - November 2010
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    A fault in hardware is indicated by Bugcheck 0x124, this is caused by outdated BIOS or defects in hardware device(s)
    Stop 0x124 - what it means and what to try

    Ensure that nothing is overclocked
    Update the BIOS
    Test the RAM RAM - Test with Memtest86+

    Code:
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa8006bd48f8, 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:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0337e6f0 fffff800`032d5a89 : fffffa80`06bd48d0 fffffa80`05519b60 fffff8a0`0000000a 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`0337ec10 fffff800`031b7667 : fffffa80`06bd48d0 fffff800`032305f8 fffffa80`05519b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`0337ec40 fffff800`0311fc45 : fffff800`03292360 fffffa80`0651f838 fffffa80`0651f830 fffffa80`05519b60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`0337ec80 fffff800`03098961 : fffff880`01101e00 fffff800`0311fc20 fffffa80`05519b60 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`0337ecb0 fffff800`0332fc06 : a80aa80a`c3f8c3f8 fffffa80`05519b60 00000000`00000080 fffffa80`054fe040 : nt!ExpWorkerThread+0x111
    fffff880`0337ed40 fffff800`03069c26 : fffff880`0316a180 fffffa80`05519b60 fffff880`031750c0 c708c708`83b783b7 : nt!PspSystemThreadStartup+0x5a
    fffff880`0337ed80 00000000`00000000 : fffff880`0337f000 fffff880`03379000 fffff880`03fb2540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    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_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7 Professional x64
    Thread Starter
       #3

    Could a USB device/driver cause this kind of error? I have an old wireless Microsoft Keyboard that operates off a transmitter plugged in to USB and I have a new Cisco USB Wireless N network adapter I suspect as possible causes. Everything updated with latest drivers. BIOS also latest version available.

    I did the stress tests and the memory tests - no problems detected. The cooling fans spun up on the stress tests but no crash. No cooling fan spin ups on the crashes - just seems to happen randomly, screen freeze, then the memory dumps. I did the SeaTools tests and CHKDSK and everything passes/no errors detected.

    I see "Vista Driver Fault" in that. Some old driver in the mix somehow?
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    dcstager said:
    Could a USB device/driver cause this kind of error? I have an old wireless Microsoft Keyboard that operates off a transmitter plugged in to USB and I have a new Cisco USB Wireless N network adapter I suspect as possible causes. Everything updated with latest drivers. BIOS also latest version available.

    I did the stress tests and the memory tests - no problems detected. The cooling fans spun up on the stress tests but no crash. No cooling fan spin ups on the crashes - just seems to happen randomly, screen freeze, then the memory dumps. I did the SeaTools tests and CHKDSK and everything passes/no errors detected.

    I see "Vista Driver Fault" in that. Some old driver in the mix somehow?
    Yes, USB can cause this, Windows7 uses the same type of driver vista used, thats why you see "Vista Driver Fault"
      My Computer


 

  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 11:48.
Find Us