Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Why it takes around 5 min to get to welcome page?


  • Please log in to reply
67 replies to this topic

#1 Pat(rick)

Pat(rick)

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 19 September 2010 - 09:17 PM

Why it takes around 5 min to get to welcome page?

I posted a thread in Am I Infected, the mod it's not because of Malware.

After I got my updates from microsoft update, my computer took around 3-5 minutes to reach the startup page (or welcome page).

wondering why...

BC AdBot (Login to Remove)

 


#2 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 19 September 2010 - 09:24 PM

Do you have a mapped network drive that is no longer available?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#3 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 19 September 2010 - 09:52 PM

what's a mapped network drive?

I only have C:\ and D:\

the other time, the D:\ one was kinda "not connected", I have to open my computer and make sure the plug/cabel (or w/e it's called) is well connected. (D:\ work again but computer startup is slowing down and no i didn't mess up with the cabels)

Edited by Pat(rick), 19 September 2010 - 09:55 PM.


#4 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 19 September 2010 - 09:56 PM

Some info on mapped network drives:

http://compnetworking.about.com/od/windows...etworkdrive.htm
http://support.microsoft.com/kb/308582
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#5 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 19 September 2010 - 10:21 PM

Please download VEW and save it to your Desktop: http://images.malwareremoval.com/vino/VEW.exe

Double-click VEW.exe then under Select log to query, select:
Application
System


Under Select type to list, select:
Critical (Vista only)
Error


Click the radio button for Number of events
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.

In Notepad, click Edit > Select all then Edit > Copy
Reply to this post, click in the reply window and press Ctrl+V on your keyboard to paste the log.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#6 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 20 September 2010 - 05:43 PM

Vino's Event Viewer v01c run on Windows XP in English
Report run at 20/09/2010 6:43:14 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Process Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Symantec AntiVirus\VPTray.exe Event Info: Terminate Process Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Thread Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

Log: 'Application' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 45 Source: Symantec AntiVirus
SYMANTEC TAMPER PROTECTION ALERT Target: C:\Program Files\Common Files\Symantec Shared\ccApp.exe Event Info: Terminate Process Action Taken: Blocked Actor Process: C:\Documents and Settings\Patrick\Desktop\TFC.exe (PID 2348) Time: Saturday, September 18, 2010 6:07:55 PM

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 18/09/2010 6:07:55 PM
Type: error Category: 0
Event: 7034 Source: Service Control Manager
The Yahoo! Updater service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 18/09/2010 6:07:54 PM
Type: error Category: 0
Event: 7034 Source: Service Control Manager
The Java Quick Starter service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 18/09/2010 6:07:54 PM
Type: error Category: 0
Event: 7034 Source: Service Control Manager
The Sandboxie Service service terminated unexpectedly. It has done this 1 time(s).

Log: 'System' Date/Time: 18/09/2010 3:39:24 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 17/09/2010 3:37:31 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 17/09/2010 7:03:48 AM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 16/09/2010 4:19:58 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 16/09/2010 7:54:42 AM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 15/09/2010 6:37:31 PM
Type: error Category: 0
Event: 29 Source: W32Time
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

Log: 'System' Date/Time: 15/09/2010 6:37:31 PM
Type: error Category: 0
Event: 17 Source: W32Time
Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer 'time.windows.com,0x1'. NtpClient will try the DNS lookup again in 15 minutes. The error was: A socket operation was attempted to an unreachable host. (0x80072751)

Log: 'System' Date/Time: 15/09/2010 6:37:19 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 15/09/2010 5:14:19 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 14/09/2010 10:54:14 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 14/09/2010 4:44:55 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 13/09/2010 5:52:07 PM
Type: error Category: 0
Event: 12 Source: PlugPlayManager
The device 'WDC WD2500JS-00MHB0' (IDE\DiskWDC_WD2500JS-00MHB0_____________________02.01C03\5&312c804a&0&0.1.0) disappeared from the system without first being prepared for removal.

Log: 'System' Date/Time: 13/09/2010 5:52:00 PM
Type: error Category: 0
Event: 7011 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for a transaction response from the PolicyAgent service.

Log: 'System' Date/Time: 13/09/2010 5:51:52 PM
Type: error Category: 0
Event: 14103 Source: PSched
QoS [Adapter {FD7CD47D-F9D4-4B7B-AD2B-F6A49CD78600}]: The netcard driver failed the query for OID_GEN_LINK_SPEED.

Log: 'System' Date/Time: 13/09/2010 2:15:17 PM
Type: error Category: 0
Event: 15 Source: atapi
The device, \Device\Ide\IdePort0, is not ready for access yet.

Log: 'System' Date/Time: 13/09/2010 2:14:28 PM
Type: error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

Log: 'System' Date/Time: 13/09/2010 2:14:28 PM
Type: error Category: 0
Event: 9 Source: atapi
The device, \Device\Ide\IdePort0, did not respond within the timeout period.

#7 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 20 September 2010 - 05:56 PM

What is the make and model number of your computer?
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#8 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 20 September 2010 - 07:17 PM

This computer (desktop) is using wireless connection.

Should I say the make and model number of the wireless hardware?

Wireless Hardware model is

D-Link WDA-2320 (gold series)

Edited by Pat(rick), 20 September 2010 - 07:19 PM.


#9 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 20 September 2010 - 08:03 PM

No I actually want to know the make and model of the computer. For example: Dell Inspiron 6400.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#10 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 23 September 2010 - 03:08 PM

Ahh, sorry for misunderstand x.x

It's Acer but now, I'm not sure because it's kinda customized (All I see when open my comp is "Phoenix Technologies, LTD" and some details)

Operating System
MS Windows XP Professional 32-bit SP3
CPU
Intel Pentium 4 531
Prescott 90nm Technology
RAM
1.5GB Dual-Channel DDR @ 200MHz (3-3-3-8)

Motherboard
Model 915GL-ICH6
Chipset Vendor Intel
Chipset Model i915P/i915G
Chipset Revision 0E
Southbridge Vendor Intel
Southbridge Model 82801FB (ICH6)
Southbridge Revision 05
BIOS
Brand Phoenix Technologies, LTD
Version 6.00 PG
Date 08/24/2005
Graphics
L206W @ 1440x900
Intel® 82915G/GV/910GL Express Chipset Family

Edited by Pat(rick), 23 September 2010 - 03:34 PM.


#11 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:40 AM

Posted 23 September 2010 - 03:53 PM

These kinds of errors that were in your log can be caused by a faulty hard drive:

Log: 'System' Date/Time: 13/09/2010 2:15:17 PM
Type: error Category: 0
Event: 15 Source: atapi
The device, \Device\Ide\IdePort0, is not ready for access yet.

Log: 'System' Date/Time: 13/09/2010 2:14:28 PM
Type: error Category: 0
Event: 11 Source: atapi
The driver detected a controller error on \Device\Ide\IdePort0.

So I think we should run a diagnostic test on the drive. To do this you can use SeaTools for Windows. Run the long or extended test and let us know if it reports any errors.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw

#12 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 24 September 2010 - 12:03 PM

Is it the Long Generic test?

omg it's taking alot of times o_o


--------------- SeaTools for Windows v1.2.0.4 ---------------
9/24/2010 12:01:43 PM
Model: SAMSUNG HD040GJ
Serial Number: S
Firmware Revision: ZG100-33
Long Generic - Started 9/24/2010 12:01:43 PM
Long Generic - Pass 9/24/2010 3:32:48 PM



--------------- SeaTools for Windows v1.2.0.4 ---------------
9/24/2010 12:02:09 PM
Model: WDC WD2500JS-00MHB0
Serial Number: WD
Firmware Revision: 02.01C03
Long Generic - Started 9/24/2010 12:02:09 PM
Long Generic Aborted 9/24/2010 3:41:46 PM
Short Generic - Started 9/24/2010 3:42:19 PM
Short Generic - Pass 9/24/2010 3:43:57 PM
SMART Aborted 9/24/2010 3:44:29 PM

Edited by Pat(rick), 24 September 2010 - 02:45 PM.


#13 Gabrial

Gabrial

  • Members
  • 468 posts
  • OFFLINE
  •  
  • Local time:11:40 AM

Posted 24 September 2010 - 03:11 PM

Does it take this long every time you boot, or just the time immediately after your windows updates were installed? Windows updates will actually update alot of system files before your welcome screen appears. You may have an update failing to complete on boot if it is happening every time.

#14 Pat(rick)

Pat(rick)
  • Topic Starter

  • Members
  • 466 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:North America
  • Local time:12:40 PM

Posted 24 September 2010 - 03:39 PM

After I got my windows updates, it takes this long... If I didn't update, it should had been quick

#15 Gabrial

Gabrial

  • Members
  • 468 posts
  • OFFLINE
  •  
  • Local time:11:40 AM

Posted 24 September 2010 - 03:54 PM

Sometimes it takes several boots to get things to normal boot speeds, as the prefetch needs updating for current updates, some updates are dependant on others, etc.

Reboot the system at least 5 times and see if it fixes if not, We should probably create a bootlog.txt using F8 and selecting it from your boot menu and then paste it here. You can find it as a hidden file at c:\bootlog.txt. That will help us diagnose your boot problems.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users