Computer randomly crashes with no error log

zbook · 21 Aug 2019

Nice progress.

Check to make sure Windows settings were maintained for startup and recovery system failure:

Automatic memory dump
Automatically restart unchecked

Dakoyta · 04 Sep 2019

I am still having the same issue. I havn't used my pc much since we last spoke. However yesterday I finally did and I crashed ~3 times and already once today within about 40 minutes of use.

Computer is still not saving any dump files.

zbook · 04 Sep 2019

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

2) Some steps that were done may be repeated

3) Open administrative command prompt and type or copy and paste:
4) sfc /scannow
5) dism /online /cleanup-image /scanhealth
6) dism /online /cleanup-image /restorehealth
7) sfc /scannow
8) chkdsk /scan
9) wmic recoveros set autoreboot = false
10) wmic recoveros set DebugInfoType = 7
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

Spectrum · 08 Sep 2019

From the logs you posted back in August, it seems that all of your bugchecks are either 0x9F, indicating a failure for a device to change power states, or 0xEA, indicating a driver was stuck.

Update drivers for:

Also update motherboard's firmware, you currently have release F31 from 5/6/2019 installed, whereas the latest is F42 from 7/31/2019.
You can get the BIOS update from Gigabyte's support website.

Dakoyta · 03 Nov 2019

Spectrum said:

From the logs you posted back in August, it seems that all of your bugchecks are either 0x9F, indicating a failure for a device to change power states, or 0xEA, indicating a driver was stuck.

Update drivers for:

Also update motherboard's firmware, you currently have release F31 from 5/6/2019 installed, whereas the latest is F42 from 7/31/2019.
You can get the BIOS update from Gigabyte's support website.

I have updated everything as you mentioned right now. I will let you know if I continue to have crashes.

Also here is some temperatures I took prior to the updates on drivers/BIOS

Temps after black screen:
GPU 103 (39 C)
CPU 106 (41 C)
RAM 108 (42 C)

Lastly here is my current set up, do you think my power supply is too weak?

Is my power supply powerful enough?

My setup:
CPU: AMD Ryzen 5 2400G
GPU: Saphire RX 560
RAM: 4 x 8 GB DDR4 - 2400
Memory: 250 SSD & 2 TB SSHD
Fans: 2 front, 1 rear (+1 if you count the cpu) with LEDs
PSU: 500 Watt 80+ EVGA

Dakoyta · 16 Jan 2020

I was finally able to get a crash log...

Code:

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\091619-9453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff800`71a00000 PsLoadedModuleList = 0xfffff800`71e475b0
Debug session time: Sun Sep 15 00:55:52.878 2019 (UTC - 7:00)
System Uptime: 0 days 3:03:37.596
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: ffffd40c68a18480, The thread currently holding on to the Pnp lock.
Arg4: ffffe406ece7d8e0, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now ffffd40c`68a18480
Unable to load image \SystemRoot\System32\drivers\amd_xata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_xata.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:  Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME:  AB350M-DS3H

SYSTEM_SKU:  Default string

SYSTEM_VERSION:  Default string

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  F31

BIOS_DATE:  05/06/2019

BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT:  AB350M-DS3H-CF

BASEBOARD_VERSION:  x.x

DUMP_TYPE:  2

BUGCHECK_P1: 4

BUGCHECK_P2: 12c

BUGCHECK_P3: ffffd40c68a18480

BUGCHECK_P4: ffffe406ece7d8e0

DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: pci

FAULTING_MODULE: fffff800762b0000 pci

CPU_COUNT: 8

CPU_MHZ: e09

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 11

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-DUOIRF0

ANALYSIS_SESSION_TIME:  01-16-2020 00:15:10.0730

ANALYSIS_VERSION: 10.0.18362.1 x86fre

BAD_STACK_POINTER:  ffffe406ece7d8a8

STACK_TEXT:  
ffffe406`ece7d8a8 fffff800`71c9f046 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffffd40c`68a18480 : nt!KeBugCheckEx
ffffe406`ece7d8b0 fffff800`71faead6 : ffffe406`ece7db10 00000000`000000d7 fffff800`6f63b800 00000000`00000001 : nt!PnpBugcheckPowerTimeout+0x76
ffffe406`ece7d910 fffff800`71a6bc59 : ffffe406`ed68b330 00000019`a6fe40ad 00000001`00000002 ffffd40c`6b54c010 : nt!PopBuildDeviceNotifyListWatchdog+0x16
ffffe406`ece7d940 fffff800`71a6a9b9 : 00000000`00000012 00000000`00989680 00000000`000669bf 00000000`000000d7 : nt!KiProcessExpiredTimerList+0x169
ffffe406`ece7da30 fffff800`71bc4be4 : ffffffff`00000000 ffff9c01`8c240180 ffff9c01`8c251240 ffffd40c`6e7460c0 : nt!KiRetireDpcList+0x4e9
ffffe406`ece7dc60 00000000`00000000 : ffffe406`ece7e000 ffffe406`ece78000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


THREAD_SHA1_HASH_MOD_FUNC:  0efaf37e6601d7f65db9dbe50a219f0403a414f7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d129f84982389b6a6b66dde2f65d6511cbf30745

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.18362.10022

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:  2019-09-15T07:55:52.000Z

OSBUILD:  18362

OSSERVICEPACK:  356

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  1fc2

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
---------

zbook · 16 Jan 2020

Please run V2 and DM log collectors to collect files > upload results:
BSOD - Posting Instructions

Dakoyta · 04 Mar 2020

Attachment 269210

I have attached a new log today.
I have been monitoring my crashes. The crashes are just a all blue or black screen. Like a CPU overheating crash. However, I cleaned and applied new thermal paste 2 months ago.

It crashed last night after a few seconds of closing a game and returning to the desktop. Temps were 61 via Coretemp.
I have enabled overheating warning via my mobo, havn't heard any "alarms" from mobo go off yet.

*UPDATED*

I also realized today on my bios that my CPU voltage was 1.38 and peaked at 1.47. I am not overclocked, sitting on "stock" settings.
Should/How would I lower this? I have read that Ryzen 5 2400 has a problem with high voltage.

zbook · 04 Mar 2020

This is an old thread so some steps will be repeated.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

14) Sometimes there are problems in the bios that produce BSOD

The BIOS: Version/Date American Megatrends Inc. F42d, 10/18/2019

15) Please check to see if this is the most up to date version

16) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

17) To ensure that there are no improper bios settings please reset the bios.

18) Sometimes there can be failure to boot after resetting the bios

19) Backup the computer files to another drive or to the cloud

20) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free
Backup and Restore with Macrium Reflect

21) Create a brand new restore point.
Create System Restore Point in Windows 10

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computer’s CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow
3 Easy Ways to Clear CMOS (Reset BIOS)
How to Clear CMOS (AKA Reset BIOS Settings)

22) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

23) Read these links on Windows driver verifier: (learn how to use the Windows RE commands reset and bootmode to turn off the tool) (do not use the tool until it is communicated in the thread)

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Dakoyta · 04 Mar 2020

Steps:

#1-11 Completed

#12 Pasted:

Code:

Microsoft Windows [Version 10.0.18363.693]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.693

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.693

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>\
'\' is not recognized as an internal or external command,
operable program or batch file.

C:\WINDOWS\system32>
C:\WINDOWS\system32>
C:\WINDOWS\system32>
C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is WINDOWS.

Stage 1: Examining basic file system structure ...
  561408 file records processed.
File verification completed.
  6689 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  272 reparse records processed.
  725578 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  272 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  82086 data files processed.
CHKDSK is verifying Usn Journal...
  38392072 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 242766744 KB total disk space.
  74759996 KB in 399928 files.
    251304 KB in 82087 indexes.
         0 KB in bad sectors.
    680528 KB in use by the system.
     65536 KB occupied by the log file.
 167074916 KB available on disk.

      4096 bytes in each allocation unit.
  60691686 total allocation units on disk.
  41768729 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-DUOIRF0\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-DUOIRF0\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}

C:\WINDOWS\system32>

#13 Default, no overclocking.

#14 Updated to newest bios.
F50a 2019/11/27

#15 Updated 2020/03/04

#16 Motherboard Link
GA-AB350M-DS3H (rev. 1.x) | Motherboard - GIGABYTE U.S.A.

#17, reset bios settings
Done

#18 Boot fail after bios reset?
Booted fine, no issues.

#19 Back up files to another drive
See step 20
#20 Make back up
Done

#21 Make a restore point
Done

#22 Images
A: Posted image of start up and recovery window
Attachment 269230
B: Post image of virtual memory
Attachment 269231
#23 Read posts about drivers..
Done