Strange blue screen bbcode 124

Page 1 of 2 12 LastLast
  1.    #1

    Strange blue screen bbcode 124


    Hello,


    I have a strange problem. 3 months ago I bought a new GPU and new CPU. Immediately PC started to give me blue screens with bbcode 124. First days screens were 5 a day, but after they appeared one in 10, 20 days. The recent 3 blue screens are 5 days after. In the beginning errors came when they wanted and in different cases, include when I was away from the PC and did nothing on it /I have never obtained blue screen while I do system or component test, playing games/. But recent 3 blue screens are while I was watching blueray rips. I uninstalled Windows 7 Codeck pack, because there was a conflict with VLC player, installed again VLC and there is no conflicts. One blue screen recently appeared while I was watching youtube.
    I have wrote and read forums in my country. Tried everything that advised me – tested CPU, DRAM, HDD with Everest and other programs, reinstalled Windows, cleaned PC, plugged components off and after in and etc. There is no errors in tests, but blues screens appears. Only one thing I can’t do – to update my BIOS software. I could not find software for my BIOS. I suspect that my problem could come from the power supply, because GPU have to minimum 450W by default. But power supply calculators gives me I have enough power with my components. But I am not sure.
    The idea to write here is to help me to find in dmp files where the problem comes from. I tried, but I see that it caused by hardware and vista driver. It is easier way to buy new mobo and other components, but I’d like to save money and resolve the problem. And if I have to buy something, to be sure what. I’d like to be sure too that my CPU or GPU are not defected.
    I am attaching needed from the forum. And bellow I will place info from WinDbg.
    If you need something else, please write me.

    Thank you in advance!

    WinDbg info:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\012911-25109-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c3deb0
    Debug session time: Sat Jan 29 22:10:37.125 2011 (UTC + 2:00)
    System Uptime: 0 days 21:14:23.219
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .......
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800490b038, b6000000, 181}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : hardware
    Followup: MachineOwner
    ---------
    0: 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: fffffa800490b038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000181, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    FAULTING_MODULE: fffff80002a09000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    BUGCHECK_STR: 0x124_AuthenticAMD
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT



    I am with:
    Windows 7 Ultimate x64
    Not original installed OS on the system.
    OS is clearly installed two months ago.
    Please see my hardware details in the profile info.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Hi there,

    Run Memtest86 overnight: RAM - Test with Memtest86+

    Run the Blend, Small FFTs, and Large FFTs hard drive tests: https://www.sevenforums.com/tutorials...t-prime95.html

    Also, upload a full system report: https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    bogo75 said:
    Hello,


    I have a strange problem. 3 months ago I bought a new GPU and new CPU. Immediately PC started to give me blue screens with bbcode 124. First days screens were 5 a day, but after they appeared one in 10, 20 days. The recent 3 blue screens are 5 days after. In the beginning errors came when they wanted and in different cases, include when I was away from the PC and did nothing on it /I have never obtained blue screen while I do system or component test, playing games/. But recent 3 blue screens are while I was watching blueray rips. I uninstalled Windows 7 Codeck pack, because there was a conflict with VLC player, installed again VLC and there is no conflicts. One blue screen recently appeared while I was watching youtube.
    I have wrote and read forums in my country. Tried everything that advised me – tested CPU, DRAM, HDD with Everest and other programs, reinstalled Windows, cleaned PC, plugged components off and after in and etc. There is no errors in tests, but blues screens appears. Only one thing I can’t do – to update my BIOS software. I could not find software for my BIOS. I suspect that my problem could come from the power supply, because GPU have to minimum 450W by default. But power supply calculators gives me I have enough power with my components. But I am not sure.
    The idea to write here is to help me to find in dmp files where the problem comes from. I tried, but I see that it caused by hardware and vista driver. It is easier way to buy new mobo and other components, but I’d like to save money and resolve the problem. And if I have to buy something, to be sure what. I’d like to be sure too that my CPU or GPU are not defected.
    I am attaching needed from the forum. And bellow I will place info from WinDbg.
    If you need something else, please write me.

    Thank you in advance!

    WinDbg info:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\012911-25109-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.20738.amd64fre.win7_ldr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c3deb0
    Debug session time: Sat Jan 29 22:10:37.125 2011 (UTC + 2:00)
    System Uptime: 0 days 21:14:23.219
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...............................
    Loading User Symbols
    Loading unloaded module list
    .......
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa800490b038, b6000000, 181}
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    Probably caused by : hardware
    Followup: MachineOwner
    ---------
    0: 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: fffffa800490b038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000181, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    FAULTING_MODULE: fffff80002a09000 nt
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    BUGCHECK_STR: 0x124_AuthenticAMD
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT



    I am with:
    Windows 7 Ultimate x64
    Not original installed OS on the system.
    OS is clearly installed two months ago.
    Please see my hardware details in the profile info.

    Nothing strange about it.

    There are several problems

    1-sptd.sys A huge BSOD cause used in daemon tools and Alcohol
    Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

    You can use MagicDisc as an alternative.

    Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview


    2-Old drivers from as far back as 2005. At least these need to be updated.


    Code:
    usbVM31b.sys    9/19/2005 1:57:34    0x432e615e    fffff880`06942000    fffff880`06964c00        0x00022c00                    
    Rt64win7.sys    2/26/2009 4:04:13    0x49a65b0d    fffff880`00dcc000    fffff880`00dfe000        0x00032000                    
    spldr.sys    5/11/2009 11:56:27    0x4a0858bb    fffff880`0165a000    fffff880`01662000        0x00008000                    
    amdxata.sys    5/19/2009 12:56:59    0x4a12f2eb    fffff880`0131a000    fffff880`01325000        0x0000b000                    
    nvstor.sys    5/20/2009 1:45:37    0x4a13a711    fffff880`00e00000    fffff880`00e2b000        0x0002b000
    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 this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads

    3-hardware. read here what it means and what to try after you fix the above which may just fix it.

    Your .dmp file shows a stop error of 0x124 which is a general hardware error .. 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. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try

    Thanks


    Ken
      My Computer

  4.    #4

    Thak you Ken,

    I'll try find and install these drivers.
    Do you think that the Deamon tool could be a problem. With old CPU and old GPU I was with this type of Deamon tool and this Windows, but there was no blue screen.
    I have read Stop 0x124 - what it means and what to try. I did all of the suggestions, without BIOS update - because I could not find the proper.
      My Computer


  5. Posts : 13,354
    Windows 7 Professional x64
       #5

    SPTD is one of the few drivers (maybe the only) that I have seen cause a 0x124 BSOD. Remove the Daemon Tools, and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x64.exe
      My Computer

  6.    #6

    Jonathan_King said:
    SPTD is one of the few drivers (maybe the only) that I have seen cause a 0x124 BSOD. Remove the Daemon Tools, and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x64.exe
    Thanks, I'll remove immediately.
      My Computer

  7.    #7

    I removed Deamon Tools and SPTD.
    But please give some advise for the out of date drivers:

    1. usbVM31b.sys - this is driver for my PC camera - it is not proper driver, but I'll try to find corect driver;
    2. Rt64win7.sys - this is Realtek driver. It is no problem to update;
    3. spldr.sys - this is Microsoft security driver and I don't know what to do;
    4. amdxata.sys - this is AMD driver and I found different places for download, but not from the manifacturer and I'm not sure what to do;
    5. nvstor.sys - this is NVIDIA SATA driver. My video drivers are up to date and I'm not sure what kind of driver it is and what to do with it.

    The questions are about 3,4 and 5.

    And tell me is it possible thess drivers to be a problem, after installing new GPU and CPU? Before I used the same operating system and softweare and there is no blue screens.
      My Computer

  8.    #8

    Any ideas about drivers?

    Thank you!
      My Computer


  9. Posts : 13,354
    Windows 7 Professional x64
       #9

    spldr.sys - don't worry about, it's a Windows driver.
    amdxata.sys- don't worry about it, it's not from Microsoft but it's a Windows driver nonetheless.
    nvstor.sys- nVidia nForce driver. The nForce 4 chipset is no longer supported, so you'll not be able to find updates for it. Don't worry about it though.
      My Computer

  10.    #10

    Jonathan_King said:
    spldr.sys - don't worry about, it's a Windows driver.
    amdxata.sys- don't worry about it, it's not from Microsoft but it's a Windows driver nonetheless.
    nvstor.sys- nVidia nForce driver. The nForce 4 chipset is no longer supported, so you'll not be able to find updates for it. Don't worry about it though.
    OK, thanks. I will update other two drivers and will hope blue screen to dissapear.
      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 14:16.
Find Us