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".

:)

 

DPC_WATCHDOG_VIOLATION

I updated my Bios driver to latest.

I could no longer boot, "BootMgr is missing". After searching the boards and troubleshooting, the bios had changed the hard drive to boot from. I was able to successfully boot up into Win10.

Cold start continued to produce BSOD, as before.

Following Team ZigZag suggestions, rename Pnp680.sys to *.bak, resolved BSOD and now cold start and warm start smoothly into Win10.

Many thanks to your quick responses.

Very helpful and much appreciated!

 

BSOD after Windows 10 upgrade

Hello Yashwanth, Thanks for your input, yes I do experience what you call BSOD, it is very difficult to remedy the problem as obviously the laptop keeps shutting down (after three shutdowns, auto repair). Am I right in understanding that after creating
USB media and the BSOD kicks in I can cold boot from USB (as you need win10 installed to do a cold boot) I have already created USB but cold boot from windows 7 / 8.1 requires serials etc ...... this I found out by trial and error, I have not thought of leaving
win10 in place and then doing a clean install from USB ???

I have spoken to Dell support over my other laptop (Inspiron 15-7548) this also flashes BSOD ...... internal power error !! after restoring to win8.1 all runs smoothly, I have run Dell built in hardware diagnostics and all system checks out, Dell support
advised waiting for a month or so for MS to iron-out all the wrinkles then try upgrading again.

Sorry if all this sounds a bit confusing, but having 2 laptops of different manufacture and neither accepting win10 upgrade is all a bit stressful and major time consuming, once again, my thanks. Terry

 

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:[/quote] 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[/quote] 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 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.

 

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.

 

• From Admin command, run: chkdsk /r C:
  NOTE: This will take a while to complete
• 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
• If sfc still gives error, you might need to re-run sfc multiple times

 

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.

 

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

 

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>

 

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.

 

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.

 

I ran check disk now, seemed good. Also, I started having these issues yesterday, I did forget to mention, I setup Memtest86 on last night and it ran for 8 full hours without any errors, and four passes. All the BSODS have basically been when the system is turned off for so long, then started. Typically the BSOD comes, and then it restarts and seems to load into the desktop just fine.

 

OK. Just want to make sure that all RAM Sticks are good. You might also want to set the voltage for the RAM manually in the BIOS according to the spec. If you leave it to Auto then sometimes it does not have enough juice at power up.

 

Roger that. Thanks for all your help and support. I'll keep monitoring it.