I don't understand why they don't just ask for a DirectX Diagnostic dump. They would get all that information and more.
Not all that info is contained in a dxdiag saved file. They may be wanting to get an idea what sorts of systems the problem occurs with so they can try and replicate it in their lab.
Further update to my observations:
Whilst I have not performed direct testing, It seems that the failure of the Management Engine to initialise is more evident on Cold boots (from power off). It seems to come back after a warm reboot.
As I say I've not had a chance to directly test this (other than a quick warm reboot just now after the first cold boot of the day a few minutes earlier). Otherwise the observations are from occasional checks whilst normal running.
System info DZ68BC / i7-3770 / Memory Kingston HyperX PnP KHX1600C9D3P1K2 (4x4GB - recognised at 1600MHz) / PSU Corsair CX600 V2. No over-clocking either before update to 0036 or since. (added PSU info to previous list)
@Flying_Kiwi / @stephenb.br - The questionnaire that stephenb.br posted is obviously a standard checklist that first line support need to provide when escalating an issue. It is clearly not targeted at this particular issue, and does not provide any hint to me (as a computer support professional myself) as to what Intel already know, suspect or are actively targeting for investigation regarding this issue.
After providing info to Intel they sent me this email
Dear Mr. ---------
Could you please try to do BIOS recovery using the latest BIOS 0036 and Sandy Bridge Processor(s), not Ivy Bridge processor(s). If the issue still remains after that please provide us with the Proof of Purchase of your board and with your address and we will replace the board for you.
And what do you think of that (and why)? If you are not happy, have you put any concerns back to them? I don't know if you are someone who has a ready stock of CPUs on standby for such situations - did you give Intel any reason to believe this is the case?
PS Steve_UK I realise it's a template response but although many may assume thats unecessary information they're asking for, those of us in the know know there's method to their madness. A full system breakdown is often very useful to get a picture of any possible incompatibilities or other possible contributing factors to problems.
I gave them peace of my mind after the above email, and let then know that i cant get and not willing to maybe go purchase a sandy bridge chip for that purpose, and let then know they should fix it through BIOS update which I'm sure it can be done, and that i am not willing to go the replacement board rout unless they agree to send me a latest gen 7 series board eg DZ77RE-75K which i would have to get first before i send my board.
Also sent them more info about the issue and how its a temporary issue that can be sorted through restart, and the issue is slowly disappearing even at cold boot most of the time now the issue is not there, only appears at times now not regularly like when it initially started.
So i suggested they produce a stable BIOS update (VISUAL BIOS)
Thanks for the updates.
I still see the ME initialisation issue on practically all cold boots and on the occasional few warm boot, but thankfully since the Bios 36 update, my system has not failed to initialise the board as a whole.
I had to buy a basic Sandy Bridge Celeron chip to allow me to get a Ivy Bridge compatible BIOS on my board (which came with BIOS 28) so I've already been down that route. I've not been in Hardware support for many years... I felt naked not having a supply of other parts on hand to help confirm and diagnose the issues that I've had with this board...
Are you having any problems with 028 that the PDF on the download page mentions 036 will correct? As always, Intel only recommends updating BIOS versions if that's needed specifically to fix problems a user may be experiencing, otherwise, if it ain't broke, don't try to fix it. Given it's clear there is at least one bug with this version re the thread subject (that wasn't present in previous versions), if I had this board, unless I was experiencing critical issues, I'd at LEAST be holding out for a version which addresses this bug.
BIOS 0037 does not fix Intel ME 0.0.0.0 issue now also causes PCH Temp to show 0
The temporary fix is as usual 1 or 2 restarts and all the issues disappear.
In most cases issue is present during initial boot up (Cold Boot)
So a restart or 2,3 should make the issue disappear.
Hey all, i have run several tests and i have found a permanent fix th the Intel ME 0.0.0.0 and PCH temp showing 0.
The fix is simple i think the BIOS 0035, 0036 & 0037 has rearranged the Memory Slots (RAM Slots), i have found out that in the first slot which is known as DIMM 3 is populated then all the above issues disappear permanently, so to make the issue disappear permanently populate DIMMs
This is for people running two memory sticks
DIMM 3 - Install Memory
DIMM 1 -
DIMM 4 - Install Memory
DIMM 2 -
For people running four memory sticks the issues are not present coz all DIMMs are populated which include DIMM 3
For some reason DIMM 3 acts like the main DIMM, while the main DIMM should be DIMM 1 & 2 if i am not mistaken
So for some reason DIMM 3 acts as main DIMM
If you populate the DIMM 3 and issue does not disappear immediately, then just restart or shut down once and then switch back on and the issue will be gone for good.
Please NOTE BIOS 0035, 0036 & 0037 are all faulty and they need to be fixed so if you dont have Ivy Bridge like Me stay away from them just use 0028
Very interesting discovery. I am assuming you are viewing the slots as follows (i.e., Dimm3 closest to CPU)?
One concern with this "fix"... The manual lists specific configurations for "dual-channel" operation, and says that any other configuration will result in "single channel memory operation". The only listed configuration for (2) Dimms is to use slots 1+2. So I'm wondering if the use of 3+4 (with 1+2 emtpy) will result in downgrading performance to single-channel.
Not sure how to check that -- anyone know how to tell if memory is actually running dual-channel or single-channel?
You assume right I'm viewing the slots in
(i.e., Dimm3 closest to CPU)?
Do not worry the memory will still work in Dual Channel Mode i tested that,
If you populate booth the black slots results to dual channel
If you populate booth the blue slots results to dual channel
If you populate Black and blue or blue and black results to single channel
If you populate all the slots results to dual channel
If you populate 3 in this order DIMM 3 Black, DIMM 1 Blue, DIMM 2 Blue with DIMM 4 left out it resalts in Dual Channel,
I have tried to simplify the above there are other things involved eg Capacity, Memory Speed, Memory Timing all this play some roles in dual or single channel configuration,
Check the Product Guide, or Technical Product Guide.
I'm aware that the Manuals say to Populate DIMM 1 & DIMM 2 (Blue Ones) First. But for this case/Intel ME & PCH Temp issue Populate DIMM 3 & DIMM 4 (Will Operate IN DUAL CHANNEL) If you only have two memory sticks to solve the issues, those who have 4 or 3 RAM sticks should not be having this issues
..."Please NOTE BIOS 0035, 0036 & 0037 are all faulty and they need to be fixed so if you dont have Ivy Bridge like Me stay away from them just use 0028"...
Agreed - A bad 0037 experience from me as well...
Updated to 0037.
Management engines showed 0.0.0.0
Two of my memory sticks are not recognised at a ll(so down to 8GB rather than 16GB)
Extremely unreliable system initialisation - Many "On" button presses the system did not stay on for more than 1 second.
Cleared CMOS memory by removing battery etc no improvement.
Regressed BIOS to 036
Still only 2 of 4 memory sticks seen and system unstable.
I have a lot of work to do tomorrow to reflash bios with SB processor, clear CMOS again and retest 036 and 037 before retrying my IB processor.
To say I'm not happy is an understatement and the fact that there is no clear explanation from Intel is outright disgusting.