-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Archived Topics
- Desktops (Archived)
- Re: Very Slow Startup
Create an account on the HP Community to personalize your profile and ask a question
05-22-2017 03:37 PM
> I guess we can't go by the Short Tests all the time?
Yes, you can.
For the test to run in a "short" length of time, it cannot possibly be as "thorough" as the "long" test.
Think of a matrix of possible outcomes:
+---------------+-----------------+----------------+
| DATA | Short test | Long test |
+---------------+-----------------+----------------+
| | | |
| Disk is good | Pass | Pass |
| | | |
+---------------+-----------------+----------------+
| | | |
| Disk is bad | Pass | Fail |
| | | |
| | | |
+---------------+-----------------+----------------+
| | | |
| Disk is bad | Fail | Fail |
| | | |
+---------------+-----------------+----------------+
| | | |
| Disk is bad | Fail | Pass |
| | | |
+---------------+-----------------+----------------+
I doubt that the bottom row is a possible result.
To make an analogy, if you have an automobile tire that is slowly leaking air, would you drive in the opposite direction, to do some shopping, and then drive to the tire-repair shop, or would you drive straight to the shop, to increase your chances of getting there before the tire goes flat?
Similarly, if the "short" test has indicated "imminent failure", what would you do first:
* make a backup of your files,
* "clone" the disk-drive (thus making a copy of your files),
* run a "long" test, or run some other extensive third-party testing software that really "works" the disk-drive, to prove that it is "failing"
???
> I also don't think it is the HDD ..
Turn the computer off.
Disconnect from the Internet.
Turn the computer on.
If it still takes over 2 minutes to boot, then I think that the most-likely cause is a failing disk-drive.
[Just a few days ago, a friend's laptop took over 30 minutes to boot, and, according to Event Viewer, the cause was bad sectors on the disk-drive, associated with a few files that Windows reads during startup, that were taking over 2 minutes to read. We've ordered a replacement disk-drive, and will "clone" the current drive, ASAP.]
05-23-2017 09:26 AM
Let me post this for now, as it looks to be the same as I would see in EVENTVIEWER. I do that also, but maybe this will tell us what is going on, I googled it to no avail. One thing that was wrong was the OS was not Activated...I must have typed in the Product Key Wrong, it's Activated now. I almost think the Updates did not go as usual, when I do a Clean Install, but when I check for updates, it runs and then says all up to date. There are of course Optional Updates, and I accepted some of them, but there are still quite a few that seemed to be of no use to me.
5/23/2017 1:12 PM Windows Error Reporting Fault bucket , type 0
Event Name: PnPRequestAdditionalSoftware
 Response: Not available
Cab Id: 0

Problem signature:
 P1: x64
P2: HID\VID_046D&PID_C52B&REV_1203&MI_01&Col03
P3: 6.1.1.0
P4: 0409
P5: input.inf
 P6: *
P7: 
P8: 
P9: 
 P10: 

Attached files:

 These files may be available here:
C:\Users\Public.Public-PC\AppData\Local\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_5d713ea0629e31fa7d55ebe27c8f7f8cc6d4794_0ec5ccc0

 Analysis symbol: 
