This HP Community is for Customer to Customer Product Support. First Time Here? Check Out Videos on How to Search, Register, Post and More.

Re: SD/SDHC/MMC Memory Card Reader& Writer on DV9000 running Vista 32 corrupt files (2039 Views)
Reply
Student
Nonesuch
Posts: 1
Registered: ‎03-07-2009
Message 1 of 2 (2,883 Views)

SD/SDHC/MMC Memory Card Reader& Writer on DV9000 running Vista 32 corrupt files

I thought I share this...  I recently had my motherboard and bezel repaired under the terms of the hp service enhancement program after the loss of my wifi card due to the overheating incurredHP fixed and returned my DV9000 very very fastBut... one of HP's fixes was to update the notebooks bios so that a new fan control algorithm could reduce system temperaturesBios version F4.1 is what they updated me to. Everything on the computer was working fine when I got it back except for my SD/SDHC/MMC Memory Card Reader& WriterIt would read and create corrupt files on any SD card that I inserted. I tried updating the Ricoh drivers, reformatting the card in a different format, but nothing worked to fix the problem. Finally what did work was dumping the version F4.1 bios that the hp techs installed while in for the service and then going back to version F3.D. All is fixed now. But I did have to reformat the previously corrupted SD cards in their cameras. Please leave a note if this posting helps you. 
Please use plain text.
Student
jon100
Posts: 1
Registered: ‎11-04-2009
Message 2 of 2 (2,039 Views)

Re: SD/SDHC/MMC Memory Card Reader& Writer on DV9000 running Vista 32 corrupt files

I had a similar problem with a dv6700 (dv6820ea) laptop which corrupted a 4Gb SDHC card.

 

After reading this post, I used HP Health Check to find the "WinFlash for HP Notebook System BIOS (with AMD Processor)" update.  For some reason it could not access the file, and I had to manually download and execute ftp://ftp.hp.com/pub/softpaq/sp42501-43000/sp42853.exe .  This updated the BIOS from version F.31 to F.32, and it seems to have fixed the problem.

 

Thanks to Nonesuch for giving me the clue that the problem could be caused by the BIOS,

Please use plain text.