Page 1 of 3 123 LastLast
  1.    05 Dec 2015 #1
    Join Date : Dec 2015
    Posts : 17
    Windows 10

    Brand new build - different BSODS from a cold boot


    This is a brand new build that I completed a few days ago, and I'm pretty baffled. I've done almost everything in my knowledge to fix the issue. Uninstalled drivers, one at a time, unplugged my additional SSD, and HDD drive, I've re-seated my RAM, reset BIOS, downgraded BIOS too. A lot of the BSOD's I'm getting are -

    Memory_management
    Kernel_security_check_thread

    Possibly one more, I cannot remember. Here is the part list of all my components that I've used in this build. Intel Core i5-6600K, Phanteks Enthoo Evolv ATX - System Build - PCPartPicker


    *Edit, here are some things I've done since; I've removed my SSD that had Win10 installed on it, plugged in another SSD and installed Win10 on it, I got two good boots from being turned off for about 10 mins or so. After that, I've left the PC off for a good two hours, come back to turn it off, and I get a vicious cycle of "Critical_Process_Died".
    Last edited by undead77; 05 Dec 2015 at 21:26.
      My ComputerSystem Spec
  2.    05 Dec 2015 #2
    Join Date : Oct 2013
    NW Florida
    Posts : 9,253
    Windows 10 Enterprise and Pro/Windows 7 Enterprise/Linux Mint

    Hello Undead77 welcome to the forum. You have 2 dump files

    Code:
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd000222af320, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd000222af278, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    and

    Code:
    Use !analyze -v to get detailed debugging information.
    BugCheck C4, {2000, fffff800aa4e4187, 0, 7067444d}
    *** WARNING: Unable to verify timestamp for asmtxhci.sys
    *** ERROR: Module load completed but symbols could not be loaded for asmtxhci.sys
    Probably caused by : asmtxhci.sys ( asmtxhci+4187 )
    Followup:     MachineOwner
    That is your Asmedia USB 3.0 driver Please go to your motherboard's web site and download that driver from MSI. You also have Driver Verifier enabled. Please disable it for right now.

    Please fill out the rest of your system specs in as much detail as possible, including your Hard drives, PSU and CPU cooler. Maybe this will help you.



    Please fill out your System Specs
    information   Information
    Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
    If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. System Specs - Fill in at Ten Forums

    Please post a screenshot of Device Manager https://www.tenforums.com/tutorials/1...en-forums.html

    Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.
      My ComputersSystem Spec
  3.    05 Dec 2015 #3
    Join Date : Dec 2015
    Posts : 17
    Windows 10
    Thread Starter

    I have reinstalled my Asmedia drivers recently, but most recent BSOD may not reflect that. It did give me a different BSOD. I've seen at least 5-6 types of error messages, with and without drivers installed. I have added two more dump files.

    I've been running sfc /scannow quite a bit. Here are my results today.

    C:\Windows\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
      My ComputerSystem Spec
  4.    05 Dec 2015 #4
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,061
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    1. From Admin command, run: chkdsk /r C:
      NOTE: This will take a while to complete
    2. From Admin command, copy and paste the line below then run.
      Dism.exe /online /Cleanup-Image /StartComponentCleanup&dism /online /cleanup-image /restorehealth&sfc /scannow&pause
    3. If sfc still gives error, you might need to re-run sfc multiple times
      My ComputerSystem Spec
  5.    05 Dec 2015 #5
    Join Date : Dec 2015
    Posts : 17
    Windows 10
    Thread Starter

    C:\Windows\system32>dism.exe /online /Cleanup-Image /StartComponentCleanup&dism /online /cleanup-image /restorehealth&sfc /scannow&pause


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================100.0%==========================]
    The operation completed successfully.


    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0


    [==========================100.0%==========================]


    Error: 0x800f081f


    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.


    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    Press any key to continue . . .


    C:\Windows\system32>


    *EDIT* I've ran this two times in a row, same results.
      My ComputerSystem Spec
  6.    05 Dec 2015 #6
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,061
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    You first need to run dism command to fix the component stores then you can proceed to run sfc.
    You also need the Windows 10 ISO from Windows 10 Download - Tech Bench. extract with Winrar or 7-zip

    1- Create a folder on desktop: mount
    2- Copy install.wim to desktop from the extracted ISO in the Sources folder.

    Open Admin Command prompt, copy each line then run:

    Dism /mount-wim /wimFile:%USERPROFILE%\Desktop\install.wim /index:1 /MountDir:%USERPROFILE%\Desktop\mount

    Dism /Online /Cleanup-Image /CheckHealth

    Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\mount\windows /LimitAccess

    Dism /unmount-wim /Mountdir:%USERPROFILE%\Desktop\mount /discard
      My ComputerSystem Spec
  7.    06 Dec 2015 #7
    Join Date : Dec 2015
    Posts : 17
    Windows 10
    Thread Starter

    I did all your steps one by one, and no issues. Here are my results after another sfc /scannow

    C:\Windows\system32>sfc /scannow


    Beginning system scan. This process will take some time.


    Beginning verification phase of system scan.
    Verification 100% complete.


    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.


    C:\Windows\system32>
      My ComputerSystem Spec
  8.    06 Dec 2015 #8
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,061
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    So if understood correctly. The DISM did fix the component stores with no error as indicated in previous post (Error: 0x800f081f). Correct ? Then you run sfc command and still got errors. You need to re-run sfc a few more times until you get it clean.
      My ComputerSystem Spec
  9.    06 Dec 2015 #9
    Join Date : Dec 2015
    Posts : 17
    Windows 10
    Thread Starter

    I rebooted Windows after my last post, ran sfc again, it said integrity was good. I'll continue to monitor and re-run. Can you explain how this is possible on a brand new install of Win10? The original install came from the media creation tool via USB thumbdrive.
      My ComputerSystem Spec
  10.    06 Dec 2015 #10
    Join Date : Jul 2014
    San Jose, California
    Posts : 2,061
    Ubuntu14.04x64 MintMate17x64 Win10Prox64

    Quote Originally Posted by undead77 View Post
    I rebooted Windows after my last post, ran sfc again, it said integrity was good. I'll continue to monitor and re-run. Can you explain how this is possible on a brand new install of Win10? The original install came from the media creation tool via USB thumbdrive.
    The MCT or Techbench would result the same with the installation except the version from MCT was created with compressed install.esd from install.wim, smaller file size, faster download. However, DISM only works with install.wim

    Some people in this forum did have sfc failure with fresh install of Windows. It has something to do with NVDIA driver.

    So now that your Windows got a clean bill of health. Keep monitoring it to see if it BSOD again.

    BTW, did you run: chkdsk /r C:
    as suggested above ?

    In addition, since you said that BSOD's happened randomly and that might be the cause for system files corruption. You might want to download: Memtest86+ - Advanced Memory Diagnostic Tool. Put in a USB and let it run over night to make sure your RAM's are all good.
      My ComputerSystem Spec

 
