Bug after firmware update 2CV102M3

[idata]

Hi! After update my SSD the line 09 "Power-On Hours Count" in SMART don't work. Has stopped on value 357 and doesn't change. All other lines work. Why the such has occurred? My configuration:

Asus P8P67 Pro

Intel X25-M SATA2 SSD (SSDSA2MH080G2R5) 80GbWestern Digital WD1001FALS SATA2 HDD 1000GbOptiarc DVD RW AD-7263S

Microsoft Windows 7 Professional x64 SP1 and last Intel RST driver

I tried to connect the SSD to other ports SATA2 and SATA3, but nothing has changed. How can I fix it? Thanx!

[idata]

Just tested myself.... Power-On Hours Count still works.

Have you refreshed the SMART page?

[idata]

Nice question Of course I refreshed the SMART page. I looked this in two programs - Intel SSD Toolbox and AIDA64. The second disc in the system is working properly and changes value of every hour. SSD formatted, reinstall windows and install new drivers. Nothing changes... A week ago 356 hours, of Monday 357, of Tuesday 357 and 357 yesterday... Great gods, I was in Groundhog Day

P.S. Maybe this bug in Cougar Point? But now the drive is connected to port SATA3... This strange

[idata]

"Specialists Intel? Why you don't answer?"

OMGosh, slow down and get real. First, this is the first report of this in the forum AFAIK.

Second, and forgive me, but do you think that employees that work for PC related companies assume that every posting in their forums about a bug warrants an immediate and high priority investigation into the issue, particularly when only one person reports it? Ask yourself, how many times did you think something was wrong with software, hardware, etc, and later discover it was simply your mistake? I've done that more times than I want to admit. If companies did what I stated, that is about all they would ever do.

I have a drive that has decided it won't report SMART data, it is enabled in the BIOS for the drive, but none are displayed. Otherwise, it works fine, for months since it became DUMB. Should I start accusing the manufacture that their firmware is bad? How would I know that anyway?

Third, if some people are investigating it, why do you expect the results to be instant? If you've ever worked with software as I have, and test for a reported bug and can't duplicate it, that is a difficult situation. So give these folks a chance.

Next, consider this. Say they find a bug. If the programmer then posted on a forum that it was true, he would probably be fired. Why? There are procedures that companies have that must be followed before announcing product problems. Plus, that would be very unprofessional. Things are never as simple as we would like them to be.

[idata]

It's all understandable. No need to write so much .

1. I understand that the bug is small. Not everyone will pay attention.

2. Special for you! Post subject written by "Bug after firmware update", not "Bug in firmware". I'm not accusing anyone, just trying to resolve the issue. 3. Earlier I reported about it in the ASUS company. Maybe it's their fault.

My position is now clear, Captain Obvious?

P.S. Sorry for offtopic

[idata]

Hi, Interesting that you both have the same mobo. Have you tried the Marvell 9120 controller or maybe another mobo altogether?