Intel(R) MEManuf Version: 7.1.50.1166
Copyright(C) 2005 - 2011, Intel Corporation. All rights reserved.
Platform stepping value is 5
FW Status Register1: 0x1E000245
FW Status Register2: 0x76000002
CurrentState: Normal
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: M0 with UMA
InitComplete: Complete
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC programmed with default values
Get FWU info command…done
Get FWU version command…done
Get FWU feature state command…done
Get ME FWU platform type command…done
Get ME FWU feature capability command…done
Feature enablement is 0x1101C70
gFeatureAvailability value is 0x1
System is running on consumer/1.5M image, start Intel(R) ME Runtime Test
Error 9317: No valid OEM ICC data programmed
Request Intel(R) ME test result command…done
vsccommn.bin was created on 04:35:50 08/08/2012 GMT
SPI Flash ID #1 ME VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xEF4016) ME VSCC value checked
SPI Flash ID #1 BIOS VSCC value is 0x2005
SPI Flash ID #1 (ID: 0xEF4016) BIOS VSCC value checked
FPBA value is 0x0
No Intel Wireless device was found
Request Intel(R) ME Runtime BIST test command…done
Get Intel(R) ME test data command…done
Total of 11 Intel(R) ME test result retrieved
Micro Kernel - Blob Manager: Set - Passed
Micro Kernel - Blob Manager: Get - Passed
Micro Kernel - Blob Manager: Remove - Passed
Policy Kernel - SMBus: Read byte - Passed
Policy Kernel - Power Package: Package 1 supported - Passed
Policy Kernel - Power Package: Default package supported - Passed
Policy Kernel - ME Configuration: Wlan Power Well - Passed
Policy Kernel - ME Configuration: CPU Missing Logic - Passed
Policy Kernel - ME Configuration: M3 Power Rails Available - Passed
Policy Kernel - Embedded Controller: Get power source - Passed
Policy Kernel - Power Package: Live Heap Test - Passed
Clear Intel(R) ME test data command…done
Error 9296: MEManuf Test Failed (9317)
Is this the exact model (A43SD)? Try Flash Programming Tool with command “fptw -greset”. If that does not help, run “MEInfo -verbose” and show us the result. Also, run “fptw -me -d me.bin” and let us know if you see an access error or not.