BSOD Possible hard drive problem?

Yesterday, after coming home from work, I noted that my computer had restarted. Thinking it was Windows Update, I jumped back into Windows. It took me almost 15 minutes to get into Windows, which is abnormal for my computer. In trying to diagnose that, it froze again, and the one thing I noted was that my hard drive didn't appear to be reading.

I decided to do some investigating, and came across the possibility based on the one time I was able to get into the event viewer was that it appeared that Windows thought there was an issue with my hard drive controller (error code 11? Windows isn't my strong point, hardware is, and I can't easily get back)

Running diagnostics on my hard drive, it came up with nothing, saying that the hard drive was fine (I used WD's LifeGuard tools). And after some time, the error seemed to go away, and I was able to go about normal activity. I did make a change though, telling Windows that if it BSOD'd, that I didn't want it to restart.

Through the night, it BSOD'd again, and does not give a process or file that is causing the problem.

The stop code is as follows.

*** STOP: 0x000000F4 (0x0000000000000003, 0xFFFFFA8010835060, 0xFFFFFA80108010835340, 0xfffff80003581510)

In researching the error message I received above when I was able to get into Windows without problem, it seemed that I would want to investigate either the hard drive controller, the hard drive itself, or the cabling, so I will be switching out the cable after I post this, and I do hope that fixes it, but I am curious as to what would cause this error code, and if I'm on the right track.

If I'm able to get a dump file, I'll be sure to post it.

That crash primarily indicates hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems. In other words, it is not necessarily the hard disk itself causing the crashes, but the hard disk is a possible culprit. Let us know what you find when you replace the cable. Here are the steps I usually give for that crash:

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

After a few days of testing, replacing the cable, it seems everything is fine. Now, if I can only figure out why my hard drive continues to read as slave...

But, that's not your problem!

Thanks so much!

Once you are confident the problem is solved, please let us know and also mark the thread solved.

For the slave issue (if you have not already resolved it): Post a new thread in Hardware & Devices - Windows 7 Forums

Seems good now; thanks guys!