Windows 10: BSOD, underperforming GPU, unexpected reboots, reliability history thinks all normal...

Purchased a new build through NZXT, had it since 9/2. Specs below:


Gigabyte X570 AORUS ELITE WIFI

AMD Ryzen 7 3700X 8-Core 3.6GHz

NZXT Aer RGB 2 120mm Fan 2XPG Core Reactor 750W Gold

G.SKILL Trident Z Royal RGB 3600MHz 4 x 8GB

Samsung 970 EVO Plus - 1.0 Tb

NZXT Kraken Z63

Added 1TB Sata HD, and have a powered USB hub plugged in.


*No GPU overlclocking

*XMP enabled as of 11/10


1.Between 9/2 and ~10/15, I had, on numerous occasions experienced freezes - didn't matter if I was running a game, watching YT, or doing absolutely nothing. It would lock up, would lose all inputs so the only option was long-press power.


Finally reached out to NZXT, ultimately reinstalled Windows from USB boot drive. Reinstalled AMD chipset drivers, MOBO drivers, GPU drivers, the lot. Hadn't had that exact issue since.


2. Really since i've gotten it - i've had inconsistent GPU performance. I would get hardware failures when running After Effects and maybe a couple tabs of chrome/YT. FPS in games such as Warzone which is poorly optimized to begin with, i understand I would get anything from 90-100FPS to 30FPS!, it's just never been stable. Error example below:



------------Error that coincided with After Effects crash



Description

A problem with your hardware caused Windows to stop working correctly.



Problem signature

Problem Event Name: LiveKernelEvent

Code: 117

Parameter 1: ffffac89f2aec200

Parameter 2: fffff8046cd60188

Parameter 3: 0

Parameter 4: 297c

OS version: 10_0_19041

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.19041.2.0.0.768.101

Locale ID: 1033



Extra information about the problem

Bucket ID: LKD_0x117_Tdr:3_TdrBug:575504_IMAGE_nvlddmkm.sys_Turing

Server information: c4192b86-69a2-42c6-947f-a78d8242b892






-------------------------- This error is the first time since I was forced to reinstall windows error on 10/21 that the "shut down unexpectedly" occurred.

Problem signature

Problem Event Name: BlueScreen

Code: 10e

Parameter 1: 33

Parameter 2: ffff9581c6de5da0

Parameter 3: 0

Parameter 4: 0

OS version: 10_0_19041

Service Pack: 0_0

Product: 768_1

OS Version: 10.0.19041.2.0.0.768.101

Locale ID: 1033



Extra information about the problem

Bucket ID: 0x10e_33_dxgmms2!VIDMM_PROCESS_ADAPTER_INFO::_VIDMM_PROCESS_ADAPTER_INFO



3. At 12:47am this morning, my computer rebooted itself. I was just on YT, no other resource-heavy applications open.



Event viewer showed the following 3 events at the time the issue occurred:

Critical kernel-power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.





- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>8</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2020-11-11T05:57:20.5458439Z" />

<EventRecordID>26762</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>DESKTOP-O2SRN7C</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="BugcheckCode">313</Data>

<Data Name="BugcheckParameter1">0x2</Data>

<Data Name="BugcheckParameter2">0x0</Data>

<Data Name="BugcheckParameter3">0x0</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">0</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">true</Data>

<Data Name="CheckpointStatus">0</Data>

<Data Name="CsEntryScenarioInstanceIdV2">0</Data>

<Data Name="LongPowerButtonPressDetected">false</Data>

</EventData>

</Event>


Error volmgr



Dump file creation failed due to error during dump creation.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="volmgr" />

<EventID Qualifiers="49156">161</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-11-11T05:57:20.4161601Z" />

<EventRecordID>26759</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="328" />

<Channel>System</Channel>

<Computer>DESKTOP-O2SRN7C</Computer>

<Security />

</System>

- <EventData>

<Data>\Device\HarddiskVolume4</Data>

<Binary>000000000100000000000000A10004C081000200010000C000000000000000000000000000000000</Binary>

</EventData>

</Event>



Error EventLog


The previous system shutdown at 12:41:31 AM on ‎11/‎11/‎2020 was unexpected.





- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="EventLog" />

<EventID Qualifiers="32768">6008</EventID>

<Version>0</Version>

<Level>2</Level>

<Task>0</Task>

<Opcode>0</Opcode>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-11-11T05:57:26.4846774Z" />

<EventRecordID>26751</EventRecordID>

<Correlation />

<Execution ProcessID="0" ThreadID="0" />

<Channel>System</Channel>

<Computer>DESKTOP-O2SRN7C</Computer>

<Security />

</System>

- <EventData>

<Data>12:41:31 AM</Data>

<Data>‎11/‎11/‎2020</Data>

<Data />

<Data />

<Data>7</Data>

<Data />

<Data />

<Binary>E4070B0003000B00000029001F003602E4070B0003000B00050029001F0036023C0000003C000000000000000000000000000000000000000100000000000000</Binary>

</EventData>

</Event>





This is the first time this particular issue occurred. I'm not sure what happened here, and it's pretty frustrating considering this build is 70 days old.

I pulled the following info from my CPU found cmd script from another post

copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"


Also included CPU_Z readout, .txt files including some of the errors pulled from Reliability History, and the errors I received this morning from the event viewer.


https://1drv.ms/u/s!AkQ-EI_NI9iXoHq6qtEdZE8Hi2hk?e=8maEre


Any thoughts/suggestions/ideas would be greatly appreciated. Thank you!

:)

 

Unexpected BSOD

I thought every BSOD is unexpected, apparently sometimes they are... *Smile

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

Show Your Reliability History


Hippsie here's my check list:

1. SFC/DISM
2. Manuel time sync in Date & Time in the CPL
3. WSReset
4. Open up Task Schedular and run these: