How to edit windows system files?

• Malogg wrote on 2011-07-12 06:58
  My computer has been getting a blue sceeen of death and crashing a lot lately. At first it only happened once a month, then once a week, and now it's happening daily. (I'm 98% sure that my computer does not have a virus.) I got a program to read the .dmp files and tell me the details. All the crashes had ntoskrnl.exe listed as one of the problems. So, I went on a different computer running the same OS as me (Windows 7, 64 bit) and got a clean version of ntoskrnl.exe. My original plan was to just go into C:\Windows\System32 and replace my ntoskrnl with the clean one. However, I can't edit system files, even as an administrator.
  
  Any ideas, Nation?
• Tatsu wrote on 2011-07-12 07:19
  Right click, take ownership. You can now do whatever you want to it.
  
  Whether or not that actually fixes your virus problem, don't ask me.
• Yoorah wrote on 2011-07-12 15:09
  Just because ntoskrnl.exe was listed, it doesn't mean it's at fault. But if you think you have system file corruption going on, try opening the command prompt with admin rights and run sfc /scannow
• Malogg wrote on 2011-07-12 21:24

  Quote from Yoorah;509537:

  Just because ntoskrnl.exe was listed, it doesn't mean it's at fault. But if you think you have system file corruption going on, try opening the command prompt with admin rights and run sfc /scannow

  
  
  Thank you! I did that, and it said it found something corrupt and fixed it. Hopefully I won't get blue screens anymore.
• Malogg wrote on 2011-07-16 00:49
  Okay, so I typed sfc /scannow, and it still crashed again. I reformatted my laptop with a fresh install of windows 7, and it still crashed. I don't know what to do now. It's a fairly new laptop, so hopefully my warranty is still good. O.o
• Yoorah wrote on 2011-07-16 00:58
  Sounds like bad hardware. Try running the Windows Memory Diagnostic; RAM is the easiest part to test. You can also test RAM with Memtest86+.
  
  If it's not the RAM, then it could be a bad HDD.. although this is unlikely. One way to check the disk for errors is the chkdsk /f command, run it from a command prompt with admin rights. There are better disk checking tools out there, like SpinRite, but those are not free. I don't know of any good free ones, maybe someone else can elaborate on that.
  
  Or it could be random component failure on the board, I don't know. D:
  Either way, you'll probably have to make use of that warranty. :(
• Malogg wrote on 2011-07-16 01:26
  Well, I ran Windows Memory Diagnostic, and it didn't find anything wrong.
  
  I used chkdsk /f in the command prompt and got this.
• Bakuryu wrote on 2011-07-16 01:31
  Answer Y, and reboot. It will then do the chkdsk.
• Malogg wrote on 2011-07-16 02:34
  Okay, I did it. How can I view the results?
• Yoorah wrote on 2011-07-16 02:48
  Event Viewer > Windows Logs > Application
  Look for Wininit as the source.
• Malogg wrote on 2011-07-16 03:06

  Quote from Yoorah;513943:

  Look for Wininit as the source.

  
  
  What do you mean by this?
  
  EDIT: I found it. But what now?
  
  Also, what do you make of this?
• Yoorah wrote on 2011-07-16 03:14
  You have to read the log and look for signs of trouble. It's kinda messy, but it should be readable. (I'm not sure why they don't have a better interface for this. >_>)
  
  Key things you want to see are: "Windows has checked the file system and found no problems." and "0 KB in bad sectors."
• Malogg wrote on 2011-07-16 03:17
  Everything seems fine to me. You can take a look, if you want.
  
  [SPOILER="Spoiler"]Checking file system on C:
  The type of the file system is NTFS.
  Volume label is OSDisk.
  
  
  A disk check has been scheduled.
  Windows will now check the disk.
  
  CHKDSK is verifying files (stage 1 of 3)...
  242944 file records processed. File verification completed.
  213 large file records processed. 0 bad file records processed. 0 EA records processed. 44 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
  284694 index entries processed. Index verification completed.
  0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
  242944 file SDs/SIDs processed. Cleaning up 2 unused index entries from index $SII of file 0x9.
  Cleaning up 2 unused index entries from index $SDH of file 0x9.
  Cleaning up 2 unused security descriptors.
  Security descriptor verification completed.
  20876 data files processed. CHKDSK is verifying Usn Journal...
  35251192 USN bytes processed. Usn Journal verification completed.
  Windows has checked the file system and found no problems.
  
  610792447 KB total disk space.
  30440332 KB in 99700 files.
  80996 KB in 20877 indexes.
  0 KB in bad sectors.
  364027 KB in use by the system.
  65536 KB occupied by the log file.
  579907092 KB available on disk.
  
  4096 bytes in each allocation unit.
  152698111 total allocation units on disk.
  144976773 allocation units available on disk.
  
  Internal Info:
  00 b5 03 00 0d d7 01 00 80 b1 03 00 00 00 00 00 ................
  c9 42 00 00 2c 00 00 00 00 00 00 00 00 00 00 00 .B..,...........
  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
  
  Windows has finished checking your disk.
  Please wait while your computer restarts.[/SPOILER]
  
  Thanks for the help, by the way.