Windows 10: BSOD errors and problems when starting up

(REMARK: I made another topic on the same problem (probably) in another subforum, but the problem managed to have fixed itself... until now. These sporadic BSOD are, however, fairly new and might give me any leads towards a solution!)

Every other day my PC does not get past the "Welcome" screen (after signing in). This "infinite" loading screen lasts for more than 20 minutes (with my HDD or other hardware not seeming to be under any load). When in Windows, programs are not getting booted as they should and explorer freezes almost instantly. Restarting the computer does not work. Only after several reboots and other desperate attempts to access my Windows, I manage to get access to the computer... only for a BSOD to make me redo the whole process again.

This is an issue that has been recurring for a few times now, but sometimes with intervals of a few weeks with the PC working perfectly. I did not notice any triggers which cause the PC to act as described above on a given day. Maybe the BSOD logs can make me any wiser (faulty RAM?).

Any help analyzing these files (of my last 2 BSOD crashes of today - a day in which my computer was all but inaccessible) is very appreciated!

Kind regards.

:)

 

Windows 10 wont shutdown properly. lights still on

any solutions sir I have been getting BSOD Critical Process Died when I opened Internet Explorer

The problem started when I got an error when I was using MovieMaker when it suddenly got errors in the program then later on, BSOD.

I do hope for your reply. the problem makes me worry.

 

Windows Store doesnt work.

already runned it, and now my pc got a fatal error : (BSoD) an error like 0xc000021A and it restarts, then when it starts it says my computer has problems starting... im really bored of these f****** errors... T_T i wasted 700€ of my PC

 

I don't see you dumps yet.
faulty RAM may cause randomly BSOD, RAM is very easy to check. good point do it first.
c:\Windows\system32\mdsched.exe

 

Sorry about that! I attached them with this post (dump files)!
Like I said in an earlier thread, memtest86 does not find any errors in the ram! Windows memory diagnosis neither, to be sure I will rerun it.

 

Just checked.

In this case, my opinion, BSOD is hardware problem.
System crashes randomly. But 2 files is not enough to analyze, both of them ntoskrnl.exe problem.

Sometimes is happens. Replace the memory, problem solved.* Or in another case, dual channel was causing the problem, replace the motherboard, problem solved.

 

<LicensingStatus>SL_LICENSING_STATUS_UNLICENSED</LicensingStatus>
@Vincort, you appear to have a illegal installation of Windows 10. Please correct this by installing and activating a legal copy. If you then get any more BSODs, run DM_Log_collector and upload the zip file and I'll be happy to take a look at it.

 

Thanks for your reply. This surprises me, however, because I should have an activated copy of Windows (I bought and used a key, and Windows does not give me any notices of false authentication!)? I will run DM_Log_collector after the next BSOD!

 

Enter slmgr /xpr and slmgr /dlv from a Command Prompt. What do you get?

 

https://i.gyazo.com/1fc1344f27ee9213...428aa78bee.png For the first one. Second one a bunch of codes (Activation ID (& other IDs); License URL;... - not sure whether I can share this on the internet).

 

Yes, it can be shared here and no need to place anywhere else, just upload a picture here directly.

Anyway, it looks like the activation is good, so onward, thanks.

Your BIOS is old. Check the MSI web site for a newer version.

Code: BIOS Version V2.8 BIOS Starting Address Segment f000 BIOS Release Date 12/19/2012[/quote]

The 1/28 7:04PM dump shows this:
Code: BugCheck 50, {ffffa2827f08bf78, 0, fffff8036dae12aa, 2} Could not read faulting driver name Probably caused by : memory_corruption[/quote] The 1/28 10:32PM dump shows:
Code: BugCheck 18, {ffffa10cd6227920, ffffa10cdb81d810, 1, 2000000000000000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+461e )[/quote]

I would start by checking your PC memory using memtest86+.
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

If that doesn't show any problems then enable Driver Verifier as follows, see if that gives us some info.
===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to


PART TWO


and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it.

 

Thanks for your reply. I tried some stuff out, but things didn't change for the better.

• I flashed the BIOS to the most recent version, to no avail.
• I swapped the RAM sticks around (2x4GB). When I put the sticks (both together, and also one by one) in the other two RAM slots (with a different colour), instant BSODs after every start-up were the result. Here, the message was clear: "faceit.sys". This refers to an anti-cheating client (for video games) which I recently installed (report is in attachment). According to me, this is, however, not the deeper root of the problem but more of a consequence. I had very similar problems with the anti-cheat program of another video game (cfr. my earlier post, last year). This leads to the conclusion that my system cannot handle anti-cheat programs (which are known to be very taxing on the RAM).
• After removing the FACEIT program (and again with my RAM sticks in different positions), I still have similar issues to access my system (only in safe mode - like now when I am typing this message - can I use my PC without problems).

In short, I still feel like there is a hardware issue. The issue is that I cannot pinpoint the problem: the separate RAM sticks and RAM slots all show the same problem (so it cannot be one RAM stick or one RAM slot).

Now I will continue to apply the Driver Verifier and I will also consider another night of memtest86+ testing (although I have no clue which RAM set-up to actually test).


EDIT1: With "issues to access my system" I mean: getting into Windows and seeing the desktop. I can use my mouse but no programs can be booted and explorer.exe does not work properly. This is different from what it used to be (stuck on the infinite loading screen after signing in) because I disabled the requirement to sign in with a password (with the hope of fixing this issue).
EDIT2: Given that I cannot access my PC anymore, I cannot run the Driver Verifier. I'll do some "memtesting" and possible a clean install as a Hail Mary attempt. If that doesn't work I might just look out for a new mobo+RAM kit.

 

Please run memtest86+ as requested. Post a picture of the final screen when it's done.

If that doesn't show anything then we can give Driver Verifier a try.

 

Apparently memtest86+ has changed a bit, as I managed to exit the screen without taking a photograph. No errors were found (after 24hours of running...), to be sure I'll run another one over the night (not like my computer has any other use atm - accessing Windows is impossible at every try), with a picture as a result this time.

The thing is I cannot try Driver Verifier as I cannot access my system in its current state. Should I go for the clean install then?

EDIT1: I managed to get Driver Verifier running, I'll let my system idle with this process active.
EDIT2: faceit.sys causes the system to go in an infinite loop of BSOD's again. Now I cannot properly access my PC again (explorer.exe not working as it should): EVERYTHING (e.g. opening file browser) is executed with HUGE delays. I'm switching back to memtest86+.

 

Sounds like a Clean Install may be the best choice.

Follow this tutorial: Windows 10 - Clean Install


What is FaceIt. I don't find a lot about it online. Can you uninstall it?