http://msdn.microsoft.com/en-us/li brary/windows/hardware/ff559211%28 v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/ff559211%28v=vs.85%29.aspx <a href="http://s63.photobucket.com/albums/h133/franpa/?action=view&amp;current=f53914fd.png" target="_blank"><img src="http://i63.photobucket.com/albums/h133/franpa/f53914fd.png" border="0" alt="Photobucket"></a> I've no clue what to do, could someone help me identify where the problem lies? I've had this happen at least twice now and some programs do cause a worrying noise to emanate from one (Or more) of my HDD's so I suspect it is a HDD intermittently failing but I'd like to be sure. I just don't know how to interpret the data, any help is appreciated.Core i7 920 @ 2.66GHZ | ASUS P6T Mother Board | 6 gig DDR3 1600 RAM | 2x 500g SATA2 HDD | Integrated sound | Gainward Geforce GTX 560Ti "Phantom 2" 2048MB PCI-E (latest drivers) | Windows 7 Home Premium x64 | Thermaltake 750watt Toughpower Power Supply | Thermaltake Armor+ MX case.
May 20th, 2012 1:26pm

1. Test your hard disk with diagnostic tool that disk vendor provides. 2. For sure test memory with memtest 3. You have not specified the "history" of error, if it is new installation or older one. For new installation you should install chipset driver first, then video, sound and network driver. 4. Any troubleshootiing procedure starts with Event log inspection. Please show here your findings 5. The aforementioned error has RESOLUTION: Resolution Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore. If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r. Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows. Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems. Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer. Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error. Make sure that the latest Windows Service Pack is installed. If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error. Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses. Regards Milos
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2012 3:23am

1. Test your hard disk with diagnostic tool that disk vendor provides. 2. For sure test memory with memtest 3. You have not specified the "history" of error, if it is new installation or older one. For new installation you should install chipset driver first, then video, sound and network driver. 4. Any troubleshootiing procedure starts with Event log inspection. Please show here your findings 5. The aforementioned error has RESOLUTION: Resolution Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore. If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r. Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows. Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems. Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer. Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean. Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error. Make sure that the latest Windows Service Pack is installed. If the preceding steps do not resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can cause this error. Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses. Regards Milos
May 21st, 2012 3:32am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics