iyarianecy10 - Tuesday, January 2, 2018 3:10 AM

Hi all, 
I have come across this issue after resetting my Windows 10:

SQL Server detected a logical consistency-based I/O error: invalid encryption key. It occurred during a read of page (2:0) in database ID 1 at offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSSQLSERER\MSSSQL\DATA\mastlog.ldf'.

Before the reset, I was able to install SQL instances smoothly using the same setup. I have read somewhere that it could be hardware issues, so I tried to reformat my PC to (super) clean install SQL but the issue remains.  I also cannot execute DBCC CHECKDB as I cannot start sql server.

I am pretty new to SQL Server. How can I fix this?
I am really grateful for any of your help . 😀

Here is the full error log:
2018-01-02 17:04:34.95 Server  Server process ID is 6812.
2018-01-02 17:04:34.95 Server  System Manufacturer: 'LENOVO', System Model: '20354'.
2018-01-02 17:04:34.95 Server  Authentication mode is MIXED.
2018-01-02 17:04:34.95 Server  Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2018-01-02 17:04:34.95 Server  The service account is 'WORKGROUP\WIN-FAN50FHH8UM$'. This is an informational message; no user action is required.
2018-01-02 17:04:34.95 Server  Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2018-01-02 17:04:34.95 Server  Command Line Startup Parameters:
     -s "MSSQLSERVER"
2018-01-02 17:04:35.17 Server  SQL Server detected 1 sockets with 2 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-01-02 17:04:35.17 Server  SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-01-02 17:04:35.17 Server  Detected 8084 MB of RAM. This is an informational message; no user action is required.
2018-01-02 17:04:35.17 Server  Using locked pages in the memory manager.
2018-01-02 17:04:35.26 Server  Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2018-01-02 17:04:35.29 Server  Query Store settings initialized with enabled = 1,
2018-01-02 17:04:35.30 Server  The maximum number of dedicated administrator connections for this instance is '1'
2018-01-02 17:04:35.30 Server  This instance of SQL Server last reported using a process ID of 12144 at 02/01/2018 5:04:13 PM (local) 02/01/2018 9:04:13 AM (UTC). This is an informational message only; no user action is required.
2018-01-02 17:04:35.30 Server  Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-01-02 17:04:35.31 Server  Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2018-01-02 17:04:35.33 Server  Software Usage Metrics is disabled.
2018-01-02 17:04:35.33 spid8s  Starting up database 'master'.
2018-01-02 17:04:35.41 Server  CLR version v4.0.30319 loaded.
2018-01-02 17:04:35.50 Server  Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2018-01-02 17:04:36.90 spid8s  Error: 824, Severity: 24, State: 2.
2018-01-02 17:04:36.90 spid8s  SQL Server detected a logical consistency-based I/O error: invalid encryption key. It occurred during a read of page (2:0) in database ID 1 at offset 0000000000000000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.