Computer Randomly BSOD's on Startup

This has been going on for months now. It can occur days or months apart. Randomly I will attempt to turn on my computer and there’s a BSOD before it can start up. I always have to use startup repair in order to get it working again. When I decide not to choose system restore and allow startup repair to fix the issue it always tells me that the only problem was one unknown bug in C:/Windows and that it was fixed using a Windows file stability check (or something like that.)

I run Windows Vista With:
Intel Core 2 Quad CPU Q8200 @2.33GHz 2.34GHz
8.00 GB RAM
64-bit

A full scan with Avast! and a quick scan with Malwarebytes came up empty (both were performed today with up-to-date definition.)

Reliability and Performance Monitor has this code for the last crash recorded (6/28/2011):
Failure Type: OS Stopped Working
Version: 6.0.6002 Service Pack 2
Failure Detail: 0x00000001
(0x00000000773c6cba,
0x0000000000000000,
0x000000000
Failure Type: Boot Failure
Version: 6.0.6002 Service Pack 2
Failure Detail: 0x1

I’ve performed diagnostics on both my memory and hard drive and found no error. I am extremely confused because no matter where I ask I never get an answers. I decided not to post this is the virus and worms category because I have no real proof it is malware (I started a thread up about this a few months ago and got no answers then either.) Any help is, of course, appreciated.

http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_install/what-is-error-code-0x00000001/a41e6e0e-84ad-4886-a11b-cd550eefde41

You can also search/ask here: http://answers.microsoft.com/en-us

Run this utility, it will give you a bit more info on your BSOD and might point you to the culprit.

http://www.nirsoft.net/utils/blue_screen_view.html

Blue screen view only labels one file red:
Filename: ntoskrnl.exe
Address In Stack: ntoskrnl.exe+5a22e
From Address: fffff800’0300f000
To Address: fffff800’03527000
Size: 0x00518000
Time Stamp: 0x4cb7275f
Time String: 10/14/2010 11:53:03 AM

As said, ask here: http://answers.microsoft.com/en-us

Microsoft way of fixing this problem.
http://support.microsoft.com/?kbid=314477