BSoD on boot after ending chkdsk


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    BSoD on boot after ending chkdsk


    Okay. If someone can figure this out, I'll give them a cookie.

    K, so I primarily use Windows 7, but also have multiple OSes underneath it, such as Ubuntu and Joli OS installed by WUBI type of installer. Now, I decided to run a chkdsk because it's normally good to run it once in a while, right? Anyways, while it was running, it stopped running for like two hours. It was stuck on one specific % (don't remember the %). Yeah, I know that you aren't supposed to shut down while chkdsk is running, but it stopped running so it was my only option. I rebooted by power button and loaded into Windows, but Windows was throwing some errors on the notification thingy in the taskbar (it would say things like "C:\$Secure" with nothing else written), so I decided to reboot again. Apparently, a bad choice.

    It starts off with my custom boot logo (not related as I've had the same boot logo for months before with no problems), but then flashes a BSoD for .5 sec and restarts itself. (Same for Safe Mode) I looked up the BSoD error number, and the majority of the comments about it relate to RAM. I decided to try running memtest86 (and memtest86+) to see if it's related to my RAM. I obtained a LiveCD of each of them and stick one of them in.... Annnnd Windows attempts to boot, Blue Screening again. Not a problem, I think. I'll just go to the BIOS and change the boot order. I press the ON button and hit F10 (which has always taken me to BIOS before).... annnnd it doesn't go to BIOS. It goes to this weird "Edit Boot Settings" thing that says what sections of the hard drive Windows is installed on. I even reseated the CMOS battery, but no dice. So I just pull out my hard drive so the LiveCD is the only bootable media in the laptop, and memtest86 loads, and all results are completely clean (Same with memtest86+). I thought that was weird because the BSoD was suggesting the RAM was the problem, but in the tests, the RAM came out completely clean. Meanwhile, I have been using my Ubuntu installed through WUBI to do my daily business (using it to type this).


    So I'm fairly certain it's the hard drive, but I don't understand why Ubuntu is working because it's on the same hard drive. I also don't understand why I can't get into the BIOS when I could before.


    Oh, and every time I run "Windows Memory Test" from the boot screen, it freezes at 21% when on "Extended Test" ONLY, it comes out completely clean on "Standard".


    Another thing I was planning on doing (I've already backed up my important stuff to an external hard drive), was just to get the Windows 7 Ultimate Product Key using one of those programs and formatting and reinstalling Windows 7 from scratch. But, when I try and use one of those programs in WINE, I get "Error 1314: Privilege not held"



    Any ideas?
      My Computer


  2. Posts : 181
    Windows 7
       #2

    might want to see this first:
    Blue Screen of Death (BSOD) Posting Instructions
    then see if we can help...
      My Computer


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

    Do chkdsk again. And look if there's disk activity. It can stall for 10 minutes but not hours! You can do it from Advanced Boot Options "repair your computer"->command prompt. Drive letters may be different as normal there! Just do chkdsk/f c, chkdsk/f d and so on. Or DIR C: to check if it's the correct disk.
    Check disk with datalifeguard (for western digital disks) or seatools (seagate disks)

    Boot into Advanced Boot Options
    and select "Disable Automatic Restart on System Failure" so you can see the BSOD longer. Tell us what is shown please.
      My Computer


  4. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #4

    cipley said:
    might want to see this first:
    Blue Screen of Death (BSOD) Posting Instructions
    then see if we can help...
    Can't do those as I can't boot into Windows


    Thanks Kaktussoft! I completely forgot that System Recovery Options had Command Prompt! I was thinking that System Recovery Options was only the Startup Repair (which doesn't work). Now I'm running chkdsk, then I'll try the Windows Memory Diagnostics, System Restore, and TOSHIBA Recovery Wizard! :)
    I'll report back after school when I try those.

    Oh, and this is the BSoD:
      My Computer


  5. Posts : 181
    Windows 7
       #5

    STOP 0x00000024: NTFS_FILE_SYSTEM

    Usual causes:
    Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

    this is puzzling since you can't enter safe mode either

    if you can boot thru other OS, try to upload the minidump files, then...
    it's in C:\Windows\Minidump
    might get better picture from there...
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Do some Disc checks.

    1. Update your SSD's Firmware (skip it, if you are not using a SSD)
    2. Re-seat the sata and power.
    3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
    4. Seatool for dos: SeaTools | Seagate download
      Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.
      My Computer


  7. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Thanks guys, but I ended up just using TOSHIBA Recovery Wizard and wiping my hard drive.

    I still gotta check on the BIOS though... I also gotta see if Windows Memory Test will come out clean after the reformat...

    Oh, and cipley, the Minidump was one of the first things I had checked when Windows first crashed, but the Minidump folder was empty...
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    To configure minidump on BSOD, follow it: Dump Files - Configure Windows to Create on BSOD
    Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

    Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


 

  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 10:51.
Find Us