Windows 10 Display shifted to the right so right part of display is on the left of the screen, Multiple DCOM errors, system restore and repair failed.

  • Thread starter Thread starter broken katana
  • Start date Start date
B

broken katana

Hello everyone, I know my subject is listing many separate issues but I think they might be connected because they all started one after the other, so listing everything that's been going on might give people a clue as to what's wrong.


Last night I turned on my laptop and everything went smoothly. I pass the sign-in screen and as soon as my desktop loads, the screen goes black for a second and when it's back on, the display has shifted to the right, with the right part of it appearing on the left side of the screen. The mouse would move accordingly - if I wanted to get to the right side of the screen I would have to pass it through the far right end to get it to appear from the left. Also, in some parts the icons and letters were appearing broken and glitchy. Dropbox - DSC_0137_2.jpg I took pictures with my phone because in print screens the display actually appeared normal.



I restarted the laptop and then the sign-in screen also became like this Dropbox - DSC_0134.JPG


When I checked the event viewer and the following errors popped up Dropbox - Screenshot 2018-07-08 00.44.13.png you can see here, like I mentioned, that in the print screen the display actually appears to be normal.


I decided to do a system restore then, only to have it get stuck at initializing for around half an hour. During this time, the display turned from this Dropbox - DSC_0138_2.jpg to this Dropbox - DSC_0139_2.jpg


I force shutdown the laptop and this time when it restarted it beeped around 10 times, I didn't manage to count properly because I was taken aback, and then went into blue screen. When I turned the laptop on again I got the automatic repair screen from which I tried system restore again only to have it fail with the unspecified error 0x80070003. Cue another restart, this time it failed to get into windows, no beeping no nothing just a broken blue screen. I unplug the power cord and leave it for a couple of hours before trying to turn it back on again. Back to the automatic repair screen and this time I chose to do a repair, which also failed.


I managed to get into safe mode today and it looks something like this Dropbox - Screenshot 2018-07-08 16.56.44.png the screen is not shifted anymore but I don't know if this issue got fixed since I can't get into normal mode on windows


I checked my error logs and there's many DCOM errors since this whole issue started:


DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server:
{DD522ACC-F821-461A-A407-50B198B896DC}



DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server:
{E48EDA45-43C6-48E0-9323-A7B2067D9CD5}



DCOM got error "1084" attempting to start the service BITS with arguments "Unavailable" in order to run the server:
{4991D34B-80A1-4291-83B6-3328366B9097}



DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server:
{581333F6-28DB-41BE-BC7A-FF201F12F3F6}



DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server:
Windows.Internal.Security.Authentication.Web.TokenBrokerInternal


DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server:
Windows.Internal.CapabilityAccess.CapabilityAccess


DCOM got error "1084" attempting to start the service lfsvc with arguments "Unavailable" in order to run the server:
{08D9DFDF-C6F7-404A-A20F-66EEC0A609CD}


DCOM got error "1084" attempting to start the service stisvc with arguments "Unavailable" in order to run the server:
{A1F4E726-8CF1-11D1-BF92-0060081ED811}



DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server:
{1BE1F766-5536-11D1-B726-00C04FB926AF}



DCOM got error "1084" attempting to start the service TermService with arguments "Unavailable" in order to run the server:
{F9A874B6-F8A8-4D73-B5A8-AB610816828B}


There were thousands of the above errors that were even popping up as I was in safe mode and then I found some others:



Crash dump initialization failed!



The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user BEL\user SID (S-1-5-21-3516631768-3393012715-1431425722-1000) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.



The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.



So, I'm at a loss of what to try to fix because I have no idea where the problem starts. At first I thought it was an issue with the GPU drivers but after the beeps and blue screen I assumed it was a hardware issue. BUT lots of software issues seem to have popped up along with it?? Currently, I'm also afraid to restart because last I tried, windows wouldn't boot in normal mode and I might not be able to get back into safe mode because I don't have the time to press F8 fast enough so I don't want to end up forcing shut downs and restarting in order to get into safe mode.

Sorry for the long post and thanks in advance to anyone who takes the time to read all this!


Specs:

OS Name Microsoft Windows 10 Home
Version 10.0.17134 Build 17134
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Hewlett-Packard
System Model HP ENVY 17 Notebook PC
System Type x64-based PC
System SKU A2Q34EA#ABB
Processor Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz, 2195 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Hewlett-Packard F.09, 1/22/2013
SMBIOS Version 2.7
Embedded Controller Version 17.36
BIOS Mode Legacy
BaseBoard Manufacturer Hewlett-Packard
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Mobile
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Hardware Abstraction Layer Version = "10.0.17134.1"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.98 GB
Available Physical Memory 4.66 GB
Total Virtual Memory 9.98 GB
Available Virtual Memory 6.36 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

Continue reading...
 
Back
Top