IMPORTANT: The following journal is intended for the use and viewing of approved persons only and may contain information that is confidential, privileged or unsuitable for overly sensitive persons with low self-esteem, no sense of humour or irrational religious beliefs. Any dissemination, distribution or copying of this work is not authorised (either explicitly or implicitly) and constitutes an irritating social faux pas. Unless the word ‘absquatulation’ has been used in its correct context somewhere other than in this warning, it does not have any legal or grammatical use and may be ignored. No animals were harmed in the creation of this journal and a minimum of Microsoft software was used. Those of you with an overwhelming fear of the unknown will be gratified to learn that there is no hidden message revealed by reading this warning backwards.
Year View| Summary| Highlights| Month View| Tuesday 15 October 2002 (Day View) – HDD Errors
Fri 11 Oct | Sat 12 Oct | Sun 13 Oct | Mon 14 Oct | Tue 15 Oct Wed 16 Oct | Thu 17 Oct | Fri 18 Oct | Sat 19 Oct |
15.10.2002 – Tuesday 15 October – Hard Drive Errors
- • The day dawned bright and early. I dawned around lunchtime.
It was a bad mistake.
When I started my PC, scandisk checked drive G:, as I had asked it to. It very thoughtfully told me this:
Checking file system on G:
Read failure with status 0xc000009c at offset 0x160a28400 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x160a28400 for 0x2000 bytes.
Folder \Dloads is entirely unreadable.
Folder entry removed.
1011312 KB in 1182 recovered files.
Read failure with status 0xc000009c at offset 0x1e09b2400 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x1e09b2400 for 0x2000 bytes.
Folder \My Documents\My Pictures\fauna is entirely unreadable.
Folder entry removed.
Read failure with status 0xc000009c at offset 0x1a1a08400 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x1a1a08400 for 0x2000 bytes.
Folder \root\temp\Brad’s Homepage_files\~dhewetts_files is entirely unreadable.
Folder entry removed.
Read failure with status 0xc000009c at offset 0x19a394400 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x19a3a0400 for 0x2000 bytes.
Read failure with status 0xc000009c at offset 0x19a3a2400 for 0x2000 bytes.
Folder \Web\pages has bad clusters.
Bad clusters removed from folder.
Convert lost chains to files (Y/N)? Yes
2344 KB in 262 recovered files.
Windows is verifying free space...
Free space verification is complete.
Windows has made corrections to the file system.
40 KB in bad sectors.
Checking file system on C:
Cleaning up 5 unused index entries from index $SII of file 0x9.
Cleaning up 5 unused index entries from index $SDH of file 0x9.
Cleaning up 5 unused security descriptors.
Read failure with status 0xc000009c at offset 0x10e0aa000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x10e0b6000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x10e197000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x10e19f000 for 0x1000 bytes. Windows replaced bad clusters in file 8767 of name \PROGRA~1\MICROS~3\Office\Xlators\MSO97V.DLL. Read failure with status 0xc000009c at offset 0x10e383000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x10e385000 for 0x1000 bytes.
Windows replaced bad clusters in file 10855 of name \DOCUME~1\ADMINI~1\LOCALS~1\Temp\PFTE9~~1\SVGFIL~1\NPSVGVw.dll.
Adding 3 bad clusters to the Bad Clusters File. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
12 KB in bad sectors.
How exciting. The rough translation is: it deleted my last two years of downloaded files, the majority of which are backed-up to CD’s but not all. It probably means either the hard drive is dying, or the disk controller, or me, or the galaxy. It’s a little hard to tell. - • A few more juice errors which might bring a smile to your dial:
Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.
Access to performance data was denied to ?????o????????? ???? as attempted from C:\WINNT\system32\mmc.exe
The timeout waiting for the performance data collection function “PerfDisk” in the “C:\WINNT\system32\perfdisk.dll” Library to finish has expired.
WMI ADAP was unable to load the perfproc.dll performance library due to an unknown problem within the library: 0x0
Detection of product ’{90280409-6000-11D3-8CFE-0050048383C9}’, feature ’ProductNonBootFiles’, component ’{EE6C0B94-C3A4-11D3-91C4-00600893B51B}’ failed. The resource ’C:\Program Files\Common Files\ODBC\Data Sources\’ does not exist.
Windows cannot load the user’s profile but has logged you on with the default profile for the system.
DETAIL – Insufficient system resources exist to complete the requested service.
RegLoadKey failed. Return value Insufficient system resources exist to complete the requested service. for C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\\UsrClass.dat.
DETAIL – Access is denied. , Build number ((2195)).
The device, \Device\Ide\IdePort0, did not respond within the timeout period.
An error was detected on device \Device\CdRom0 during a paging operation.
The device, \Device\Harddisk0\DR0, has a bad block.
Application popup: Windows – Fatal Application Exit : Tiny Personal Firewall
Driver: MsgDigestCalculate: Unable to open file ’C:’: 0x1
KernelOpenFile: strlen(Filename) < 2 ?!?
AppendFragmentToLongPath: OpenDirectoryObject error: C0000044, Directory: \??\C:\Program Files\Opera
The description for Event ID ( 4000 ) in Source ( fwdrv ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: \Device\FWDRV, MsgDigestCalculate: Unable to open file ’C:’: 0x1.
KernelOpenFile: strlen(Filename) < 2 ?!?.
AppendFragmentToLongPath: OpenDirectoryObject erro.
RSM cannot manage library PhysicalDrive2. It encountered an unspecified error. This can be caused by a number of problems including, but not limited to, database corruption, failure communicating with the library, or insufficient system resources.
The ring buffer that stores incoming mouse data has overflowed (buffer size is configurable via the registry).
The driver has detected a device with old or out-of-date firmware. The device will not be used.
The keyboard device does not exist or was not detected.
Could not set the keyboard indicator lights.
Could not set the keyboard typematic rate and delay.
The device sent an incorrect response(s) following a keyboard reset.
The driver detected a controller error on \Device\Ide\IdePort0. - • I’m not sure what, but something gave me the impression that somewhat was wrong with my PC, I think it was when it deleted my entire Dloads folder, which I was rather fond of. So I’ve been trying to burn my photos and other vital data to CD’s (as it is currently only backed up to another drive but with errors like this, who knows what the problem is?). Unfortunately, I only have four blank CD’s and my computer politely froze just before writing the table of contents to the second CD, which effectively turned it into a fancy coaster. It also annoyed me ever so slightly, and seeing how it is now going on 4:30 AM, I am going to bed – and the data can prepare to meet its maker.
- • Oh, just in case you thought everything was going too smoothly – I did have something that went wrong today. The web hosting, which I ordered and paid for on Sunday, still hadn’t arrived (so to speak) so I emailed them and got the reply that my account had been approved but they had now resent my activation email, but needless to say, I’ve still not received it.
- • Maybe I should’ve been a truck driver.