Author

Topic: S9 Temperature Spiking Issue (Read 162 times)

sr. member
Activity: 1478
Merit: 264
July 31, 2019, 08:35:04 PM
#8
I will try again!

Use mineral oil for cooling and sound damping. The build works but the fuckhead moderators deletes the ideas they don't like!

https://www.youtube.com/watch?v=X-cjF1ZqIsw

I assume it is because they did'nt get it first!
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
July 31, 2019, 08:28:52 PM
#6
Op isolate the bad board.

And run two boards.  You need to clean all boards and fully remove them to do so.

Tricky boards happen.  That board moving up to 135+ is pretty much a death rattle.

Good s9s run with an error rate of under 0.0050%.

That miner is up to 0.0271% which is okay if that temp was not jumping up to 135

The  problem has happened to me and most often board dies once it does this often.
legendary
Activity: 3374
Merit: 3095
BTC price road to $80k
July 31, 2019, 06:03:42 PM
#5
Thanks for ideas, I think it's the sensor, just based on how fast the temperature spikes and then returns to "normal" and that it takes 10mins after turning on for the first spike. And runs normally in between spikes.  Do you have a picture of the temp sensor or anything to help me find it? Or is it something that will be obvious when I pull out the hashboard?

No, I don't have an image for temp sensor I'm honestly looking for this and a hashboard diagram for a long time but no one sharing it.
I just heard that the temp sensor can be found in the middle of the board on the back.

How about moving the hashboard in the middle slot and maybe it will help to remove the temp spike I just got the idea from this reddit post below.

- Bitmain S9 higher temp on one hash board. Also much higher HW errors on Chain #6. Normal?
newbie
Activity: 2
Merit: 0
July 31, 2019, 05:29:39 PM
#4
135 chip temps are always a bad temp and according to "Miner normal operating temperature range" it is a maximum chip temp but according to one of your image it shows 149 which is too bad for your hashboard. It seems a faulty temp sensor if you are getting some temp spike.

Can you try to find which hashboard is getting high chip temp you can check this guide below?

--> https://support.bitmain.com/hc/en-us/articles/226142788-Test-hash-board-one-by-one

After you find the one hashboard which is getting high temp then try to clean the hashboard or look for the temp sensor to clean I don't know where it is located on the board but I heard you can find the temp sensor on the middle back of the hashboard then test it again.

Thanks for ideas, I think it's the sensor, just based on how fast the temperature spikes and then returns to "normal" and that it takes 10mins after turning on for the first spike. And runs normally in between spikes.  Do you have a picture of the temp sensor or anything to help me find it? Or is it something that will be obvious when I pull out the hashboard?

After a few years of operation you might just be seeing signs of wear and components may just start failing. I've never run s9's but when's the last time you checked and cleaned the miner? If it's all clear then you have to take the above advice and figure out which board is faulty and inspect it.

You can do so by disconnecting and reconnecting boards until you isolate the problem. Then you'll need to do a visual inspection for anything out of the ordinary like a scorch mark on the board or something loose. Bonus is that you can still run the machine off 2 boards or find used parts for replacement as they are EOL gear.

I cleaned them out a few months ago with air cans and leaf blower, but I didn't remove any hashboards, so I guess maybe that would be a good idea to do to all of them just in case there is any residual buildup.
legendary
Activity: 1554
Merit: 2036
July 31, 2019, 04:42:20 PM
#3
After a few years of operation you might just be seeing signs of wear and components may just start failing. I've never run s9's but when's the last time you checked and cleaned the miner? If it's all clear then you have to take the above advice and figure out which board is faulty and inspect it.

You can do so by disconnecting and reconnecting boards until you isolate the problem. Then you'll need to do a visual inspection for anything out of the ordinary like a scorch mark on the board or something loose. Bonus is that you can still run the machine off 2 boards or find used parts for replacement as they are EOL gear.
legendary
Activity: 3374
Merit: 3095
BTC price road to $80k
July 31, 2019, 04:33:23 PM
#2
135 chip temps are always a bad temp and according to "Miner normal operating temperature range" it is a maximum chip temp but according to one of your image it shows 149 which is too bad for your hashboard. It seems a faulty temp sensor if you are getting some temp spike.

Can you try to find which hashboard is getting high chip temp you can check this guide below?

--> https://support.bitmain.com/hc/en-us/articles/226142788-Test-hash-board-one-by-one

After you find the one hashboard which is getting high temp then try to clean the hashboard or look for the temp sensor to clean I don't know where it is located on the board but I heard you can find the temp sensor on the middle back of the hashboard then test it again.
newbie
Activity: 2
Merit: 0
July 31, 2019, 03:13:04 PM
#1
My S9's have been mining away uneventfully for a couple years.  Then last week started noticing a lower hashrate with one of them and when I investigated I noticed some temperature display issues.  Not sure if it's actual temperature or maybe its a bad sensor? Seems to change pretty rapidly.

After initial boot-up:
https://imgur.com/zBXooxQ
Notice the top one has a lower overall hashrate.
Miner status of that one:
https://imgur.com/mBOXu5x
At 40 HW already.

A few minutes later it then does this:
https://imgur.com/6RwyLaX
Miner status again:
https://imgur.com/kxkRPzX
Temperature jumped drastically.
And then on the next page refresh
https://imgur.com/NQiZlSG
So over the course of 30 seconds it jumps some 50+ degrees and then back.

Miner System Stats
https://imgur.com/ZWqvhgN

And the log file
https://pastebin.com/BjEEag65

I don't really know what to try next or what needs replacing.  Any help appreciated.  Thanks.
Jump to: