BSOD On New Build

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 10
       #1

    BSOD On New Build


    Hi guys,

    Can anyone please help me? I've literally wasted so much time trying to identify why my system sometimes goes many hours fine, and on some days it BSOD's... mostly when using Adobe applications.

    Machine:
    i9 7940 X Stock
    32GB HyperX Predator (MemTest run for 24 hours... no issues using XMP profile at 2996MHz)
    970GTX
    3x 970 EVO SSDs NVMe
    PSU 850W Gold CoolerMaster



    Code:
    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR  Unique Expertise, Guaranteed Results)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 17763 MP (14 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 17763.1.amd64fre.rs5_release.180914-1434
    Machine Name:
    Kernel base = 0xfffff801`5f69e000 PsLoadedModuleList = 0xfffff801`5fab9a70
    Debug session time: Mon Dec 10 14:06:43.966 2018 (UTC - 5:00)
    System Uptime: 0 days 0:03:36.721
    *******************************************************************************
    *                                                                             *
    *                        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: ffffba081f7e4028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000070005, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                  ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                  ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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: fffff8015f69e000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    ffff9001`b838bd08 fffff801`5f649677 : 00000000`00000124 00000000`00000000 ffffba08`1f7e4028 00000000`b2000000 : nt+0x1b1130
    ffff9001`b838bd10 fffff80f`3c0f146b : ffffba08`1f7e4028 ffffba08`144e3d60 ffffba08`144e3d60 ffffba08`144e3d60 : hal!HalBugCheckSystem+0xd7
    ffff9001`b838bd50 fffff801`5f9bbe6e : ffffba08`1f7e4028 00000000`00000000 ffffba08`144e3d60 ffffba08`144e3d60 : PSHED!PshedBugCheckSystem+0xb
    ffff9001`b838bd80 ffffba08`1f7e4028 : 00000000`00000000 ffffba08`144e3d60 ffffba08`144e3d60 00000000`00000000 : nt+0x31de6e
    ffff9001`b838bd88 00000000`00000000 : ffffba08`144e3d60 ffffba08`144e3d60 00000000`00000000 fffff801`5f9bbbf2 : 0xffffba08`1f7e4028
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
    Last edited by Brink; 10 Dec 2018 at 13:17. Reason: code box
      My Computer

  2. Ztruker's Avatar
    Posts : 13,505
    Windows 10 Pro X64 20H4 19042.746
       #2

    Hi DMacX,

    Attachment 216878
      My Computers


  3. Posts : 7
    Windows 10
    Thread Starter
       #3

    Ztruker said:
    Your link doesn't take me anywhere?
      My Computer

  4. f14tomcat's Avatar
    Posts : 53,027
    Multi-boot Windows 10 - RTM, RP, Beta, and Insider
       #4

    DMacX said:
    Your link doesn't take me anywhere?
    Top of page #1....... BSOD - Posting Instructions - Windows 10 Forums
      My Computers


  5. Posts : 7
    Windows 10
    Thread Starter
       #5

    f14tomcat said:
    Thank you! On it now :)
      My Computer


  6. Posts : 7
    Windows 10
    Thread Starter
       #6

    Here you go - is this helpful? Thank you for the instructions.
      My Computer


  7. Posts : 7
    Windows 10
    Thread Starter
       #7

    Bump?
    Last edited by DMacX; 12 Dec 2018 at 07:30.
      My Computer

  8. Ztruker's Avatar
    Posts : 13,505
    Windows 10 Pro X64 20H4 19042.746
       #8

    Sorry for the delay. Looking at the dumps I'm getting a bunch of symbol file errors indicating that Microsoft hasn't updated their symbol servers with the latest 1809 build symbols so can't really do anything with the dumps.

    There were 60 Bluescreen entries detected in the WER data of msinfo32.nfo. That's a lot of BSODs.
    They are a mix of A0 and 124 fails. Both are serious.

    The A0 indicates an internal power error. This means a driver has attempted to transition a component to idle without a preceding active request, so this is a driver problem. For what device, I don't know yet.

    The 124 indicates a potential hardware problem with the CPU. Without symbol file resolution I can't look at the error record to see the cause.

    We need Microsoft to update the symbols to do any more debugging.

    Mean time, if you are doing any over clocking or over/under voltage, reset everything to nominal and see if that resolves the problem.

    I also see several of thes in the Eventlog:
    Code:
    Event[12649]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Boot
      Date: 2018-12-10T19:03:07.780
      Event ID: 29
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-M5R2LL4
      Description: 
    Windows failed fast startup with error status 0xC0000001.
    Turn off Fast Startup, see if that makes a difference: How to Turn On or Off Fast Startup in Windows 10
      My Computers


  9. Posts : 7
    Windows 10
    Thread Starter
       #9

    Ztruker said:
    Sorry for the delay. Looking at the dumps I'm getting a bunch of symbol file errors indicating that Microsoft hasn't updated their symbol servers with the latest 1809 build symbols so can't really do anything with the dumps.

    There were 60 Bluescreen entries detected in the WER data of msinfo32.nfo. That's a lot of BSODs.
    They are a mix of A0 and 124 fails. Both are serious.

    The A0 indicates an internal power error. This means a driver has attempted to transition a component to idle without a preceding active request, so this is a driver problem. For what device, I don't know yet.

    The 124 indicates a potential hardware problem with the CPU. Without symbol file resolution I can't look at the error record to see the cause.

    We need Microsoft to update the symbols to do any more debugging.

    Mean time, if you are doing any over clocking or over/under voltage, reset everything to nominal and see if that resolves the problem.

    I also see several of thes in the Eventlog:
    Code:
    Event[12649]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Boot
      Date: 2018-12-10T19:03:07.780
      Event ID: 29
      Task: N/A
      Level: Error
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DESKTOP-M5R2LL4
      Description: 
    Windows failed fast startup with error status 0xC0000001.
    Turn off Fast Startup, see if that makes a difference: How to Turn On or Off Fast Startup in Windows 10
    Your post is so helpful - thanks SO much for taking the time to help me! I appreciate it allot.

    Now, I think I may have it.. I have a rogue memory stick (despite MemTest coming back with 0 errors) - I can confirm when I removed 2 of my sticks and left two in - I no longer get the BSOD. Even running Prime95, Cinebench, PP and Lightroom all at the same time.

    What do you think to it being a stick of RAM?
      My Computer


  10. Posts : 38,342
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    There are two log collectors: DM and BETA
    Please temporarily insert all RAM modules.
    Then run the BETA log collector and post a new zip into this thread.
    Then return to the current configuration using just two RAM modules.

    BSOD - Posting Instructions - Windows 10 Forums
    https://www.tenforums.com/attachment...-v2-beta15.zip
    (extract all > open)
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 18:30.
Find Us




Windows 10 Forums