BSOD working on Reason, a DAW from Propellerhead

Page 2 of 2 FirstFirst 12

  1. Posts : 14,901
    Windows 10 Pro
       #11

    What I say is that this kind of output is caused by symbol errors.
    Code:
    ****************************************************************************                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   *** *************************************************************************
    The symbol issue prevents proper analysis of the dump making troubleshooting unreliable.

    What you want to do is up to you, but as the OS is Windows 10 Insider I doubt that this is a memory data structure corruption caused by faulty memory.
      My Computers


  2. Posts : 26
    windows 10 build 14332
    Thread Starter
       #12

    axe0 said:
    What I say is that this kind of output is caused by symbol errors.
    Code:
    ****************************************************************************                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   *** *************************************************************************
    The symbol issue prevents proper analysis of the dump making troubleshooting unreliable.

    What you want to do is up to you, but as the OS is Windows 10 Insider I doubt that this is a memory data structure corruption caused by faulty memory.
    Thanx axe0.

    To finalize I'd like you explain me two things.

    1) What do you mean by symbols errors? They are corrupted or there is lack of symbols information because this is a new build (14931)?
    2) What do you suggested I do in order to troubleshot my problem? What did you do!?

    Thanx again,
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #13

    1. The current stable release is build 14393, 14931 is a technical preview release. For TP releases symbols are usually not released to the public until the TP is at it's final stages. The issue is due to a lack of symbols.

    2. As it is a TP version the possibility that this crash was caused by a bug of Windows is significantly higher than with a release, you could try driver verifier but the results of driver verifier most probably won't be the same so I wouldn't recommend it.
    As long as another crash doesn't occur within a short period I personally wouldn't worry about it too much.
      My Computers


  4. Posts : 26
    windows 10 build 14332
    Thread Starter
       #14

    axe0 said:
    1. The current stable release is build 14393, 14931 is a technical preview release. For TP releases symbols are usually not released to the public until the TP is at it's final stages. The issue is due to a lack of symbols.

    2. As it is a TP version the possibility that this crash was caused by a bug of Windows is significantly higher than with a release, you could try driver verifier but the results of driver verifier most probably won't be the same so I wouldn't recommend it.
    As long as another crash doesn't occur within a short period I personally wouldn't worry about it too much.
    Thank you for your help and attention axe0.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #15

    You're welcome.
      My Computers


  6. Posts : 26
    windows 10 build 14332
    Thread Starter
       #16

    Hi axe0,

    After all, I realize I have more questions. I hope you can help me.
    Why in my WinDbg, when I run !verifier or !thread , the answer is something like: unable to get the verifier list or unable to get thread contents?
    Is this behavior due to the lack of symbols also or there's something wrong with some setting in my WinDbg??

    Thanx for your help axe0
      My Computer


  7. Posts : 14,901
    Windows 10 Pro
       #17

    When there are symbol issues, many things cannot be accessed because it cannot be loaded.

    Another reason, if there are no symbol issues, is because the dump doesn't contain enough information to provide the requested data.
      My Computers


  8. Posts : 26
    windows 10 build 14332
    Thread Starter
       #18

    axe0 said:
    When there are symbol issues, many things cannot be accessed because it cannot be loaded.

    Another reason, if there are no symbol issues, is because the dump doesn't contain enough information to provide the requested data.
    Thank you axe0 !
      My Computer


 

  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 17:31.
Find Us




Windows 10 Forums