Page 1 of 3 123 LastLast


Similar Threads
Thread Forum
Win 10 after a cold boot
This happens when I power up the pc and it boots. The desktop appears, and when I click normally on an icon (a desktop shortcut) to open it, it doesn't open. Instead I get the menu that I would get if I had right-clicked on the icon. If I open...
General Support
BSOD from cold boot if computer has been off a while
BSOD happens only when the computer cold boots from a prolonged inactive state. If the PC is off for several hours and is turned on it occurs. Computer typically blue screens, sometimes it freezes at the bios splash screen where they Windows 10...
BSOD Crashes and Debugging
Solved Multiple BSODs playing any games on brand new PC. Various reasons.
--solved--
BSOD Crashes and Debugging
Daily BSODs, brand new HD and windows 10
Hi, I recently got a new HD and have a fresh install of Windows 10 on it. It's less than a week old. I get a BSOD about once a day. They all appear to be caused by ntoskrnl.exe. Googling suggests that this is usually caused by bad RAM. I've run...
BSOD Crashes and Debugging
Slow warm boot & Fast cold boot
Hello, My Lenovo laptop is pretty fast at cold boot. It takes about 12 seconds from initial bios screen to desktop. On the other hand, warm boot is really slow. The same period takes about 51 seconds, involving a long black screen. ...
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 08:44.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums