• Please note that we've updated the Mount & Blade II: Bannerlord save file system which requires you to take certain steps in order for your save files to be compatible with e1.7.1 and any later updates. You can find the instructions here.

Need More Info Game doesn't launch via Steam + web-site support via ticket ignores my ticket for a week.

Users who are viewing this thread

Version number
1.6.4
Branch
Main
Modded/unmodded
No, I didn't use any mods.

Count Rugel

On probation
WBNW
Ok I'm still looking into this but in the meantime can you also delete the Win64_Shipping_Client folder and verify? Might as well try.
Sure. Will do after work.(3-4 hours since this post)

Not sure that will help, but that won't make things worse either. Worth a shot.
 

Count Rugel

On probation
WBNW
Ok I'm still looking into this but in the meantime can you also delete the Win64_Shipping_Client folder and verify? Might as well try.
Hi!
So the update.
Did as you asked. Nothing new unfortunately. I get the process starting in the task manager for a few seconds, after that is shuts down as before. Doesn't matter if I load the launcher usual way or via administrator mode.

Downloaded the Win software development kit, trying to figure out the debugger functions (never used that before, reading manuals). I'm gonna try to launch the launcher via this thing. I've read at StackOverflow that this might show more info for this the .NET Framework error happening.
 

Count Rugel

On probation
WBNW
Btw, here's the log for the debugger when I tried to run the launcher through it.

CommandLine: "D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\TaleWorlds.MountAndBlade.Launcher.exe"

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
ModLoad: 00000190`c4210000 00000190`c422a000 TaleWorlds.MountAndBlade.Launcher.exe
ModLoad: 00007ffd`b9050000 00007ffd`b9245000 ntdll.dll
ModLoad: 00007ffd`96e10000 00007ffd`96e75000 C:\Windows\SYSTEM32\MSCOREE.DLL
ModLoad: 00007ffd`b7330000 00007ffd`b73ee000 C:\Windows\System32\KERNEL32.dll
ModLoad: 00007ffd`b6c90000 00007ffd`b6f59000 C:\Windows\System32\KERNELBASE.dll
ModLoad: 00007ffd`b3ba0000 00007ffd`b3c30000 C:\Windows\SYSTEM32\apphelp.dll
(4134.167c): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00007ffd`b91206b0 cc int 3
0:000> g
ModLoad: 00007ffd`b85d0000 00007ffd`b867c000 C:\Windows\System32\ADVAPI32.dll
ModLoad: 00007ffd`b7b90000 00007ffd`b7c2e000 C:\Windows\System32\msvcrt.dll
ModLoad: 00007ffd`b7810000 00007ffd`b78ab000 C:\Windows\System32\sechost.dll
ModLoad: 00007ffd`b7c30000 00007ffd`b7d5a000 C:\Windows\System32\RPCRT4.dll
ModLoad: 00007ffd`95c30000 00007ffd`95cda000 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
ModLoad: 00007ffd`b72d0000 00007ffd`b7325000 C:\Windows\System32\SHLWAPI.dll
ModLoad: 00007ffd`b5010000 00007ffd`b5022000 C:\Windows\SYSTEM32\kernel.appcore.dll
ModLoad: 00007ffd`b0910000 00007ffd`b091a000 C:\Windows\SYSTEM32\VERSION.dll
ModLoad: 00007ffd`55340000 00007ffd`55e01000 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
ModLoad: 00007ffd`b8cd0000 00007ffd`b8e71000 C:\Windows\System32\USER32.dll
ModLoad: 00007ffd`b6fb0000 00007ffd`b6fd2000 C:\Windows\System32\win32u.dll
ModLoad: 00007ffd`9a360000 00007ffd`9a376000 C:\Windows\SYSTEM32\VCRUNTIME140_CLR0400.dll
ModLoad: 00007ffd`91700000 00007ffd`917bd000 C:\Windows\SYSTEM32\ucrtbase_clr0400.dll
ModLoad: 00007ffd`b7270000 00007ffd`b729b000 C:\Windows\System32\GDI32.dll
ModLoad: 00007ffd`b6770000 00007ffd`b687b000 C:\Windows\System32\gdi32full.dll
ModLoad: 00007ffd`b6a40000 00007ffd`b6add000 C:\Windows\System32\msvcp_win.dll
ModLoad: 00007ffd`b6ae0000 00007ffd`b6be0000 C:\Windows\System32\ucrtbase.dll
ModLoad: 00007ffd`b72a0000 00007ffd`b72d0000 C:\Windows\System32\IMM32.DLL
ModLoad: 00007ffd`b7410000 00007ffd`b7765000 C:\Windows\System32\combase.dll
(4134.167c): Unknown exception - code 04242420 (first chance)
ModLoad: 00007ffd`b7260000 00007ffd`b7268000 C:\Windows\System32\psapi.dll
ModLoad: 00007ffd`43910000 00007ffd`44f10000 C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\26a845b249aefca961715129e3e55539\mscorlib.ni.dll
ModLoad: 00007ffd`b84a0000 00007ffd`b85ca000 C:\Windows\System32\ole32.dll
ModLoad: 00007ffd`b7410000 00007ffd`b7765000 C:\Windows\System32\combase.dll
ModLoad: 00007ffd`b7010000 00007ffd`b7093000 C:\Windows\System32\bcryptPrimitives.dll
ModLoad: 00007ffd`8f670000 00007ffd`8f7bf000 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
ModLoad: 00000190`c44f0000 00000190`c4520000 TaleWorlds.Library.dll
ModLoad: 00000190`c4520000 00000190`c4550000 TaleWorlds.Library.dll
ModLoad: 00007ffd`9eff0000 00007ffd`9f016000 C:\Windows\assembly\NativeImages_v4.0.30319_64\netstandard\f9a59923dd9196982d2a51bca73b78d0\netstandard.ni.dll
ModLoad: 00007ffd`b60a0000 00007ffd`b60b8000 C:\Windows\SYSTEM32\CRYPTSP.dll
ModLoad: 00007ffd`b57d0000 00007ffd`b5804000 C:\Windows\system32\rsaenh.dll
ModLoad: 00007ffd`b6fe0000 00007ffd`b7007000 C:\Windows\System32\bcrypt.dll
ModLoad: 00007ffd`b60c0000 00007ffd`b60cc000 C:\Windows\SYSTEM32\CRYPTBASE.dll
ModLoad: 00007ffd`42c90000 00007ffd`43901000 C:\Windows\assembly\NativeImages_v4.0.30319_64\System\43b97e99fab55055761ec7618b2bf77b\System.ni.dll
ModLoad: 00007ffd`541e0000 00007ffd`54c55000 C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\73d4c7241519af17f6f645768e72fed4\System.Core.ni.dll
ModLoad: 00000190`c4550000 00000190`c4564000 TaleWorlds.TwoDimension.Standalone.dll
ModLoad: 00000190`c4580000 00000190`c4594000 TaleWorlds.TwoDimension.Standalone.dll
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): CLR exception - code e0434352 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): CLR exception - code e0434352 (first chance)
(4134.167c): C++ EH exception - code e06d7363 (first chance)
(4134.167c): CLR exception - code e0434352 (first chance)
ModLoad: 00007ffd`8f7c0000 00007ffd`8f92a000 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
(4134.167c): CLR exception - code e0434352 (!!! second chance !!!)
KERNELBASE!RaiseException+0x69:
00007ffd`b6cc4f99 0f1f440000 nop dword ptr [rax+rax]
 

Count Rugel

On probation
WBNW
Ok I'm still looking into this but in the meantime can you also delete the Win64_Shipping_Client folder and verify? Might as well try.
I can't uninstall Framework. 4.8 is fully integrated into Win10 as I see. And judging by the fact that clean install of OS to a formatted SSD didn't help at all...

Out of ideas for now.

Is the log in the message above helpful?
 
Last edited:

MRay

Developer
Can you run
Code:
sfc /scannow
in a cmd window?

33232fc8-2344-0210-ba5f-72fffc15339f.png
 

Count Rugel

On probation
WBNW
Can you run
Code:
sfc /scannow
in a cmd window?

33232fc8-2344-0210-ba5f-72fffc15339f.png
Done.

1st iteration found some minor bugs (I believe that was left after power blackout in the neighbourhood a week ago) and fixed them, 2nd iteration found none.

Launcher is still persistent in its unwillingness to function though...
 

TrebuchKill

Recruit
Sorry for inserting myself. While I doubt, I will be of any help, I'll need to give it a shot. Sorry, if it is a waste of time.

Launcher in Steam isn't launching at all. Not even an error message shows up.
How exactly are you launching the launcher? Are you going into the steam client, using a steam created desktop shortcut or a self created desktop shortcut?
Did you try launching "TaleWorlds.MountAndBlade.Launcher.exe" directly from it's install directory? (Not the .Singleplayer/.Multiplayer variants)
Are you able to run "Bannerlord.exe" directly (not .native.exe)? Is it present (same directory as the launcher: Bannerlord\bin\Win64_Shipping_Client), with this exact spelling (capital B, rest small)?
 

