When you had the prior problem with windows driver verifier what where the test settings used?
Which link did you use?
How did you break the loop?
Run the DM log collector to see what happens with the msinfo32:
BSOD - Posting Instructions - Windows 10 Forums
The DM collector was used five minutes ago, it got stuck with msinfo32 so I ended that exe manually. That dump is already uploaded, making a new one just now will have no difference.
I followed the verifier instructions from this post. Turning it off by cmd didn't work so I restored my restore point.
Is there any info in the event wiever or the watchdog?
Sorry, I meant instructions from this FORUM.
No definitive misbehaving driver identified yet.
There were some boot-start drivers this year that did not load.
Uninstall ESET and Malwarebytes.
Turn on Windows defender.
Uninstall ESET manually using the ESET uninstaller toolESET Knowledgebase
Look at the 2 links on windows driver verifier.
One link has 19 customized tests at one time.
The other has 3 customized tests at one time.
Using 3 tests should enable you to use the tool.
First uninstall Eset and Malwarebytes.
Then run the log collector to see if these software programs were interfering.
They didn't interfiere earlier days, and malwarebytes its actually disabled, so that doesn't make much sense...
I will try verifier this weekend and post back, as I can't right now.
Thank you very much for all the support.
Can you uninstall Oracle VM VirtualBox 5.2.4 during the troubleshooting process?
These are the boot-start drivers that failed to load at the end of January:
If you uninstall Eset, Malwarebytes, and Virtual box that takes care of all of the non-Microsoft drivers with the exception ofCode:Event[577]: Log Name: System Source: Service Control Manager Date: 2018-01-25T17:00:21.360 Event ID: 7026 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: SOBREMESA1 Description: The following boot-start or system-start driver(s) did not load: AFD bam BfLwf CSC dam Dfsc eamonm ehdrv epfw ESProtectionDriver FileCrypt GpuEnergyDrv MsSecFlt NetBIOS NetBT npsvctrig nsiproxy Psched rdbss tdx VBoxDrv VBoxNetLwf VBoxUSBMon vwififlt
bflwfx64.sys
Bigfoot Networks Bandwidth Control Wireless NDIS Light Weight Filter driver
http://www.bigfootnetworks.com/suppo...nloads&_a=view
There were 4 Eset drivers and 3 V box boot- start drivers that had failed to load.
The removal of Eset, malwarebytes, and vbox should reduce the confounding factors.
May the eth driver be the cause??
For any driver problems they can be uninstalled, uninstalled and reinstalled, or updated.
If you can update any driver that misbehaves or has a boot-start problem that should improve performance.
The Eset and Malwarebytes can be uninstalled and reinstalled at a later time.
If you can uninstall V Box that would be useful.
And if you can update or uninstall the software related to bflwfx64.sys that should take care of all of the non-Microsoft drivers that were identified in the event log.
The windows driver verifier tool will stress the other drivers to see which one(s) may be behaving.
For Windows driver verifier these are the methods to turn off the tool. They should be done in order and only if the prior method failed. They are all done using the Windows advanced troubleshooting menu.
1) startup options (not startup repair) > click restart > select #6 safe mode with command prompt > type:
verifier /reset
2) command prompt > Administrator: X:\windows\system32\cmd.exe > X:\sources> type:
verifier /bootmode resetonbootfail
3) system restore
System restore often leads to a loss of the dump file and little progress is made in the troubleshooting.
To practice using the windows advanced troubleshooting menu > open administrative command prompt and type:
shutdown /r /o /f /t 00
An alternative method is to click restart while holding down the shift key.
If there are no problems using windows driver verifier with 3 customized tests you can modify the test settings by increasing the tests 2 -3 at a time up to the 19 used in the Microsoft link. If there is/are problems you could always remove a few and add a few every 3 - 4 hours so that you will have ran through all of the tests. If you do it this way keep the 3 original customized tests during the 48 hours.
I will and post back.
I uninstalled VirtualBox, ESET and MBAM and msinfo32 still fails. Even on safe mode. I will post about verifier when I try it.
Quote