This bug was filed from the Socorro interface and is report bp-f59a5f29-ecee-4bba-b9c2-0018a2131202. ============================================================= This looks like another instance of the AMD bug. The Aurora hits show the typical pattern: - Only occurs on one day's build - AMD family 20 model 1 and 2 CPUs - We've inexplicably jumped into the middle of an instruction This is the first known flare-up after the BIOS manufacturer logging was added. Here is the breakdown from 204 hits on 20131128004001: 53 American Megatrends Inc. 35 LENOVO 27 Insyde Corp. 27 Hewlett-Packard 21 Acer 19 AMI 13 TOSHIBA 4 Dell Inc. 3 Infoway Note A7520 1 eMachines 1 Gateway

The above may be skewed by repeated hits from the same users. Here's the breakdown based on 147 unique install-times: 37 American Megatrends Inc. 23 Insyde Corp. 21 LENOVO 19 Acer 16 Hewlett-Packard 14 AMI 9 TOSHIBA 3 Infoway Note A7520 3 Dell Inc. 1 eMachines 1 Gateway

160 unique install times broken down by CPU model: Family 20 Model 1: 20 American Megatrends Inc. 15 Insyde Corp. 11 Hewlett-Packard 11 LENOVO 9 Acer 4 TOSHIBA 3 AMI 2 Infoway Note A7520 1 eMachines 1 Gateway Family 20 Model 2: 21 American Megatrends Inc. 14 LENOVO 12 Acer 11 AMI 10 Insyde Corp. 6 Hewlett-Packard 5 TOSHIBA 3 Dell Inc. 1 Infoway Note A7520

I don't see any of these on crash-stats in the past month

(In reply to Wayne Mery (:wsmwk) from comment #3) > I don't see any of these on crash-stats in the past month That's expected. The AMD bug comes and goes every few months, and often takes a new signature. We may or may not see this one again.

Closing because no crash reported since 12 weeks.

Closing because no crash reported since 12 weeks.