Hard drive light blinking constantly windows 10

Acer 5274 laptop/core i3Windows 7 Home PremiumHitachi HTS545050B9A300 hard drive



It might be the operating device polling the optical drive to view if you have actually inserted anything - the tough disk and optical disk share widespread circuitry and so the LED may use to both. You can try turning off autoinsert alert (Device Manager - look at the properties of the optical drive) and also autorun.

You watching: Hard drive light blinking constantly windows 10

A bit even more information here: .../cdtTipAutoRun.htm (broken, replacement: http://web.archive.org/web/20100527203945/http://www.base40.com/cdtTipAutoRun.htm)



If you want to view what is going on, on your system, tright here is a cool tool from sysinternals(they make all the cool tools) called processmon It will tell you literally every little thing that is going on. You may be shocked to see just how much stuff is active when your not.

I"m not saying you will be able to stop your light from blinking every once in a while, however at leastern you can watch what is going on.


The genuine culprit of HDD LED blinking on my Acer notebook was the company internally called BrcmCardReader with the lengthy name Broadcom Card Reader Service. As soon as I"ve quit the organization the blinking quit too. And of course I didn"t need to disable the CD-ROM or cover the LED through the tape to attain this. Contrary to what"s created in the various other write-ups here, the operating mechanism itself isn"t so badly composed to poll anypoint. But this service written by Broadcom is an additional story.

I"ve first tried to figure out what reasons the bweb links only to find that it was something prefer wbem wmiprvse.exe that did points favor IRP_MJ_QUERY_INFORMATION and IRP_MJ_QUERY_VOLUME_INFORMATION for every drive. As I kbrand-new that wmiprvse is actually a WMI execution component written by Microsoft I even tried making use of Event Log to trace the WMI activity, as documented on MSDN. It wasn"t beneficial, I was able to observe only

ProviderInfo for GroupOperationId = 101; Operation = Provider::CreateInstanceEnum - CIMWin32 : Win32_LogicalDisk; HostID = 2368; ProviderName = CIMWin32; ProviderGuid = d63a5850-8f16-11cf-9f47-00aa00bf345c; Path = %systemroot%system32wbemcimwin32.dll

Microsoft obviously does negative job in this trace: the CIMWin32, the host id, the provider guid and also the course all suggest to the binary executing the WMI, not to the program making WMI queries. So at that minute I wasn"t able to discover that Broadcom Card Reader Service does it as nothing logged pointed to it, that"s why I"m quoting all this in order to ease the pain for anybody that puts these items in the search machine. This incapacity to see that actually regulates the task is also the explanation why some world right here case that "it"s an operating system:" whoever before stops at this point does not see anything else. But I kbrand-new that wmiprvse isn"t doing it on itself, I knew tright here need to be some various other procedure commanding.

So finally someday after I"ve made an image backup of my whole mechanism, I began through the brute force method, turning off the things one by one, until the blinking quit. So currently I"m certain. It is the Broadcom Card Reader Service. And as I"m actually a programmer, I"ve also inspected the strings inside of c:Program FilesBroadcomMemoryCardBrcmCardReader.exe and also I"ve found what it exactly does, as soon as it"s turned on:

SELECT * FROM __InstanceDeletionEvent WITHIN 1 WHERE TargetInstance ISA "Win32_LogicalDisk"

SELECT * FROM __InstanceCreationEvent WITHIN 0.1 WHERE TargetInstance ISA "Win32_LogicalDisk"

Due to the fact that the blinking happens so frequently, it"s apparent that it is polling continuously. That is unbelievably bad programming of the business. Observe the WITHIN clause in the queries. Specifically, Microsoft documents just how such constructs behave actually in the WMI:


Keep in mind that the WITHIN clause mentions the polling interval for intrinsic occasion classes. Due to the fact that the course being monitored does not have a matching occasion provider, the WMI polling mechanism is offered to periodically inspect if an intrinsic event has actually emerged for the specific class. This polling interval is mentioned by the WITHIN keyword and measured in seconds.

See more: Prime95 Rounding Was 0.5 Expected 0.4, Memory Oc Stability

So I currently know that Broadcom organization programmers decided to poll for the __InstanceDeletionEvent of eincredibly logical disk eincredibly second and also for __InstanceCreationEvent even 10 times per second! And they regulate to involve COM, sepaprice processes and execute this over WMI/wmiprvse in a means that it"s not observable (at leastern I haven"t uncovered out) that their business is doing this!

Bad, amazingly poor programming.

And there"s appropriate solution for services and also applications: RegisterDeviceNotification. A real alert (that is, quiet as soon as there"s nothing new happening) deserve to be obtained by solutions using the SERVICE_CONTROL_DEVICEEVENT event. See for example:


After knowing all this, the search for Broadcom Card Reader Service actually returns a few articles of civilization that discovered it earlier: on community.acer.com (I"m quoting the articles for which I haven"t discovered permalinks):

Just found that Broadcom Card Reader Service is leading to hdd caused blink multiple times per second, all the time. Stopping and setting this company to hands-on or even disabled fix the blinking problem through no impact to card reader use."

on the bleepingcomputer system.com:

"Cheesenbranston Posted 28 May 2013 - 04:47 AM

I"ve had a comparable issue since installing Win8 pro x64 as a fresh install i.e. not an upgrade. In Task Manager although disk throughput didn"t seem specifically high usage was constantly at 100%. I think I"ve determined the worry as being the Broadcom Card Reader organization."

and also on Amazon.co.uk, a review by S. J. Harvey on 1 Feb 2013:


The one point that REALLY bugged me (note the previous tense) is that the drive light flickered constantly. It wasn"t HDD activity and after a pair of hours I traced the culprit. It was the Broadcom Card-Reader service.

He even more argues switching the service to hands-on, on my computer system I had to disable it completely though.

So civilization also reported greater resource usage, apart from just HDD LED blinking.

See more: Can'T Setup Custom Resolution Settings Are Not Compatible With This Display

The final solution: disable the "Broadcom Card Reader Service": in Services go to its properties, soptimal it and adjust its startup kind to "disabled". The blinking will lastly sheight. I"d really like to recognize what"s the purpose of it anymethod -- what I"m absent by turning it off? Seing how poorly it is programmed, I wouldn"t be surprised that the whole purpose of the service is to adjust some icon once the memory card is inserted! What I"m sure is that misutilizing the WMI is really bad programming.