Win7: "Driver overran stack buffer" 0x000000F7 BSOD

[Frick]

Hey hey.

So my boss came to work this morning and the system installed Windows 10 for him. His Elitebook 8560w has Windows 7, automatic updates enabled with "install absolutely everything" on. When it was done with doing its thing, he declined (on the prompt you get), so it reverted the entire thing. But now the computer won't start Windows because of the BSOD. Also the restoration points are all gone, for some reason.

You get as far as the login screen, but the system BSODs almost immedietly. The starting sound gets "stuck" during the BSOD.

Now, the thing is that it seems the drivers causing it are random. So far it's been cause by aksfridge.sys, discache.sys, rdpencdd.sys, usbehci.sys and dfsc.sys. All the times the boss tried rebooting and look for restoration points it was caused by aksfridge.sys, but the times I've tried various things it's been seemingly random.

Safe mode works.

What I've tried so far:

Registry magickery (CCleaner)
chkdsk and sfc /scannow
Memory check with the built in tool, nothing came up
There's nothing to uninstall really, nothing recent anyway, so I haven't uninstalled anything

And now I've no idea, short of a reinstall that it is ... but that would be a bitch. Because it's the bossman's computer, and he has zero concept of sane data storage, or order. Everything important in his life he writes in Sticky Notes (which is extra funny because he has two monitors at the office and the notes randomly rearrange themselves when he goes from laptop mode to desktop mode and vice versa). And he uses Outlook 2010, and I have learned to loathe Outlook, especially when the pst files are approaching several digits of jiggabytes. I did get him an external HDD and told him to make backups, but I suspect he simply uses it for storage. He has already dropped it once, but thank goodness the HDD only came loose from the internal connectors. He looked a bit pale then.

The system is an Elitebook 8560w. 500GB HDD, 4GB RAM, i5 something something, Firepro something something.

Thanks for looking!

EDIT: No wait, there's actually and SSD in there. That's why I don't hate it I suppose.

 

[RejZoR]

Any mention of any .sys file on the BSOD ? That would be helpful.

Also, if Safe Mode works, go to it and check Event Viewer if there are any red marked events and if there is more info in them.

 

[Frick]

Any mention of any .sys file on the BSOD ? That would be helpful.

Aye.

Now, the thing is that it seems the drivers causing it are random. So far it's been cause by aksfridge.sys, discache.sys, rdpencdd.sys, usbehci.sys and dfsc.sys.

And the only related events are the bugchecks and restarts.

 

[RejZoR]

Well, we have to get rid of aksfridge.sys to fix the issue. Apparently it belongs to program/device that isn't compatible with Win10. All I could find is that it's related to Alladin Systems.

Are they using any USB authentication dongles for security or anything along those lines?

Best for now would be to start system in safe mode, run Autoruns app (MS app, Google it) and only uncheck this driver so you'll be able to boot system in normal mode. That should work imo.

Once in normal mode, I suggest you fire up Driver Booster and just scan if it finds any driver that needs updating and is related to Alladin Systems device. I have very good experience with this driver updater, if not for anything, just to see if there is any newer driver in existence.

 

[95Viper]

aksfridge.sys is an ESafe encryption file... if the company uses it then that may be driving the problem.
ESafe is now owned by gemalto... you may need to contact them for support.

Just a bit of info...

End of Sale of eSafe for Windows

Note: eSafe V6 FR2 was the last eSafe version to support Windows.

Please take note of the following important issues regarding eSafe on Windows:

 New products will be released only for HG Appliances, VACD, and VMWare.

 Windows platforms will have product bug fixes, engine security improvements, and updates available according to the product lifecycle (End of Life and End of Updates for version 6.2 will be in December 2010).

 Effective immediately, new installations based on Windows will not be offered. In existing sales processes, customers should install HG or VACD eSafe versions. No new eSafe Windows sales will be allowed from June 30, 2008.

For customers who do insist on Windows installations, please be advised that future versions of eSafe (Version 7) are planned to support VMWare and will be available for installation on a VMWare environment running on Windows based servers.

If not, then, you may want to run some A/V and anti-malware software on it.

 

[Frick]

Well, we have to get rid of aksfridge.sys to fix the issue.

What about the other ones? It's not always that one, it's just the most common. The other ones aren't related to it either.



EDIT: Heeeeyyyy it did it! WHY THE FUDGE WOULD THAT THING CAUSE BUFFER OVERFLOWS IN OTHER DRIVERS? Code monkeys.

 

[RejZoR]

What have you done? Have you disabled the driver with Autoruns or in some other way?

 

[Frick]

What have you done? Have you disabled the driver with Autoruns or in some other way?

Autoruns.

 

[RejZoR]

Cool. Nice to know the recommended solution actually worked