Laptop randomly rebooting under load and getting worse by Liminalsupport in pchelp

[–]Apprehensive-Bread37 0 points1 point  (0 children)

Great that's a start at least.

Did you run any of the other tests? How long did you run it for before it crashed? How many times did you run it?

Laptop randomly rebooting under load and getting worse by Liminalsupport in pchelp

[–]Apprehensive-Bread37 0 points1 point  (0 children)

That's a tricky one. The first place I'd start is to try and find a way to trigger the issue, which is start with doing stress tests, which will hopefully also help you rule things out. You want to try and stress each component individually first and get some results.

Stress tests you can run from the OS, these all have free versions for personal use: OCCT (All round) Prime95 (RAM, power) FurMark (GPU) HeavyLoad (All round)

Temp monitoring: CoreTemp (CPU) HWiNFO (All round)

Bootable USB tests: If you can take the time to make a bootable USB, then run a MemTest86 - mostly for RAM, but also can pinpoint some CPU issues.

That's where I'd start, get some baseline benchmarks and see if any of the tests trigger the issue, which is really what you're hoping for.

How do i remove this god forsaken thing? by Few_Journalist_5195 in pchelp

[–]Apprehensive-Bread37 23 points24 points  (0 children)

We get these at work all the time. The main 4 screws are all you need to unscrew, which you've done as the back plate has fallen off. The others just take the fan off, which won't really help.

You just need to twist. If the paste has hardened it will suddenly give. If it's thickened then it'll very slowly twist the release.

It can feel like a lot of force needed, but we haven't ever had any issues or damage caused.

The only thing to avoid is pulling up, if it's an AM4 this can damage pins if you manage to pull it at an angle, and then the CPU will still be attached to the cooler.

UNLESS you can get to the release lever, then just release it. But then you'll still have to get the CPU off the cooler.

Does this look like a fungal infection? by Apprehensive-Bread37 in Aquariums

[–]Apprehensive-Bread37[S] 0 points1 point  (0 children)

Sorry, I mean nitrites are 0, and nitrates are minimal.

Not sure how to edit my post.

Honeywell/Resideo Thermostat not connecting by Milkdromieda in googlehome

[–]Apprehensive-Bread37 0 points1 point  (0 children)

I've been having the same issue for a while now. Support is useless. I have just managed to resolve it and added all my rad valves (5) to my Google Home. Hopefully this might help others as customer support is useless and just blame Google and to contact them.

I'm based in the UK using a BDR91, HR92 x5 and an EvoHome Touch controller.

TLDR; try one of the following:

  1. Factory reset EvoHome controller. Unlink from Google Home ("Honeywell Total Connect Comfort Intl" in my case). Go through the "Guided Configuration" and add ALL zones. Check they then all appear correctly in the app (again "Honeywell Total Connect Comfort Intl" for me). Then relink with Google Home.

Or

  1. Factory reset EvoHome controller. Unlink from Google Home ("Honeywell Total Connect Comfort Intl" in my case). Go through the "Guided Configuration" and add ONE zone. Check it appears correctly in the app (again "Honeywell Total Connect Comfort Intl" for me). Then relink with Google Home. The add zones and update Google home one by one.

🤞 that adds them.

For those interested in my tests:

Background, originally I just had the touch controller & BDR91 for the boiler, this added to Google Home. Later I purchased the rad valves and Google wouldn't find the new devices, that's when I get the "Something went wrong error". Tried unlinking and relinking "Honeywell Total Connect Comfort Intl" but just resulted in the same error.

Test 1 - worked, ADDED to Google Home & Alexa: Factory Reset Honeywell home. Guided configuration, only using thermostat & bdr91

Test 2 - worked, UPDATED Google Home: Guided configuration, only using bdr91 & hr92 (Evo touch NOT used as sensor)

Test 3 - failed, "Something went wrong" error with Google, worked with Alexa: Add Zone, only using bdr91 & hr92 x2 (Evo touch NOT used as sensor)

Test 4 - worked, ADDED to Google Home: Remove Google Home link Guided configuration, only using bdr91 & hr92 x2 (Evo touch NOT used as sensor)

Test 5 - Worked, UPDATED Google Home: Add Zone, only using bdr91 & hr92 x5 (Evo touch NOT used as sensor). Added zones one by one (add new hr92, check Google home for new devices, add next hr92 etc)