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

zbook said:

Please make the following changes:
1) Move the dot from custom size to system managed size
2) Check the box to Automatically manage paging file size for all drives
3) Change system failure write debugging information from Kernel memory dump to Automatic memory dump
4) Reboot
5) Recheck the settings for Virtual memory and system failure to make sure that they are reset to the above settings.
6) Indicate the progress made with increasing free space on the C: drive
7) What were the steps made to fix Comodo?

1-6)
Changed the settings to your recommended values and checked they persist after restart.
C: Drive has 32,1GB of free space

7) After a few BSODs windows booted to a system recovery screen. Since I did not have any restore points, the only thing I could think of was to rename the culprit driver in system32. Luckily windows ignored the missing driver on next boot. Once I booted into the system, I renamed the driver back. Then COMODO decided to update (to a version which works with the latest windows update). I then restarted, windows booted normally, and I uninstalled COMODO.

Please run the beta version of the log collector using extract.
Sometimes different browsers may need to be used.
log collector v2-beta08.zip
In case the beta version does not work please use the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums

zbook said:

Please run the beta version of the log collector using extract.
Sometimes different browsers may need to be used.

Not sure what you meant by using extract, or different browsers, but I ran the tool. It had the same warnings this time as well

Code:

Listing installed software...
Get-ItemProperty : Specified cast is not valid.
At D:\_DATA\Desktop\KEK\log collector v2-beta08\resources\main.ps1:267 char:1
+ Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersi ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ItemProperty], InvalidCastException
    + FullyQualifiedErrorId : System.InvalidCastException,Microsoft.PowerShell.Commands.GetItemPropertyCommand

Listing installed Windows updates...
Finding network information...

Here's the zip:
Attachment 178808

Download and install Whocrashed:
http://www.resplendence.com/whocrashed
In the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Click analyze > view whocrashed report > post an image into the thread using a one drive or drop box share link
Run the beta log collector after the crash dump test.
Open file explorer > this PC > C: > in the right upper corner search for memory.dmp > zip > post a share link into the thread

Probably way off here but have you ensured all non essential usb devices are disconnected. I have a different extremely intermittent boot problem which I believe the internal card reader to be responsible for. I won’t bore with the details but does your machine have one of these? Can you disconnect it from the motherboard to test?

it could be power related too. I know you ruled it out but PSU is worth changing out for sure. Not always easy but try a different wall plug if possible

zbook said:

Download and install Whocrashed:
http://www.resplendence.com/whocrashed
In the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Click analyze > view whocrashed report > post an image into the thread using a one drive or drop box share link
Run the beta log collector after the crash dump test.
Open file explorer > this PC > C: > in the right upper corner search for memory.dmp > zip > post a share link into the thread

After the BSOD, I restarted my computer, and it happened again. It rebooted by itself 3 times - on the 3rd reboot it finally booted to windows. That's unusual, it never exited from a bootloop before.

Beta log collector crashed so I ran the other collector:

Code:

New-Item : Access to the path 'C:\Users\Justas\AppData\Local\Temp\error-temp.txt' is denied.
At D:\_DATA\Desktop\KEK\log collector v2-beta08\resources\main.ps1:76 char:1
+ New-Item -ItemType File -Path $ErrorFile -Force -ErrorAction Stop > $ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (C:\Users\Justas...\error-temp.txt:String) [New-Item], UnauthorizedAccessException
    + FullyQualifiedErrorId : NewItemUnauthorizedAccessError,Microsoft.PowerShell.Commands.NewItemCommand

Old logcollector: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Report image: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Memory dump: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Scottyboy99 said:

Probably way off here but have you ensured all non essential usb devices are disconnected. I have a different extremely intermittent boot problem which I believe the internal card reader to be responsible for. I won’t bore with the details but does your machine have one of these? Can you disconnect it from the motherboard to test?

it could be power related too. I know you ruled it out but PSU is worth changing out for sure. Not always easy but try a different wall plug if possible