Rechecking for solution: 0
Report Id: 64f13b04-3fb9-11e7-bf2d-e0cb4e9d4eab
Report Status: 4
05-23-2017 09:50 AM
I did not understand exactly how to get info from Event Viewer so did the best I could. I did not see how to sort by "Performance" so went to "Windows Logs">"System" and this is what I see, looks to be the Main problem is Nvida Maybe? I went through System Logs and was seeing Errors, so will post them and hope they are helpful. See some DNS Stuff also, but I wonder if all this is due to the Nvidia Driver being the MS Default, that was Installed During Clean Install with Retail Image? Thanks for your time!
Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 5/23/2017 10:45:26 AM Event ID: 10016 Task Category: None Level: Error Keywords: Classic User: SYSTEM Computer: Public-PC Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" /> <EventID Qualifiers="49152">10016</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2017-05-23T14:45:26.000000000Z" /> <EventRecordID>3980</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>Public-PC</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="param1">application-specific</Data> <Data Name="param2">Local</Data> <Data Name="param3">Launch</Data> <Data Name="param4">{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}</Data> <Data Name="param5">{344ED43D-D086-4961-86A6-1106F4ACAD9B}</Data> <Data Name="param6">NT AUTHORITY</Data> <Data Name="param7">SYSTEM</Data> <Data Name="param8">S-1-5-18</Data> <Data Name="param9">LocalHost (Using LRPC)</Data> </EventData> </Event> ----------------------------------------------------------------------- Log Name: System Source: Service Control Manager Date: 5/23/2017 10:41:47 AM Event ID: 7016 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Public-PC Description: The NVIDIA Display Driver Service service has reported an invalid current state 32. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7016</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2017-05-23T14:41:47.504800000Z" /> <EventRecordID>3862</EventRecordID> <Correlation /> <Execution ProcessID="528" ThreadID="1476" /> <Channel>System</Channel> <Computer>Public-PC</Computer> <Security /> </System> <EventData> <Data Name="param1">NVIDIA Display Driver Service</Data> <Data Name="param2">32</Data> </EventData> </Event> ---------------------------------------------------------------- Log Name: System Source: Microsoft-Windows-DNS-Client Date: 5/23/2017 9:35:54 AM Event ID: 1014 Task Category: None Level: Warning Keywords: User: NETWORK SERVICE Computer: Public-PC Description: Name resolution for the name ssum.casalemedia.com timed out after none of the configured DNS servers responded. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" /> <EventID>1014</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2017-05-23T13:35:54.741000000Z" /> <EventRecordID>3687</EventRecordID> <Correlation /> <Execution ProcessID="1040" ThreadID="4132" /> <Channel>System</Channel> <Computer>Public-PC</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> <Data Name="QueryName">ssum.casalemedia.com</Data> <Data Name="AddressLength">28</Data> <Data Name="Address">170000350000000020010558FEED0000000000000000000100000000</Data> </EventData> </Event> ------------------------------------------- Log Name: System Source: Microsoft-Windows-DNS-Client Date: 5/23/2017 9:35:54 AM Event ID: 1014 Task Category: None Level: Warning Keywords: User: NETWORK SERVICE Computer: Public-PC Description: Name resolution for the name ssum.casalemedia.com timed out after none of the configured DNS servers responded. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" /> <EventID>1014</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2017-05-23T13:35:54.741000000Z" /> <EventRecordID>3687</EventRecordID> <Correlation /> <Execution ProcessID="1040" ThreadID="4132" /> <Channel>System</Channel> <Computer>Public-PC</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> <Data Name="QueryName">ssum.casalemedia.com</Data> <Data Name="AddressLength">28</Data> <Data Name="Address">170000350000000020010558FEED0000000000000000000100000000</Data> </EventData> </Event> -------------------------------------- Log Name: System Source: Microsoft-Windows-DNS-Client Date: 5/17/2017 11:07:53 AM Event ID: 1014 Task Category: None Level: Warning Keywords: User: NETWORK SERVICE Computer: Public-PC Description: Name resolution for the name sf.symcd.com timed out after none of the configured DNS servers responded. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" /> <EventID>1014</EventID> <Version>0</Version> <Level>3</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2017-05-17T15:07:53.711500000Z" /> <EventRecordID>1909</EventRecordID> <Correlation /> <Execution ProcessID="932" ThreadID="5060" /> <Channel>System</Channel> <Computer>Public-PC</Computer> <Security UserID="S-1-5-20" /> </System> <EventData> <Data Name="QueryName">sf.symcd.com</Data> <Data Name="AddressLength">28</Data> <Data Name="Address">170000350000000020010558FEED0000000000000000000100000000</Data> </EventData> </Event>
05-23-2017 10:01 AM
That's a lot of text to parse.
Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 5/23/2017 9:35:54 AM
Event ID: 1014
Level: Warning
User: NETWORK SERVICE
Computer: Public-PC
Description:
Name resolution for the name ssum.casalemedia.com timed out after none of the configured DNS servers responded.
Yes, this is a "warning", but it just means that your web-browser could not access a web-site that downloads "advertisements", and inserts them onto a specific web-page for you to view.
Their "loss", not yours, when your computer could not display their advertisement.
05-23-2017 05:09 PM
I found some success installing drivers, only after running sfc, chkdsk and looking at all the logs. I knew the Drive was good, just had a feeling after seeing many bad drives, this one did not act bad.
I installed:
1. SATA Hard Disk Drive Firmware Update, this appeared not to install, as it said something about not being compatible with my system.
2. Original NVIDIA Serial ATA Controller Drive, this one seemed to fix the booting issue, but, when this one was done, upon reboot, number one above was asking for a reboot also? weird?
3. Original NVIDIA Graphics Driver: Installed this one also but it looks worse now? but at least the original problem is fixed.
So the HP Support Assistant would have fixed the issue, but don't want all that HP Junk on my computer?
Thanks!
05-23-2017 05:26 PM
I'm still lacking this Device Driver in Device Manager, can you guys help me with this one? I looked around but cannot find the driver for this. I was hoping the drivers I installed would fix this but it did not.
Coprocessor Driver Details D Manager
PCI\VEN_10DE&DEV_0753&SUBSYS_2A9E103C&REV_A2
PCI\VEN_10DE&DEV_0753&SUBSYS_2A9E103C
PCI\VEN_10DE&DEV_0753&CC_0B4000
PCI\VEN_10DE&DEV_0753&CC_0B40
05-23-2017 10:39 PM
A Google-search for: PCI\VEN_10DE&DEV_0753&SUBSYS_2A9E103C
suggested a solved problem on this forum.
See:
05-23-2017 10:43 PM
> when this one was done, upon reboot, number one above was asking for a reboot also? weird?
Not weird at all.
Update #1 must be applied after #2 -- #2 is a "prerequisite" for #1.
Try to tell a three-year-old boy to "put on your underwear before putting on your pants".
He just does not understand "prerequisites".
05-24-2017 06:21 AM - edited 05-24-2017 06:23 AM
@mdklassen wrote:> when this one was done, upon reboot, number one above was asking for a reboot also? weird?
Not weird at all.
Update #1 must be applied after #2 -- #2 is a "prerequisite" for #1.
Try to tell a three-year-old boy to "put on your underwear before putting on your pants".
He just does not understand "prerequisites".
Are you calling me a three year old? ha ha, just kidding. I did think of this After my post LOL, the Prerequisite thing, I'm a little slow with these things still. Very happy though, now have 53.xx Second Boot time, good enough. The weird part was, it did not seem to install, but it actually did. It told me that it would not install, so I moved on to the next lol.
The link for that driver is not accessible to me, did you try it?
Thanks, pcpunk
05-24-2017 09:27 AM - last edited on 08-15-2018 03:33 AM by Chao_L
> Are you calling me a three year old? ha ha, just kidding.
If I was offered a chance to "restart" as a three-year-old, I might take it.
> The link for that driver is not accessible to me, did you try it?
Yes, before I originally posted, and again, seconds ago.
Take these 2 pieces, and "glue" them together:
and see if it works for you, if "clicking" my original hyperlink does not work for you.
Didn't find what you were looking for? Ask the community