Hello Fernando,
I re-checked few things and i have got it done!. Everything is working same stable as with old v8.1.0.1248 ME FW.

Additional Edit No. 3:

I checked again all settings.
Then i retried setup told on first page, as first when the directory was changed to C:\Win64\ i wrote "FWUpdLcl64" then waited ca. 0.5 min,
then wrote "flash" (without .bat suffix), waited for about 1 min ---- the update procedure started,
and IT worked (why just now, not sooner), then did shut down + power off and after it i removed battery for 1 min.

Then turned pc on and booted to W8.1 U1 OS .... checked It with "MeInfoWin64" command and everything is now working smoothly.
It now shows in ME FW line: 8.1.52.1496

Was my procedure correct or not? Because the system or tool didn't show a warning or error message... as before.
What happened in it?
My PC is working normally - OS is stable, without crashes or BSODS.

So your files and tools worked also for my chipset/pc, now i am really grateful not only for
your advices but mostly for correct installation of provided (by you) new ME FW file.

Now i am really happy. And can proceed to installation of standard up-to-date .exe vga and other drivers.
Down there is the screen from a fresh run of MEInfo64 tool - as proof:

I just read some info, about that using - writing "FWUpdLcl64", that used one commentator
and posted it - it was between 2nd around up to 7th page in this thread.

He wrote there that sometimes the "flash.exe" command didn't worked, so he tried that "FWUpd...64"
or just typed "flash", when his directory was already set to be in that tool's Win64 folder.
And that way it worked in his case.

I didn't modify anything in my original .514 BIOS from MSI or "fixed"
a thing or two in the ME FW flash tool provided by you.

I just retried it, using experience of another member.

The flashing tool successfully finished updating process,
finished all of 19 steps or so, and prompted me for a reboot (shut down).

So, i finally solved it without messing with BIOS "modding". :D

Thanks for all of your help (and also for others experiences)

I have a problem with my newy installed win 8.1 on my laptop. When I put it to sleep, it sleeps properly but when I try to turn it on it lights for one second and it turns off. And then when I turn it on for the 2nd time, it turns on properly but will give an unexpected shutdown error message in event viewer. Could the lower version of MEI firmware/driver cause this issue? I'm thinking this is because of a driver.

Zitat von Fernando im Beitrag #491

---

Zitat von kevindd992002 im Beitrag #490

---

Could the lower version of MEI firmware/driver cause this issue? I'm thinking this is because of a driver.

---

Which "lower version" of the Intel MEI firmware/driver are you currently using?

---

Zitat von Fernando im Beitrag #493

---

Zitat von kevindd992002 im Beitrag #492

---

It's the v7.1.60.1193 firmware/v7.1.70.1198 combination.

---

The v7.1.60.1193 ME Firmware is the latest for your system. You may try a later Intel ME driver version, but I doubt, that this will solve your problem.
What about the other BIOS (CPU C-States) and OS (Power Options) settings?

---

Zitat von Fernando im Beitrag #495

---

Zitat von kevindd992002 im Beitrag #494

---

I used a more latest firmware version before flashing the one you recommended. This means that I did a downgrade.

---

According to >this< post your previous Intel ME firmware was v7.1.52.1176. So flashing of the v7.1.60.1193 would have been an update.

Zitat

---

I need to confirm what version is that but I got it from station-drivers before. Can you confirm this on your end?

---

AFAIK I am offering the latest Intel ME Firmware versions within the start post of this thread.
There is an Intel ME Firmware v7.1.85.1216 available (look >here<), but this version is only usable with ME7 5M (Business) systems.

---

Oops! You're right, it was indeed an upgrade. I'm not sure what I was thinking.

Hmmm, I guess if it's the latest then it shouldn't post any problems with sleep. I have to dig in deeper.

Try running "powercfg /energy" from command line, it will generate report about your system power consumption, sleep states and will give you advice on better configuration. There some other fancy parameters, you can Google it for more.
You should also run "powercfg sleepstudy", this might give you some insight into your issues (however, study command line parameters more closely if you have an unexpected shutdown after sleep).

My bet is on corrupt driver(-s), I had something similar on my desktop PC, which was happily dealt with after updating (sometimes downgrading) drivers.

Zitat von oxygen15 im Beitrag #497

---

Try running "powercfg /energy" from command line, it will generate report about your system power consumption, sleep states and will give you advice on better configuration. There some other fancy parameters, you can Google it for more.
You should also run "powercfg sleepstudy", this might give you some insight into your issues (however, study command line parameters more closely if you have an unexpected shutdown after sleep).

My bet is on corrupt driver(-s), I had something similar on my desktop PC, which was happily dealt with after updating (sometimes downgrading) drivers.

---

I'm no expert, just gave you some friendly advice in analyzing your issue a little deeper.
And you should install all the drivers for all your hardware, starting with drivers provided by your PC/MoBo manufacturer (support CD or Webpage), because sometimes they tend to tweak their hardware which may not be reflected in generic drivers.

You can post a link to your report here too, probably, it won't harm anyone :)

Zitat von oxygen15 im Beitrag #499

---

I'm no expert, just gave you some friendly advice in analyzing your issue a little deeper.
And you should install all the drivers for all your hardware, starting with drivers provided by your PC/MoBo manufacturer (support CD or Webpage), because sometimes they tend to tweak their hardware which may not be reflected in generic drivers.

You can post a link to your report here too, probably, it won't harm anyone :)

---