How to troubleshoot "3183" error importing a bank into SQLSERVER 2012

Question

Good afternoon! First of all, I warn you, I’m a layperson. I need to run a local bank on my machine to work on a project.

I installed the programs: SQLSERVER Express 2012 SQL Management Studio 2012

I use a Macbook Pro and run a Win7 VM through Paralells.

The database you sent me has 8GB and the guidelines were to rename the file to . dmp and run the query:

RESTORE DATABASE meu_banco
    FROM DISK = N'C:\meu_banco.dmp'
WITH REPLACE,
MOVE 'vod_muzika' TO 'C:\sqlserver\meu_banco.mdf',
MOVE 'vod_muzika_log' TO 'C:\sqlserver\meu_banco.ldf'
GO

But the error returns to me:

Msg 3183, Level 16, State 2, Line 1 RESTORE Detected an error on page (8192:536879104) in database "vod_muzika" as read from the backup set. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally.

From what I’ve looked at online, it looks like the bank is corrupted. Since I already downloaded this 4x bank and other people downloaded the same bank and managed to import without problems. The error is only with me.

Is there any other possibility without being the corrupted bank and how it could resolve?

UPDATING

Following the tip of the friend Reginaldo, I did the following:

RESTORE DATABASE meu_banco 
FROM DISK = N'C:\meu_banco.dmp'
WITH CONTINUE_AFTER_ERROR, REPLACE,
MOVE 'meu_banco' TO 'C:\sqlserver\vod_muzika.mdf',
MOVE 'meu_banco_log' TO 'C:\sqlserver\vod_muzika.ldf';
GO

I tried with WITH RECOVERY too and got the following error:

Location: gfh.cpp:2911 Expression: rec. Size () < MAX_PROPERTY_ROW_LENGTH SPID: 52 Process ID: 1820 Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally. Msg 3624, Level 20, State 1, Line 2 A system assertion check has failed. Check the SQL Server error log for Details. Typically, an assertion Failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft During setup, a mini dump will be sent to Microsoft. An update Might be available from Microsoft in the Latest Service Pack or in a QFE from Technical Support.

Answer 1

Yes this corrupted. You must lose something. To continue restoration even after error use

RECOVER DATABASE ... WITH CONTINUE_AFTER_ERROR

The bank will be in SUSPECT after restoration and you can try to repair it.