Win10 PC crashes/reboots irregularly. No BSOD. No log events. No overheating.
Win10 PC. Appears to randomly cut power & reboot, no BSOD. Can be while gaming, browsing the internet or doing nothing. I've disabled "reboot after hardware failure" but it still does this.
System details:
CPU: Intel Core i5-6600 (Skylake-S, R0) 3300 MHz (33.00x100.0) @ 800 MHz (8.00x100.0) Motherboard: ASUS Z170-A BIOS: 3802, 03/15/2018 Chipset: Intel Z170 (Skylake PCH-H) Memory: 8192 MBytes @ 1400 MHz, 16-18-18-36 - 8192 MB PC22400 DDR4 SDRAM - Patriot Memory (PDP Systems) 2800 C16 Series Graphics: ASUS STRIX R9 390 DirectCU III OC AMD Radeon R9 390, 8192 MB GDDR5 SDRAM Drive: SanDisk SDSSDA240G, 234.4 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: ST2000DM001-1ER164, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Sound: Intel Skylake PCH-H - High Definition Audio Controller Sound: ATI/AMD Hawaii - High Definition Audio Controller Network: Intel Ethernet Connection I219-V OS: Microsoft Windows 10 Home (x64) Build 18363.693 (1909/November 2019 Update)
As far as I can tell, the only critical event log is that the computer restarted after an unexpected power loss (log entry copied below)
Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 3/8/2020 10:37:32 AM Event ID: 41 Task Category: (63) Level: Critical Keywords: (70368744177664),(2) User: SYSTEM Computer: DESKTOP-GE0UPC6 Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
<System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>6</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2020-03-08T17:37:32.656463900Z" /> <EventRecordID>42353</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>DESKTOP-GE0UPC6</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</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">false</Data> <Data Name="CheckpointStatus">0</Data> </EventData> </Event>Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
Drivers are up to date, BIOS Firmware at most recent available version.
I've run the SFC & DISM scans. One file was found & repaired. Problem persisted.
I suspected the power supply as the usual culprit - replaced it, and problem persisted.
I've run the win10 built in memory tester. PC crashed during this, so i figured it was a memory module. I tried booting without 1, then the other. One failed to POST, the other started fine.
So I started running with 1x8 gig module. This was running issue-free for 1 day.
Then the crashes/restarts started again.
Edit: Steps taken since posting:
Ran memtest86. P.C. died/restarted during first pass.
Bought new ram, installed successfully (updated settings in bios to be correct for new sticks, etc...) problem happened within a few minutes of browsing the web.
Felt bad.
Posted Mar 8, 2020, 6:19 PM UTC · edited
it looks like there is a issue with memory,try memtest86 and perform atleast 4 passes.
normally it will show results if there is a problem with RAM
It happened again Mid-test.
Test was running. Bam, black screen & rebooting.
Seems like my memory has some major issue?
not windows native memory test.
try memetest86 bootable usb drive
That's the test I was running. Installed memtest86 to USB. UEFI boot to test, let tests run on default setting 4 passes. Comp died before 1 full pass.
if memtest86 is dead then its definitely bad memory.
try replacing it