Question Whea-Logger id 18

Nov 25, 2020
11
0
10
0
My newly built PC keeps on restarting randomly. Sometimes, it will run for 6-10 hours without any issue. Then other times it will simply restart when I open an application (browser, tabs, etc.) or games and sometimes it just restarts at its will. Every time it restarts. I using lates drivers and bios. ı can not read dmp files. Can someone help to find problem. Thats my dump files https://1drv.ms/u/s!Aiw32n8H1Nh5gwO7jSdadYFQWUNl?e=HMIqns
 

Darkbreeze

Retired Mod
Hopefully @johnbl or @gardenman will come along to run the dumps, since Rogue leader suggested you come here from PCG for help. In the meantime, it would be very helpful for you to list your full hardware specifications including EXACT model numbers or series/family for all hardware that you know such as CPU, CPU cooler, memory kit (And what exact slots they are installed in), motherboard, power supply (Model. Model. Model. NOT "watts"), graphics card, Windows version and build release version, list of 3rd party installed applications or utilities and maybe a basic outline of what you have already tried that didn't work.
 
Nov 25, 2020
11
0
10
0
My specs: ryzen 3500x
asus b450m dragon bios 2002
Asus tuf 3 evo 5600xt (latest driver installed)
G.skills Ripjaws 8gb 3200mhz cl 16 ram x1 (first slot)
thermaltake 650w (LTP-650al2nk)
my cpu heat max 72 C when ı playing games
I didnt overclock excluding Docp(for ram speed)
windows pro 64 bit 10.0 build 19041
ı tried bios default and I reinstalled windows
 

Darkbreeze

Retired Mod
I don't even SEE a BIOS version that is 2002. Are you sure it isn't 2202? If it's not, then I'd highly recommend that you update to that version and hopefully you did NOT update to version 2406 because the BIOS update page specifically recommends that you do NOT update to that BIOS if you are running Ryzen 3000 series CPUs.


If you are running any version older than 2202, I would update to version 2202 and see if that resolves your issues.

MORE important, by FAR, is the absolutely horrific poor quality of your power supply. The Thermaltake Litepower series are 150% garbage. You need to throw that unit directly into the trash can and get a power supply that is reliable and capable, which that isn't.

Read the information in my guide at the link below for more information.

 
Nov 25, 2020
11
0
10
0
I don't even SEE a BIOS version that is 2002. Are you sure it isn't 2202? If it's not, then I'd highly recommend that you update to that version and hopefully you did NOT update to version 2406 because the BIOS update page specifically recommends that you do NOT update to that BIOS if you are running Ryzen 3000 series CPUs.


If you are running any version older than 2202, I would update to version 2202 and see if that resolves your issues.

MORE important, by FAR, is the absolutely horrific poor quality of your power supply. The Thermaltake Litepower series are 150% garbage. You need to throw that unit directly into the trash can and get a power supply that is reliable and capable, which that isn't.

Read the information in my guide at the link below for more information.

my bios is 2202 . Sorry for the misinformation. I will change my psu at the first opportunity. on the other hand Appmodel-Runtime error id 65 (0x57) error code ErrorCode 87 .
 
Nov 25, 2020
11
0
10
0
XML detail

<Event xmlns=" ">


- <System>
<Provider Name="Microsoft-Windows-AppModel-Runtime" Guid="{f1ef270a-0d32-4352-ba52-dbab41e1d859}" />
<EventID>65</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x2000000000000001</Keywords>
<TimeCreated SystemTime="2020-11-25T22:33:45.1513457Z" />
<EventRecordID>1891</EventRecordID>
<Correlation />
<Execution ProcessID="7696" ThreadID="5224" />
<Channel>Microsoft-Windows-AppModel-Runtime/Admin</Channel>
<Computer>DESKTOP-P6ICE5U</Computer>
<Security UserID="S-1-5-21-448087873-566298773-4018267218-1001" />
</System>
- <EventData>
<Data Name="ErrorCode">87</Data>
<Data Name="PackageFullName">Windows</Data>
</EventData>
</Event>
 

Darkbreeze

Retired Mod
I have no idea about the dumps, but I'd make sure you have ALL the latest drivers from your motherboard product page, I'd run the DDU and install the latest graphics drivers and if you are using an older Windows installation that has seen use on a system prior to this one or has been through several spring or fall major Windows updates, it might be a good idea to do a clean install of Windows.

If you are using peripherals that require third party drivers it would also be a good idea to check for both driver and firmware updates for those as well.

Also, without a quality power supply, that we KNOW is good and is reliable, trying to diagnose any of this stuff is almost a waste of time if we're being honest.
 

Colif

Win 10 Master
Moderator
i looked at dumps, from my limited understanding they aren't telling me a lot. Most of the time the stack text gives a hint of what cause might be but all 5 just say

fffff38a45b8e190 fffff80228159ebf : ffffb785cad23bf0 0000000000000000 ffffb785cad23c10 0000000000000022 : nt!LkmdTelCreateReport+0x13e
fffff38a45b8e6d0 fffff80228159db6 : ffffb785cad23bf0 fffff80200000000 0000005700000000 000000572ca7f6a0 : nt!WheapReportLiveDump+0x7b
fffff38a45b8e710 fffff80227fb628d : 0000000000000001 fffff38a45b8eb80 000000572ca7f6a0 00000000000001e8 : nt!WheapReportDeferredLiveDumps+0x7a
fffff38a45b8e740 fffff80227e9a467 : 0000000000000000 fffff38a45b8ea00 0000000000000103 0000000000000000 : nt!WheaCrashDumpInitializationComplete+0x59
fffff38a45b8e770 fffff80227c06bb8 : ffffb785cc460000 ffffb785cc449d70 fffff38a45b8eb80 ffffb78500000000 : nt!NtSetSystemInformation+0x1f7
fffff38a45b8eb00 00007ff854e8f2d4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000572ca7f648 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`54e8f2d4
which is in first in, last out order, meaning the things at top happened last. System seems to have crashed just getting system information maybe?

strange bios info isn't showing in the dump details. Maybe a clue?

This is all happening at boot, as soon as PC is starting up. Highest uptime in all 5 is about 4 seconds?

a lot of the times event viewer is the last place to look for error information. Many of the errors are one offs and the same transaction works normally every other time.

I didn't even know a 3500X existed, 6 cores,6 threads.
You would have been better off with 2 sticks of ram on ryzen as you get a high frame rate. Even with same amount of ram.

WHEA errors can be any hardware in PC, I have seen them be hdd or anything really... its why I saw called by CPU but not necessarily caused by CPU as it isn't always the CPU.

it could be that PSU... it could be anything.

how to test CPU -
Prime 95 bootable - https://www.infopackets.com/news/10113/how-fix-bootable-prime95-stress-test-hardware

Prime 95 Guide: http://www.playtool.com/pages/prime95/prime95.html
 
Last edited:
Reactions: BlackSangal
all of the memory dumps are red herrings and are secondary to your real problem.
IE the system had a power issue, the motherboard reset the cpu and windows rebooted before the power to the CPU was stable. this caused the CPU to get an internal memory error and call for a bugcheck.

you can turn off fastboot or fast startup (what ever it is called now) and it will reduce the chance of this error. Or you can get a powersupply and motherboard combo that correctly reads the PSU power ok pin. (still does not fix your problem, your system will still hang but it will prevent this bugcheck and you will have a hung system without a debug dump)

I will look a one memory dump to see if I see any clear problem with it.
-----------
yep this debug dumps just shows a cpu starting up and getting internal errors and calling a bugcheck.

you need to look for heating/cooling problems, make sure your bios is up to date, look for power issues.
I would look into some of these drivers: amdgpio3.sys has a different date from the other files
amdtools64.sys would be suspect also depending on what it does.
not sure about some of the others since I do not know what they do.

amdfendr amdfendr.sys Mon Oct 19 17:48:11 2020 (5F8E33CB)
amdgpio2.sys Tue Jan 14 03:57:49 2020 (5E1DACBD)
amdgpio3.sys Mon Mar 14 03:19:36 2016 (56E69038)
amdkmdag.sys Fri Nov 13 12:08:24 2020 (5FAEE7B8)
amdkmpfd.sys Fri Nov 6 12:02:44 2020 (5FA5ABE4)
AMDPCIDev.sys Fri Apr 10 04:34:34 2020 (5E9059CA)
amdppm.sys C9C03000 (This is a reproducible build file hash, not a timestamp)
amdpsp.sys Fri Mar 6 13:04:04 2020 (5E62BAC4)
AmdTools64.sys Thu Feb 15 03:09:50 2018 (5A856A7E)
amdxe amdxe.sys Thu Jul 23 15:18:02 2020 (5F1A0C9A)
AsIO2.sys Tue Apr 9 02:59:16 2019 (5CAC6CF4)

debugger did not know what cpu you had installed. this could be caused by the CPU calling the bugcheck as a panic
 
Last edited:
Reactions: BlackSangal

Darkbreeze

Retired Mod
To be entirely forthcoming, I have to say that in EVERY thread I've ever participated in where there were problems going on and that person had a Thermaltake Litepower power supply, regardless of actual model within that series, the problem WAS undisputedly the power supply. Nothing can work right if the power supply doesn't work right.
 
Nov 25, 2020
11
0
10
0
Thank you for your help and suggestions. Due to the density, I could find time today. I will do stress tests today. In the coming days, I will change psu at the first opportunity.
 
Thread starter Similar threads Forum Replies Date
osarusan Systems 10

ASK THE COMMUNITY