Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

win 10 BSOD BCD is missing


  • Please log in to reply
8 replies to this topic

#1 FroggieFrog

FroggieFrog

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 23 June 2017 - 05:59 AM

Hi!

I restarted my PC and then there was this annoying blue screen. (win 10 x64, uefi/gpt, german)

I tried the following via a usb-stick created with current mediacreation-tool:

  • bootrec /fixboot
  • bootrec /rebuildbcd -> no installations found
  • SFC /scannow -> no errors found
  • automatic startup repair -> could not repair; see srttrail.txt
  • bcdboot C:\windows /s C: -> bfsvc error could not open the bcd template store

Do you have any idea?

I can not attach the file, so here is the excerpt:

...

Durchgeführter Test:
---------------------------
Name: Fehlercodeanalyse / bugcheck
Ergebnis: Erfolgreich abgeschlossen. Fehlercode =  0x0
Erstellungszeit = 156 ms

Gefundene Fehlerursache:
---------------------------
Fehlercode c000021a. Parameter = 0xffff9b866e4e9530, 0xffffffffc0000428, 0x0, 0x272919c0000.
Die für den Start erforderliche Datei "" ist beschädigt.

---------------------------

...



BC AdBot (Login to Remove)

 


#2 mikey11

mikey11

  • Members
  • 1,488 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Psychiatric Ward @ Beelitz-Heilstatten Hospital, Beelitz, Germany
  • Local time:06:32 AM

Posted 23 June 2017 - 06:32 AM

boot to command prompt....type....

 

C: <enter>

 

chkdsk c: /f /r <enter>



#3 FroggieFrog

FroggieFrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 25 June 2017 - 11:58 PM

Thank you for your idea, but there were no errors or issues found.

Any other idea?

 

Can I copy the boot partition from another Win 10 Pro PC? All data is there, but only the boot config is missing.



#4 FroggieFrog

FroggieFrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 26 June 2017 - 03:54 AM

I managed to get to the desktop by disabling the "verification od driver signature".

Otherwise I get a blue screen.

While on desktop I'm using "sfc /scannow" from an admin-cmd and the tool is finding issues, but is not able to repair it.

The same command from a win 10 usb stick finds no issues (using offwindir etc. because of win PE).

I used this command 5 times (sfc, reboot, sfc, reboot ...) and is still finding issues, but can not repair it.



#5 mikey11

mikey11

  • Members
  • 1,488 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Psychiatric Ward @ Beelitz-Heilstatten Hospital, Beelitz, Germany
  • Local time:06:32 AM

Posted 26 June 2017 - 06:36 AM

I managed to get to the desktop by disabling the "verification od driver signature".

Otherwise I get a blue screen.

While on desktop I'm using "sfc /scannow" from an admin-cmd and the tool is finding issues, but is not able to repair it.

The same command from a win 10 usb stick finds no issues (using offwindir etc. because of win PE).

I used this command 5 times (sfc, reboot, sfc, reboot ...) and is still finding issues, but can not repair it.

 

 

 

when it finds an error does it ask you to insert your windows cd or usb?


Edited by mikey11, 26 June 2017 - 06:36 AM.


#6 FroggieFrog

FroggieFrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 26 June 2017 - 06:41 AM

No, it does not ask me anything.

 

I already tried the command "dism /online /cleanup-image /restorehealth".

The first time it found errors and repaired them. After rebooting there were no errors with the dism-command, but the sfc-command still finds errors nad is not able to repair them.

Also i downloaded a fresh iso and mounted it. Then I used the dism-command with ":esd:path to install.esd:1 /limitaccess". There were no issues found.

 

The PC is still getting the same BSOD when starting. After the 3 restarts I can choose "disable driver verification" and everything starts normal.

So there has to be a solution to this...



#7 mikey11

mikey11

  • Members
  • 1,488 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Psychiatric Ward @ Beelitz-Heilstatten Hospital, Beelitz, Germany
  • Local time:06:32 AM

Posted 26 June 2017 - 09:51 AM

does the computer run fine in safe mode?

 

can you post a picture of the BSOD ?



#8 FroggieFrog

FroggieFrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 27 June 2017 - 01:38 AM

When starting safe mode, then there is also the same blue screen. It does not matter which of those 3 options I choose for safe mode.

 

The system is in german, but that should not matter.

Link to the images on OneDrive: https://1drv.ms/f/s!Av7-UzLNlqG8swpn7PyDOw20QgJy



#9 FroggieFrog

FroggieFrog
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:06:32 AM

Posted 27 June 2017 - 04:58 AM

I also installed "Malwarebytes", but nothing was found.

The build in "Windows Defender Security Center" also found nothing.

 

I also tried the driver signature check from this post: https://www.bleepingcomputer.com/forums/t/635023/bsod-at-startup-0xc000021a/#entry4145355

The results are here: https://1drv.ms/f/s!Av7-UzLNlqG8sw2w0H8uHnh3p6ZQ

 

I also made an excerpt from the cbs.log-file: https://1drv.ms/t/s!Av7-UzLNlqG8sw4kXqrp_H7DPc6K






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users