Blank BSOD when booting Windows 7

Hi there.
I have a bizarre problem. I have had no luck finding anyone with this issue. I dont understand why this happens.

I have a laptop running Windows 7. It's a bit old. It's from 3 years ago or so.

There's a really strange BSOD I get when it's loading. Why is it strange? Well.. it's blank. I'm not kidding. There is no text on the screen that displays what the problem was. It simply goes blue and never turns off. No cursor, it never gets to the Windows 7 login screen. It will however sometimes load into Windows, but sometimes I have to reboot it up to 10 times just to get it to start.

There is nothing in the Event Viewer, and no log is ever created. I don't understand why this happens. The same problem will occur in Safe Mode, Safe Mode with Networking, and Safe Mode with Command Prompt. It just blank BSODs at the final file, but like regular mode, rebooting it enough times will get it to start.

Startup Recovery does not start. It just lays at the "Windows is loading files", makes it to the full thing, and never loads anything.

However, once I finally get it to start (after several reboots usually), Windows 7 will work perfectly normal. No errors, no strange problems, games play fine, etc. And sometimes it'll just start up without crashing at all.

I have reinstalled Windows 7 twice. I don't understand why this is happening. This same issue happens on Windows 8. (Yes, it has the same blank BSOD, not the frowny face, but a Windows 7-style BSOD, but blank.)

To help everyone understand this better I recreated what it looks like.

Golden said:

Are there any .dmp files in C:\Windows\Minidump?

No, there are none in C:\Windows\Minidump.

However after doing a little bit of testing (By killing csrss.exe) I have found that EVERY BSOD is blank, not just the startup one.

Try re-installing/updating the drivers. Might be an issue with drivers and their updates.

You can also try running any diagnostic tools you have for your graphics card (if available)

Otherwise, I'd start backing up with a disk image utility like Acronis True Image or a snapshot tool like Rollback rx. Whatever is causing this, it's likely an update either to a driver or the OS (or an incompatibility between both). Either way, you'll want to start backing up in case this happens again.