Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 49
  1. #21
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Sorry Donna I seem to have lost the previous 3 or 4 replies....I know I sent you the logs you asked for but I've lost all other communications somehow....what on earth is wrong with my stupid computer??????

  2. #22
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Hi DonnaB, I'm now typing this from my laptop because my desktop computer is seriously throwing a tantrum. I don't know if you got my last post but my desktop suffered a blue screen with the words...'kernel_data_inpage_error', followed by, 'crash dump', and...'stop ox0000007A. Can you put me out of my misery & tell me that my desktop computer is dead or dying? I'm throwing it out of the window soon...!!!!!!

  3. #23
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Hi DonnaB, sorry but I've absolutely no idea what is going on here...I've posted messages to you that I can no longer find, I'm now on my laptop because my desktop which is having the problems has now suffered a blue Screen....the system has crashed.....and right now the idea of throwing the computer out the window seems very appealing.......please can you help an old timer to understand what the hell is going on coz I sure as hell have no idea???

  4. #24
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,524
    Points
    563

    Default

    Hi Number7,

    Yes, I did receive the logs. All of your other posts seem to be posting just fine as well.

    Did you see where I had posted here concerning the Windows Updates, the 0x7A KERNEL_DATA_INPAGE_ERROR and asked you to do another chkdsk. I also provided instructions on how to find the log that chkdsk produces and can be found in the Eventviewer.

    Take your time and please don't toss your computer out the window.

    Could you also tell me what the make and model of your desktop is. You should be able to find this on a sticker attached to the tower somewhere.

    Donna
    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

  5. #25
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Thank you DonnaB for having much patience with me...you'll be pleased to know that my desktop PC (The one with the problems) hasn't gone out the window....yet!! I started a chkdsk as you requested but by stage 4, the system froze, and I was presented with another blue screen.... I've now initiated a second chkdsk attempt & will keep you informed......I must be your worst client.....sorry.

  6. #26
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    sorry Donna....where do I find the 'clipboard' please?

  7. #27
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,524
    Points
    563

    Default

    The clipboard is actually invisible. Normal copy/paste/cut actually stores the content/data in a temporary resource called the "clipboard" which is a file within Windows. When you copy anything it is saved to memory and when you find the location in which you want to paste or cut what you have copied, memory will be accessed and whatever you had clicked on to copy will be pasted or cut into that location of choice.

    Once you have clicked that copy button, come to your thread, click in a Quick Reply box and choose paste. Memory will be accessed and the data that was copied to the "clipboard" will be pasted into the post.

    Took me awhile to understand how copy, paste and cut work without actually being able to see it happen.

    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

  8. The Following User Says Thank You to DonnaB For This Useful Post:


  9. #28
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Sorry.....what do I type in the 'run' box again to see the results to be copied for you? Got to find 'wininet' somewhere?

  10. #29
    Member
    Join Date
    Aug 2010
    Location
    Kent, England
    Posts
    250
    Points
    0

    Default

    Hi DonnaB, 3 times I've attempted a chkdsk, and 3 times the scan has frozen at 10%, stage 4 out of 5, and given me a blue screen. The only results I have are the ones listed below that you requested.....sorry...

    Log Name: Application
    Source: Microsoft-Windows-Wininit
    Date: 29/05/2013 17:37:35
    Event ID: 1001
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: Chris-PC
    Description:


    Checking file system on C:
    The type of the file system is NTFS.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x10d78 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x104e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 4174.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x4051b for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3fbf is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 16319.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x13d944 for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x8e2b is already in use.
    Deleted corrupt attribute list entry
    with type code 128 in file 36395.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xe0000000001ad. The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 429.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x405cb for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xee5b is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 61019.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x24014 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xf5d9 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 62937.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x41404 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xf6e0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63200.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x80ac for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x161ae is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90542.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1fa20 for possibly 0x7 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x161b2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90546.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x80c0 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16267 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90727.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe6ac for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x16646 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 91718.
    Attribute record of type 0xa0 and instance tag 0x2 is cross linked
    starting at 0xbb208 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x2
    in file 0x1839a is already in use.
    Deleted corrupt attribute list entry
    with type code 160 in file 99226.
    Unable to locate attribute with instance tag 0x2 and segment
    reference 0x400000001fcbd. The expected attribute type is 0xa0.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 130237.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x13fa17 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x183aa is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 99242.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x564f9 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x19bff is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 105471.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x405c9 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1aa3e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 109118.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x1fc0b for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1c9f0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 117232.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x8efc for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1ce5a is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118362.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x564fa for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1ce94 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118420.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe2e7 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1cff3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118771.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x3fe36c for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1d215 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119317.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x40bb6d for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1d2a2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119458.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x21de8 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d402 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119810.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3a63bfc for possibly 0x4a clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d4a2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119970.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x9df8 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d4c7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120007.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0xc9710 for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x1d63f is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120383.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0xbf20 for possibly 0x2aa clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x1d6e3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120547.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe2e8 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x20d0e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 134414.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c41a for possibly 0x95 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22aa4 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 141988.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c4af for possibly 0x7d clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22aaa is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 141994.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c52c for possibly 0x18 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22ab0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142000.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c544 for possibly 0x14 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22ada is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142042.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c558 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22bc7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142279.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x34a07 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x26046 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 155718.
    161280 file records processed.

    File verification completed.
    Deleting orphan file record segment 429.
    279 large file records processed.

    0 bad file records processed.

    0 EA records processed.

    60 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 3)...
    Index entry MS6F25~1.HTM of index $I30 in file 0x965a points to unused file 0x1c9e9.
    Deleting index entry MS6F25~1.HTM in index $I30 of file 38490.
    The file reference 0x2100000001c9e8 of index entry MSBB5A~1.HTM of index $I30
    with parent 0x965a is not the same as 0x1f00000001c9e8.
    Deleting index entry MSBB5A~1.HTM in index $I30 of file 38490.
    Index entry msn-hp-video-module-tab2[10].htm of index $I30 in file 0x965a points to unused file 0x1c9e9.
    Deleting index entry msn-hp-video-module-tab2[10].htm in index $I30 of file 38490.
    The file reference 0x2100000001c9e8 of index entry msn-hp-video-module[9].htm of index $I30
    with parent 0x965a is not the same as 0x1f00000001c9e8.
    Deleting index entry msn-hp-video-module[9].htm in index $I30 of file 38490.
    The file reference 0xe00000001d430 of index entry IM2944~1.JPG of index $I30
    with parent 0xa4c6 is not the same as 0x900000001d430.
    Deleting index entry IM2944~1.JPG in index $I30 of file 42182.
    The file reference 0xe00000001d430 of index entry ImageCAPGSMU5.jpg of index $I30
    with parent 0xa4c6 is not the same as 0x900000001d430.
    Deleting index entry ImageCAPGSMU5.jpg in index $I30 of file 42182.
    Index entry 13052300_stream of index $I30 in file 0xf485 points to unused file 0x1d414.
    Deleting index entry 13052300_stream in index $I30 of file 62597.
    Index entry 130523~1 of index $I30 in file 0xf485 points to unused file 0x1d414.
    Deleting index entry 130523~1 in index $I30 of file 62597.
    The index bitmap for index $I30 in file 0x1839a is invalid or missing.
    Correcting error in index $I30 for file 99226.
    The index bitmap $I30 is present but there is no corresponding
    index allocation attribute in file 0x1839a.
    Correcting error in index $I30 for file 99226.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff 87 c8 36 4d e3 54 ce 01 ..........6M.T..
    87 c8 36 4d e3 54 ce 01 87 c8 36 4d e3 54 ce 01 ..6M.T....6M.T..
    Sorting index $I30 in file 99226.
    Index entry skype.com of index $I30 in file 0x1ca8c points to unused file 0x1d4be.
    Deleting index entry skype.com in index $I30 of file 117388.
    Index entry preferences.sol of index $I30 in file 0x1d4d5 points to unused file 0x1d4bd.
    Deleting index entry preferences.sol in index $I30 of file 120021.
    Index entry PREFER~1.SOL of index $I30 in file 0x1d4d5 points to unused file 0x1d4bd.
    Deleting index entry PREFER~1.SOL in index $I30 of file 120021.
    208706 index entries processed.

    Index verification completed.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
    Recovering orphaned file MIA6AC~1.CAT (17144) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-sensors-package~31bf3856ad364e35~amd64~th-th~6.1.7601.17514.cat (17144) into directory file 99226.
    Recovering orphaned file MI3E2A~1.CAT (17157) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-sideshow-package~31bf3856ad364e35~amd64~es-es~6.1.7601.17514.cat (17157) into directory file 99226.
    Recovering orphaned file MI64EE~1.MUM (17158) into directory file 99226.
    Recovering orphaned file microsoft-windows-branding-ultimate-client-package~31bf3856ad364e35~amd64~zh-cn~6.1.7601.17514.mum (17158) into directory file 99226.
    Recovering orphaned file AMA685~1.175 (28212) into directory file 99226.
    Recovering orphaned file amd64_netfx-mscordbi_dll_b03f5f7f11d50a3a_6.1.7601.17514_none_fcd566500495183b (28212) into directory file 99226.
    Recovering orphaned file MI6544~1.CAT (47299) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-locationbasic-package~31bf3856ad364e35~amd64~hu-hu~6.1.7601.17514.cat (47299) into directory file 99226.
    Recovering orphaned file SED13D~1.MUM (60998) into directory file 99226.
    Recovering orphaned file server-help-package.cliententerprisen~31bf3856ad364e35~amd64~zh-hk~6.1.7601.17514.mum (60998) into directory file 99226.
    Recovering orphaned file MI7292~1.CAT (99205) into directory file 99226.
    Recovering orphaned file microsoft-windows-printing-foundation-starter-package~31bf3856ad364e35~amd64~es-es~6.1.7601.17514.cat (99205) into directory file 99226.
    Recovering orphaned file MIA1AB~1.CAT (99224) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~ro-ro~6.1.7601.17514.cat (99224) into directory file 99226.
    Recovering orphaned file MIB79E~1.CAT (102476) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~zh-tw~6.1.7601.17514.cat (102476) into directory file 99226.
    Recovering orphaned file MIFC21~1.CAT (102478) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~ja-jp~6.1.7601.17514.cat (102478) into directory file 99226.
    Recovering orphaned file GFOOTE~1.CSS (117173) into directory file 38490.
    Recovering orphaned file gfooter_override[2].css (117173) into directory file 38490.
    Recovering orphaned file star[1].css (117179) into directory file 42119.
    Recovering orphaned file STAR_1~1.CSS (117179) into directory file 42119.
    Recovering orphaned file GFOOTE~3.CSS (117180) into directory file 38490.
    Recovering orphaned file gfooter[2].css (117180) into directory file 38490.
    Recovering orphaned file icon[1].css (117181) into directory file 42137.
    Recover
    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="2013-05-30T00:37:35.000000000Z" />
    <EventRecordID>1190</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Chris-PC</Computer>
    <Security />
    </System>
    <EventData>
    <Data>

    Checking file system on C:
    The type of the file system is NTFS.


    One of your disks needs to be checked for consistency. You
    may cancel the disk check, but it is strongly recommended
    that you continue.
    Windows will now check the disk.

    CHKDSK is verifying files (stage 1 of 3)...
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x10d78 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x104e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 4174.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x4051b for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x3fbf is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 16319.
    Attribute record of type 0x80 and instance tag 0x0 is cross linked
    starting at 0x13d944 for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x0
    in file 0x8e2b is already in use.
    Deleted corrupt attribute list entry
    with type code 128 in file 36395.
    Unable to locate attribute with instance tag 0x0 and segment
    reference 0xe0000000001ad. The expected attribute type is 0x80.
    Deleting corrupt attribute record (128, "")
    from file record segment 429.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x405cb for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xee5b is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 61019.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x24014 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0xf5d9 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 62937.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x41404 for possibly 0x3 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0xf6e0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 63200.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x80ac for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x161ae is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90542.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x1fa20 for possibly 0x7 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x161b2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90546.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x80c0 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x16267 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 90727.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe6ac for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x16646 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 91718.
    Attribute record of type 0xa0 and instance tag 0x2 is cross linked
    starting at 0xbb208 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0xa0 and instance tag 0x2
    in file 0x1839a is already in use.
    Deleted corrupt attribute list entry
    with type code 160 in file 99226.
    Unable to locate attribute with instance tag 0x2 and segment
    reference 0x400000001fcbd. The expected attribute type is 0xa0.
    Deleting corrupt attribute record (160, $I30)
    from file record segment 130237.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x13fa17 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x183aa is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 99242.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x564f9 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x19bff is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 105471.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x405c9 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1aa3e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 109118.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x1fc0b for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1c9f0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 117232.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x8efc for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1ce5a is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118362.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x564fa for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1ce94 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118420.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe2e7 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1cff3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 118771.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x3fe36c for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1d215 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119317.
    Attribute record of type 0x80 and instance tag 0x3 is cross linked
    starting at 0x40bb6d for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x3
    in file 0x1d2a2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119458.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x21de8 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d402 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119810.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3a63bfc for possibly 0x4a clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d4a2 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 119970.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x9df8 for possibly 0x4 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x1d4c7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120007.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0xc9710 for possibly 0x5 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x1d63f is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120383.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0xbf20 for possibly 0x2aa clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x1d6e3 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 120547.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x3fe2e8 for possibly 0x1 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x20d0e is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 134414.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c41a for possibly 0x95 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22aa4 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 141988.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c4af for possibly 0x7d clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22aaa is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 141994.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c52c for possibly 0x18 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22ab0 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142000.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c544 for possibly 0x14 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22ada is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142042.
    Attribute record of type 0x80 and instance tag 0x1 is cross linked
    starting at 0x3b3c558 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x1
    in file 0x22bc7 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 142279.
    Attribute record of type 0x80 and instance tag 0x4 is cross linked
    starting at 0x34a07 for possibly 0x2 clusters.
    Some clusters occupied by attribute of type 0x80 and instance tag 0x4
    in file 0x26046 is already in use.
    Deleting corrupt attribute record (128, "")
    from file record segment 155718.
    161280 file records processed.

    File verification completed.
    Deleting orphan file record segment 429.
    279 large file records processed.

    0 bad file records processed.

    0 EA records processed.

    60 reparse records processed.

    CHKDSK is verifying indexes (stage 2 of 3)...
    Index entry MS6F25~1.HTM of index $I30 in file 0x965a points to unused file 0x1c9e9.
    Deleting index entry MS6F25~1.HTM in index $I30 of file 38490.
    The file reference 0x2100000001c9e8 of index entry MSBB5A~1.HTM of index $I30
    with parent 0x965a is not the same as 0x1f00000001c9e8.
    Deleting index entry MSBB5A~1.HTM in index $I30 of file 38490.
    Index entry msn-hp-video-module-tab2[10].htm of index $I30 in file 0x965a points to unused file 0x1c9e9.
    Deleting index entry msn-hp-video-module-tab2[10].htm in index $I30 of file 38490.
    The file reference 0x2100000001c9e8 of index entry msn-hp-video-module[9].htm of index $I30
    with parent 0x965a is not the same as 0x1f00000001c9e8.
    Deleting index entry msn-hp-video-module[9].htm in index $I30 of file 38490.
    The file reference 0xe00000001d430 of index entry IM2944~1.JPG of index $I30
    with parent 0xa4c6 is not the same as 0x900000001d430.
    Deleting index entry IM2944~1.JPG in index $I30 of file 42182.
    The file reference 0xe00000001d430 of index entry ImageCAPGSMU5.jpg of index $I30
    with parent 0xa4c6 is not the same as 0x900000001d430.
    Deleting index entry ImageCAPGSMU5.jpg in index $I30 of file 42182.
    Index entry 13052300_stream of index $I30 in file 0xf485 points to unused file 0x1d414.
    Deleting index entry 13052300_stream in index $I30 of file 62597.
    Index entry 130523~1 of index $I30 in file 0xf485 points to unused file 0x1d414.
    Deleting index entry 130523~1 in index $I30 of file 62597.
    The index bitmap for index $I30 in file 0x1839a is invalid or missing.
    Correcting error in index $I30 for file 99226.
    The index bitmap $I30 is present but there is no corresponding
    index allocation attribute in file 0x1839a.
    Correcting error in index $I30 for file 99226.
    The down pointer of current index entry with length 0x18 is invalid.
    00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
    ff ff ff ff ff ff ff ff 87 c8 36 4d e3 54 ce 01 ..........6M.T..
    87 c8 36 4d e3 54 ce 01 87 c8 36 4d e3 54 ce 01 ..6M.T....6M.T..
    Sorting index $I30 in file 99226.
    Index entry skype.com of index $I30 in file 0x1ca8c points to unused file 0x1d4be.
    Deleting index entry skype.com in index $I30 of file 117388.
    Index entry preferences.sol of index $I30 in file 0x1d4d5 points to unused file 0x1d4bd.
    Deleting index entry preferences.sol in index $I30 of file 120021.
    Index entry PREFER~1.SOL of index $I30 in file 0x1d4d5 points to unused file 0x1d4bd.
    Deleting index entry PREFER~1.SOL in index $I30 of file 120021.
    208706 index entries processed.

    Index verification completed.
    CHKDSK is scanning unindexed files for reconnect to their original directory.
    Recovering orphaned file MIA6AC~1.CAT (17144) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-sensors-package~31bf3856ad364e35~amd64~th-th~6.1.7601.17514.cat (17144) into directory file 99226.
    Recovering orphaned file MI3E2A~1.CAT (17157) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-sideshow-package~31bf3856ad364e35~amd64~es-es~6.1.7601.17514.cat (17157) into directory file 99226.
    Recovering orphaned file MI64EE~1.MUM (17158) into directory file 99226.
    Recovering orphaned file microsoft-windows-branding-ultimate-client-package~31bf3856ad364e35~amd64~zh-cn~6.1.7601.17514.mum (17158) into directory file 99226.
    Recovering orphaned file AMA685~1.175 (28212) into directory file 99226.
    Recovering orphaned file amd64_netfx-mscordbi_dll_b03f5f7f11d50a3a_6.1.7601.17514_none_fcd566500495183b (28212) into directory file 99226.
    Recovering orphaned file MI6544~1.CAT (47299) into directory file 99226.
    Recovering orphaned file microsoft-windows-mobilepc-client-locationbasic-package~31bf3856ad364e35~amd64~hu-hu~6.1.7601.17514.cat (47299) into directory file 99226.
    Recovering orphaned file SED13D~1.MUM (60998) into directory file 99226.
    Recovering orphaned file server-help-package.cliententerprisen~31bf3856ad364e35~amd64~zh-hk~6.1.7601.17514.mum (60998) into directory file 99226.
    Recovering orphaned file MI7292~1.CAT (99205) into directory file 99226.
    Recovering orphaned file microsoft-windows-printing-foundation-starter-package~31bf3856ad364e35~amd64~es-es~6.1.7601.17514.cat (99205) into directory file 99226.
    Recovering orphaned file MIA1AB~1.CAT (99224) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~ro-ro~6.1.7601.17514.cat (99224) into directory file 99226.
    Recovering orphaned file MIB79E~1.CAT (102476) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~zh-tw~6.1.7601.17514.cat (102476) into directory file 99226.
    Recovering orphaned file MIFC21~1.CAT (102478) into directory file 99226.
    Recovering orphaned file microsoft-windows-photobasicpackage~31bf3856ad364e35~amd64~ja-jp~6.1.7601.17514.cat (102478) into directory file 99226.
    Recovering orphaned file GFOOTE~1.CSS (117173) into directory file 38490.
    Recovering orphaned file gfooter_override[2].css (117173) into directory file 38490.
    Recovering orphaned file star[1].css (117179) into directory file 42119.
    Recovering orphaned file STAR_1~1.CSS (117179) into directory file 42119.
    Recovering orphaned file GFOOTE~3.CSS (117180) into directory file 38490.
    Recovering orphaned file gfooter[2].css (117180) into directory file 38490.
    Recovering orphaned file icon[1].css (117181) into directory file 42137.
    Recover</Data>
    </EventData>
    </Event>

  11. #30
    Member Spyware Fighter DonnaB's Avatar
    Join Date
    Apr 2009
    Location
    Illiana, Ill. USA
    Posts
    3,524
    Points
    563

    Default

    Hi Number7,

    I am sorry for the delay.

    Is this the original OS (operating system) that came pre-installed on this computer?

    If you think you might be infected with malware or have recently cleansed your computer of malware without the help of an expert, please read and follow the instructions in How to Start Removing Viruses and Spyware from your Computer. This can alleviate time consumed in trouble shooting your current computer problems.

    If your problem is solved, here's how to say thanks!

    Very proud parent of a U.S. Navy "CB"



    "People may forget what you say,
    People may forget what you did,
    but People will never forget how you made them feel!"

Page 3 of 5 FirstFirst 12345 LastLast