Windows 10 PC, issues with sleep and slow boots

[Mussels]

This is my fiancees machine, recently assembled out of spare parts. Previous setup did not have this issue, so its confusing me. Only real change is the ram and CPU from an i5 2400

i5 2320
Gigabyte GA-Z68A-D3-B3
Corsair GS600W PSU
XFX 6870 1GB
1TB samsung HDD.

Windows 10.


So the problems are fun and interesting:

1. The intel management Interface is showing a Code 10 "status_device_power_failure" in device manager. I've tried 9.5, 10 and 11 drivers from the intel website. same problem on all.

2. Sleep mode simply does not work - waking the system seems to work, after 2 seconds it reboots and powers up from a cold boot like it was hibernated (boots very slowly too). With hibernate disabled, it just does a very slow cold boot.

3. I may just be used to SSD's, but the system seems to boot a lot slower than i expect it should even from a cold boot.

Thoughts, suggestions, fixes etc?

 

[Drone]

Try to upgrade MEI firmware

 

[Mussels]

Try to upgrade MEI firmware

How?

i've found tools that supposedly let me do this, but since the driver wont load they arent working.

 

[Ja.KooLit]

you may have done it already but worth mentioning that have you done cmos reset after change of cpu and ram?

 

[Mussels]

you may have done it already but worth mentioning that have you done cmos reset after change of cpu and ram?

right before making this thread, yes. still a decent idea.

i did a fresh install on a spare HDD, and it had the same problem so its not a software issue unique to the OS install. firmware update seems like a good idea, but i seriously may need to fire up a windows 7 DVD or something to go that route -.-

 

[rtwjunkie]

@Mussels Welcome to the most widespread, yet elusive to pin down problem plaguing W10 even with SSD's! (meaning it's not your HDD)

You can googlebing to your heart's content and try every wild-assed fix out there, but you'll only make a dent in your frustration level.

What has MOSTLY helped me is turning off hibernation by turning off all sleep and power saving options in Windows, and turning off fast boot by deleting hiberfil through the CMD line (as an admin).

Now it only hangs on boot or restart 1 out of 5 times. LOL, and I call that progress. I have two steps to take that look like they might be promising.

I'm going to disable all power saving features in BIOS, and try a new BIOS which was released after W10.

No one, including M$ has figured it out yet. Some of the speculative fixes you'll find come from their own forums where so-called Windows experts seem to be the most clueless of everyone.

Anyway, I listed what has helped me somewhat after 4 weeks.

 

[Drone]

How?

i've found tools that supposedly let me do this, but since the driver wont load they arent working.

If driver won't load then don't use Win version. Usually tools have both versions (Windows and DOS). Try to do that in DOS

 

[Mussels]

If driver won't load then don't use Win version. Usually tools have both versions (Windows and DOS). Try to do that in DOS

good thinking. i shall now attempt that.

 

[Mussels]

even DOS hates me.

"cannot locate ME device driver"

 

[Batou1986]

Update the bios ?
I had to update the bios on a build I did recently to even get win10 to install

 

[Drone]

Didn't try to update bios? The latest version was beta though.

edit: this page says they fixed mei problems in F7 version

http://www.gigabyte.com.au/products/product-page.aspx?pid=3863#bios

 

[Mussels]

the beta for that board was a friggin nightmare and took me hours to downgrade. breaks crossfire/secondary PCI-E slots amongst other things.

its on F11 at present.

 

[Mussels]

Ugh, i dont want to have to go to that beta BIOS since it totally breaks OCing and crossfire on that board, does anyone have tips on how to make the DOS tool work since its not recognising the "device driver" even in DOS?

 

[Drone]

z68 uses Intel ME 7 Consumer 1.5MB Firmware. Current version is 7.1.80.1214.

edit: duh corrected

 

[Mussels]

i just tried something dumb, and it worked.

i tried flashing 7.1 as recommended in one thread, and 8.1. no luck.

reflashed the goddamn BIOS its already on twice in a row and cleared the CMOS for 10 minutes, and its bloody working.

 

[R-T-B]

i just tried something dumb, and it worked.

i tried flashing 7.1 as recommended in one thread, and 8.1. no luck.

reflashed the goddamn BIOS its already on twice in a row and cleared the CMOS for 10 minutes, and its bloody working.

Did you sacrifice a goat or something in between?

Seriously, glad you got it working...

 

[Ja.KooLit]

i just tried something dumb, and it worked.

i tried flashing 7.1 as recommended in one thread, and 8.1. no luck.

reflashed the goddamn BIOS its already on twice in a row and cleared the CMOS for 10 minutes, and its bloody working.

This is something to look into in the future. Weird that older firmware will work with newer OS. Odd but glad you figure it out. Thanks for sharing.

 

[Mussels]

to give some backstory to that board, i think the following was the problem:

I had flashed that board to the BETA BIOS, and had to jump through a ton of hoops to get back on the regular one to fix crossfire and OCing. I was getting slow boots, the MEI driver issues, and 'two boots' when powering on the system like it had failed an OC (and i was getting failed OC warnings some boots)

All of that is gone now. I can only assume that the downgrade process for the BIOS left the wrong firmware version for the MEI on the board, and a reflash/full CMOS clear somehow corrected it.

 

[Ferrum Master]

i just tried something dumb, and it worked.

i tried flashing 7.1 as recommended in one thread, and 8.1. no luck.

reflashed the goddamn BIOS its already on twice in a row and cleared the CMOS for 10 minutes, and its bloody working.

Mussels, I had a clash about things how MEI works few months ago ... well MEI doesn't reflash during bios flash. Those are different regions, after the bios usualy reboots and sets a task upon a fresh boot, the agent wakes up and does the update or flash using intel tool.

You can only use MEI flashers that had came with the same MEI release, same group releases only then they will work.

MEI does not reset using CMOS jumper... actually as I said... there are no thing as CMOS anymore. The code loads up in the firmware hub microcontroller and lives there from the 5SBV and does his mojo NSA related stuff. So you have to power down the device and cut off the power, and only then the microcontroller will load the new firmware bullet proof correctly(it is done code wise to act like that from cold boot), the clear nvram switches tend to not work... as they are seldom tested actually.

As for 6th and X79 mei... you can use only 7.1 and 8.1 for those who has it out of the box from a BIOS update and the bios image is made compatible with it. You cannot up the version so much.