PC Freezes with No Audio - Hard Shutdown Required


  1. Posts : 6
    Windows 10 Pro
       #1

    PC Freezes with No Audio - Hard Shutdown Required


    Hi everyone,

    I've been having this issue for a while. Typically while playing games my PC will freeze and become unresponsive requiring hard shutdown. This is typically while playing Dota 2. Any help would be appreciated!


    CPU: i7 4770k
    MB: Asus Maximus VI Hero
    GPU: NVIDIA GTX 1080 (Driver version 527.56)
    Memory x2:PC Freezes with No Audio - Hard Shutdown Required-new-bitmap-image-2-.jpg

    Windows Version: 21H2
    Windows Build: 19044.2486
    PC Freezes with No Audio - Hard Shutdown Required Attached Files
      My Computer


  2. NTN
    Posts : 969
    W10 19045.2546
       #2

    In 3D-settings Nvidia Control Panel: Prefer maximum performance under Power management mode.

    And also try these values in the Register for TdrDelay and TdrDiDelay.
    PC Freezes with No Audio - Hard Shutdown Required-tdrdelay.jpg
      My Computers


  3. Posts : 6
    Windows 10 Pro
    Thread Starter
       #3

    Was already on prefer maximum performance. Have added the reg keys as see if that helps.

    I dont see the hwschmode key, does that make a difference?

    PC Freezes with No Audio - Hard Shutdown Required-new-bitmap-image-2-.jpg
      My Computer


  4. Posts : 885
    10 Pro/11 Pro Dual Boot
       #4

    LJOE182 said:
    Hi everyone,

    I've been having this issue for a while. Typically while playing games my PC will freeze and become unresponsive requiring hard shutdown. This is typically while playing Dota 2. Any help would be appreciated!


    CPU: i7 4770k
    MB: Asus Maximus VI Hero
    GPU: NVIDIA GTX 1080 (Driver version 527.56)
    Memory x2:PC Freezes with No Audio - Hard Shutdown Required-new-bitmap-image-2-.jpg

    Windows Version: 21H2
    Windows Build: 19044.2486
    most recent dmp file (all dump files are the same)
    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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffff9a035e7e7028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------

    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
    *** ***
    *************************************************************************

    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2609

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 3193

    Key : Analysis.Init.CPU.mSec
    Value: 171

    Key : Analysis.Init.Elapsed.mSec
    Value: 4394

    Key : Analysis.Memory.CommitPeak.Mb
    Value: 77


    DUMP_FILE_ATTRIBUTES: 0x8
    Kernel Generated Triage Dump

    BUGCHECK_CODE: 124

    BUGCHECK_P1: 0

    BUGCHECK_P2: ffff9a035e7e7028

    BUGCHECK_P3: bf800000

    BUGCHECK_P4: 124

    CUSTOMER_CRASH_COUNT: 1

    PROCESS_NAME: steamcmd.exe

    STACK_TEXT:
    ffffd800`1393c8e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


    MODULE_NAME: GenuineIntel

    IMAGE_NAME: GenuineIntel.sys


    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

    Followup: MachineOwner
    ---------
      My Computers


  5. NTN
    Posts : 969
    W10 19045.2546
       #5

    [QUOTE=LJOE182;2512555]Was already on prefer maximum performance. Have added the reg keys as see if that helps.

    I dont see the hwschmode key, does that make a difference?

    Hardware-accelerated GPU scheduling enables more efficient GPU scheduling between applications by reducing latency and improving video output performance.
    hwschmode key=1 OFF
    hwschmode key=2 ON

    GeForce Game Ready Driver | 528.49 | Windows 10 64-bit, Windows 11 | NVIDIA
    Latest driver for you is 528.49.
    Last edited by NTN; 13 Feb 2023 at 06:17.
      My Computers


  6. Posts : 6
    Windows 10 Pro
    Thread Starter
       #6

    tomdsr said:
    most recent dmp file (all dump files are the same)
    Is there something I should do with this? I'm not sure I see any next steps?
      My Computer


  7. Posts : 885
    10 Pro/11 Pro Dual Boot
       #7

    LJOE182 said:
    Is there something I should do with this? I'm not sure I see any next steps?
    it is a hardware error with your processor. is it under warranty still?
      My Computers


  8. Posts : 6
    Windows 10 Pro
    Thread Starter
       #8

    tomdsr said:
    it is a hardware error with your processor. is it under warranty still?
    No the system is pretty old. I've been reading around and I've seen it could be a chipset driver issue? Thoughts?
      My Computer


  9. Posts : 885
    10 Pro/11 Pro Dual Boot
       #9

    LJOE182 said:
    No the system is pretty old. I've been reading around and I've seen it could be a chipset driver issue? Thoughts?
    possible, but unlikely. here is more info concerning this error taken from the dmp file:

    7: kd> !errrec ffff9a035e7e7028
    ===============================================================================
    Common Platform Error Record @ ffff9a035e7e7028
    -------------------------------------------------------------------------------
    Record Id : 01d92f9e8d5c215f
    Severity : Fatal (1)
    Length : 936
    Creator : Microsoft
    Notify Type : Machine Check Exception
    Timestamp : 1/24/2023 3:21:36 (UTC)
    Flags : 0x00000000

    ===============================================================================
    Section 0 : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor @ ffff9a035e7e70a8
    Section @ ffff9a035e7e7180
    Offset : 344
    Length : 192
    Flags : 0x00000001 Primary
    Severity : Fatal

    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
    *** ***
    *************************************************************************
    No valid data fields are present.

    ===============================================================================
    Section 1 : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor @ ffff9a035e7e70f0
    Section @ ffff9a035e7e7240
    Offset : 536
    Length : 128
    Flags : 0x00000000
    Severity : Fatal

    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_PROCESSOR_ERROR_SECTION ***
    *** ***
    *************************************************************************
    No valid data fields are present.

    ===============================================================================
    Section 2 : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor @ ffff9a035e7e7138
    Section @ ffff9a035e7e72c0
    Offset : 664
    Length : 272
    Flags : 0x00000000
    Severity : Fatal

    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_MCA_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_MCA_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_MCA_SECTION ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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: hal!_WHEA_XPF_MCA_SECTION ***
    *** ***
    *************************************************************************
    Error : Unknown (Proc 0 Bank 0)
    Status : 0x0000000000000000
      My Computers


  10. Posts : 6
    Windows 10 Pro
    Thread Starter
       #10

    tomdsr said:
    possible, but unlikely. here is more info concerning this error taken from the dmp file:
    Sorry to revive an old thread but I reviewed some system settings and wanted to update. It looked like my RAM timing was clocked lower than what they were made for. I adjusted and I haven't had any issues since. Does this make any sense given the logs that I have? System is very stable and have had zero issues since adjusting the timing.
      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 05:33.
Find Us




Windows 10 Forums