BSOD after YouTube, now can't boot pc, ntfs.sys corrupted

Page 1 of 5 123 ... LastLast

  1. Posts : 24
    Win 7 pro 64
       #1

    BSOD after YouTube, now can't boot pc, ntfs.sys corrupted


    While watching YouTube video, pc gave me a BSOD about graphics driver, and proceeded to reboot. It then gave me startup repair, saying that wi cows can't boot. Upon completing the automatic repair, this is what i get

    Problem signatures
    Problem event name. StartupRepairOffline
    Problem signature 1 6.1.7600.16385
    Problem signature 2 6.1.7600.16385
    Problem signature 3 unknown
    Problem signature 4 21200746
    Problem signature 5 autofailover
    Problem signature 6 7
    Problem signature 7 corruptfile
    Os version 6.1.7600.2.0.0.256.1
    Locale Id 1033


    Upon viewing diagnostic and repair details, this is what I get

    At first, it was 0x0 on everything except 1 root cause, which was saying that ntfs.sys was corrupt. I searched online for solutions, and found people saying I should put in install cd, and use command line to manually rename the ntfs.sys to ntfs.old and copy a new file from the windows cd. I did that, but it did not fix the problem. Now, however, the startup repair does not say anything about ntfs.sys, and Instead gives this

    Root cause found
    Startup repair has tried several times but still cannot determine the cause of problem


    I still have the original ntfs.sys renamed as ntfs.old
    I have windows install cd
    It's wi 7 pro 64, legal and licensed

    So any help would be appreciated!
    Thanks


    Edit
    Forgot to add. Even though in windows my drives are named C ( windows ssd drive), I and J, and cd drive being E, Inside command prompt and startup repair they become F (windows drive) and X (cd drive). Is that normal?
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Anakonda said:
    While watching YouTube video, pc gave me a BSOD about graphics driver, and proceeded to reboot. It then gave me startup repair, saying that wi cows can't boot. Upon completing the automatic repair, this is what i get

    Problem signatures
    Problem event name. StartupRepairOffline
    Problem signature 1 6.1.7600.16385
    Problem signature 2 6.1.7600.16385
    Problem signature 3 unknown
    Problem signature 4 21200746
    Problem signature 5 autofailover
    Problem signature 6 7
    Problem signature 7 corruptfile
    Os version 6.1.7600.2.0.0.256.1
    Locale Id 1033


    Upon viewing diagnostic and repair details, this is what I get

    At first, it was 0x0 on everything except 1 root cause, which was saying that ntfs.sys was corrupt. I searched online for solutions, and found people saying I should put in install cd, and use command line to manually rename the ntfs.sys to ntfs.old and copy a new file from the windows cd. I did that, but it did not fix the problem. Now, however, the startup repair does not say anything about ntfs.sys, and Instead gives this

    Root cause found
    Startup repair has tried several times but still cannot determine the cause of problem


    I still have the original ntfs.sys renamed as ntfs.old
    I have windows install cd
    It's wi 7 pro 64, legal and licensed

    So any help would be appreciated!
    Thanks


    Edit
    Forgot to add. Even though in windows my drives are named C ( windows ssd drive), I and J, and cd drive being E, Inside command prompt and startup repair they become F (windows drive) and X (cd drive). Is that normal?


    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.




      My Computer


  3. Posts : 24
    Win 7 pro 64
    Thread Starter
       #3

    Unfortunately, as I have stated, I cannot boot into windows, not even safe mode.
    All I have access to is startup repair and windows install disk, which also provides a startup repair
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Anakonda said:
    Unfortunately, as I have stated, I cannot boot into windows, not even safe mode.
    All I have access to is startup repair and windows install disk, which also provides a startup repair
    Understood.

    If your computer is out of warranty and is a desktop you can try removing all but one stick of ram. That sometimes makes it bootable.

    If you cant boot normally, in safe mode, or from the dvd, your options are limited.


      My Computer


  5. Posts : 24
    Win 7 pro 64
    Thread Starter
       #5

    Boot from DVD?

    I have windows install DVD, the original, so I can use it to boot - but it boots into a version of startup repair, only with an extra option of installing windows. From there I have access to command line, system restore(I was stupid and did t make a restore point), automatic repair (which doesn't work) and some two other not help options. Is that what you meant?

    Also, I ran the memory test, and it came fine. Do you think it still could be something to do with ram? It all started with the ntfs.sys being corrupt, isn't that something to do with hard drive partitioning?
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Anakonda said:
    Boot from DVD?

    I have windows install DVD, the original, so I can use it to boot - but it boots into a version of startup repair, only with an extra option of installing windows. From there I have access to command line, system restore(I was stupid and did t make a restore point), automatic repair (which doesn't work) and some two other not help options. Is that what you meant?

    Also, I ran the memory test, and it came fine. Do you think it still could be something to do with ram? It all started with the ntfs.sys being corrupt, isn't that something to do with hard drive partitioning?

    Boot from dvd means just that. If you can boot from the dvd (and it appears you can) and you have a backup you can restore it from there.

    If you dont have a backup you can do a repair install, or better yet a clean install.

    Ntfs.sys is an OS file and it does not reflect HD partitioning.

      My Computer


  7. Posts : 24
    Win 7 pro 64
    Thread Starter
       #7

    Unfortunately I do not know how to make a repair install. I have two options - install windows and repair. Repair leads me back to autostartup repair. Install giveS me option to upgrade (which I cant because it tells me to run it from inside windows proper), or do a custom install (which is basically a fresh install). Am I doing something wrong?
      My Computer


  8. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #8

    Do a sfc (system file checker) form dvd
    SFC /SCANNOW : Run in Command Prompt at Boot
    see step 7
    problems found? Also you can do a "system restore" from recovery environment
    System Restore (option 2)
      My Computer


  9. Posts : 24
    Win 7 pro 64
    Thread Starter
       #9

    Hmm I though I added that already. Apparently I didn't.
    I have already attempted the sfc command. When I run it normally, message tells me that it can't be run during repair. When I use it with the offline command (don't remember, I think it was something like /offboot=f:/ \offwindir=f:/ or something, I dont remember the exact syntax right now. But then it gave me the cannot execute the program error. Something about windows protect shell not executing it or something

    Also I cannot use system restore because no restore points have been created. Stupid, I know.
      My Computer


  10. Posts : 10,796
    Microsoft Windows 7 Home Premium 64-bits 7601 Multiprocessor Free Service Pack 1
       #10

    sfc /scannow /offbootdir=f:\ /offwindir=f:\windows
    read the tutorial carefully! maybe you have to use e: instead of f:
    Run this command from "recovery environment". Post the error (if any)
      My Computer


 
Page 1 of 5 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:50.
Find Us