From: MrPounder@RationalThought.com   
      
   "JJ"  wrote in message   
   news:15tjubbtpvk4d$.rettczk432s7.dlg@40tude.net...   
   > On Tue, 19 Aug 2014 18:20:10 +0100, Mr Pounder wrote:   
   >> I used chkdsk /v   
   >> Then chkdsk /f   
   >> I had to schedial a reboot to use chkdsk /f   
   >> Then, I used chkdsk /v - saw the same results. I then pasted it into my   
   >> email.   
   >   
   > Do a RAM diagnosis first, to see if the harddisk file system is really   
   > corrupted or not.   
   >   
   > If RAM is OK, boot using the Windows DVD or any Windows based recovery CD   
   > and run CHKDSK /F from there. Perform it multiple times to make sure no   
   > more   
   > errors are found. If there are still errors after 3-4 fixes, the file   
   > system   
   > may have been severely corrupted.   
   >   
   > If all of the errors have been fixed, boot into harddisk and do CHKDSK   
   > (without /F) again. If there are errors again, there could be disk related   
   > third party drivers interfering the system. Virus/malware is also a   
   > possibility, but I doubt it since nowadays, most of them are dumb phishing   
   > malwares.   
      
   How would I do a RAM diagnosis?   
   Please excuse my lack of knowledge.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)