Count Rugel

On probation
WBNW
Sorry for inserting myself. While I doubt, I will be of any help, I'll need to give it a shot. Sorry, if it is a waste of time.


How exactly are you launching the launcher? Are you going into the steam client, using a steam created desktop shortcut or a self created desktop shortcut?
Did you try launching "TaleWorlds.MountAndBlade.Launcher.exe" directly from it's install directory? (Not the .Singleplayer/.Multiplayer variants)
Are you able to run "Bannerlord.exe" directly (not .native.exe)? Is it present (same directory as the launcher: Bannerlord\bin\Win64_Shipping_Client), with this exact spelling (capital B, rest small)?
Hi!
Ok, I'll anwser point by point.
1) I tried to launch the launcher every way you mentioned. Usually I launch it via Steam of course. None of them work.
2) No, I can't run Bannerlord.exe, only .native.exe. It does present in the same directory as the launcher and has this exact spelling as you gave, with capital B and the rest are small.
 
Last edited:

TrebuchKill

Recruit
Thanks. Btw, some hours after posting, I realized for windows/ntfs the spelling is not important, B or b should have been fine. I did not correct this, because I assumed worst case it would have been wasting less then a minute or so. Sorry for that.

Do you know or is Event Viewer giving you any information, why bannerlord.exe isn't running? As I understand, the launcher is loading bannerlord.exe as a dependency as startup. If bannerlord.exe fails to start, it might be, because it (or one of its dependencies) fails to load, which would affect the launcher starting up. (After doing some more testing, I am not 100% positive about this part. But the launcher definitely depends at some point on bannerlord.exe)

Or in other words: my working theory is: when bannerlord.exe will be able to run, then the launcher should be able to run. Assuming I am correct in Bannerlord.exe being the problem. On the other hand, it could be something, both the launcher and bannerlord.exe are depending on.

Btw, here's the log for the debugger when I tried to run the launcher through it.
After playing with WinDbg myself: did you set the Working Directory (or Start Directory, as WinDbg calls it)? It's important, that the "Working Directory" is set to the directory, where the launcher is in. Otherwise, the will show an log, which may imply bannerlord.exe was not found.
For me the launcher is working, but got almost the same output, when I did not set Working Directory/Start Directory. You can do it by using the "Launch executable (advanced)" option.

Just in case: If you or Taleworlds wishes me to stop, just say so. I didn't see anything in the rules banning other people helping here (or at least try) and for some reason, I think I may be helpful.
 

Count Rugel

On probation
WBNW
Thanks. Btw, some hours after posting, I realized for windows/ntfs the spelling is not important, B or b should have been fine. I did not correct this, because I assumed worst case it would have been wasting less then a minute or so. Sorry for that.

Do you know or is Event Viewer giving you any information, why bannerlord.exe isn't running? As I understand, the launcher is loading bannerlord.exe as a dependency as startup. If bannerlord.exe fails to start, it might be, because it (or one of its dependencies) fails to load, which would affect the launcher starting up. (After doing some more testing, I am not 100% positive about this part. But the launcher definitely depends at some point on bannerlord.exe)

Or in other words: my working theory is: when bannerlord.exe will be able to run, then the launcher should be able to run. Assuming I am correct in Bannerlord.exe being the problem. On the other hand, it could be something, both the launcher and bannerlord.exe are depending on.


After playing with WinDbg myself: did you set the Working Directory (or Start Directory, as WinDbg calls it)? It's important, that the "Working Directory" is set to the directory, where the launcher is in. Otherwise, the will show an log, which may imply bannerlord.exe was not found.
For me the launcher is working, but got almost the same output, when I did not set Working Directory/Start Directory. You can do it by using the "Launch executable (advanced)" option.

Just in case: If you or Taleworlds wishes me to stop, just say so. I didn't see anything in the rules banning other people helping here (or at least try) and for some reason, I think I may be helpful.
Well, I have no problem in trying to solve this with multiple minds at work.

So about Event Manager and WinDbg...
I was launching only the launcher right now and it provided me with such error:

Faulting application name: Bannerlord.exe, version: 1.0.0.0, time stamp: 0x6177f622
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0xc9db1934
Exception code: 0xe0434352
Fault offset: 0x0000000000034f99
Faulting process id: 0x3998
Faulting application start time: 0x01d7cf54a4abce8b
Faulting application path: D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\Bannerlord.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 7f101b21-71f8-4d78-a954-97631f8f9499
Faulting package full name:
Faulting package-relative application ID:

Application: Bannerlord.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Console.ReadKey(Boolean)
at TaleWorlds.Starter.Library.Program.Starter()
at ManagedStarter.Program.Main(System.String[])

