Certain Games Crashing, Screen Goes Black And Gpu Fans Ramp Up

Discussion in 'Software' started by Jalbanese1441, Jun 12, 2020.

  1. Jalbanese1441

    Jalbanese1441 Private E-2

    Every time I go to open a game once the game is just about done loading the computer’s screen goes black, and my GPU fans ramp up. They stay like that for about 10 min, then the pc reboots, runs into the BSoD, then reboots after a while and is fine. If I press and hold down the power button to force shutdown my computer then robot it, I don’t get the BSoD. Can anyone please help me?


    My system specs:

    · Ryzen 7 3800x (4.45 GHz, no OC)

    · 40 Gb ram (2600MHz, XMP and OC)

    · 3x Sata SSD’s

    · NVMe M.2 (1 Tb, boot)

    · Radeon RX 580 (8Gb, no OC)

    · EVGA 850-watt PSU (Just a year old)

    · MSI x470 Gaming Plus

    · 5 case fans

    · 2 RGB led strips (+ motherboard RGB)

    What I have tried:

    · Using only one set of ram sticks

    · Using different GPU ports and cables

    · Using another monitor

    · Rolling back recently installed drivers

    · Uninstalling and reinstalling GPU drivers

    · Using old GPU drives that I know worked at the time

    · Updating windows and every driver on my pc

    · Did a full virus scan (Kaspersky)

    · Disabled all background processes when starting up a game

    · Tweaked Radeon Soft where

    · Uninstalled MIS Afterburner

    · Reinstalled MSI Afterburner

    · Disabled ram XMP profiles

    · Tested voltages using HWiNFO64

    · Note: I can still play two games, Minecraft and Shadow of the Tomb Raider (both tested with free sync on and off, as well at different refresh rates)

    · During a benchmark in Shadow of the Tomb Raider GPU temps are: 35-50C and CPU temps are: 45-50 C

    · Disabled FreeSycn

    · Reenabled FreeSync and tested different refresh rates (59HZ, 60HZ and 144HZ)

    · Tried moving the GPU to a different PCI slot

    · Increasing the power and temp limits on the GPU

    · Underclocking the GPU

    · Verifying the game files for the games that keep crashing my pc (Using Steam)

    · Plugged pc into a power bar and a different outlet (same room)

    · Tried running different power cables from PSU to GPU

    · Disabled fast boot

    I have included a drop box link with all of the files from my testing.

    https://www.dropbox.com/s/adpwubly8lt6pw8/INFO.zip?dl=0
     
  2. Jared.

    Jared. Private E-2

    Have you tried reinstalling Windows 10 completely either through a restore point or resetting it? If that doesn't work try wiping the partition and doing a full installation. Before doing so, I would recommend trying another operating system, such as Manjaro or Ubuntu, to assure whether the issue isn't hardware related but is due to a possible corruption upon Window's end.
     
  3. Jalbanese1441

    Jalbanese1441 Private E-2

    I will try that and get back to you, thanks
     
  4. satrow

    satrow Major Geek Extraordinaire

    It looks like it's hardware-related, specifically PCI/SATA/NVMe (poss. GPU), but the trigger seems to be in power state switching/synchronisation - most likely the chipset drivers all need updating (AMD/MSI?) and maybe the GPU drivers too. Some might need rolling back.

    This seems to be a variation of an 0x9f bugcheck that I've not seen before (search for 0x9f_4_amd_sata_stackptr_error_image_pci.sys for a few similar cases), basic analysis:

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
       subsystem.
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: ffffde8dbf1d4040, The thread currently holding on to the Pnp lock.
    Arg4: ffff8001990ed8e0, nt!TRIAGE_9F_PNP on Win7 and higher
    
    Debugging Details:
    ------------------
    
    Implicit thread is now ffffde8d`bf1d4040
    Unable to load image \SystemRoot\System32\drivers\amd_xata.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for amd_xata.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 400
    
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    
    SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.
    
    SYSTEM_PRODUCT_NAME:  MS-7B79
    
    SYSTEM_SKU:  To be filled by O.E.M.
    
    SYSTEM_VERSION:  2.0
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  A.G0
    
    BIOS_DATE:  11/11/2019
    
    BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.
    
    BASEBOARD_PRODUCT:  X470 GAMING PLUS (MS-7B79)
    
    BASEBOARD_VERSION:  2.0
    
    DUMP_TYPE:  2
    
    BUGCHECK_P1: 4
    
    BUGCHECK_P2: 12c
    
    BUGCHECK_P3: ffffde8dbf1d4040
    
    BUGCHECK_P4: ffff8001990ed8e0
    
    DRVPOWERSTATE_SUBCODE:  4
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  1d5e3c2e
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff80166e90000 pci
    
    CPU_COUNT: 10
    
    CPU_MHZ: f3c
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 17
    
    CPU_MODEL: 71
    
    CPU_STEPPING: 0
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    ANALYSIS_SESSION_HOST:  BLACKBEAST
    
    ANALYSIS_SESSION_TIME:  06-12-2020 06:22:51.0795
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    BAD_STACK_POINTER:  ffff8001990ed8a8
    
    STACK_TEXT: 
    ffff8001`990ed8a8 fffff801`65c9f706 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffde8d`bf1d4040 : nt!KeBugCheckEx
    ffff8001`990ed8b0 fffff801`65faf9a6 : ffff8001`990edb10 00000000`00000021 fffff801`5fec6800 00000000`00000001 : nt!PnpBugcheckPowerTimeout+0x76
    ffff8001`990ed910 fffff801`65a512d9 : ffff8001`99ef4330 00000001`5c236471 00000001`00000002 ffffde8d`b9e21010 : nt!PopBuildDeviceNotifyListWatchdog+0x16
    ffff8001`990ed940 fffff801`65a50039 : 00000000`00000018 00000000`00989680 00000000`00005709 00000000`00000021 : nt!KiProcessExpiredTimerList+0x169
    ffff8001`990eda30 fffff801`65bc5ece : ffffffff`00000000 ffffb300`bb1ca180 ffffb300`bb1db440 ffffde8d`b9fa3080 : nt!KiRetireDpcList+0x4e9
    ffff8001`990edc60 00000000`00000000 : ffff8001`990ee000 ffff8001`990e8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x7e
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  0efaf37e6601d7f65db9dbe50a219f0403a414f7
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  35f5391c79b2a52bd16f694404c33c6c0d318fbb
    
    THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
    
    FOLLOWUP_NAME:  MachineOwner
    
    IMAGE_VERSION:  10.0.18362.752
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    FAILURE_BUCKET_ID:  0x9F_4_amd_sata_STACKPTR_ERROR_IMAGE_pci.sys
    
    BUCKET_ID:  0x9F_4_amd_sata_STACKPTR_ERROR_IMAGE_pci.sys
    
    PRIMARY_PROBLEM_CLASS:  0x9F_4_amd_sata_STACKPTR_ERROR_IMAGE_pci.sys
    
    TARGET_TIME:  2020-06-10T20:27:38.000Z
    
    OSBUILD:  18362
    
    OSSERVICEPACK:  900
    
    SERVICEPACK_NUMBER: 0
    
    OS_REVISION: 0
    
    SUITE_MASK:  784
    
    PRODUCT_TYPE:  1
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    
    OS_LOCALE: 
    
    USER_LCID:  0
    
    OSBUILD_TIMESTAMP:  2012-07-06 22:22:33
    
    BUILDDATESTAMP_STR:  190318-1202
    
    BUILDLAB_STR:  19h1_release
    
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    
    ANALYSIS_SESSION_ELAPSED_TIME:  2c51
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x9f_4_amd_sata_stackptr_error_image_pci.sys
    
    FAILURE_ID_HASH:  {15e29c45-2cf8-a37e-bebc-d0c20c6b9de8}
    
    Followup:     MachineOwner
    ---------
    
    15: kd> !thread ffffde8dbf1d4040
    THREAD ffffde8dbf1d4040  Cid 0004.10ac  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (WrResource) KernelMode Non-Alertable
        ffff80019b309960  SynchronizationEvent
    Not impersonating
    GetUlongFromAddress: unable to read from fffff80165e2ca14
    Owning Process            ffffde8dade96040       Image:         System
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      37275      
    Context Switch Count      87600          IdealProcessor: 14  NoStackSwap
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Win32 Start Address nt!ExpWorkerThread (0xfffff80165a83840)
    Stack Init ffff80019b309c90 Current ffff80019b3094e0
    Base ffff80019b30a000 Limit ffff80019b304000 Call 0000000000000000
    Priority 12 BasePriority 12 PriorityDecrement 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    ffff8001`9b309520 fffff801`65aa468d : ffffb300`ffffffff 00000000`00000000 ffffb300`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76
    ffff8001`9b309660 fffff801`65aa3514 : ffffde8d`bf1d4040 00000000`00000000 00000000`00000000 ffffde8d`00000000 : nt!KiSwapThread+0xbfd
    ffff8001`9b309700 fffff801`65aa2cb5 : 00000000`00000062 fffff801`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
    ffff8001`9b3097a0 fffff801`65aa5f2d : ffff8001`9b309960 ffff878e`0000001b 00000000`00000000 00000000`41706e00 : nt!KeWaitForSingleObject+0x255
    ffff8001`9b309880 fffff801`65a9f267 : fffff801`65e629e0 ffff8001`9b309948 ffff8001`00010224 fffff801`65b5a710 : nt!ExpWaitForResource+0x6d
    ffff8001`9b309900 fffff801`660eac2c : ffff8001`9b309a49 00000000`00000007 ffff878e`20e2b8a0 ffffde8d`bf76c801 : nt!ExAcquireResourceExclusiveLite+0x217
    ffff8001`9b309990 fffff801`6612f84f : ffffde8d`bf76c800 00000000`00000007 ffffde8d`bf5f8510 00000000`00000000 : nt!PpDevNodeLockTree+0x58
    ffff8001`9b3099c0 fffff801`661091ae : ffff8001`9b309b10 ffffde8d`bf76c900 ffff8001`9b309b00 ffff878e`20e2b8a0 : nt!PnpProcessQueryRemoveAndEject+0x77
    ffff8001`9b309ab0 fffff801`65fc96d8 : ffff878e`32f177f0 ffff878e`20e2b8a0 ffff878e`20e2b8a0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xea
    ffff8001`9b309ae0 fffff801`65a83945 : ffffde8d`ade74c40 ffffde8d`bf1d4040 ffffde8d`ade74c40 fffff801`65e61480 : nt!PnpDeviceEventWorker+0x2d8
    ffff8001`9b309b70 fffff801`65b1e135 : ffffde8d`bf1d4040 00000000`00000080 ffffde8d`ade96040 00000000`00000001 : nt!ExpWorkerThread+0x105
    ffff8001`9b309c10 fffff801`65bc99a8 : ffffb300`bb124180 ffffde8d`bf1d4040 fffff801`65b1e0e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
    ffff8001`9b309c60 00000000`00000000 : ffff8001`9b30a000 ffff8001`9b304000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
     
  5. Jalbanese1441

    Jalbanese1441 Private E-2

    I have updated the chipset drivers and I didn't notice a difference. I don't think it's the GPU drivers because in my testing I reinstalled a version of the GPU drivers from when I knew they were working.
    I then tried to reinstall windows (keeping my files and program) and was met with the following error message:
    0xC1900101 - 0x40021
    The installation failed in the SECOND_BOOT phase with an error during SYSPREP_RESPECALIZE operation

    Thank you for your help so far.
     
  6. Jalbanese1441

    Jalbanese1441 Private E-2

  7. satrow

    satrow Major Geek Extraordinaire

    You 'think'?

    Had you installed it previously? Uninstalled it? Paid extra for a license to use it? Do you have any details about when it was installed originally?

    Do you know that AMD have pulled it? https://www.anandtech.com/show/1570...eveloping-new-software-for-later-this-quarter

    Something lingering from that software could easily be related to the problems you've been having.
     
  8. Jalbanese1441

    Jalbanese1441 Private E-2

    When I first got my computer I had a 250 gb boot sata ssd and a 2tb hdd for my files and games. I eventually upgraded to an all ssd system. I had completely forgotten about it until not. I assumed that is was uninstalled when I migrated my os to a new 1 TB M.2 ssd and also moved my second drive to a 2tb ssd (I had a free copy of the software that came with my motherbaord). I don't think I still have it, but I don't know how to confirm that (also, I did not know that AMD had pulled it. If you have any suggestions I would appreciate them, thanks
     
  9. satrow

    satrow Major Geek Extraordinaire

    I have zero experience of this software, sorry.
     
  10. xenialouna

    xenialouna Private E-2

    Have you tried reinstalling Windows 10 completely either through a restore point or resetting it? If that doesn't work try wiping the partition and doing a full installation. Before doing so, I would recommend trying another operating system, such as Manjaro or Ubuntu, to assure whether the issue isn't hardware related but is due to a possible corruption upon Window's end.
     
  11. Jalbanese1441

    Jalbanese1441 Private E-2

    Yes
    Yes I have but I keep getting errors. I have tried this a few time (using different methods), and used SetupDiag. Here is a link to the logs it collected:
    https://www.dropbox.com/s/7b20boshhhnwksn/Logs from SetupDiag.zip?dl=0
     
  12. satrow

    satrow Major Geek Extraordinaire

    'Jared''s alter ego spewing more generic blurb?
     
  13. Jalbanese1441

    Jalbanese1441 Private E-2

    I have done some more testing and was able to produce some more logs. I noticed that my PC crashed less often with freesync disabled. I also have played around with underclocking and over clocking my card as well as with voltages and I've noticed absolutely no difference at all. I've also dropped my monitor refresh rate down to 60 Hertz and have also not noticed anything. Most of the time, like 99% of the time, my game crashes when playing Rainbow 6 Siege I have uninstalled the game and reinstall the game repeated that on a different SSD it have seen no difference (Also did the same from battleye). I'm hoping these new logs could help me. anything you guys can do is greatly appreciated. thanks.


    https://www.dropbox.com/s/p6w5h9cx8r0vkaw/AMD Bug Report.zip?dl=0
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds