Constant BSOD on Windows 7 64

Guys,

I need some help diagnosing a constant BSOD I am getting. I have reason to think its has something to do with the OS losing access to the hard drive, as I am not getting min dumps recorded off the BSOD, and I am seeing IDLE port failures in the event log.

Brief history:
At first the PC ran great off a new format. Then it started crashing, say every 5 hours or so, the longer the problem has persisted the more frequent they have become, now sometimes upon windows loading. I did boot in safe mode the other day, left it running overnight, no BSOD when I turned my monitor on, but once i started loading programs, loading a movie on VLC and going to afew web sites in firefox, it crashed on me again.

I was hoping someone could at least give me some areas this sounds like, I am a computer guy, cisco, checkpoint etc, but not a windows engineer to say the least...

Does the BSOD stay on screen long enough for you to see the stop code ? Down near the bottom of the screen you should see the stop code which should give you at least an indication of why the OS cannot continue and produces the BSOD - refer to the link below for a list of codes....

List of Blue Screen Error Codes (STOP Codes)

Apologies if you have already done this, I was trying to be helpful.

Firstly, check this directory:

Code:

C:\Windows\Minidump

Then, I would suggest checking your configuration settings (ensure it is set to a Minidump) - Dump Files - Configure Windows to Create on BSOD

This may be helpful - BSODs but no Dump Files? - Sysnative Forums

I have not done an overnight meme test, but the BSOD is not logging. Here is some more info

Ok I have the BSOD it log in the c:/windows/minidump folder, but it is not getting written to it for some reason..

Here are the specs:

Asus M4A88TD-V EVO/US3 AM3
Amd Phenom II X4 955
2 x G.Skill2x2 gig 4GB 240 pin DDR3 SDRAM 1333 PC3 10666
MSI R6870 Twin Frozer II Radeon 1 gig PCI Express
WD Blue 500 gig hard drive with OS


I also have 3 older SATA drives and an IDE one attached to the motherboard

The IDE is pretty old btw, not sure how old but at least 5 years I would say.

I will also try the whocrashed program, maybe I get better luck with that then the mindump logging that will not log
Ok I did disconnect the other hard drives, so I am just running on that one with the OS on it, 500 gig WD Blue. It still crashing, same BSOD code.

Also
I unplugged the other three hard drives, still crashed.
I ran the WD Hard drive check on the drive, three times, it passed.
I changed the SATA port on the HD is connected to on my MoBo and still crashing.

OneHate said:

Ok I have the BSOD it log in the c:/windows/minidump folder, but it is not getting written to it for some reason..

What do you mean by logged? Is the BSOD being written to Event Log and then not getting written?

Let's try and create a BSOD with Driver Verifier:

Run Driver Verifier to scan for any corrupted drivers which may be causing problems, this program works by running various stress tests on drivers, in order to produce a BSOD which will locate the driver; run for least 24 hours:

• Driver Verifier - Enable and Disable
  
  
     Information

  Additional Help - Using Driver Verifier to identify issues with Drivers

Running it now and also set the PC up for a full memory dump next crash... My only question here is why am I not selecting any Microsoft drivers here?

The largest I would have set it to is a Kernel Memory dump, which is the size of the Kernel Mode address space.

A third-party driver may be interacting with a Microsoft driver, giving the false impression that the Microsoft driver is the problem when it is not. Drivers work in a layered structure.

OK so it crashed again yesterday and no BSOD log was created, but the BSOD did not show up, I have this instead which happens every once in awhile during it crashes. When I get this screen shot what happens is the computer usually will look good, IE windows will up, I can move the mouse but nothing at all happens....after being frozen for afew minutes it the screen goes all haywire and will sit there until I reboot..

I also had verifier on but it did not seem to record anything here.