Fault bucket 1369694686792743484, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Bannerlord.exe
P2: 1.0.0.0
P3: 6177f622
P4: mscorlib
P5: 4.8.4420.0
P6: 6109ca9c
P7: b57
P8: c
P9: System.InvalidOperationException
P10:


And this one is for Laucher:

Faulting application name: TaleWorlds.MountAndBlade.Launcher.exe, version: 1.0.0.0, time stamp: 0x6177f622
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0xc9db1934
Exception code: 0xe0434352
Fault offset: 0x0000000000034f99
Faulting process id: 0x43b8
Faulting application start time: 0x01d7cf54ad64708b
Faulting application path: D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\TaleWorlds.MountAndBlade.Launcher.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 6b203f02-c3f9-4585-849b-06c0cc55d145
Faulting package full name:
Faulting package-relative application ID:

Application: TaleWorlds.MountAndBlade.Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NotSupportedException

Exception Info: System.IO.FileLoadException
at System.Reflection.RuntimeAssembly._nLoad(System.Reflection.AssemblyName, System.String, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(System.Reflection.AssemblyName, System.Security.Policy.Evidence, System.Reflection.RuntimeAssembly, System.Threading.StackCrawlMark ByRef, IntPtr, Boolean, Boolean, Boolean)
at System.Reflection.RuntimeAssembly.InternalLoadFrom(System.String, System.Security.Policy.Evidence, Byte[], System.Configuration.Assemblies.AssemblyHashAlgorithm, Boolean, Boolean, System.Threading.StackCrawlMark ByRef)
at System.Reflection.Assembly.LoadFrom(System.String)
at TaleWorlds.MountAndBlade.Launcher.Program.OnAssemblyResolve(System.Object, System.ResolveEventArgs)
at System.AppDomain.OnAssemblyResolveEvent(System.Reflection.RuntimeAssembly, System.String)

Exception Info: System.IO.FileLoadException
at TaleWorlds.MountAndBlade.Launcher.Program.Main(System.String[])

Fault bucket 2189274514586233090, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: TaleWorlds.MountAndBlade.Launcher.exe
P2: 1.0.0.0
P3: 6177f622
P4: KERNELBASE.dll
P5: 10.0.19041.1202
P6: c9db1934
P7: e0434352
P8: 0000000000034f99
P9:
P10:


Looks like that's NET Framework issue, but strangely I experience this on 2 different OSs - Win7 (2 years ago, dropped my attempts) and Win10 (now), not really old system.

Dunno what could cause this if the only similarity right now is the hardware...

I'll try your option as soon as I'll get to the game again.
 

TrebuchKill

Recruit
Update.
Checked them all.
Nope, no check marks on "read only".
Only the folders have it and it's unremovable - it's automatically sets to every folder on the HDD and sets again if removed (even tried to do it to my 600Gb folder of Steam Library), but files aren't affected. It doesn't impede other games from launching etc.
Btw, I just noticed here you are just mentioning "read only". The post from MRay mentions "unblock". If you look at the image of the specific post, there are the "Attributes: [] Read-only [] Hidden" and below it "Security: *bla bla bla* [] Unblock". If you look up the post and image, see below the "advanced" button (bottom right corner).
As far as I can tell, looking at your last report, considering "bannerlord.exe" (Error 1026), while the crash is unrelated, this crash only happens, because "Taleworlds.Dotnet.dll" could not be loaded or something inside of it couldn't be accessed (as far as I can tell).
Could you please verify, " TaleWorlds.DotNet.dll" exists (same directory as the launcher or bannerlord.exe) and the properties menu of it (Right Click -> Properties) either completely lack the Security section, or if it is present, Unblock is checked? (If I remember correctly, the moment you unblock it, this section vanishes, but I'm not certain.)
This assumes, you did just double click bannerlord.exe in the directory (or equivalent), and not tried running it through WinDbg or something else, as a unset working directory may invalidate this diagnosis.

Can you go over the .dlls and .exes in the "\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client" folder and check their properties to see if they need to be "unblocked" or not?


There should be 174 files, I know it's a lot but I would really appreciate it. You can start from the launcher exe and dlls that have "launcher" in their names.

Edit: If I could read, I would have seen, this was already asked at a later point. Sorry. The rest is probably wrong, too. But I am still curious, why it behaves like "Taleworlds.Dotnet.dll" is missing or it can't load it. All the "I can't read" part is still there but crossed out.
 
Last edited:

Count Rugel

On probation
WBNW
Btw, I just noticed here you are just mentioning "read only". The post from MRay mentions "unblock". If you look at the image of the specific post, there are the "Attributes: [] Read-only [] Hidden" and below it "Security: *bla bla bla* [] Unblock". If you look up the post and image, see below the "advanced" button (bottom right corner).
As far as I can tell, looking at your last report, considering "bannerlord.exe" (Error 1026), while the crash is unrelated, this crash only happens, because "Taleworlds.Dotnet.dll" could not be loaded or something inside of it couldn't be accessed (as far as I can tell).
Could you please verify, " TaleWorlds.DotNet.dll" exists (same directory as the launcher or bannerlord.exe) and the properties menu of it (Right Click -> Properties) either completely lack the Security section, or if it is present, Unblock is checked? (If I remember correctly, the moment you unblock it, this section vanishes, but I'm not certain.)
This assumes, you did just double click bannerlord.exe in the directory (or equivalent), and not tried running it through WinDbg or something else, as a unset working directory may invalidate this diagnosis.



Edit: If I could read, I would have seen, this was already asked at a later point. Sorry. The rest is probably wrong, too. But I am still curious, why it behaves like "Taleworlds.Dotnet.dll" is missing or it can't load it. All the "I can't read" part is still there but crossed out.
Well, unblocking thing isn't my case here.

"Unblock" only shows (as I know) when you access these files remotely via shared drives within home network. It's even mentioned near the check mark - "This file came from another computer and might be blocked to help protect this computer". That's not my case since the hard drive the game runs on is domestic, I just don't have that option showing.

Regarding to the dotnet file - yes, I found it. 51.9KB size, doesn't have "read only" marks on it.


1.png
 

MRay

Developer
That's not my case since the hard drive the game runs on is domestic, I just don't have that option showing.
It's not related to that. Even if the dll is on the hdd, windows won't let you load it if the dll itself came from a different computer(or it thinks it did). For later versions of .net it'll sandbox the loaded dll etc. You don't see the option so it doesn't matter anyway.

I really think there is some dependency missing or corrupted on your computer. Something related to .net framework, directx or windows update idk.
 

Count Rugel

On probation
WBNW
It's not related to that. Even if the dll is on the hdd, windows won't let you load it if the dll itself came from a different computer(or it thinks it did). For later versions of .net it'll sandbox the loaded dll etc. You don't see the option so it doesn't matter anyway.

I really think there is some dependency missing or corrupted on your computer. Something related to .net framework, directx or windows update idk.
Ok.
I'll try every of them out today.
Right now sfc scan doesn't find any problems, .NET framework repair tool either. And as far as I know, when I don't experience any .NET framework related error on my computer with other apps/games/etc.

Looks like my PC doesn't get something right with loading TaleWorlds.TwoDimension.Standalone.dll at some point...

And thanks for explanation about unblocking.)

Will get back to you this evening with the results.
 

Count Rugel

On probation
WBNW
It's not related to that. Even if the dll is on the hdd, windows won't let you load it if the dll itself came from a different computer(or it thinks it did). For later versions of .net it'll sandbox the loaded dll etc. You don't see the option so it doesn't matter anyway.

I really think there is some dependency missing or corrupted on your computer. Something related to .net framework, directx or windows update idk.
Ok.

I've tried reinstalling every piece of softfare listed here. Launcher doesn't react, while installers and fix tools keep telling that everything works in order. Win updates are all installed too. The only option remaining is reinstalling OS from my perspective.
But I sincerely doubt that will help. I've reinstalled OS several times during these 2 years of ownership of the game. And every time I tried to launch the game out of curiosity - it never helped. Even when I switched from Win7 to Win10.

I'll do system reinstal at once if you tell me, but yup, I gave my suspicion on that idea above since the problem was migrating between OSs for 2 years at this PC... And it's unique to the Bannerlord Launcher as far as I remember. Every other occuring problem with dll exceptions with other apps I was able to fix one way or another if they ever happened.

Do we have anything else we might try before going through the reinstall? Asking because, well, reinstalling OS is the last resort measure and kinda tedious to set things running up again everywhere.
 
Last edited:

Klakman

Recruit
Your issue is different than @Count Rugel I'm guessing from the stack that you're able to see the launcher but the game either doesn't open when you press Play or closes immediately.

I suggest you delete the Win64_Shipping_Client folder completely and verify the game.
i have this issue but deleting it and verify doesnt work, i tried alot of things i found on forums nothing worked.
 

SwuXeL

Recruit
M&BWBWF&S
This maybe an empty tought but can you install crystal disk info and tell me about the health of your drives.
 
Top Bottom