S2Nice
New member
I have an ASUS BC-12B1ST SATA combo drive that works great from a cold boot, but never comes online after a reboot. It's done this since install a year or so ago, and it's not bothered me much because I was leaving the machine on 24/7 for BOINC anyways.
I had a MB & processor fry out lately, likely due to prolonged high load from running BOINC on 4 to 6 cores full throttle for 2 years plus. After that, I decided no more BOINC for this machine, and once I got parts in, including a fresh mobo, processor, and PSU, I have been shutting the machine down when not in use. It's really just an annoyance that I can't reboot if I want to use the optical drive. Of course this happens only if I've had updates that require a reboot.
As I said, it's done this since day 0. I imagine it's due to a power conditioning/protection function within the drive that prevents it from operating on what it sees as poor quality power. Anyone have an idea how to change this behavior?
Edit:
I should also point out that, during a reboot, the activity light on the drive doesn't come on at all, and that the eject button doesn't do anything. It acts as though the drive isn't powered. Windows doesn't see the drive, but I wouldn't expect it to if the drive itself is refusing to power on. I'll go through the fixes mentioned in the kb article mentioned by Shimshom anyways, just in case. I'll report back if anything changes.
Edit 2:
Even though I didn't have a yellow exclamation in device manager, I went through with steps 1 - 3 as referenced in the KB article. Even though the troubleshooter and fixit didn't find any problems to fix, and the upper and lower limit entries were not found in the registry, miraculously my drive is alive after restarts now. If it goes afoul again (and I remember this thread exists) I'll update the post.
Edit 3:
I should have known. Within a few days I noticed that the optical drive doesn't come back online on reboots. I think it's probably the drive itself.
In the meantime, thank you Shimshom for pointing me to that article. I'm glad I posted even though it didn't bother me much. Perhaps someone else seeing the same annoyance on their machine will run across this thread and get resolution.
Oh, and Shimshom's avatar is driving me nuts. I keep wanting to smash that bug. Maybe I'll treat my monitor with some pesticide to see if it stops
I had a MB & processor fry out lately, likely due to prolonged high load from running BOINC on 4 to 6 cores full throttle for 2 years plus. After that, I decided no more BOINC for this machine, and once I got parts in, including a fresh mobo, processor, and PSU, I have been shutting the machine down when not in use. It's really just an annoyance that I can't reboot if I want to use the optical drive. Of course this happens only if I've had updates that require a reboot.
As I said, it's done this since day 0. I imagine it's due to a power conditioning/protection function within the drive that prevents it from operating on what it sees as poor quality power. Anyone have an idea how to change this behavior?
Edit:
I should also point out that, during a reboot, the activity light on the drive doesn't come on at all, and that the eject button doesn't do anything. It acts as though the drive isn't powered. Windows doesn't see the drive, but I wouldn't expect it to if the drive itself is refusing to power on. I'll go through the fixes mentioned in the kb article mentioned by Shimshom anyways, just in case. I'll report back if anything changes.
Edit 2:
Even though I didn't have a yellow exclamation in device manager, I went through with steps 1 - 3 as referenced in the KB article. Even though the troubleshooter and fixit didn't find any problems to fix, and the upper and lower limit entries were not found in the registry, miraculously my drive is alive after restarts now. If it goes afoul again (and I remember this thread exists) I'll update the post.
Edit 3:
I should have known. Within a few days I noticed that the optical drive doesn't come back online on reboots. I think it's probably the drive itself.
In the meantime, thank you Shimshom for pointing me to that article. I'm glad I posted even though it didn't bother me much. Perhaps someone else seeing the same annoyance on their machine will run across this thread and get resolution.
Oh, and Shimshom's avatar is driving me nuts. I keep wanting to smash that bug. Maybe I'll treat my monitor with some pesticide to see if it stops
Last edited:
My Computer
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Custom build
- OS
- Win7Pro(64), WinVistaHome(64), Ubuntu 14.10 Desktop(64)
- CPU
- AMD FX-8350
- Motherboard
- GA-990FXA-UD3
- Memory
- 8GB (4GB x 2) Corsair Vengeance (Blue) 1600Mhz
- Graphics Card(s)
- NVIDIA GeForce GTX 550 Ti
- Hard Drives
- OS -- Crucial M4 64GB
Storage -- WD Black 250GB WD2500BEKX
- Antivirus
- MSE
- Browser
- Chrome
