Sometimes computer enters boot loop, other times I see black screen

zbook said:

For drive performance aim for 20 - 25 % free space.
Windows will automatically delete Memory dump files when free space is < or = 25 GB.
Windows upgrade may fail if free space is < 20 GB.

For a 125 GB drive 25% free space is 31 - 32 GB.
During the troubleshooting process please maintain free space so that it is 30 - 35 GB or more.

There are 3 methods to turn off or recover from using Windows driver verifier.
All methods use 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
The methods used to turn off Windows driver verifer should be used in the above order. Only advance to the next method if the prior method fails. Using system restore often leads to a loss of the dump file and little progress is made in the troubleshooting.

When you feel comfortable using the tool and have made a brand new restore point you can start using it.
For any BSOD > run the beta log collector > post a zip into the thread.
log collector v2-beta08.zip

Finally got around to turn on driver verifier. Got BSOD before Windows finished loading.
Here's log collector output: Attachment 186762

1) Please increase the free space on the Windows drive so that there is > 30 GB available.
At some point a memory dump may be needed for troubleshooting.

Code:

Event[870]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-05-01T00:25:26.062
  Event ID: 1018
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: SIURBLYS
  Description: 
The dump file at location: C:\WINDOWS\MEMORY.DMP was deleted because the disk volume had less than 25 GB free space.

2) Uninstall Virtual Box > restart Windows driver verifier to see if there are other misbehaving drivers.
3) If you need to use virtual box then reinstall it.

VBoxDrv.sys
VirtualBox
Downloads – Oracle VM VirtualBox

4) In the left lower corner search type: msinfo32
Save as NFO > zip > post a one drive or drop box share link into the thread.

1) 29,5 should be good enough
2) Done, it still crashes. Attachment 186766
3) I do, but I guess I can't reinstall it while we haven't finished debugging this.
4) Stays "not responding" for a long while. I'm still waiting for it to finish. Edit: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

1) Uninstall the software related to: atmelwindrvr.sys
Atmel WinDriver

Code:

atmelwindrvr atmelwindrvr           atmelwindrvr           Kernel        Manual     Stopped    OK         FALSE       FALSE        0                 266 240     0          2015-08-12 11:44:44    C:\WINDOWS\system32\drivers\atmelwindrvr.sys     4 096

2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

zbook said:

1) Uninstall the software related to: atmelwindrvr.sys
Atmel WinDriver

Code:

atmelwindrvr atmelwindrvr           atmelwindrvr           Kernel        Manual     Stopped    OK         FALSE       FALSE        0                 266 240     0          2015-08-12 11:44:44    C:\WINDOWS\system32\drivers\atmelwindrvr.sys     4 096

2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

I uninstalled the related software, but the driver is still there. Hmm...

Here are the logs:

Code:

Justas@SIURBLYS C:\Users\Justas
$ sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

Justas@SIURBLYS C:\Users\Justas
$ dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.16299.15

Image Version: 10.0.16299.371

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Keep repeating the uninstall and restart of windows driver verifier until there are no more BSOD.
Then continue running windows driver verifier for an additional 36 hours.

If necessary use Revo uninstaller: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

For anyone reading this in the future after more thorough debugging it appeared to be a faulty chipset. Since fixing it was not trivial I opted to get a new motherboard. After new motherboard was installed the issue never appeared again.

Glad to read about the results.
Thank you for the followup.

The log collector has improved over the past 20 months.
If you upload a V2 the logs can be scanned:
BSOD - Posting Instructions