Page 1 of 2 12 LastLast
  1.    28 Jan 2017 #1
    Join Date : Dec 2016
    Posts : 7
    Windows 10 64bit

    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.
      My ComputerSystem Spec
  2.    28 Jan 2017 #2
    Join Date : Jan 2017
    Posts : 32
    Windows 10, MacOS Lion

    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
      My ComputerSystem Spec
  3.    28 Jan 2017 #3
    Join Date : Dec 2016
    Posts : 7
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by GregoryP View Post
    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.
      My ComputerSystem Spec
  4.    28 Jan 2017 #4
    Join Date : Jan 2017
    Posts : 32
    Windows 10, MacOS Lion

    Quote Originally Posted by Vincort View Post
    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.
      My ComputerSystem Spec
  5.    29 Jan 2017 #5
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,343
    Windows 10 Pro X64 16299.19

    <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.
      My ComputersSystem Spec
  6.    30 Jan 2017 #6
    Join Date : Dec 2016
    Posts : 7
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by Ztruker View Post
    <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!
      My ComputerSystem Spec
  7.    30 Jan 2017 #7
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,343
    Windows 10 Pro X64 16299.19

    Enter slmgr /xpr and slmgr /dlv from a Command Prompt. What do you get?
      My ComputersSystem Spec
  8.    30 Jan 2017 #8
    Join Date : Dec 2016
    Posts : 7
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by Ztruker View Post
    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).
      My ComputerSystem Spec
  9.    30 Jan 2017 #9
    Join Date : Apr 2014
    Space coast of Florida
    Posts : 5,343
    Windows 10 Pro X64 16299.19

    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
    Cause

    Bug check 0x50 can occur after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    Another possible cause is the installation of a faulty system service or faulty driver code.
    Antivirus software can also trigger this error, as can a corrupted NTFS volume.
    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
    The 1/28 10:32PM dump shows:
    Code:
    BugCheck 18, {ffffa10cd6227920, ffffa10cdb81d810, 1, 2000000000000000}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+461e )
    Cause

    The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object, the driver calls a kernel routine to increase the reference count of the object by one. When the driver is done with the pointer, the driver calls another kernel routine to decrease the reference count by one.
    Drivers must match calls to the routines that increase (reference) and decrease (dereference) the reference count. This bug check is caused by an inconsistency in the object's reference count. Typically, the inconsistency is caused by a driver that decreases the reference count of an object too many times, making extra calls that dereference the object. This bug check can occur because an object's reference count goes to zero while there are still open handles to the object. It might also occur when the object's reference count drops below zero, whether or not there are open handles to the object.
    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   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   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.
      My ComputersSystem Spec
  10.    02 Feb 2017 #10
    Join Date : Dec 2016
    Posts : 7
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by Ztruker View Post
    Yes, it can be shared here and no need to place anywhere else, just upload a picture here directly.
    ...
    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.
    Last edited by Vincort; 02 Feb 2017 at 16:22.
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Problems with errors in Event Viewer relating to AMD graphics
The error report below I believe is saying that permission is denied accessing a file under ProgramData. This I think is linked to Permissions which appear to be a hot topic with Windows 10. I do have loads of other errors in the ACCEEvent Log...
Graphic Cards
BSOD when starting PC.
Guys I am having a small problem which is kind of bothering me. During start up for some reason the pc bsods and restarts (i cannot physically see the bsod) but i notice cause the bios screen shows up twice. Otherwise the PC is running...
BSOD Crashes and Debugging
Solved Problems starting Windows 10 update
Back when the 10 update first came out, I tried updating from Windows Updates, downloaded ISO/Images from disk and CD, all failing due to the very informative error "Your Windows 10 Update Failed". Anyway, I figured on trying it again, before...
Installation and Upgrade
Windows 10: Constant BSOD errors, different errors each time. HELP!!!!
Hi my name is Peter I am new to this so please excuse any mistakes in posting this I might make. I have very recently built myself a new pc to game on. Once I put the system together and installed windows 10 almost immediately I got BSOD with a...
BSOD Crashes and Debugging
Windows 10 Start menu errors and a few minor problems.
I installed windows 10 a few months ago and I was using it for about 4 weeks, then one day everything on my task bar (including start menu, cortana, calendar volume) stopped responding, only my opened windows worked (Chrome, skype) and there was no...
Performance & Maintenance
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:03.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums