Surface Pro 4 Discussion Thread

Discussion in 'Microsoft' started by spinedoc77, Oct 6, 2015.

Thread Status:
Not open for further replies.
  1. jyan_osu

    jyan_osu Scribbler - Standard Member

    Messages:
    407
    Likes Received:
    115
    Trophy Points:
    56
    Oh yes, themes with a lot of graphics and code to adjust where everything goes and looks can also cause CPU processes.
     
  2. dstrauss

    dstrauss Comic Relief Senior Member

    Messages:
    11,138
    Likes Received:
    9,743
    Trophy Points:
    331
    Will give that a try.
     
    jnjroach likes this.
  3. mgerbasio

    mgerbasio Scribbler - Standard Member

    Messages:
    355
    Likes Received:
    134
    Trophy Points:
    56
    A lot of my problems cleared up after I found corrupt files with sfc /scannow. MS told me it was a hard drive failure but even a new SP4 had the same issues. Had to run dism with a system image to clear it. Now, my SP4 isn't perfect, I still have issues but they're infrequent.
     
  4. mertzi

    mertzi Pen Pal - Newbie

    Messages:
    43
    Likes Received:
    5
    Trophy Points:
    16
    My current SP4 (third) has two, the first had one. I'm going to replace it, just have too much else to do ATM.

    I had to go through three Nexus 5 in 2014 to get one without. LCD truly is amazing.
     
  5. dellaster

    dellaster Non-Creative Plebe Senior Member

    Messages:
    1,552
    Likes Received:
    1,467
    Trophy Points:
    181
    Yeah, I was thinking that same thought right up until till the moment I saw the stuck pixel on my SP4 a few months ago. I think the last time I had a stuck/dead pixel was around 2006 with a Dell desktop monitor and I had to live with it 'cause back then they were allowed in writing to have a few of those (how many depended on the manufacturer and model).
     
  6. Steve S

    Steve S Pen Pro - Senior Member Super Moderator

    Messages:
    8,328
    Likes Received:
    3,837
    Trophy Points:
    331
  7. ElectronicFur

    ElectronicFur Pen Pal - Newbie

    Messages:
    93
    Likes Received:
    12
    Trophy Points:
    16
    For those of you who have reinstalled Windows 10 from an image, what does

    Code:
    sfc /verifyonly
    report? With the /verifyonly option it doesn't make any changes to your PC, it just reports.

    When I ran it on my new SP4, which is as it came from MS, but with all Windows updates installed, it still found integrity violations.
    It made me a bit dubious on how good the sfc tool is, and whether they really are integrity violations, or not. But perhaps it shows how crap MS Windows updates are.

    And how are those who followed the sfc instructions at https://www.reddit.com/r/Surface/comments/49g46p/i_am_going_to_make_one_post_to_convey_a_fix_for/ getting on? I kind of held of running it when Spinedoc reported the fix seemed to be only temporary. Had hoped MS would have fixed the issue by now, but as I'm still getting crashes on wakeup from sleep, I'm thinking of doing the sfc fixes.
     
  8. metalsiren

    metalsiren Scribbler - Standard Member Senior Member

    Messages:
    856
    Likes Received:
    262
    Trophy Points:
    76
    yea @dstrauss , I am in the same boat... I love it ... and then WTF moment and then I love it, rinse and repeat.
     
  9. dstrauss

    dstrauss Comic Relief Senior Member

    Messages:
    11,138
    Likes Received:
    9,743
    Trophy Points:
    331
    OK - has been 30 hours (+/-) since restore when I ran sfc - Great - now what:

    Windows Resource Protection found integrity violations. Details are included
    in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in
    offline servicing scenarios.


    Damned if I can make out the gibberish in the CBS.log (reading it in Word is giving me a headache:

    2016-03-30 23:50:37, Info CBS TI: --- Initializing Trusted Installer ---
    2016-03-30 23:50:37, Info CBS TI: Last boot time: 2016-03-30 21:00:56.585
    2016-03-30 23:50:37, Info CBS Starting TrustedInstaller initialization.
    2016-03-30 23:50:37, Info CBS Ending TrustedInstaller initialization.
    2016-03-30 23:50:37, Info CBS Starting the TrustedInstaller main loop.
    2016-03-30 23:50:37, Info CBS TrustedInstaller service starts successfully.
    2016-03-30 23:50:37, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
    2016-03-30 23:50:37, Info CBS Startup processing thread terminated normally
    2016-03-30 23:50:37, Info CBS Starting TiWorker initialization.
    2016-03-30 23:50:37, Info CBS Ending TiWorker initialization.
    2016-03-30 23:50:37, Info CBS Starting the TiWorker main loop.
    2016-03-30 23:50:37, Info CBS TiWorker starts successfully.
    2016-03-30 23:50:37, Info CBS Universal Time is: 2016-03-31 04:50:37.859
    2016-03-30 23:50:37, Info CBS Loaded Servicing Stack v10.0.10586.168 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.168_none_76587b40265ca57e\cbscore.dll
    2016-03-30 23:50:37, Info CSI 00000001@2016/3/31:04:50:37.874 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe271e4699 @0x7ffe27511248 @0x7ffe2752150b @0x7ff73f342ee0 @0x7ff73f3438e1 @0x7ffe4edfd533)
    2016-03-30 23:50:37, Info CBS NonStart: Set pending store consistency check.
    2016-03-30 23:50:37, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy1/Windows/System32/config/SOFTWARE' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SOFTWARE'.
    2016-03-30 23:50:37, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy1/Windows/System32/config/SYSTEM' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SYSTEM'.
    2016-03-30 23:50:37, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}GLOBALROOT/Device/HarddiskVolumeShadowCopy1/Windows/System32/config/SECURITY' from path '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Windows\System32\config\SECURITY'.

    Is it terminal (pun intended)...


    Well, since the image reinstall it is generally more quiet (the fans come on about 25-50% of the time now) but the random shutdowns haven't returned (yet - knocking on wood) and sleep/resume has been rock solid.

    But then I ran @ElectronicFur requested test, and now I wonder if I am fubar again...

    SOME GOOD NEWS - made it through a one hour client meeting without the pen crapping out!
     
    Last edited: Apr 1, 2016
  10. dellaster

    dellaster Non-Creative Plebe Senior Member

    Messages:
    1,552
    Likes Received:
    1,467
    Trophy Points:
    181
    Nope. I discovered the stuck pixel while attempting--and failing--to repair the SP4 after config file corruption gave me the black screen on boot. Neither touch nor USB keyboard would work and I had no type cover (never used it for my previous SP2, so skipped it this time). Being a wuss as far as masochism goes, I gave up in frustration and sent it back to MS.

    If it was *just* the pixel I would have tried to unstick it.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page