- Nov 13, 1999
- 11,875
- 282
- 126
Well this is rather difficult to explain, but here goes. I have a SCSI raid array that I run WinXP Pro on my home workstation. I have installed the OS several times on this array. I have to install Win2k because of the way the array controller has to be setup and then upgrade to WinXP. In each of these installs after the OS is finished being installed and the basic programs installed and updates completed I do a defrag of the system. In each case the defrag ends with about an inch and a half freespace gap from the beginning of the graph to the beginning of the stored data files that are defragged. You can click on the link below to see what I mean, its represented by the before defrag in the first image. This evening I suddenly had an error on my system while retreving email. It read like this "Thor Conn Wnd Class: Outlook Exe. Application Error the instruction 0x450f2853 referrenced memory at 0x450f2853- The required data was not placed into memory because of an IO error Staus 0xc 0000185 Click OK to terminate program". When this occured my system became very unstable and then rebooted... it then ran Check Disk on its own... locked up...rebooted then did Check disk again. It then showed numerous "orphan" files recovered and repaired the disk. 0 bad sectors and rebooted. After getting back into windows I decided to do a defrag. This first image shows the result. After all this time with that free space at the beginning of the graph, WinXP decides to finally use it! You can see the final result of this initial defrag.
This
Now I then went to all my programs and opened them to see if they all still worked. Everyone of them worked fine and opened even faster than they had in the past. Only one program of all on my system had to repair itself, MS Photo Draw and even that was a quick repair. After that repair was done it opened and operated just fine like all the rest. I then went back and defragged again the below is a PIC of that final result. Even looks better. Now system works just fine, all programs work fine and all is very stable. Can anyone explain what WinXP did here? Is this all part of NTFS indexing and it simply corrected itself?
THIS
This
Now I then went to all my programs and opened them to see if they all still worked. Everyone of them worked fine and opened even faster than they had in the past. Only one program of all on my system had to repair itself, MS Photo Draw and even that was a quick repair. After that repair was done it opened and operated just fine like all the rest. I then went back and defragged again the below is a PIC of that final result. Even looks better. Now system works just fine, all programs work fine and all is very stable. Can anyone explain what WinXP did here? Is this all part of NTFS indexing and it simply corrected itself?
THIS