locked
Blue screen error RRS feed

  • Question

  • You have a email I can send the dmp files to so you can see?
    Saturday, February 28, 2015 3:45 AM

Answers

  • MD

    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them in this wiki

    Since your refers to authentic AMD I would start by running a cpu stress test

    You also need to update  quite a few drivers

    iirsp.sys    12/13/2005 4:47:54 PM        fffff880`01536000    fffff880`01547000    0x00011000    0x439f418a                        
    nfrd960.sys    6/6/2006 4:11:48 PM        fffff880`017d8000    fffff880`017e8000    0x00010000    0x4485ef94                        
    adpu320.sys    2/27/2007 7:04:15 PM        fffff880`01200000    fffff880`0122f000    0x0002f000    0x45e4c6ff                        
    adpahci.sys    5/1/2007 12:30:09 PM        fffff880`0138e000    fffff880`013e4000    0x00056000    0x46377921                        
    arc.sys    5/24/2007 4:27:55 PM        fffff880`0147b000    fffff880`01494000    0x00019000    0x4656035b                        
    SiSRaid2.sys    9/24/2008 1:28:20 PM        fffff880`019ad000    fffff880`019bb000    0x0000e000    0x48da86c4                        
    sisraid4.sys    10/1/2008 4:56:04 PM        fffff880`019bb000    fffff880`019d3000    0x00018000    0x48e3f1f4                        
    adp94xx.sys    12/5/2008 6:54:42 PM        fffff880`01313000    fffff880`0138e000    0x0007b000    0x4939bf42                        
    lsi_fc.sys    12/9/2008 5:46:09 PM        fffff880`01547000    fffff880`01566000    0x0001f000    0x493ef531                        
    arcsas.sys    1/14/2009 2:27:37 PM        fffff880`01494000    fffff880`014af000    0x0001b000    0x496e3ca9                        
    ql2300.sys    1/22/2009 6:05:06 PM        fffff880`01809000    fffff880`019ad000    0x001a4000    0x4978fba2                        
    vsmraid.sys    1/30/2009 8:18:57 PM        fffff880`0162b000    fffff880`01655000    0x0002a000    0x4983a701                        
    elxstor.sys    2/3/2009 5:52:11 PM        fffff880`014af000    fffff880`01536000    0x00087000    0x4988ca9b                        
    stexstor.sys    2/17/2009 6:03:36 PM        fffff880`019d3000    fffff880`019dd000    0x0000a000    0x499b4248                        
    amdsbs.sys    3/20/2009 1:36:03 PM        fffff880`0124d000    fffff880`01294000    0x00047000    0x49c3e213                        
    lsi_scsi.sys    4/16/2009 5:13:50 PM        fffff880`01579000    fffff880`01598000    0x0001f000    0x49e7ad9e                        
    spldr.sys    5/11/2009 11:56:27 AM        fffff880`01e51000    fffff880`01e59000    0x00008000    0x4a0858bb                        
    lsi_sas.sys    5/18/2009 7:20:23 PM        fffff880`00de3000    fffff880`00e00000    0x0001d000    0x4a11fb47                        
    lsi_sas2.sys    5/18/2009 7:31:48 PM        fffff880`01566000    fffff880`01579000    0x00013000    0x4a11fdf4                        
    megasas.sys    5/18/2009 8:09:46 PM        fffff880`01598000    fffff880`015a4000    0x0000c000    0x4a1206da                        
    ql40xx.sys    5/18/2009 8:18:11 PM        fffff880`01400000    fffff880`0145f000    0x0005f000    0x4a1208d3                        
    MegaSR.sys    5/18/2009 8:25:54 PM        fffff880`01666000    fffff880`0170a000    0x000a4000    0x4a120aa2                        

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022715-28969-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*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 Personal
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c890
    Debug session time: Fri Feb 27 22:17:48.922 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:11.062
    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, fffffa8007ba88f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: 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: fffffa8007ba88f8, 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`03d775b0 fffff800`02ec9cb9 : fffffa80`07ba88d0 fffffa80`06c5c040 00000000`00000013 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03d77ad0 fffff800`02daa157 : fffffa80`07ba88d0 fffff800`02e242d8 fffffa80`06c5c040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03d77b00 fffff800`02d11505 : fffff800`02e85d00 00000000`00000001 fffffa80`083ea690 fffffa80`06c5c040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03d77b40 fffff800`02c86a95 : fffff880`015d4e00 fffff800`02d114e0 fffffa80`06c5c000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03d77b70 fffff800`02f1bb8a : 00000000`00000000 fffffa80`06c5c040 00000000`00000080 fffffa80`06b9b9e0 : nt!ExpWorkerThread+0x111
    fffff880`03d77c00 fffff800`02c6e8e6 : fffff880`03b89180 fffffa80`06c5c040 fffff880`03b940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03d77c40 00000000`00000000 : fffff880`03d78000 fffff880`03d72000 fffff880`04fd2730 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

    • Proposed as answer by Deason Wu Friday, March 6, 2015 2:51 AM
    • Marked as answer by Cloud_TS Friday, March 6, 2015 6:10 AM
    Monday, March 2, 2015 12:24 PM
  • MD

    There are 22 drivers listed above including 8 Storage drivers which I suspect you do not need.  The most important one to update and it may have some relevance to the hardware crash is the iirsp.sys    12/13/2005 4:47:54 PM        (Related to iirsp.sys Intel/ICP Raid Storport Driver from Intel Corp./ICP vortex GmbH.)


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Cloud_TS Friday, March 6, 2015 6:09 AM
    Monday, March 2, 2015 4:31 PM

All replies

  • BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 1033

    Additional information about the problem:
      BCCode: 124
      BCP1: 0000000000000000
      BCP2: FFFFFA8007BA88F8
      BCP3: 0000000000000000
      BCP4: 0000000000000000
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1
    Saturday, February 28, 2015 3:47 AM
  •  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

    Saturday, February 28, 2015 4:14 AM
  • https://onedrive.live.com/redir?resid=3BD76E015AAA0EBD!106&authkey=!AK-Hf3fUuOjubSw&ithint=file%2czip

    Monday, March 2, 2015 5:20 AM
  • MD

    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them in this wiki

    Since your refers to authentic AMD I would start by running a cpu stress test

    You also need to update  quite a few drivers

    iirsp.sys    12/13/2005 4:47:54 PM        fffff880`01536000    fffff880`01547000    0x00011000    0x439f418a                        
    nfrd960.sys    6/6/2006 4:11:48 PM        fffff880`017d8000    fffff880`017e8000    0x00010000    0x4485ef94                        
    adpu320.sys    2/27/2007 7:04:15 PM        fffff880`01200000    fffff880`0122f000    0x0002f000    0x45e4c6ff                        
    adpahci.sys    5/1/2007 12:30:09 PM        fffff880`0138e000    fffff880`013e4000    0x00056000    0x46377921                        
    arc.sys    5/24/2007 4:27:55 PM        fffff880`0147b000    fffff880`01494000    0x00019000    0x4656035b                        
    SiSRaid2.sys    9/24/2008 1:28:20 PM        fffff880`019ad000    fffff880`019bb000    0x0000e000    0x48da86c4                        
    sisraid4.sys    10/1/2008 4:56:04 PM        fffff880`019bb000    fffff880`019d3000    0x00018000    0x48e3f1f4                        
    adp94xx.sys    12/5/2008 6:54:42 PM        fffff880`01313000    fffff880`0138e000    0x0007b000    0x4939bf42                        
    lsi_fc.sys    12/9/2008 5:46:09 PM        fffff880`01547000    fffff880`01566000    0x0001f000    0x493ef531                        
    arcsas.sys    1/14/2009 2:27:37 PM        fffff880`01494000    fffff880`014af000    0x0001b000    0x496e3ca9                        
    ql2300.sys    1/22/2009 6:05:06 PM        fffff880`01809000    fffff880`019ad000    0x001a4000    0x4978fba2                        
    vsmraid.sys    1/30/2009 8:18:57 PM        fffff880`0162b000    fffff880`01655000    0x0002a000    0x4983a701                        
    elxstor.sys    2/3/2009 5:52:11 PM        fffff880`014af000    fffff880`01536000    0x00087000    0x4988ca9b                        
    stexstor.sys    2/17/2009 6:03:36 PM        fffff880`019d3000    fffff880`019dd000    0x0000a000    0x499b4248                        
    amdsbs.sys    3/20/2009 1:36:03 PM        fffff880`0124d000    fffff880`01294000    0x00047000    0x49c3e213                        
    lsi_scsi.sys    4/16/2009 5:13:50 PM        fffff880`01579000    fffff880`01598000    0x0001f000    0x49e7ad9e                        
    spldr.sys    5/11/2009 11:56:27 AM        fffff880`01e51000    fffff880`01e59000    0x00008000    0x4a0858bb                        
    lsi_sas.sys    5/18/2009 7:20:23 PM        fffff880`00de3000    fffff880`00e00000    0x0001d000    0x4a11fb47                        
    lsi_sas2.sys    5/18/2009 7:31:48 PM        fffff880`01566000    fffff880`01579000    0x00013000    0x4a11fdf4                        
    megasas.sys    5/18/2009 8:09:46 PM        fffff880`01598000    fffff880`015a4000    0x0000c000    0x4a1206da                        
    ql40xx.sys    5/18/2009 8:18:11 PM        fffff880`01400000    fffff880`0145f000    0x0005f000    0x4a1208d3                        
    MegaSR.sys    5/18/2009 8:25:54 PM        fffff880`01666000    fffff880`0170a000    0x000a4000    0x4a120aa2                        

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\022715-28969-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*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 Personal
    Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
    Machine Name:
    Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4c890
    Debug session time: Fri Feb 27 22:17:48.922 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:11.062
    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, fffffa8007ba88f8, 0, 0}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: 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: fffffa8007ba88f8, 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`03d775b0 fffff800`02ec9cb9 : fffffa80`07ba88d0 fffffa80`06c5c040 00000000`00000013 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03d77ad0 fffff800`02daa157 : fffffa80`07ba88d0 fffff800`02e242d8 fffffa80`06c5c040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03d77b00 fffff800`02d11505 : fffff800`02e85d00 00000000`00000001 fffffa80`083ea690 fffffa80`06c5c040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03d77b40 fffff800`02c86a95 : fffff880`015d4e00 fffff800`02d114e0 fffffa80`06c5c000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03d77b70 fffff800`02f1bb8a : 00000000`00000000 fffffa80`06c5c040 00000000`00000080 fffffa80`06b9b9e0 : nt!ExpWorkerThread+0x111
    fffff880`03d77c00 fffff800`02c6e8e6 : fffff880`03b89180 fffffa80`06c5c040 fffff880`03b940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03d77c40 00000000`00000000 : fffff880`03d78000 fffff880`03d72000 fffff880`04fd2730 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

    • Proposed as answer by Deason Wu Friday, March 6, 2015 2:51 AM
    • Marked as answer by Cloud_TS Friday, March 6, 2015 6:10 AM
    Monday, March 2, 2015 12:24 PM
  • Which drivers need updated I have geforce graphics card and everything says up to date. 
    Monday, March 2, 2015 2:44 PM
  • MD

    This has absolutely nothing to do with your video driver.  If you look at my post above there are drivers from as far back as 2005 and anything prior to July 2009 needs updating BUT  This is almost certainly hardware related. SEE THE WIKI

    You cannot use windows update as it works from a list that may or may not be current


    Wanikiya and Dyami--Team Zigzag

    Monday, March 2, 2015 2:52 PM
  • I went into system manager and tried to update everything by searching online and it all says updated and working properly. I will go through it more and see if I can manually install them up to date
    Monday, March 2, 2015 2:57 PM
  • Did you run the CPU stress test?????

    You are avoiding the fact that this is almost certainly hardware and no matter what drivers you update it will still be hardware.

    How To Find Drivers:


    Search
     Google for the name of the driver
    Compare the Google results with what's installed on your system to figure out which device/program it belongs to
    Visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    If there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program

    The most common drivers are listed on these pages: 
    http://www.carrona.org/dvrref.php
    http://sysnative.com/drivers/

    Driver manufacturer links are on this page: http://www.carrona.org

    Wanikiya and Dyami--Team Zigzag


    Monday, March 2, 2015 3:10 PM
  • I'm not avoiding that fact I was just wondering which was out of date. I figured it was my memory chip bad. And I haven't had time to run the test yet, but I will have it ran tomorrow and let you know more. And thank you for the links to the drivers

    Monday, March 2, 2015 4:00 PM
  • MD

    There are 22 drivers listed above including 8 Storage drivers which I suspect you do not need.  The most important one to update and it may have some relevance to the hardware crash is the iirsp.sys    12/13/2005 4:47:54 PM        (Related to iirsp.sys Intel/ICP Raid Storport Driver from Intel Corp./ICP vortex GmbH.)


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by Cloud_TS Friday, March 6, 2015 6:09 AM
    Monday, March 2, 2015 4:31 PM