New
#11
I am not sure why.
I see it with attachment.
Attachment 202093
I am not sure why.
I see it with attachment.
Attachment 202093
I think I was too quick. It's there now and it's the Beta zip, thank you.
I see a lot of Nvidia software installed, other than the necessary video and PhysX drivers. I'd liek you to do the following and see if it helps. You have version 398.36 dated 24/06/2018. Versipn 399.07 dated 27/08/2018 is available from the web site.
Remove and install latest Nvidia drivers:
I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode. Then get the latest driver for your Nvidia card here: NVIDIA Driver Downloads
Then do a custom install of only the NVidia graphics driver and the PhysX driver.
See if that gets rid of the problem.
The event logs are still not in English. Please check carefully and see if you missed a step in adding and activating English.
I reinstalled GPU drivers as advised.
I am checking that thing about languages, but I think I followed guide properly.
Although Windows display language can be easily changed, some system elements will remain in original language. One of these elements is Event Log, events prior to language change.
If something happened when the PC's display language was Czech as in this OP's case, that entry is written and remains in Czech also after changing display language to English. Only events happening after display language change will be written in English.
Nothing much OP can do for it. As far as I can tell from OP's posts and screenshots, display language was correctly changed.
Kari
Last edited by Kari; 03 Sep 2018 at 18:22. Reason: Some typos fixed
A couple of the entries in the event logs were transalated.
There were events related to chkdsk and nvlddmkm.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) 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
5) chkdsk /r /v
Run this command on all drivers using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.
This may take many hours so plan to run overnight.
C:\WINDOWS\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)
Type: Y
reboot
6) Use the txt and images in this thread to find the chkdsk reports in the event viewer > copy and paste > notepad > post one drive or drop box share links into the thread
7) Update the specs in the "My Computer" section:
System Specs - Fill in at Ten Forums | Windows 10 Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums
Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)
8) The BIOS: BIOS Version/Date American Megatrends Inc. 1.A0, 15/12/2017
There were multiple BIOS upgrades in 2018.
Select the most applicable up to date BIOS firmware for your computer from this link:
Support For B350M MORTAR | Motherboard - The world leader in motherboard design | MSI Global
Code:Event[348]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2018-08-12T11:37:55.033 Event ID: 98 Task: N/A Level: Upozornınİ Opcode: Informace Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-79HN2PS Description: Svazek F: (\Device\HarddiskVolume7) vy×aduje online kontrolu. Online kontrola bude automaticky spuÜtına v rßmci dalÜİ naplßnovanÚ ˙lohy ˙dr×by. DalÜİ mo×nostİ je spustit p°İkaz CHKDSK /SCAN mİstnı na p°İkazovÚm °ßdku, p°İpadnı p°İkaz REPAIR-VOLUME <jednotka:> -SCAN, a to bu´ mİstnı, nebo vzdßlenı prost°ednictvİm rozhranİ PowerShell.
Code:Event[1396]: Log Name: System Source: Display Date: 2018-08-29T09:39:22.279 Event ID: 4101 Task: N/A Level: Upozornınİ Opcode: Informace Keyword: KlasickÚ nastavenİ User: N/A User Name: N/A Computer: DESKTOP-79HN2PS Description: OvladaŔ zobrazenİ nvlddmkm p°estal odpovİdat a byl ˙spıÜnı obnoven.
Okay, thank you Kari. Makes sense now that you've explained it to me. Data already recorded would not be translated to a different language.
@Dolovias, sorry for not understanding. Will keep working on this and ask for translations for any events I need to understand.
Can we start with the ones I already posted please?
Kari,
Please see this link.
Somehow the OP was able to change the languge to English using Windows home and the logs (old) changed to English (it did not change on the first attempt).
BSOD in Ryzen 2200G ''CRITICAL PROCESS DIED'' - Windows 10 Forums
Wondering if there is a step in one thread that may be different?
As you commented I had noticed that some old entries don't change.
And in many of the threads from China or Korea changing the language may create gibberish when changed to English.
Then the only option is to clean install and start the logs in English.
That is very interesting,
Logically thinking it should not happen. Just checked, I have 369 .evtx files in C:\Windows\System32\winevt\Logs, difficult to understand how display language change would also change all these existing log files to another language, instead of only starting to use new display language when appending them. I need to test this.
Anyway, I am happy for the OP that he was able to get you logs to read in English.
Kari