KB2813347

Discussion in 'Windows 7' started by piercekalton, Nov 22, 2018.

  1. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
  2. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    2,628
    2,280
    90
    Can happen sometimes if an update supersede chain is broken (MS have done themselves in the past with their Update Cleanup, by accident). WU would, in this case, only download and apply the update metadata to restore the chain, not the actual update.

    Alternatively, changing languages can cause old updates to re-appear, in order to get the correct MUI files for the new language. They are pretty stable and might not be updated for ages, so the offered updates might be... old.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    ok I'll do it then. it's remote desktop anyway which I'm not currently using.

    edit: I did a manual large file cleanup so that probably has something to do with it
     
  4. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    #4 piercekalton, Nov 23, 2018
    Last edited: Nov 23, 2018
    (OP)
    GAH!

    probably shouldn't have. could also be unrelated.

    can anyone decipher this?

    Code:
    Problem signature:
      Problem Event Name:   BlueScreen
      OS Version:   6.1.7601.2.1.0.256.1
      Locale ID:   1033
    
    Additional information about the problem:
      BCCode:   1a
      BCP1:   0000000000000403
      BCP2:   FFFFF6800009BE48
      BCP3:   D90000002793A967
      BCP4:   FFFFF68000048048
      OS Version:   6_1_7601
      Service Pack:   1_0
      Product:   256_1
    
    Files that help describe the problem:
      C:\Windows\Minidump\112318-15662-01.dmp
      C:\Users\xx\AppData\Local\Temp\WER-29187-0.sysdata.xml
    
    edit: never had a BSOD on this before.

    edit: I hope it isn't hardware related. I could system restore but I feel like it will just happen again.
     
  5. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    first I'm going to do memtest.

    then chkdsk.

    let me know if there's anything obvious.
     
  6. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    669
    940
    30
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,880
    22,899
    340
    #8 Enthousiast, Nov 23, 2018
    Last edited: Nov 23, 2018
    Did you by any chance use a tool called rebase?

    And you can run this in an elevated cmd to see what sfc found:
    Code:
    findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
    
     
  8. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    I did the memtest and it failed so now I'm back to basics with the box before I try any kind of OS repair. I'll report back. working 3 systems right now (all my own)

    I'm glad this happened today because I have nothing else to do.
     
  9. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    no never heard of it. I assume it is third party.
     
  10. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    669
    940
    30
    I had a similar problem a couple of years ago with my old Lenovo T400 Thinkpad. If I remember correctly, the error code in the BSOD translated to "Memory page fault in non-paging area". That means it's in the machine's physical memory.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Joe C

    Joe C MDL Guru

    Jan 12, 2012
    2,667
    1,482
    90
    I've seen hard drives with bad sectors throw that error too
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    update: memory test failed so I did partial hardware cleaning and re-sat the RAM. now memtest+ 86 5.01 is working (it had red failures, it doesn't now)

    there was so much dust, it needed a cancer treatment. problem is I probably inhaled a bunch of crap in the process.

    I'm not worried about the drives so much but I am worried about the file system. so next will be chkdsk. I'll use the Server 2019 DVD because they probably updated chkdsk without telling anyone or it is buried in some obscure MS document.

    I advise everyone here to ask for bulk air dusters for Christmas. I used a whole can. (and yes I know how to use it, short bursts)

    PS: what does it mean if it sounds like there is sand in a hard drive?
     
  13. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    what is the word on using MHDD with a hybrid SSD? maybe the SSD has bad sectors. CRAP lol. this was supposed to be my day off.
     
  14. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    669
    940
    30
    Glad to hear that your current memory passed memtest86+ and you didn't have to buy any new DIMM's. I tried cleaning and re-seating the DIMM's in my Lenovo to no avail. The error still occurred at the exact same memory address.

    As far as your HDD making noises, some are normal and some are not. A whirring or whining noise is normal during system boot, this is the drive motor spinning up to speed. During intense write activity, like when you're defragging the file system, it's normal to hear a faint sound similar to corn popping. And a hard clicking sound is normal during sleep or shutdown, it's the read/write heads parking themselves. A grinding sound isn't normal. It might be a good idea to examine the drive's S.M.A.R.T. data or run the OEM's HDD diagnostic software to see if there's a problem.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    7 sparse file record segments.
    1382 reparse records.

    do I dare a boot? hmm..
     
  16. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    good info on the memory. when I say the HDD sounds like sand is in it I mean when I physically take it out and gently shake it near my ear.

    ALSO AND IM SORRY. that was not the physical disk I was talking about with the chkdsk. it was just one of the storage disks.
     
  17. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    669
    940
    30
    You'll have to boot the system in order to run chkdsk. Don't forget to include the /f option to fix the filesystem in case there are errors. ( chkdsk /f c: )
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. piercekalton

    piercekalton MDL Senior Member

    Apr 2, 2010
    263
    11
    10
    that's what I did /f. see no reason for the /r yet
     
  19. John Sutherland

    John Sutherland MDL Addicted

    Oct 15, 2014
    669
    940
    30
    O.K. I guess the next step would be to boot into Safe Mode and run sfc /scannow three times in a row. Hopefully you'll see the message "Windows found no integrity violations" after the third pass.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...