That's very likely, but if I saw a temp reporting 248, I'd be sure to shut down that unit, pull it apart and look for any obvious signs of a problem.  Obviously something's amiss, since the unit should have shutdown by itself at 80C, unless it was changed in the configuration.  Better safe than burnt to a crisp.

do we need preorders

I fixed the x on the asic in the gui by removing the heatsink and reapplying thermal paste.  However I had the opposite issue others have reported.  There was not enough paste.  Looks like someone got a talking to about using too much and is now being too conservative.  There were large areas of pretty much every chip that had clearly not had any paste on them at all.  I applied paste with an exacto blade to all the chips on both blades and put it back together and now the x is gone.  I'm not sure the hashrate is any better though, still only doing about 430 but its only been a few minutes.

On the bright side it saved you the time of cleaning them up. That took a bit of time for me the other day. Hopefully they will get to 441 for you.

Tell them to take their time and work it out for a few more months so we can ROI

first what clock?

second what psu?

As to the beeping issue when the share difficulty changes, don't most P2Pools allow you to set a user defined share difficulty via the password? The one I use for scrypt mining does anyway.

Yes you can.  Add1024 I believe to end of your payout address.  That'll force it to the highest difficulty supported by the current version of p2pool.

Note this won't at all affect your payout, as this is just the psuedoshare difficulty.  The "real" difficulty is much much higher.

M

I tried OC on both but too many HW errors.  So they were both back to stock.  Since this one that had the x went to a - I tried OCing it again and it seems to work at 225 with zero HW but still can't even pull 430 hashrate.  These are both duds.

Forgot to mention the PSU.  Corsair CX750M.  One per miner.