Everytime I boot I get stuck on this screen

[zxcv]

Hello,
Everytime I boot I get stuck on a screen saying:

0.000000] __common_interrupt: 1.55 No irq handler for vector
0.000000] __common_interrupt: 2.55 No irq handler for vector
0.000000] __common_interrupt: 3.55 No irq handler for vector
0.000000] __common_interrupt: 4.55 No irq handler for vector
0.000000] __common_interrupt: 5.55 No irq handler for vector
1.467633] ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corru
1.467656] ldm_parse_tocblock(): Cannot find TOCBLOCK, database may be corru

I am very new to linux so I don't know what to do.

[SGS]

Try

Computer doesn’t boot, boots to a black screen, or stops at a message

While there are many potential reasons why your installation doesn’t boot to a desktop, the primary reason is that the graphics drivers haven’t loaded correctly so your login/display manager (DM) doesn’t start. This is why you get a “black screen” or stuck at an [ OK ] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This can happens when the mirror you are updating from is not fully synchronised, or times out, and so y…

or use last working snapshot.
and

[elloquin]

Your drive is failing or you have a bad connector/cable.

[filo]

If this can be of any help, at a quick look into the forum (only), I've found a couple of threads, only in relation to "No irq handler for vector".
In the first one the problem seems to have been solved with a BIOS update.
It might have been a coincidence or different issue, anyway you could check if your BIOS is up-to-date...
In the second one it was solved with a kernel boot parameter.
You could try as well, at least from the grub, before making it permanent.
Please consider that in the linked Manjaro thread there are a myriad of different parameter combinations... I don't think it would worth following/trying it completely...

[tbg]

@elloquin

Your drive is failing or you have a bad connector/cable.

Or your filesystem somehow got corrupted. This can happen when a power outage or hard power down event occurs. Run some smartmon tests on your drive.