From: look@sig.bcause.this.is.invalid   
      
   John Conway wrote:   
      
   >   
   > I have looked at lots of websites trying to find the answers   
   > to my problem without success so hopefully someone here may   
   > help me.   
   >   
   > My Son's pc all of a sudden got the dreaded BSOD with the   
   > following message,   
   >   
      
      
   >   
   > I hought the HDD had gone so I bought a brand new one and   
   > started to install XP on it, and then it happened again before   
   > the operating system had really started to install, I can't   
   > even get to re-format it.   
   >   
   > All I can give you to go on is the technical info after the   
   > message which is STOP: 0x00000024 (0x001902FE, 0xf79026dc,   
   > 0xf7902308, 0xf0c30A4?   
   >   
   > NTFS.sys address f70c3004 base at f7073000, datestamo 41107eea   
   >   
   >   
   > Any help would be greatly appreciated.   
   >   
      
   The reason for STOP: 0x00000024 (or NTFS_FILE_SYSTEM)   
   is explained in the ~"WinXP Inside Out" book as;   
      
   "The most likely cause is a hardware failure in a disk or disk   
   controller." and suggestions as "Check all physical connections   
   to all hard disks in the system and run the Check Disk utility ..."   
      
   ( Your similar problem with a new HDD leaves the controller as a   
   suspect. )   
      
   I'd follow Lynsey's suggestions first (cleaning the fans and   
   testing the RAM), but if possible i'd also connect the HDD to the   
   other IDE socket (or another SATA socket depending on type),   
   possibly try another Data-cable (perhaps exchange with the one   
   used for the Optical Drive) to see if that would make any   
   difference as a way to troubleshoot.   
      
   ... And not overclocking ... perhaps restoring BIOS Setup defaults.   
      
      
   --   
   Nah-ah. I'm staying out of this. ... Now, here's my opinion.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)