Hi All,
I have an older Core2Quad machine I use as a storage/file server on my home network.
Lately it's been rebooting at random times.. about once per day. I've tried disconnecting everything.. all usb stuff (minus key/mouse), network, etc. Ran prime95 for 12 hours no issue.. no heat issue with cpu.. Ran memtest for over 24 hours and no issue.
Power supply tests fine. it's new too.
I've tried disconnecting things one at a time, and still can't pin the reboots to anything.
Event Viewer has a mess of errors everytime it happens, and it always starts with a 'Critical Kernel-Power' error
Ultimately, I'm wondering if there is a way I can run a trace on the system to catch the reboot in more detail, like what faults before it reboots. All I'm seeing to spawn the reboot is the Kernel-Power error..
Thoughts?
I have an older Core2Quad machine I use as a storage/file server on my home network.
Code:
System Information
------------------
Time of this report: 1/10/2018, 12:19:50
Machine name: SERVER
Machine Id: {DDB48BA5-7600-4BF2-A414-22D9E2B2C0E8}
Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Inspiron 530
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4 CPUs), ~2.4GHz
Memory: 4096MB RAM
Available OS Memory: 4086MB RAM
Page File: 1673MB used, 6507MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.16299.0015 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No sound card was found. If one is expected, you should install a sound driver provided by the hardware manufacturer.
Input Tab: No problems found.
Lately it's been rebooting at random times.. about once per day. I've tried disconnecting everything.. all usb stuff (minus key/mouse), network, etc. Ran prime95 for 12 hours no issue.. no heat issue with cpu.. Ran memtest for over 24 hours and no issue.
Power supply tests fine. it's new too.
I've tried disconnecting things one at a time, and still can't pin the reboots to anything.
Event Viewer has a mess of errors everytime it happens, and it always starts with a 'Critical Kernel-Power' error
Code:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 1/9/2018 11:31:04 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: SERVER
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.
Event Xml:
<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>6</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2018-01-10T05:31:04.987105600Z" />
<EventRecordID>2024</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>SERVER</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">true</Data>
<Data Name="CheckpointStatus">0</Data>
</EventData>
</Event>
Ultimately, I'm wondering if there is a way I can run a trace on the system to catch the reboot in more detail, like what faults before it reboots. All I'm seeing to spawn the reboot is the Kernel-Power error..
Thoughts?
