locked
BSOD Registry error RRS feed

  • Question

  • The problem is i turn on my computer and log in as normal, it looks to start as normal but then just blue screens on me please help below i linked the system data and dump if that helps?

    Also the computer starts up fine in safe mode.

    https://onedrive.live.com/redir?resid=BC8FD5F10649AB2F!154&authkey=!ACoqqk5efBwIyKs&ithint=file%2c.dmp
    https://onedrive.live.com/redir?resid=BC8FD5F10649AB2F!155&authkey=!ADxOGi0hzeyNYJE&ithint=file%2c.xml

    Saturday, March 15, 2014 7:15 PM

Answers

  • BRE

    It is indeed a registry error.  Your options include restoring back to a date prior to the problem, doing a repair install from the win 7 dvd, or better yet a clean install.  I would remove Rapport as it has known issue with win 7 on some systems.

    The other possible cause since this is I/O is a HD issue.  For this I would run CHKDSK

    Something has gone badly wrong with the registry.  If a kernel debugger
    is available, get a stack trace. It can also indicate that the registry got
    an I/O error while trying to read one of its files, so it can be caused by
    hardware problems or filesystem corruption.
    

    CHKDSK /R /F
    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.

    CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 15, 2014 11:04 PM
    Saturday, March 15, 2014 7:32 PM

All replies

  • BRE

    It is indeed a registry error.  Your options include restoring back to a date prior to the problem, doing a repair install from the win 7 dvd, or better yet a clean install.  I would remove Rapport as it has known issue with win 7 on some systems.

    The other possible cause since this is I/O is a HD issue.  For this I would run CHKDSK

    Something has gone badly wrong with the registry.  If a kernel debugger
    is available, get a stack trace. It can also indicate that the registry got
    an I/O error while trying to read one of its files, so it can be caused by
    hardware problems or filesystem corruption.
    

    CHKDSK /R /F
    Chkdsk disclaimer: While performing chkdsk on the hard drive if any bad sectors are found  any data available on that sector might be lost so as usual backup your data.
    Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
    Do this for each hard drive on your system.
    When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.

    Then reboot and let the test run.
    It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
    http://www.howtogeek.com/howto/windows-vista/guide-to-using-check-disk-in-windows-vista/


     See "CHKDSK LogFile" below in order to check the results of the test.

    CHKDSK LogFile:

    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post. 


    Wanikiya and Dyami--Team Zigzag

    • Marked as answer by ZigZag3143x Saturday, March 15, 2014 11:04 PM
    Saturday, March 15, 2014 7:32 PM
  • I think this is what you wanted


    Chkdsk was executed in read-only mode.  A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.  

    Checking file system on C:
    The type of the file system is NTFS.
    The volume is in use by another process. Chkdsk
    might report errors when no corruption is present.
    Volume label is Acer.

    WARNING!  F parameter not specified.
    Running CHKDSK in read-only mode.

    CHKDSK is verifying files (stage 1 of 3)...
      805120 file records processed.                                          File verification completed.
      1588 large file records processed.                                      0 bad file records processed.                                        0 EA records processed.                                              93 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 3)...
      1015468 index entries processed.                                         Index verification completed.
      0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 3)...
      805120 file SDs/SIDs processed.                                         Cleaning up 243 unused index entries from index $SII of file 0x9.
    Cleaning up 243 unused index entries from index $SDH of file 0x9.
    Cleaning up 243 unused security descriptors.
    Security descriptor verification completed.
      105175 data files processed.                                            CHKDSK is verifying Usn Journal...
    The USN Journal entry at offset 0x6ae7f0000 and length 0x26d54235 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f1000 and length 0xdeee5222 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f2000 and length 0x7c910bbd crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f3000 and length 0xc663f7f8 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f4000 and length 0xb9a2a32e crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f5000 and length 0xb3522986 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f6000 and length 0xf4fa103 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f7000 and length 0x281d3b14 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f8000 and length 0x516caefc crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7f9000 and length 0xd9ac3b1f crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7fa000 and length 0xbcf759ef crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7fb000 and length 0x400971f3 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7fc000 and length 0xd02b26f8 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7fd000 and length 0x900c6a46 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7fe000 and length 0xdbe62e79 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae7ff000 and length 0xc8b74f41 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae800000 and length 0x9f09a700 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae801000 and length 0x238831e8 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae802000 and length 0x1644b7bf crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae803000 and length 0xfa3d9f99 crosses
    the page boundary.
    The USN Journal entry at offset 0x6ae804000 and length 0x5c24d003 crosses
    the page boundary.

    Examining Usn Journal file record segment.
      36970184 USN bytes processed.                                             Usn Journal verification completed.
    The master file table's (MFT) BITMAP attribute is incorrect.
    The Volume Bitmap is incorrect.
    Windows found problems with the file system.
    Run CHKDSK with the /F (fix) option to correct these.

     481159167 KB total disk space.
     453943840 KB in 667286 files.
        369316 KB in 105176 indexes.
             4 KB in bad sectors.
        924443 KB in use by the system.
         65536 KB occupied by the log file.
      25921564 KB available on disk.

          4096 bytes in each allocation unit.
     120289791 total allocation units on disk.
       6480391 allocation units available on disk.
    Saturday, March 15, 2014 8:13 PM
  • BRE

    Now you need to run it with /F, /R to repair the problems


    Wanikiya and Dyami--Team Zigzag

    Saturday, March 15, 2014 8:20 PM
  • I have ran the /r and /f should this have fixed the problem i think it may as i didnt have the bsod this time on so thank you!
    Saturday, March 15, 2014 9:07 PM
  • BRE

    I will stay subscribed just in case and thanks for letting us know.


    Wanikiya and Dyami--Team Zigzag

    Saturday, March 15, 2014 11:03 PM
  • Unfortunatly i guess it hasnt been fixed as the computer has been fine to use for a few days but it happened again i havnt done anything out of the normal, no new programs i realy dont know here is the dump file
     https://onedrive.live.com/redir?resid=BC8FD5F10649AB2F!160&authkey=!AFAmdxWJILjWBC4&ithint=file%2c.dmp
     please help again
    Tuesday, March 18, 2014 6:49 AM
  • BRE

    Still a registry error.  Time for a repair install refresh, or reinstall.


    Wanikiya and Dyami--Team Zigzag

    Tuesday, March 18, 2014 12:12 PM