Double posting is no bother for me, I personally prefer double posting above editing a post with the reason that edits may get ignored because we don't know about it.
This doesn't look good, your Nvidia graphics card is using the filerepository driver, the driver in the drivers directory is not present.
What drivers were installed by driver booster 3?
Please disable driver verifier
- Open an admin command prompt
- Enter "verifier/reset" (without quotes)
Verifier disabled, db3 installed a lot of drivers but not the gpu one's, I used recovery system and installed all them manually with no 3rd party software after that. The biggest problem is that i can't recover the system before the anniversary edition of windows 10 update, I formated the pc and it came with all the updates again. Before that it was working properly
Right now i read that virtualization technology from Intel was causing issues with Windows 10, a lot of people with that same kind of bsod kernel related because of that enabled, I disabled that right now in my Bios settings and will test again
You could hide the update :)
I'm currently hiding the anniversary update from the moment it came to my laptop and have yet to see it returning.
Windows Updates - Hide or Show in Windows 10 - Windows 10 Forums
Thanks for that tip!
I will start testing with the virtualization disabled and see if the bsod's continues, if they do I will try to uninstall that update, will post as soon as I have results, thanks for now axe0!
Hello one more time axe0!
I went back some builds but the one I got I still have problems with windows... posting the 2 bsods I got here and maybe on that you can help, like the same problems before... already executed the sfc /scannow, windows found some problems and fixed them but I still get bsod, got all the drivers manually (device manager) and from manufacturer website, still a little lost in the problems, did the full memtest86 (8 passes) on this new build of win10 and no errors.
Thanks one more time for everything!
Last edited by dmtzera; 19 Aug 2016 at 02:44.
I used the driver verifier one more time and It crashed, the one driver that says "never loaded" is the hwpolicy.sys, that means he is the problem?
Here is the latest minidump (which crashed while the driver verifier was opened and I saw that hwpolicy.sys never loaded)
==================================================
Dump File : 081916-17500-01.dmp
Crash Time : 19/08/2016 04:15:02
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`d19d7f47
Parameter 3 : ffffd000`21f461c8
Parameter 4 : ffffd000`21f459e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+147f47
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10586.162 (th2_release_sec.160223-1728)
Processor : x64
Crash Address : ntoskrnl.exe+147f47
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081916-17500-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10586
Dump File Size : 220.020
Dump File Time : 19/08/2016 04:16:34
==================================================
Upload a new zip, the data you posted isn't very useful without a dump.I used the driver verifier one more time and It crashed,
No, it is a driver from Windows.the one driver that says "never loaded" is the hwpolicy.sys, that means he is the problem?
Driver Reference Table - hwpolicy.sys
If it were as easy as saying 'that driver is unloaded, it is causing your problem' many would've diched Windows already. This is because whenever I had checked for unloaded drivers (did it quite often to learn more about the loaded & unloaded modules some months back) the hwpolicy.sys driver was in this list. It is the same with some other Windows drivers.
In order for me to know you did it I requested a photo of the result :)Hello one more time axe0!
I went back some builds but the one I got I still have problems with windows... posting the 2 bsods I got here and maybe on that you can help, like the same problems before... already executed the sfc /scannow, windows found some problems and fixed them but I still get bsod, got all the drivers manually (device manager) and from manufacturer website, still a little lost in the problems
Thanks one more time for everything!
Quote