Bitlocker keeps crashing my PC

Max Griner said:

Hi Zbook, all,

just tried to let WIndows create the partitions for me, so instead of clicking "new" on the initial partition screen, i just clicked "next" on "unallocated space". Then went to patch windows to newest patches on 20H2, and then enabled bitlocker, however upon restart, it goes directly into this bluescreen and then start the drive analysis and repair loop. Once it gives me advanced options i will try to get a command prompt and see if i can get the logs
Attachment 317091

- - - Updated - - -

Update,

yesterday i did 4 re-installs where i tried new things to overcome these Bitlocker issues.

1. Enabled Samsung Magician encryption, did reinstall of windows, crashed again
2. Did Bitlocker without the last checkmark in "verify bitlocker", drive C: encrypted, and then acted really weird, search did not work, could not execute anything. Upon restart PC crashed again.
3. Downgraded BIOS from 1.53 BETA to 1.40 stable release. no change.
4. After windows install before bitlocker, i updated all X570 AMD drivers to see if it would change anything with newer drivers on the disk controllers. also same result.

I'm slowly starting to believe that I wont be able to solve this. Which annoys me like crazy. Only thing that comes to my mind i can try is to remove both m2's and then try with just one, if it fails, try the other one. just to rule out its not one of the ssd's which has a defect.

I tried to pull logs, but i couldnt last time i tried as C: was corrupt (it said when i was trying to go C: from CMD).

If anyone has ideas i havent tried please do let me know.

That stop code: Particularly bad, associated with loss of RAM integrity! Wouldn't be surprised if you're getting the classic signs of RAM instability. You don't have to be OC'ing the RAM or having the latencies too low, it's more likely the RAM isn't seated properly, you have bad RAM slot(s) or a bad CPU RAM controller. (or a problem with the socket where the connection is bad to the RAM.)

This is a problem I have been tackling with a socket 1366 system, where I at the least, can't add RAM to at least one of the black slots, or I will get "PAGE_FAULT_IN_NON_PAGED_AREA" BSOD when updating Windows. (Windows 7 SP1 on that system)

Looks like you need to reseat that 32 GB o' RAM and then should disable XMP! Unfortunately, for troubleshooting, need to drop that RAM down to 2133(/2).

RJARRRPCGP said:

That stop code: Particularly bad, associated with loss of RAM integrity! Wouldn't be surprised if you're getting the classic signs of RAM instability. You don't have to be OC'ing the RAM or having the latencies too low, it's more likely the RAM isn't seated properly, you have bad RAM slot(s) or a bad CPU RAM controller. (or a problem with the socket where the connection is bad to the RAM.)

This is a problem I have been tackling with a socket 1366 system, where I at the least, can't add RAM to at least one of the black slots, or I will get "PAGE_FAULT_IN_NON_PAGED_AREA" BSOD when updating Windows. (Windows 7 SP1 on that system)

Looks like you need to reseat that 32 GB o' RAM and then should disable XMP! Unfortunately, for troubleshooting, need to drop that RAM down to 2133(/2).

Hi,
Thanks for the input. 2 days ago i had the ram out and reseated them, and ran around 10 installations without xmp enabled because i downgraded the bios to non-beta. If it is related to bad memory then at least it did not help to reseat them. I dont get any BSOD though, pc just goes into disk repair / analyse loop after restarting it.

Also the pc with xmp enabled and amd auto Tune performs very good and its stable too, it has run for days before i tried bitlocker first time. I will try to pull out one m2 tonight and see if that does any difference. Also will pull new logs after Windows install before bitlocker as zbook suggested

Regarding the RAM:

If you are not occupying all memory slots, make sure to read user guide for your MD as many will require particular slots to be occupied before others. Also, you might want to simply run the Windows Memory Diagnostics as described in this tutorial:

Run Windows Memory Diagnostics Tool in Windows 10

hsehestedt said:

Regarding the RAM:

If you are not occupying all memory slots, make sure to read user guide for your MD as many will require particular slots to be occupied before others. Also, you might want to simply run the Windows Memory Diagnostics as described in this tutorial:

Run Windows Memory Diagnostics Tool in Windows 10

Thanks hsehestedt, i have all occupied, 4x8 GB g.skill cl16 3600

List any of these installed non-Microsoft software:

antivirus
firewall
drive encryption


If none are installed then run each:
V2
DM

If there are any problems each can be ran again in safe mode.

Also run LOGS again.

Hi Zbook,

tried to run V2 and Logs again. (not sure what DM is?)

should be shared here: Dropbox - logs - Simplify your life

thanks

- - - Updated - - -

hsehestedt said:

Regarding the RAM:

If you are not occupying all memory slots, make sure to read user guide for your MD as many will require particular slots to be occupied before others. Also, you might want to simply run the Windows Memory Diagnostics as described in this tutorial:

Run Windows Memory Diagnostics Tool in Windows 10

Hi hsehestedt,

I ran the memory check thing and it found no issues with memory. thanks for the link!

zbook said:

See if troubleshooting this error message makes a difference:

Code:

Device Encryption Support	
Reasons for failed automatic device encryption: 
PCR7 binding is not supported, Hardware Security Test Interface failed 
and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected

Modify the Dell suggested steps to MSI: (see video)
https://www.dell.com/community/XPS/X...7412306/page/2


https://docs.microsoft.com/en-us/win...%20DMA%20ports.

Hi Zbook,

I saw the video, but TPM is already in state "ready to use". However i dont have that extra partition they mention, i only have EFI, main partition and Recovery partition..

Secure boot enabled
TPM enabled and says "ready for use"

I am unsure how to get rid of that error, in what file did you find it? i ran logs.bat again and uploaded it again, as i did some change, enabling secure boot (was not enabled first time i ran logs.bat) and i also activated some key stuff in bios to be able to enable secure boot.

i have uploaded new logs with logs_new on dropbox

thank you

- - - Updated - - -

Hi Zbook, all,

Quick status on my issues.

changes:
Updated to new MSI bios released 1.50 version non-beta (just released)
Took out second m2, now only trying with 1 mounted m2


status on system (will try bitlocker again tonight)

UEFI Mode enabled
Secure boot enabled
TPM Enabled
TPM available as device
TPM status "Ready for use"



If it fails again tonight, i have one last thing i can try, i have an old SATA ssd i can try to install to, just to see if it changes anything not using the m2's. But its really killing me it is so hard to get bitlocker to work on such a new system

- - - Updated - - -

Quick update,

Zbook the error you found seems that it could sound like having impact. i think i got half of it removed:
PCR7 now ok:



But the Device Encryption Support is still not ok:


How on earth can i make that ok? i have everything enabled. Even read a forum that it was due to AMD has to have some CPU virtual mode enabled, found it in bios and enabled it. I knew i should have stayed with Intel, I am almost sure this is due to the AMD platform lack of compatibility. If anyone has any idea how to fix "Reasons for failed automatic device encryption: Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected" please do let me know

thanks all

Hi MAX, I have also built two PC's and am using Bitlocker on both, currently on Windows 10 Pro 19042.789. The motherboards are both ASUS, a Prime X570Pro and an X570P. I fitted discrete SPI TPM 2.0 modules to both. They both are using AMD Ryzen 5 3600 CPU's with 16GB Memory. A similar setup to yourself.
I think you have a setting wrong in the BIOS with the result that when the PC reboots to start the encryption, it is trying to use the firmware on the CPU . I don't think that exists with these CPU's and so you get the failure. Look at your BIOS setting in Post #1. I looked at the MSI manual and I think you should set it to disabled as per this. It will now use the TPM Module. Hope I've read the problem correctly!!

See if there is available customer support from MSI.

Microsoft provides free support for update / upgrade failures.

An additional option in case bitlocker troubleshooting does not produce a fix, consider testing third party encryption software.
(some encryption software can interfere with Windows upgrades)