|
-
Jul 9th, 2005, 09:22 AM
#1
Thread Starter
Supreme User
Finding Where The Problem Lies?
I mentioned previously before that im experiencing slow startups, ie the pc hangs on the "Starting Windows" and "Welcome" screen. I find when i switch the pc on the morning on, it hangs, but when i reset it, it seems to load ok about 90% of the time. Its like it needs warming up first. Although the problem seems more logic to be a driver problem, if so, how do i find out which driver file is causing this?
Cheers
-
Jul 9th, 2005, 10:47 AM
#2
Fanatic Member
Re: Finding Where The Problem Lies?
un-plug all of your usb && firewire things plugged into your computer (including mouse and keyboard) then start up the computer and see if it goes any faster...
if it does plug them back in one at a time and see which one is doing it, then get a new one.
happened to a client of mine, it was his printer
-
Jul 9th, 2005, 12:01 PM
#3
Thread Starter
Supreme User
Re: Finding Where The Problem Lies?
Could one of the driver files just need updating, or is that the best way?
-
Jul 9th, 2005, 04:35 PM
#4
Fanatic Member
Re: Finding Where The Problem Lies?
depends where it hangs up... if it takes along time for windows to fire (it hangs in the bios) than it would not be a driver... if it hangs when windows tries to start up, then it is possable, but unlikley.
-
Jul 9th, 2005, 04:41 PM
#5
Re: Finding Where The Problem Lies?
The registry could just be full of junk. Best to format and reinstall. It sped up my machine. I couldn't believe how fast it shut down, and starts up!
-
Jul 10th, 2005, 04:12 AM
#6
Thread Starter
Supreme User
Re: Finding Where The Problem Lies?
I was thinking of formatting it, just been too lazy to backup my projects and files
-
Jul 11th, 2005, 05:00 AM
#7
Re: Finding Where The Problem Lies?
I've actually seen this happen, and it was a dying motherboard that caused it, granted it had Windows 98 installed, but the symptoms were the same, sometimes it loaded fine, sometimes it locked up where you said, though it also locked up just before, during and after POST also, which made it [kinda] easy to diagnose.
I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
-
Jul 11th, 2005, 10:07 AM
#8
Thread Starter
Supreme User
Re: Finding Where The Problem Lies?
Well when the computer got upgraded 2 months ago or so it was fitted with a new motherboard, surely it hasnt gone already? Is there anyway to check its health?
-
Jul 11th, 2005, 11:55 AM
#9
Re: Finding Where The Problem Lies?
Did you reformat when you installed the new motherboard? That's like the kiss of death to a windows operating system to replace the motherboard and use the same installation.
Bill
-
Jul 11th, 2005, 10:11 PM
#10
Re: Finding Where The Problem Lies?
 Originally Posted by Madboy
Well when the computer got upgraded 2 months ago or so it was fitted with a new motherboard, surely it hasnt gone already? Is there anyway to check its health?
The only way I know of, is to install another motherboard and see if the problem is the same.
I use Microsoft Visual Basic 2005. (Therefore, most code samples I provide will be based around the .NET Framework v2.0, unless otherwise specified)
-
Jul 12th, 2005, 11:41 AM
#11
Thread Starter
Supreme User
Re: Finding Where The Problem Lies?
 Originally Posted by conipto
Did you reformat when you installed the new motherboard? That's like the kiss of death to a windows operating system to replace the motherboard and use the same installation.
Bill
Good point, i think the motherboard was inserted after the clean install, maybe doing a reformat like previously suggested might do the trick
-
Jul 12th, 2005, 02:14 PM
#12
Re: Finding Where The Problem Lies?
also check for memory cards. mine was corrupted and caused a slow response to things. it didn't boot at times. now i got new memory cards and so far things look good.
Everything that has a computer in will fail. Everything in your life, from a watch to a car to, you know, a radio, to an iPhone, it will fail if it has a computer in it. They should kill the people who made those things.- 'Woz'
save a blobFileStreamDataTable To Text Filemy blog
-
Jul 13th, 2005, 07:28 AM
#13
Thread Starter
Supreme User
Re: Finding Where The Problem Lies?
 Originally Posted by Madboy
Good point, i think the motherboard was inserted after the clean install, maybe doing a reformat like previously suggested might do the trick
Saying that though, the problem would of been from day one, not these recent weeks. So im guessing something other than the motherboard
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|