Solved Constant BSoDs (Windows 10)

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
Yes leave it for the time being please, I have only just come online
I will post as soon as possible
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
OK
Send this please
open the attachment and follow the instructions below

Used with the kind permission of Brink - Admin of WindowsTenForums - where I also assist with problems
https://www.tenforums.com/members/brink.html

Save log collector V2 log collector 1.07.zip to where (downloads for example) you want.
Right click on V2 log collector 1.07.zip in the Downloads folder and select Extract all. This will create a V2 log collector 1.07 folder.
Open the V2 log collector 1.07 folder and double click on the log-collector shortcut.
A Command Prompt window will open with the Ten Forums Log Collector running in it. Press the Enter key to start the collection process.
Command Prompt window will open. Press enter to close it. Note the Output location as that is where the zip file is located.
Attach that please to your reply using the upload a file button.
 
Last edited:

Kalmana

Thread Starter
Joined
Jul 6, 2020
Messages
31
I ran it. And it's a bit weird. In the installed apps location in the zip folder, it said i still had sophos installed, when earlier i did follow the steps and it showed that it was fully uninstalled. I'm going to go through the process again of getting it removed. But here is the file either way.

Yeah, looks like the apps are indeed showing up still. And despite the apps not showing up with the microsoft uninstaller tools, they are still showing up in the program folders themselves
 

Attachments

Last edited:

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
You have
CCleaner Smart Cleaning "c:\program files\ccleaner\ccleaner64.exe" /monitor DESKTOP-IMV1NES\Kalmana HKU\S-1-5-21-689797363-1548851331-783936658-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

That running at startup, disable it, it is both unnecessary and unwise to use it on windows 10
CCleaner was very useful on XP and to some extent on 7.
As a system maintenance app on 10 it is no benefit.
As a troubleshooter it has a role to play
 

Kalmana

Thread Starter
Joined
Jul 6, 2020
Messages
31
Okay, it has been disabled.

Honestly, should I just uninstall it? Part of the reason I had it was to help clear registry files when I uninstalled applications. But I recently have been using Ashampoo WinOptimizer 18 for that task, but i found that Ccleaner was able to catch some things that the Ashampoo app wasn't able to find.

Or really, do you have a recommendation for what I should be using for basic maintenance like clearing caches / registry files?
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
Cleaning the registry is the kiss of death
See this
https://community.ccleaner.com/topic/58572-ccleaner-crashing-windows-10/
Not to do with registry but CCleaner
It seems to have produced more problems than it did when it was owned by Piriform
It has for sometime now been owned by Avast.

Ashampoo WinOptimizer 18
With respect you are going the wrong road
Leave windows 10 to look after itself and your system will run far better
Third party maintenance tools, defraggers, optimizers, etc are not needed and will invariably produce problems

Registry cleaners
The problem is and always has been that registry cleaners decide which entry in the registry is not needed
Their decision, is not always correct and they delete a key, a sub key, or modify a value and problems result

"Registry Structure: The Tree, Nodes and Keys
The data is stored in the registry in a tree structure format, for those who have never opened the Registry Editor, you'd find its layout is similar to what you would see when you open your Windows Explorer. Each node within the registry tree contains a key which may have both subkeys and data entries (called values). Depending on the application you run, the application may need only the associated key while others may need the value data set for that specific key. A hive in the registry is a group of keys, subkeys, and values in the registry that has a set of supporting files containing backups of its data. The Windows boot process automatically retrieves data from these supporting files.

AND my attempt to explain it in simple terms - therein lies the problem with the so-called registry cleaner/optimizer programs. the program decides what is not needed and can be deleted. However, frequently the inter-dependence of the various branches of the tree are not recognised by the program AND this is where it goes horribly wrong. - MACBOATMASTER"
 

Kalmana

Thread Starter
Joined
Jul 6, 2020
Messages
31
Gotcha. Okay. I will turn off the cleaners and let Windows do it's own thing then. I'll give it a few days and let you know what happens.
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
I may have found the problem
Event[17336]:
Log Name: System
Source: Ntfs
Date: 2020-07-11T17:13:52.867
Event ID: 55
Task: N/A
Level: Error
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\SYSTEM
Computer: DESKTOP-IMV1NES
Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.
The file reference number is 0x1b000000015e42. The name of the file is "\ProgramData\Razer\GameManager\Logs\GameManagerClient_RazerCentralService.log".

There should NEVER be corruption in the Master File Table
WAIT PLEASE for me to complete this post
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
Re the post above
Open a cmd prompt with admin rights
right click the start flag, left of taskbar
click cmd prompt admin
when the cmd window opens type

chkdsk C: /r

If the response is force dismount type N
The response should then be do you wish to run on restart
type Y
That maybe the response in the first place

When the computer is rebooted and the check completed go to event viewer and get the results please
as here.
https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
I am signing off
I will be back online about 2000hrs UK time
If that chkdsk proves to NOT show problems
Then we will have to look at another approach

Do not worry I am sure we will sort the problem, or at least establish its cause.
 

Kalmana

Thread Starter
Joined
Jul 6, 2020
Messages
31
Honestly, right now I am glad that i'm at least getting somewhere as opposed to blindly running in the dark like I have been.

I'm not too sure what you want from the event log, but here it is. But it looks like at least on step 1 it at least mentions deleting a corrupted list entry


Checking file system on C:
The type of the file system is NTFS.

One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Deleted corrupt attribute list entry
with type code 80 in file 15E42.
Unable to find child frs 0x19af7 with sequence number 0xd.
452352 file records processed.
File verification completed.
10836 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
435 reparse records processed.
Correcting error in index $I30 for file 5FD42.
Correcting error in index $I30 for file 5FD42.
The index bitmap $I30 in file 0x5fd42 is incorrect.
CHKDSK discovered free space marked as allocated in the bitmap for index $I30 for file 5FD42.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ?? ................
Sorting index $I30 in file 5FD42.
618364 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Recovering orphaned file F9A4E1~1 (1585F) into directory file 5FD42.
Recovering orphaned file f9a4e1872494b9c5_0 (1585F) into directory file 5FD42.
Recovering orphaned file 01995A~1 (5FD43) into directory file 5FD42.
Recovering orphaned file 01995a1c997ce40e_0 (5FD43) into directory file 5FD42.
Recovering orphaned file 04216E~1 (5FD44) into directory file 5FD42.
Recovering orphaned file 04216e3f35b22420_0 (5FD44) into directory file 5FD42.
Recovering orphaned file 1D80C0~1 (5FD45) into directory file 5FD42.
Recovering orphaned file 1d80c09e220419f3_0 (5FD45) into directory file 5FD42.
Recovering orphaned file 2A95FC~1 (5FD46) into directory file 5FD42.
Recovering orphaned file 2a95fcfda1c3f72d_0 (5FD46) into directory file 5FD42.
Skipping further messages about recovering orphans.
41 unindexed files scanned.
41 unindexed files recovered to original directory.
0 unindexed files recovered to lost and found.
435 reparse records processed.

Stage 3: Examining security descriptors ...
Cleaning up 160 unused index entries from index $SII of file 0x9.
Cleaning up 160 unused index entries from index $SDH of file 0x9.
Cleaning up 160 unused security descriptors.
Security descriptor verification completed.
Inserting data attribute into file 15E42.
83008 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
452336 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
108661019 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

499446783 KB total disk space.
64057808 KB in 326587 files.
205912 KB in 83008 indexes.
0 KB in bad sectors.
538987 KB in use by the system.
65536 KB occupied by the log file.
434644076 KB available on disk.

4096 bytes in each allocation unit.
124861695 total allocation units on disk.
108661019 allocation units available on disk.

Internal Info:
00 e7 06 00 fc 3f 06 00 95 97 0b 00 00 00 00 00 .....?..........
6f 01 00 00 44 00 00 00 00 00 00 00 00 00 00 00 o...D...........

Windows has finished checking your disk.
Please wait while your computer restarts.
 

Macboatmaster

Trusted Advisor
Spam Fighter
Joined
Jan 14, 2010
Messages
23,900
There are no serious errors on the chkdsk.
The orphaned files as the name suggests means in simple terms, they have no parents,
That means again in very simple terms they were in the the wrong place
As you can see
41 unindexed files recovered to original directory.
The use of your optimizers and other cleaners etc., MAY well be the cause.

What happens is that Windows looks for those files and cannot find them as they are not where they should be.

When a file is needed the whole drive cannot be searched, it searches the Master file table, the index in effect
When they are not there, problems result and as you can see 41 files were NOT indexed

My strong advice is to uninstall all of your WinOptimizers, Ashampoo, CCleaner and whatever else you may have that purports to maintain the system.
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 807,865 other people just like you!

Latest posts

Members online

Top