I have an HP Elitebook with Win 7 Pro 64 bit on a notebook with a docking station.
Basic Stats:
HP Elitebook 8440P Core i5 4 GB with the Nividia 3100m graphics I have everything except a WAN card installed.
Product Number is XU035UA#ABA (I added in the blue tooth card, otherwise it is as shipped from the factory)
It is the advanced Docking Station 120 watt NZ222AA#ABA with the exact same Seagate Momentus (sp?) 7200.4 drive installed in the machine and the docking station drive bay.
THe machine was freshly installed from HP recovery media for Win Pro 64 Bit. No Drive encryption active and the secone time it failed I didn't even have the encyption software installed.
Besides the basic HP software I had Office Pro 2010 Visio Pro 2010 Project 2010 Standard
Windows Live Essentials and all the updates both HP and Windows UP would push me..
I also have added iOne Display 2 screen calibration software and Norton 360 v4 that is it.. nothing else because
I had just set up the machine and I wait until the machine is completely installed to set up my WLM sync folders. There were a couple of docking and undocking events 20 minutes or more before the crash.. (done in sleep or hybernation) to test
confirm the Intel Recovery Volume was working.
Twice this weekend within an hour of setting up sync'd folders on this system running Intel Matrix Raid with the Docking station HD set up as a recovery drive in continious mode.. WLM would crash. Just while the note
book was sitting there or doing something easy like browsing Ebat not during an install or even during a "redocking" event. It was docked at the time.
WLM both times Pop and error first time it said one of its files was now corrupt, second time after hours of reinstalling the system it jsut said the WLM OS had failed and my
OS drive was TRASHED!!!..the OS would run but some programs like Outlook would no longer start due to "corrupt XLM"
When I reboot the system wold trigger a check on the C: drive and Chk disk would dump pages of bad files entries... pages of errors.. This tashed data was on both drives as it is not at the hardware level... So RAID replicated it
out to the mirror / recovery drive. And sure enough if I got through an entire CHKDSK run there were never any bad sectors just lots of orphaned files.. and repaired directory "stuff" sorry I was not in a test case mode.. so I don't have all the failure
mode details or logs.
I have run either Intel Raid in Recovery Mode system OR Windows Live Mesh perfectly for long periouds on this system... But both together and BOOM soon after.
I run the same RAID driver version on my desktop in RAID 5 and RAID 1 configs with no problem with Mesh. So it is either the Recovery Mode mirroring and WLM or something in the HP software along with the two.. but two times both minutes (les
than an our) after the last piece was installed feels like it might be a reproducable Priortiy One Bug... I don't have another day to give to testing this.. I have the notebook running perfectly all day with WLM and the Intel Raid drivers treating
both drives as normal volumes and will be letting Windows back up push nightly backups for now.
There has been no problem.. as long as I don't set up the recovery volume mode in the Intel Raid software.. this happend with both the final 2010 version called Matrix and the new verions renamed Rapid Storage Technology.
That is all I know.. but I did actually work in Testing at MS for almost 3 years back in the 1990s and I am betting I would happen again.. if I activated the recovery mode again. I will note in both cases the recovery drive was set up and synched before
I set up my WLM sync folder.
WHERE is the right place to report this!?!?!
