Random 0x0000007B BSOD, Windows Server 2008 R2 on HP Server

The server at my company has been acting strange for as long as I know. Since it is a production server, we rarely do a complete shutdown/restart, but when we do, at random times we got a BSOD for some several times before it finally boots back into Windows (nothing to change, just normal resets).

I expected to get a dump file after each BSOD, but strangely enough I never got one. I have checked the startup configurations in the advance settings many times to make sure that it is configured to create a dump file, but still I haven't got any so far.

The error at the BSOD is specifically like this:

0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

and it is running Windows Server 2008 R2 Enterprise on a HP Proliant DL120 G6 server.

I have tried the latest updates from Windows, also tried to check hardware issues and configuration, and even geet support from HP people which they said it must be the OS error.

By some googling around, some people says that it's a filter driver error (second switch of 0x34), and I tried to remove all the filter driver instance with no luck.

Any ideas how I could fix this or at least troubleshoot it?

Update: I forgot to mention, that entering safe mode (any kind of safe mode) also triggers the BSOD, so it's not an option.

I would look at the dump files and see if there is an obvious way to identify a driver issue.

http://blogs.technet.com/b/askcore/archive/2008/11/01/how-to-debug-kernel-mode-blue-screen-crashes-for-beginners.aspx#3476888

http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx

These steps sometimes give an obvious answer quite quickly. If not, I would not spend much time looking further with this method, because that needs very specialised knowledge. Microsoft support would be able to pursue the investigation.