BSOD, changing error codes, usually after hibernation

darkwhite · 19 Nov 2016

Hello all.

Where to start with this issue?
Ever since I ran the upgrade to Windows 10 coming from Win 7 I am seeing BSODs. So I decided to get rid of any Win 7 remains, bought a new SSD and did a fresh install. The old Win 10 is still sitting on another ssd but is only used whenever i notice i forgot to move some data.
With brand-new SSD and install, the days of bsods seemed to be over, at least until recently when it started to become as bad as before.

Error codes change but are mostly either 0x0000001a, 0x0000007e or 0x0000012b. In most cases, like 9 out of 10, blue screens show up after booting from hibernate and only rarely during normal operations. I do like hibernate mode and would hate to switch it off.

I did the usual stuff, like ran memcheck multiple times (no errors), scandisk, updated all major drivers but I am still having these bsods. would really appreciate if some of the experts here at tenforums could please have a look at these issues and into the files attached: Attachment 110609

Thank you very much in advance.

Ztruker · 19 Nov 2016

You are at 10586 build which is the old Threshold2 release. Do you do image backups? If not I suggest you start, it will simplify recovery when trying different things. Macrium Reflect Free and an external USB hard drive are the best way to go.

Once you have that I suggest installing all updates, including the Anniversary update build 14393 then all updates after that until you get to the latest build which is 14393.447. Is there are BSODs then run DM_Log_collector and upload the zip file and we'll work on the problems with the OS at the latest level.

If things go to hell then use the Macrium Reflect Rescue disc you create the first time you use it, to restore back to the saved image.

Alternatively, do a Clean Install but use the latest available ISO which I believe is 14393 rather than 10586. Apply all updates until you get to 14393.447 then test.

darkwhite · 01 Dec 2016

Hello again,

I updated to the latest build and hoped for the best. First everything seemed to be fine, but the BSODs are back now. I waited some more to present a nice collection of crash dumps. (Which I thereby present here: Attachment 112134)

Like before these BSODs happened after starting up from hibernation, a feature I really would like to use.

Thank you in advance for your help.

Ztruker · 01 Dec 2016

Try a newer Intel Management Engine driver from here: Download IntelÂ® Management Engine Driver (1.5M) for WindowsÂ® 10 for IntelÂ® NUC D54250WYK/B and D34010WYK/B

The one you have is dated 7/7/2015. The one on the Intel website is dated 6/30/2016. May not help but worth a shot.

darkwhite · 04 Dec 2016

Thanks. Installed the newer drivers but unfortunately I am still having the BSODs.

Ztruker · 04 Dec 2016

Run DM_Log_collector again and post the resulting zip file please.

darkwhite · 06 Dec 2016

Here we go: Attachment 112624

Thanks.

Ztruker · 06 Dec 2016

Got some info this time:

Code:

BUGCHECK_STR:  0x139

PROCESS_NAME:  boinc.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

Uninstall BOINC and see if that resolves the problem.

What version do you have installed. The latest beta version says it may be unstable.

BOINC

darkwhite · 08 Jan 2017

Hello and Happy New Year.

Sorry for the late reply, first I had to go on some business trips and then I wanted to make sure I had it all checked out.

Bottom line: You're amazing, you did it!

For a couple of runs, I always paused BOINC before hibernation... no more blue screens at bootup.
Next days I made sure to not pause BOINC ... and had the occasional BSOD at boot
Now I let BOINC run dry so there are no more chunks to compute and just let the tool run as if it had something to do ... no more BSODs.

I do not think anyone before noticed the issue with BOINC (btw: I am running the stable version but will have to check for an update). So I do not know whether there is a fix for it, besides not forgetting to pause prior hibernation.

Thank you, you solved an issue that had kept bugging me for quite some time!

Ztruker · 08 Jan 2017

That's good to hear. Take care.