BSOD at seeminly random times with different error messages

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 7 Ultimate 64 bit
       #1

    BSOD at seeminly random times with different error messages


    I've been getting the BSOD on my desktop for quite a while now. I tried reinstalling Windows, which cut down on the problem but it still happened. Then Windows was telling me it was my RAM. So, I used memtest and determined that one of my sticks of RAM had errors, so I thought that not using that stick of RAM would fix it but it has still blue screened twice in the past two days. And now I'm way past any amount of computer knowledge I have so I have to ask for help! I included the last two dump files since that was after I took out the stick of RAM that had errors (let me know if I should post all of them that I've gotten post Windows reinstall).

    Windows 7 Ultimate 64 Bit
    Processor: Pentium Dual Core CPU E5200@ 2.50GHz 2.50 GHz
    Installed Memory: 3.00 GB (Used to have 4 but took the stick of RAM out that generated errors in memtest)

    Let me know if any more information is needed! And I'll try my best to figure it out! Thank you so much!!
      My Computer


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

    Your Avast is directly blamed.

    Avast can be a contributing cause of BSOD'S . Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


    http://files.avast.com/files/eng/aswclear5.exe

    Microsoft Security Essentials - Free Antivirus for Windows
      My Computer


  3. Posts : 6
    Windows 7 Ultimate 64 bit
    Thread Starter
       #3

    Thank you so much for your help!! I did what you suggested and hopefully the blue screens will stop. :)
      My Computer


  4. Posts : 6
    Windows 7 Ultimate 64 bit
    Thread Starter
       #4

    Unfortunately, I ended up getting another BSOD this morning. I attached the dump file. Thanks to anyone who takes the time to help!
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [D:\Kingston\BSODDmpFiles\sleepysara\042012-31995-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c91650
    Debug session time: Fri Apr 20 10:51:28.578 2012 (UTC - 6:00)
    System Uptime: 0 days 14:58:40.653
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff880037385aa, 8, fffff880037385aa, 0}
    
    
    Could not read faulting driver name
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+456cf )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff880037385aa, memory referenced.
    Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
    Arg3: fffff880037385aa, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfb100
     fffff880037385aa 
    
    FAULTING_IP: 
    +6232323661313365
    fffff880`037385aa ??              ???
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800584a8e0 -- (.trap 0xfffff8800584a8e0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8002a88638
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff880037385aa rsp=fffff8800584aa70 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=fffff880009eb0c0
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff880`037385aa ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a7625c to fffff80002ac9c80
    
    STACK_TEXT:  
    fffff880`0584a778 fffff800`02a7625c : 00000000`00000050 fffff880`037385aa 00000000`00000008 fffff880`0584a8e0 : nt!KeBugCheckEx
    fffff880`0584a780 fffff800`02ac7dae : 00000000`00000008 fffff880`037385aa 00000000`00000000 fffffa80`02a88620 : nt! ?? ::FNODOBFM::`string'+0x456cf
    fffff880`0584a8e0 fffff880`037385aa : fffffa80`02a88620 00000000`c000009a 00000000`00000000 00000000`000007ff : nt!KiPageFault+0x16e
    fffff880`0584aa70 fffffa80`02a88620 : 00000000`c000009a 00000000`00000000 00000000`000007ff 00000000`00000000 : 0xfffff880`037385aa
    fffff880`0584aa78 00000000`c000009a : 00000000`00000000 00000000`000007ff 00000000`00000000 00000000`00000000 : 0xfffffa80`02a88620
    fffff880`0584aa80 00000000`00000000 : 00000000`000007ff 00000000`00000000 00000000`00000000 00000000`00000000 : 0xc000009a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+456cf
    fffff800`02a7625c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+456cf
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55
    
    FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+456cf
    
    BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+456cf
    
    Followup: MachineOwner
    ---------
    Difficult to tell what the cause is. The above crash often indicates memory, but there are other possibilities as well.
    • If you are overclocking any hardware, please stop.

    • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

      For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
      1. Shut down and turn off your computer.
      2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
      3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
      4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.

      Once these steps have been followed, it is safe to remove and replace components within your computer.

    • An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
      a. Backup your system and user files
      b. Create a system restore point
      c. If you do not have a Windows 7 DVD, Create a system repair disc
      d. In Windows 7:
      • Click the Start Menu
      • Type verifier in Search programs and files (do not hit enter)
      • Right click verifier and click Run as administrator
      • Put a tick in Create custom settings (for code developers) and click next
      • Put a tick in Select individual settings from a full list and click next
      • Set up the individual settings as in the image and click next
        Attachment 208465
      • Put a tick in Select driver names from a list
      • Put a tick next to all non-Microsoft drivers.
      • Click Finish.
      • Restart your computer.


      If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

      Thanks to zigzag3143 for contributing to the Verifier steps.
      If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
      The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

      When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
      verifier /reset
      -> Restart your computer.
    Last edited by writhziden; 22 Apr 2012 at 21:06.
      My Computer


  6. Posts : 6
    Windows 7 Ultimate 64 bit
    Thread Starter
       #6

    Thanks for the reply!

    My friend originally set up some...type of overclocking on my computer and I thought that might be causing it to blue screen but I assumed when I reformatted the overclocking would stop. Is this correct? If not, can I stop the overclocking by just selecting return to setup defaults in BIOS??

    I ran memtest86+ before and one stick of RAM returned errors. I took that stick out and then tested the remaining three sticks and that did not return any errors (after running overnight).

    I did the driver verifier thing and uploaded the dump files. The dump files that are from 4/21 are from before the verifier was running. The ones from 4/22 are from when the verifier was running. I don't know if this is relevant or if this is supposed to happen but my usb wireless card stopped working while verifier was running. (Thought I'd just include in case it was important).

    Hopefully I did everything correctly! I'm not super computer savvy... Thank you so much everyone for taking the time to help me!!
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #7

    The Verifier enabled crashes point to memory, network, and data corruption as the likely causes.

    The regular crashes indicate hardware, which may be due to the overclocking. Go into your BIOS, go to the exit section, and load setup defaults. Save and exit.

    Also, I realized I did not include the image for the Verifier settings. We may enable Verifier later with those settings, but for now, please disable and leave Verifier disabled. See if resetting the BIOS to defaults and disabling Verifier provide more system stability.
      My Computer


  8. Posts : 6
    Windows 7 Ultimate 64 bit
    Thread Starter
       #8

    So, I loaded the setup defaults in the BIOS. It took a while to get a couple blue screens so maybe that fixed some of the problem? But I attached the dump files for the three blue screens I've gotten in the past three days. Thank you so much for all the help!!
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #9

    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\sleepysara\Dump Files\042412-27752-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
    Machine Name:
    Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02ca5650
    Debug session time: Tue Apr 24 17:11:53.456 2012 (UTC - 6:00)
    System Uptime: 0 days 0:16:22.173
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 1, fffff80002abd7af}
    
    Probably caused by : ntkrnlmp.exe ( nt!KeSetEventBoostPriority+3f )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002abd7af, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f100
     0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeSetEventBoostPriority+3f
    fffff800`02abd7af f00fba2907      lock bts dword ptr [rcx],7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  VSSVC.exe
    
    TRAP_FRAME:  fffff8800494b550 -- (.trap 0xfffff8800494b550)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa80049ba438 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002abd7af rsp=fffff8800494b6e0 rbp=fffffa80038e1150
     r8=0000000000000000  r9=0000000000000000 r10=fffff8800494b840
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    nt!KeSetEventBoostPriority+0x3f:
    fffff800`02abd7af f00fba2907      lock bts dword ptr [rcx],7 ds:00000000`00000000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002add229 to fffff80002addc80
    
    STACK_TEXT:  
    fffff880`0494b408 fffff800`02add229 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`0494b410 fffff800`02adbea0 : 00000000`1e24a800 00000000`1e24a800 fffffa80`0467b710 fffff800`02c52e80 : nt!KiBugCheckDispatch+0x69
    fffff880`0494b550 fffff800`02abd7af : fffff880`0494ba80 fffff880`012be6ff fffffa80`06035d90 fffffa80`06035ce0 : nt!KiPageFault+0x260
    fffff880`0494b6e0 fffff800`02ad32df : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`01222b80 : nt!KeSetEventBoostPriority+0x3f
    fffff880`0494b750 fffff880`0128c6bd : fffffa80`06035ce0 fffffa80`035b7180 00000000`00000000 00000000`00000001 : nt!ExpReleaseResourceForThreadLite+0x2bf
    fffff880`0494b7b0 fffff880`01294fad : fffffa80`06035ce0 fffffa80`035b7180 00000000`00120101 00000000`00000000 : Ntfs!NtfsFlushVolume+0x4a1
    fffff880`0494b8e0 fffff880`012956b4 : fffffa80`06035ce0 fffffa80`0629ec10 fffffa80`05588d10 00000000`00000000 : Ntfs!NtfsCommonFlushBuffers+0x459
    fffff880`0494b9c0 fffff880`01064bcf : fffffa80`0629efb0 fffffa80`0629ec10 fffffa80`06035ce0 fffff880`0494b9e8 : Ntfs!NtfsFsdFlushBuffers+0x104
    fffff880`0494ba30 fffff880`010636df : fffffa80`0349a040 00000000`00000000 fffffa80`0349a000 fffffa80`0629ec10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`0494bac0 fffff800`02de4ffb : 00000000`00000002 fffffa80`05588d10 00000000`00000000 fffffa80`0629ec10 : fltmgr!FltpDispatch+0xcf
    fffff880`0494bb20 fffff800`02d79b91 : fffffa80`0629ec10 fffffa80`038e1150 fffffa80`05588d10 fffff800`02c52e80 : nt!IopSynchronousServiceTail+0xfb
    fffff880`0494bb90 fffff800`02adcf13 : fffffa80`038e1150 00000000`ff792270 fffffa80`0349a040 fffffa80`05588d10 : nt!NtFlushBuffersFile+0x171
    fffff880`0494bc20 00000000`77a817ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`034bf4c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a817ca
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KeSetEventBoostPriority+3f
    fffff800`02abd7af f00fba2907      lock bts dword ptr [rcx],7
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!KeSetEventBoostPriority+3f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f
    
    BUCKET_ID:  X64_0xA_nt!KeSetEventBoostPriority+3f
    
    Followup: MachineOwner
    ---------
    The most recent crashes are related to hard disk errors: you either have corrupted data, a bad connection, a bad hard disk, or corrupted/out dated hard disk controller drivers. Test for corruption first.
    • Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
      For any drives that do not give the message:
      Windows has checked the file system and found no problems
      run disk check again as above. In other words, if it says:
      Windows has made corrections to the file system
      after running the disk check, run the disk check again.

    • Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
      My Computer


  10. Posts : 6
    Windows 7 Ultimate 64 bit
    Thread Starter
       #10

    The system file check came back with no integrity violations on the first full run. I had to run it a couple times because it would blue screen in the middle of the check. I uploaded the most recent dump files (don't know if you need them or not!) Thank you!!

    This is the disk check info from my HD with Windows on it.
    Code:
    Log Name:      Application
    Source:        Microsoft-Windows-Wininit
    Date:          4/27/2012 12:54:57 PM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      Sara-PC
    Description:
    
    
    Checking file system on C:
    The type of the file system is NTFS.
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    CHKDSK is verifying files (stage 1 of 5)...
      629248 file records processed.                                         
    
    File verification completed.
      646 large file records processed.                                   
    
      0 bad file records processed.                                     
    
      2 EA records processed.                                           
    
      60 reparse records processed.                                      
    
    CHKDSK is verifying indexes (stage 2 of 5)...
      907758 index entries processed.                                        
    
    Index verification completed.
      0 unindexed files scanned.                                        
    
      0 unindexed files recovered.                                      
    
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      629248 file SDs/SIDs processed.                                        
    
    Cleaning up 46 unused index entries from index $SII of file 0x9.
    Cleaning up 46 unused index entries from index $SDH of file 0x9.
    Cleaning up 46 unused security descriptors.
    Security descriptor verification completed.
      139256 data files processed.                                           
    
    CHKDSK is verifying Usn Journal...
      33701672 USN bytes processed.                                            
    
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      629232 files processed.                                                
    
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      61231207 free clusters processed.                                        
    
    Free space verification is complete.
    Windows has checked the file system and found no problems.
    
     312466431 KB total disk space.
      66418136 KB in 471030 files.
        377840 KB in 139257 indexes.
             0 KB in bad sectors.
        745627 KB in use by the system.
         65536 KB occupied by the log file.
     244924828 KB available on disk.
    
          4096 bytes in each allocation unit.
      78116607 total allocation units on disk.
      61231207 allocation units available on disk.
    
    Internal Info:
    00 9a 09 00 fa 4f 09 00 36 f3 13 00 00 00 00 00  .....O..6.......
    db 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....<...........
    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.
    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-04-27T19:54:57.000000000Z" />
        <EventRecordID>4171</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>Application</Channel>
        <Computer>Sara-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
    
    Checking file system on C:
    The type of the file system is NTFS.
    
    A disk check has been scheduled.
    Windows will now check the disk.                         
    
    CHKDSK is verifying files (stage 1 of 5)...
      629248 file records processed.                                         
    
    File verification completed.
      646 large file records processed.                                   
    
      0 bad file records processed.                                     
    
      2 EA records processed.                                           
    
      60 reparse records processed.                                      
    
    CHKDSK is verifying indexes (stage 2 of 5)...
      907758 index entries processed.                                        
    
    Index verification completed.
      0 unindexed files scanned.                                        
    
      0 unindexed files recovered.                                      
    
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      629248 file SDs/SIDs processed.                                        
    
    Cleaning up 46 unused index entries from index $SII of file 0x9.
    Cleaning up 46 unused index entries from index $SDH of file 0x9.
    Cleaning up 46 unused security descriptors.
    Security descriptor verification completed.
      139256 data files processed.                                           
    
    CHKDSK is verifying Usn Journal...
      33701672 USN bytes processed.                                            
    
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      629232 files processed.                                                
    
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      61231207 free clusters processed.                                        
    
    Free space verification is complete.
    Windows has checked the file system and found no problems.
    
     312466431 KB total disk space.
      66418136 KB in 471030 files.
        377840 KB in 139257 indexes.
             0 KB in bad sectors.
        745627 KB in use by the system.
         65536 KB occupied by the log file.
     244924828 KB available on disk.
    
          4096 bytes in each allocation unit.
      78116607 total allocation units on disk.
      61231207 allocation units available on disk.
    
    Internal Info:
    00 9a 09 00 fa 4f 09 00 36 f3 13 00 00 00 00 00  .....O..6.......
    db 00 00 00 3c 00 00 00 00 00 00 00 00 00 00 00  ....&lt;...........
    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.
    </Data>
      </EventData>
    </Event>
    This is the disk check info from my external HD.
    Code:
    Log Name:      Application
    Source:        Chkdsk
    Date:          4/27/2012 1:52:29 PM
    Event ID:      26214
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      Sara-PC
    Description:
    Chkdsk was executed in read/write mode.  
    
    Checking file system on E:
    Volume label is Elements.
    
    CHKDSK is verifying files (stage 1 of 5)...
      7424 file records processed.                                         
    
    File verification completed.
      0 large file records processed.                                   
    
      0 bad file records processed.                                     
    
      0 EA records processed.                                           
    
      0 reparse records processed.                                      
    
    CHKDSK is verifying indexes (stage 2 of 5)...
      8652 index entries processed.                                        
    
    Index verification completed.
    
    
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      7424 file SDs/SIDs processed.                                        
    
    Cleaning up 14 unused index entries from index $SII of file 0x9.
    Cleaning up 14 unused index entries from index $SDH of file 0x9.
    Cleaning up 14 unused security descriptors.
    Security descriptor verification completed.
      615 data files processed.                                           
    
    CHKDSK is verifying Usn Journal...
      5938584 USN bytes processed.                                            
    
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      7408 files processed.                                                
    
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      21182232 free clusters processed.                                        
    
    Free space verification is complete.
    Windows has checked the file system and found no problems.
    
     117219799 KB total disk space.
      32404388 KB in 6752 files.
          3568 KB in 616 indexes.
         82911 KB in use by the system.
         65536 KB occupied by the log file.
      84728932 KB available on disk.
    
          4096 bytes in each allocation unit.
      29304949 total allocation units on disk.
      21182233 allocation units available on disk.
    
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Chkdsk" />
        <EventID Qualifiers="0">26214</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-04-27T20:52:29.000000000Z" />
        <EventRecordID>4186</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Sara-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
    
    Checking file system on E:
    Volume label is Elements.
    
    CHKDSK is verifying files (stage 1 of 5)...
      7424 file records processed.                                         
    
    File verification completed.
      0 large file records processed.                                   
    
      0 bad file records processed.                                     
    
      0 EA records processed.                                           
    
      0 reparse records processed.                                      
    
    CHKDSK is verifying indexes (stage 2 of 5)...
      8652 index entries processed.                                        
    
    Index verification completed.
    
    
    CHKDSK is verifying security descriptors (stage 3 of 5)...
      7424 file SDs/SIDs processed.                                        
    
    Cleaning up 14 unused index entries from index $SII of file 0x9.
    Cleaning up 14 unused index entries from index $SDH of file 0x9.
    Cleaning up 14 unused security descriptors.
    Security descriptor verification completed.
      615 data files processed.                                           
    
    CHKDSK is verifying Usn Journal...
      5938584 USN bytes processed.                                            
    
    Usn Journal verification completed.
    CHKDSK is verifying file data (stage 4 of 5)...
      7408 files processed.                                                
    
    File data verification completed.
    CHKDSK is verifying free space (stage 5 of 5)...
      21182232 free clusters processed.                                        
    
    Free space verification is complete.
    Windows has checked the file system and found no problems.
    
     117219799 KB total disk space.
      32404388 KB in 6752 files.
          3568 KB in 616 indexes.
         82911 KB in use by the system.
         65536 KB occupied by the log file.
      84728932 KB available on disk.
    
          4096 bytes in each allocation unit.
      29304949 total allocation units on disk.
      21182233 allocation units available on disk.
    </Data>
        <Binary>001D0000D41C00004C2A0000000000002C0F0000000000000000000000000000</Binary>
      </EventData>
    </Event>
      My Computer


 
Page 1 of 2 12 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 23:42.
Find Us