Long black screen delay after "Welcome!" message HELP!

Itbankrock

Honorable
May 31, 2013
6
0
10,510
0
Hey guys I'm having problems with my Windows 7 (Ultimate SP1 64-bit). It's so weird that at my specs this is happening for almost months now. This has never happened to me before, my old pc even starts up faster than this! Please HELP ME! My pc is already 2 years old I didn't do any reformats... but I did do full Anti-Virus scan (I use Microsoft Security Essentials), Defrags, Cleanups, Regsitry cleanups (CCleaner)

Here's a YouTube video about it (skip to 1:02 if you wanna see the problem)
http://youtu.be/f4E9B-c1XTE

[flash=450,253]http://www.youtube.com/v/f4E9B-c1XTE[/flash]

My PC Specs:
Date bought: March 2011
Operating System: Windows 7 Ultimate SP1 64-bit
PSU: Aerocool 600W
Motherboard: GIGABYTE P67A-UD3-B3 (BIOS ver. F9 2012 build)
Processor: Intel® Core™ i7 2600k Quad Core CPU 3.40GHz
Graphics Card: MSI N550GTX-Ti Cyclone II 1GB GDDR5
RAM: Dual Kingston 4GB (8GB) 1333MHz DDR3
Hard Disk Drive: Western digital 1TB/ Blue SATA 3 HDD
 

TheMentalist

Honorable
May 13, 2013
1,458
0
11,960
372
Okay, you can try these first, also can you tell us whats happening in event viewer?
> Make a new user profile and log in with that, if the problem disappears, its your old user profile then
> Update your display drivers, sometimes old or partly corrupt drivers may cause issues while loading
> Clean up your registry, your user profile may be loading some entries which are bad
 

Itbankrock

Honorable
May 31, 2013
6
0
10,510
0


Uhm, I don't know, noob here :) What should I tell you about my Event Viewer? (Yes I know how to open it).
 

HEXiT

Champion
Herald
clear out your startup items only leaving your mouse, keyboard,gfx and antivirus apps to load. clear out your restor points. keep the oldest 1 but the rest can go
then clean the registry. ccleaner will do the job well enough. repeat clean till you get no more errors.
reboot.
also check the admin tools event logs in application and system and note down any errors that coincide with the last boot.
service control errors can be ignored for now as they just complain about disabled or manual start services already running.
other errors you can ignore. error 41 it just means your pc has recovered from an off and that its been logged. it wont tell you why so can be ignored.











 

noidea_77

Distinguished

Just scan the windows / system protocol for error and warnings while the the pc starts. The time stamp helps to identify the black screen period.
 

Itbankrock

Honorable
May 31, 2013
6
0
10,510
0


Here's the XML of my Events (I only imported the ERRORS, CRITICALS AND WARNINGS)

http://www.mediafire.com/?b6gqhkgd3jsbnvy

Import it to your Event Viewer and tell me what to do :) Thanks in advance!
 

Itbankrock

Honorable
May 31, 2013
6
0
10,510
0
Alright if you guys are lazy to import it... I got lots of "WARNINGS" "CRITICALS" ERRORS"

Some of them I found to have these words "Diagnostics-Performance, Boot Performance Monitoring"

BUT I FOUND THIS:
It happened last May 18, 2013
CRITICAL
Windows has started up:
Boot Duration : 161819ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎05‎-‎18T03:24:49.671600300Z

Full details:

Log Name: Microsoft-Windows-Diagnostics-Performance/Operational
Source: Microsoft-Windows-Diagnostics-Performance
Date: 5/18/2013 11:28:00 AM
Event ID: 100
Task Category: Boot Performance Monitoring
Level: Critical
Keywords: Event Log
User: LOCAL SERVICE
Computer: Santiago
Description:
Windows has started up:
Boot Duration : 161819ms
IsDegradation : false
Incident Time (UTC) : ‎2013‎-‎05‎-‎18T03:24:49.671600300Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
<EventID>100</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>4002</Task>
<Opcode>34</Opcode>
<Keywords>0x8000000000010000</Keywords>
<TimeCreated SystemTime="2013-05-18T03:28:00.580734400Z" />
<EventRecordID>4464</EventRecordID>
<Correlation ActivityID="{03AC3C60-F800-0004-E4D0-FA407753CE01}" />
<Execution ProcessID="1516" ThreadID="1528" />
<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
<Computer>Santiago</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="BootTsVersion">2</Data>
<Data Name="BootStartTime">2013-05-18T03:24:49.671600300Z</Data>
<Data Name="BootEndTime">2013-05-18T03:27:56.275126900Z</Data>
<Data Name="SystemBootInstance">1456</Data>
<Data Name="UserBootInstance">1338</Data>
<Data Name="BootTime">161819</Data>
<Data Name="MainPathBootTime">140619</Data>
<Data Name="BootKernelInitTime">20</Data>
<Data Name="BootDriverInitTime">1260</Data>
<Data Name="BootDevicesInitTime">3538</Data>
<Data Name="BootPrefetchInitTime">46511</Data>
<Data Name="BootPrefetchBytes">473882624</Data>
<Data Name="BootAutoChkTime">0</Data>
<Data Name="BootSmssInitTime">14868</Data>
<Data Name="BootCriticalServicesInitTime">1117</Data>
<Data Name="BootUserProfileProcessingTime">720</Data>
<Data Name="BootMachineProfileProcessingTime">0</Data>
<Data Name="BootExplorerInitTime">47303</Data>
<Data Name="BootNumStartupApps">9</Data>
<Data Name="BootPostBootTime">21200</Data>
<Data Name="BootIsRebootAfterInstall">false</Data>
<Data Name="BootRootCauseStepImprovementBits">0</Data>
<Data Name="BootRootCauseGradualImprovementBits">512</Data>
<Data Name="BootRootCauseStepDegradationBits">0</Data>
<Data Name="BootRootCauseGradualDegradationBits">0</Data>
<Data Name="BootIsDegradation">false</Data>
<Data Name="BootIsStepDegradation">false</Data>
<Data Name="BootIsGradualDegradation">false</Data>
<Data Name="BootImprovementDelta">0</Data>
<Data Name="BootDegradationDelta">0</Data>
<Data Name="BootIsRootCauseIdentified">true</Data>
<Data Name="OSLoaderDuration">1547</Data>
<Data Name="BootPNPInitStartTimeMS">20</Data>
<Data Name="BootPNPInitDuration">3584</Data>
<Data Name="OtherKernelInitDuration">2017</Data>
<Data Name="SystemPNPInitStartTimeMS">5505</Data>
<Data Name="SystemPNPInitDuration">1215</Data>
<Data Name="SessionInitStartTimeMS">6816</Data>
<Data Name="Session0InitDuration">6905</Data>
<Data Name="Session1InitDuration">508</Data>
<Data Name="SessionInitOtherDuration">7454</Data>
<Data Name="WinLogonStartTimeMS">21685</Data>
<Data Name="OtherLogonInitActivityDuration">70910</Data>
<Data Name="UserLogonWaitDuration">1239</Data>
</EventData>
</Event>
 

HEXiT

Champion
Herald
first off get bluescreenviewer its a lot more concise and easier to read.
pfc sys was blocked for compatibility reasons. this may well slow your startup. thing is its a windows driver. normally this error would cause a lock up rather than a slow boot.
also your other errors are also related to it because pfc.sys is part of the storage drivers. so it looks like you have an incomparable drive of some kind. likely your dvd drive or some other kind of mass storage is being detected wrong.
so remove all but the boot drive and see what happens.

 

HEXiT

Champion
Herald
another thing. if your using MS essentials please get something else. its catch rate is very very poor at best. its so bad they refuse to have it tested against every other antivirus payed or free.
a good free alternative would be avira, avast,avg personally i use avira with a payed version of malwarebytes to back it up.
 

malynch7

Honorable
Oct 20, 2013
9
0
10,520
1
I know this is an old thread, but I just recovered from this problem after doing a clean install on my y580, and wanted to post a solution. I actually did a few installs due to this problem. I eventually found it to be a usb conflict. I had installed windows 7 with my mouse already plugged in, so the drivers never loaded correctly. This caused them to conflict with the synaptics drivers I use with my system. I unplugged, uninstalled, and reinstalled the drivers to the sweet melody of a fast boot.

It's my understanding that this is usually caused by either graphic driver problems or a usb/bluetooth/network conflict, in that order of likelyhood. Try isolating each and hopefully you will find your problem. If not, google "troubleshoot using clean boot". It's a trial and error process, but it will get you there. Best of luck!
 

Similar threads


TRENDING THREADS