I don't have any internal card reader. I have previously tried booting my computer with all peripherals disconnected only to face the same issue again.
Unfortunately I can't test the PSU right now as I don't have a replacement. I'm pretty sure the wall plug is fine. But thanks for your input.

The BSOD dump files were debugged and they displayed 2 misbehaving drivers.
There was 1 software driver (Bitdefender) (atc.sys) (atc.sys Thu Feb 01 07:15:34 2018 (5A7312F6))
And there was 1 hardware driver (Nvidia GPU) (nvlddmkm.sys)
nvlddmkm.sys Fri Oct 27 10:49:39 2017 (59F35593)
23.21.13.8813, 16,15



Perform the following steps:
1) Uninstall Bitdefender:
Uninstall Bitdefender
Repairing or removing Bitdefender Free Edition
2) Wait 2 weeks after the last BSOD to reinstall Bitdefender.
If there are BSOD after the reinstallation > find an alternative AV software product
If there are no BSOD after the reinstallation > continue using the AV software product.
The longer the waiting period before reinstalling Bitdefender the stronger the cause and effect..
3) Turn on Windows defender
4) Uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
5) Re-install the Nvidia GPU driver from the Nvidia website
6) Make sure that you check the clean install box and if available install the physx driver.
Display Driver Uninstaller Download version 17.0.8.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
7) If there are any BSOD please run the beta log collector (using extract then open) and post a new zip into the thread: If there are poblems using the beta log collector then use the DM log collector:
log collector v2-beta08.zip
BSOD - Posting Instructions - Windows 10 Forums

Code:

Name    NVIDIA GeForce GTX 770PNP Device ID    PCI\VEN_10DE&DEV_1184&SUBSYS_36061458&REV_A1\4&1286464&0&0008Adapter Type    GeForce GTX 770, NVIDIA compatibleAdapter Description    NVIDIA GeForce GTX 770Adapter RAM    (1 048 576) bytesInstalled Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvldumdx.dllDriver Version    23.21.13.8813INF File    oem49.inf (Section022 section)Colour Planes    Not AvailableColour Table Entries    4294967296Resolution    1920 x 1200 x 59 hertzBits/Pixel    32Memory Address    0xF6000000-0xF70FFFFFMemory Address    0xE0000000-0xE9FFFFFFMemory Address    0xE8000000-0xE9FFFFFFI/O Port    0x0000E000-0x0000EFFFIRQ Channel    IRQ 16I/O Port    0x000003B0-0x000003BBI/O Port    0x000003C0-0x000003DFMemory Address    0xA0000-0xBFFFFDriver    c:\windows\system32\driverstore\filerepository\nv_ref_pubwu.inf_amd64_2e7fa54192fe16d0\nvlddmkm.sys (23.21.13.8813, 16,15 MB (16 936 048 bytes), 2017-11-09 05:40)

nvlddmkm.sys

nVidia Video drivers

http://www.nvidia.com/Download/index.aspx Get from OEM for laptops

zbook said:

Perform the following steps:

OK, thanks for the help. I will do what you suggested and try to reproduce my bootloop problem. Will come back to you with my findings.

zbook said:

If there are BSOD after the reinstallation > find an alternative AV software product
If there are no BSOD after the reinstallation > continue using the AV software product.
The longer the waiting period before reinstalling Bitdefender the stronger the cause and effect..

You might have reasons for suggesting this, and I could just misunderstand them. But I just want to stress that it was never a BSOD problem for me, but rather a bootloop (The only BSOD that I got was a known issue with an incorrect version of COMODO). Also I installed Bitdefender just a few days ago, to replace COMODO.

OK, tried restarting my computer. Got into a bootloop again. As always, playing around with RAM sticks solved the problem.
I think I'm going to try testing RAM again, perhaps I missed one chip or something. I have no other ideas.

Please post a new beta log collector zip using extract followed by open:
log collector v2-beta08.zip
See if it can work with different browsers.
If it does not open to collect the logs then use the DM log collector:
BSOD - Posting Instructions - Windows 10 Forums