Update your post to include full system hardware specs and OS information.
Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?
Disk drive(s): make model, capacity, how full?
= = = =
How close is the air conditioner to the PC? Does the air conditioner blow directly on the PC or just near by?
Consider that there could be two problems: the first problem when PC is "too warm" and the second problem when the PC is "too cool".
And the end result being a matter of expansion or contraction. Something loose tightens (expansion) and regains connectivity. Something tight connected (contracts) and looses connectivity.
All being intermittment and a function of temperature. Vibrations and case air flows may be involved.
Sort of a perfect storm scenerio. Or Gremlins....
Worth a look into Reliability History and Event Viewer for error codes, warnings, and informational events that may be associated with the failures.
= = = =
Power down the PC, unplug, open the case.
Clean out dust and debris.
Verify by sight and feel that all connections, cards, RAM, jumpers, and case connectors are fully and firmly in place.
Use a bright flashlight to inspect for any signs of damage: bare conductor showing, melting, kinked or pinched wires, loose or missing screws, browned or blackened components/areas. GPU sagging, fan blades - dirty, cracked, blocked. Corrosion. Swollen components, scratches, solder joints, any physical damage at all.
= = = =
Revert to a bare bones build with the objective of achieving a reliable pc power on that is independent of air conditioning.
Take your time, be methodical, double check everything (User Guides/Manuals), keep notes. Change only one thing at a time allowing time between changes.
Key is to discover patterns and/or results that can be duplicated at will: If X then pc consistently powers on. If not X then pc fails to consistently power on.
Doing so is going to take some time and effort.
Update your post to include full system hardware specs and OS information.
The link below have most of information you asked and then some...
Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?
Maker: MyMax
Model: ATX 500W 80+ Bronze
Wattage: 500W
Age: 1 year and 3 months
Condition: New
Disk drive(s): make model, capacity, how full?
Disk drivers: Maker: Acclamator SS 512GB
Seagate ST1000DM010-2EP102 (1TB)
= = = =
How close is the air conditioner to the PC? Does the air conditioner blow directly on the PC or just near by?
Air conditioner: About three meters away from computer
Does not blow directly on the PC
The air conditioner is a 220V unit and the PC is 110V
Consider that there could be two problems: the first problem when PC is "too warm" and the second problem when the PC is "too cool".
I live in Rio de Janeiro. I don'nt think there is a "too cool" weather around here. However, "too hot and damp" is , sometimes the case.
And the end result being a matter of expansion or contraction. Something loose tightens (expansion) and regains connectivity. Something tight connected (contracts) and looses connectivity.
All being intermittment and a function of temperature. Vibrations and case air flows may be involved.
Sort of a perfect storm scenerio. Or Gremlins....
Worth a look into Reliability History and Event Viewer for error codes, warnings, and informational events that may be associated with the failures.
Looked into reliability history but could not get any clue from there.
Event viewer has quite a few Event 41, Kernel-Power. General 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.
Below are list of EventData. I am unable to interpret them.
- EventData
BugcheckCode 209
BugcheckParameter1 0x28
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 16
ConnectedStandbyInProgress true
SystemSleepTransitionsToOn 1
CsEntryScenarioInstanceId 13
BugcheckInfoFromEFI true
CheckpointStatus 0
CsEntryScenarioInstanceIdV2 13
LongPowerButtonPressDetected false
LidReliability false
InputSuppressionState 0
PowerButtonSuppressionState 0
LidState 3
There are 19,009 administrative events
Most of them are "Event 7, disk" with the general description "The device, \Device\Harddisk1\DR1, has a bad block."
The first instance of the event is dated: 08/10/2022 17:48:05
The second more frequent is:
"Autopilot.dll WIL error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128
Message: NULL
= = = =
Power down the PC, unplug, open the case.
Clean out dust and debris.
Verify by sight and feel that all connections, cards, RAM, jumpers, and case connectors are fully and firmly in place.
Use a bright flashlight to inspect for any signs of damage: bare conductor showing, melting, kinked or pinched wires, loose or missing screws, browned or blackened components/areas. GPU sagging, fan blades - dirty, cracked, blocked. Corrosion. Swollen components, scratches, solder joints, any physical damage at all.
I did the above recommendation except by cleaning the dust as there was almost none.
I tighten all screws that hold the motherboard (some of them were almost loose).
I did not find any loose connection, card jumpers, case connectors. They all seemed to be firmly in place.
I could not signs of damage, corrosion, swollen components, scratches, solder joint or any other physical damage.
= = = =
Revert to a bare bones build with the objective of achieving a reliable pc power on that is independent of air conditioning.
I will do this tomorrow morning before powering on the air conditioner and having the PC in the same situation that the problem happens.
By "Revert to bare bones" I believe you mean disconnecting everything but memory (including the disk drives). Right?
Take your time, be methodical, double check everything (User Guides/Manuals), keep notes. Change only one thing at a time allowing time between changes.
Key is to discover patterns and/or results that can be duplicated at will: If X then pc consistently powers on. If not X then pc fails to consistently power on.
Doing so is going to take some time and effort.
+=+=+=+=+=+
Thanks for your help!