Windows 10 rebooted every day and dont know why

Link: death.evtx - Google Drive

Windows 10 error, reboots all the time - reinstalled OS, reseated all components, updated drivers and still nothing

The ram when first setup is 2400 - i moved it to 3200, i just chose the auto overclock. unsure on what i need to actually set it too.

RAM: Kingston HyperX Predator RGB 32GB (4x8GB) DDR4
PC4-25600C16 3200MHz Quad Channel Kit
CPU: AMD Ryzen 9 3900X Twelve Core 4.6GHz (Socket AM4) Processor
M/B: Gigabyte X470 Aorus Ultra Gaming AMD X470 (Socket AM4) DDR4
ATX Motherboard

If this helps

I use Aorus app centre easy tune - XMP Profifle - Memory Frequency - 32 DRAm voltage 1.35v

See link: Thanks for looking into this with me

LOKI-(2020-08-02_00-47-21).zip - Google Drive

Please move the page file from E: to C: during the troubleshooting.

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

Code:

Event[4693]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2020-07-14T17:36:06.590
  Event ID: 1004
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: LOKI
  Description: 
Unable to move dump file from the temporary location to the final location.

The computer has rebooted from a bugcheck.
The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8057a80b85d, 0xffffcd8da9a077a0, 0x0000000000000000). A full dump was not saved.


Crash dump initialization failed!

I currently use Hyper-V yes for several VMs

I will complete the PC spec shortly - the hard drives are mainly use for Plex data, cctv, Hyper-V machines, Plex cache data etc

-----------------------

Microsoft Windows [Version 10.0.18363.959](c) 2019 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning 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>dism /online /cleanup-image /scanhealthDeployment Image Servicing and Management toolVersion: 10.0.18362.900Image Version: 10.0.18363.959[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.18362.900Image Version: 10.0.18363.959[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>sfc /scannowBeginning 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 /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 1160960 file records processed.File verification completed. 23603 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 1622 reparse records processed. 1881426 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 1622 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 360234 data files processed.CHKDSK is verifying Usn Journal... 39541792 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 487298766 KB total disk space. 419801872 KB in 770583 files. 516668 KB in 360235 indexes. 0 KB in bad sectors. 1287394 KB in use by the system. 65536 KB occupied by the log file. 65692832 KB available on disk. 4096 bytes in each allocation unit. 121824691 total allocation units on disk. 16423208 allocation units available on disk.C:\WINDOWS\system32>wmic recoveros set autoreboot = falseUpdating property(s) of '\\LOKI\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk16\\Partition2"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7Updating property(s) of '\\LOKI\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk16\\Partition2"'Property(s) update successful.C:\WINDOWS\system32>wmic recoveros get autorebootAutoRebootFALSEC:\WINDOWS\system32>wmic recoveros get DebugInfoTypeDebugInfoType7C:\WINDOWS\system32>bcdedit /enum {badmemory}RAM Defects-----------identifier {badmemory}C:\WINDOWS\system32>

Attachment 290764Attachment 290762Attachment 290762

1) For virtual memory:
a) check the box to Automatically manage paging file size for all drives
b) reboot to maintain settings


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

3) For any hangs or freezes requiring a manual power off / on > report into the thread

4) When was the RAM replaced?

5) The RAM modules were not seen on the Qualified Vendor List (QVL).
Please swap test the RAM modules with RAM displayed on the motherboard's QVL.


6) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums