Windows 10: Starting with BSOD after noticing strange symbols in registry

Hi all,I'm not sure what's going on with my PC, but it started with my Desktop Wallpaper not changing - again - and seeing strange symbols in the Registry error (but that's for another topic)So now I've been getting BSOD's the past couple of days. I tried running a chkdsk /R, but it got stuck at around 16% and never got any further than that (how many hours would I have to wait if it's just that it needs a long time to scan?)Anyway, I have my BSOD scan results attached

:)

 

japanese/strange characters in registry?

I also have the strange objects in my registry. Unlike the other poster (vault2008), I have had issues. My computer shuts down and reboots. This has happened around 10 times over the last couple of weeks. I was wondering if it might be related to the
weird symbols.

My friend looked at his Win10 registry on two computers; there were NO strange objects. I don't know how long they have been in mine. I uninstalled Nero and checked the registry to delete Nero there before installing. That's when I noticed the symbols.
(Yesterday)

I'm thinking about setting a restore point and deleting the symbols.

Comments?

 

japanese/strange characters in registry?

I had been following another post on the shut down and reboot issue and have the problem myself as well. Does your pc have AMD graphics by any chance?

 

Update your drivers.
I prefer using Driver booster, but I saw a post that said driver booster is not so good program

 

Hi Gaz1701,

Welcome to Ten Forums BSOD forum.
There were multiple misbehaving software drivers.
aswStm
vsdatant
cmdguard


1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
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
6) Uninstall Avast:
Avast Uninstall Utility | Download aswClear for Avast Removal
7) Uninstall Zone Alarm
ZoneAlarm Uninstall Tool Download
8) Uninstall Superantispyware
SUPERAntiSpyware FAQ - How do I uninstall SUPERAntiSpyware?
9) Uninstall Comodo
How to uninstall Comodo AntiVirus (CAV) - Powered by Kayako Help Desk Software
10) Uninstall Malwarebytes
Malwarebytes Anti-Malware Cleanup Tool Download
11) Turn on Windows defender
12) Open the computer's website for drivers and post a URL or hyperlink into the thread.
13) Run HDTune: HD Tune website
to check the health,
scan for errors, no quick scan but full scan
run a benchmark.
It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following
the health,
the error scan,
the benchmark incl. following
transfer rate,
access time,
burst rate,
cpu usage.
Take Screenshot in Windows 10 General Tips Tutorials
14) open device manager > click view > show hidden devices > expand all rows > look for icons with yellow triangles and black exclamation marks > post images into the thread





Code: Microsoft PS/2 Mouse ACPI\PNP0F03\4&6D8F23D&0 This device is not present, is not working properly, or does not have all its drivers installed.[/quote] vsdatant.sys Zone Alarm TrueVector Device Driver http://www.zonealarm.com/security/en...ce-support.htm
aswStm.sys avast! Antivirus Stream Filter driver http://support.avast.com/

cmdguard.sys COMODO Firewall Pro Sandbox Driver Comodo Discussion Board and Support Forums | Comodo Community Requires registration

Code: 09/12/2017 18:30 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80fc674e844 P4: ffff8e01f66f4fd0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\120917-45281-01.dmp \\?\C:\WINDOWS\TEMP\WER-50437-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_5b3b26963fa6f1db78b293a16420b6e422282_00000000_cab_170f2c2e Analysis symbol: Rechecking for solution: 0 Report Id: 4d458462-cd56-4559-96ca-cd00cf794ef8 Report Status: 2048 Hashed bucket:09/12/2017 18:27 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80fc674e844 P4: ffff8e01f66f4fd0 P5: 0 P6: 10_0_14393 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\120917-45281-01.dmp \\?\C:\WINDOWS\TEMP\WER-50437-0.sysdata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_5b3b26963fa6f1db78b293a16420b6e422282_00000000_03207e54[/quote] Code: Event[16394]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-12-13T17:33:46.724 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Gareth-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\Quarantine\S-1-5-21-899439446-1050486960-3159781026-1001-12132017173344776-ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: Event[16318]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-12-13T16:47:31.390 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Gareth-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21-899439446-1050486960-3159781026-1001-12132017164727842-ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.[/quote] Code: Event[15560]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-12-08T23:17:38.275 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: Gareth-PC Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\PROGRAMDATA\MALWAREBYTES\MBAMSERVICE\S-1-5-21-899439446-1050486960-3159781026-1001-12082017231733629-ntuser.dat' was corrupted and it has been recovered. Some data might have been lost.[/quote]