Saved Bookmarks
| 1. |
Solve : Interesting Mystery? |
|
Answer» First off im not an IT newb, i have 14 years in the industry with more certs then i care to count, with that being SIAD some of the most interesting puzzles we have to solve are often our own Once it starts the HP runs OK. - Right? well if this forum doesnt have real tech people at least its got funny ones LOL, i never turn my pc off, thats one of the first things they break you of in REAL IT school lol Some empirical research shows taught each installation of Windows has some difference, even if the hardware is the same. No simple theory explains this. If you need an explanation, here is one. The hardware design is asynchronous, that is to say, not all the hardware is driven by the same clock or phase. This is by desing. But during installation some errors are made in timing and this results is slight changes in settings. Hard to prove.UMM *censored* so your saying my hardware is slowing down the startup i think lol *censored* was that was that even english lol This might help- it's a KB article detailing an issue where setting a Solid Color background can cause around a 30-second wait time during startup. This links to a similar issue with a similar delay time due to Group Policy settings here. Another possibility is if you have a network drive on an unavailable machine that Windows cannot access, it will cause a similar delay if it's set to "reconnect at startup". They are only 30 second wait times though. One thing I can think of is that Active Directory's Default timeout is 3 minutes, so if the computer thinks it is on a domain or some part of it thinks it is it might be causing everything to wait for it to timeout. I'm sure if Geek-9pm continues posting in this thread we can have a feast on red herrings.Does the same thing happen in safe mode? If not, try a selective startup: Open msconfig and on the General tab choose "selective startup" (uncheck all three items) and reboot. Does the problem still occur? If not, start adding items back to msconfig one or two at a time, rebooting after each change, until the problem reappears and you'll have identified the offending process. This is clearly a time consuming procedure, but it is the best way to DETERMINE if some process loading with the system is the cause of your problem. After you've isolated the cause, do not use msconfig to permanently disable the process. Instead, if it is a service go to START - RUN and type: services.msc (then press enter) and disable the service OR, if it a program, you can download & run a simple app such as Mike Lin's Startup Control Panel (http://www.mlin.net/StartupCPL.shtml) to enable, disable, or otherwise manage startup programs. Also, welcome to the forum . In the future, please give your topics a subject that relates to the question. "Interesting Mystery" is cute, but not helpful. Thank you.I hate to send you on a treasure hunt/goose chase, but you may want to compare the msconfig, and Manage=>Services=>Services and Applications to "good" installations:
If you're going to start comparing config files, etc., THAT is the order in which you'd want to compare them. Also -
There is a program called "Soluto" that, once installed and REBOOTED, will show you which programs are sucking up how much time during your boot. It's basically a graphical interface of your "Services and Applications", but with the durations added. Also, patio once suggested to me a piece of software called Startup CPL from Mike Lin that helps manage startup apps. thanks for some solid answers as for the info requested its not on a domain its on a workgroup, its a businessm odel machine but its the only one, its in a home setting, mainly configured for light graphics editing, video editing, and web design, plus general office work, it has a NAS connected to it as well as a usb external drive, (there is the standard error when windows comes up on the desktop :windows cant connect to one or more of your drives blah blah blah) but 3 minutes solid for that, the background is a pic of the golden gate at night, ill try that program Ill take a peek in the MSconfig area and with the services, but unknown whats causing it, when i bought it this machine was a refurb, however i wiped it and put my own install in it, before you ask yes it was doing this with the factory settings as well Some good stuff to look through, ill get back to you soon! Thanks everyone! went to soluto site, its a business program that costs per membership, NOTHING im interested in, our IT company has a proprietary software that runs circles around that for our remote monitoring, ill look for some boot time freeware ill get back to you all when i have some more info FYI their site is slower then dirt, lol Interesting that Soluto has changed so much since I installed it! The version I have is free, and it basically runs something called "Chop Boot", where it shows everything that loads as part of your boot, and how much time each is, and you can decide whether or not it loads in your boot, delays and loads in background later, or is on demand. It's a desktop app, not any kind of enterprise solution. Sorry for outdated advice - it works for me! Yeah i have found that a good product rarely stays free, they build it, test it, develop it, sign people up, then raise prices, which causes all but a few to go to the next "free thing" and those that stay keep the company afloat I digress though, the winner in this mystery seems to go to BC_Programmer, i found out NAS which ahs its own drive letter and IP at boot might have caused it, by disconnecting the NAS and then rebooting i was able to boot from POST to desktop wallpaper in around 30 seconds, the sad thing is i need that NAS to be connected and mapped, it seems tho for now whenever i must reboot i will have to "disconnect" and remap it, i tried creating a shortcut so that if disconnected when i clicked the shortcut it would reconnect, but that just sent winblows on a search for a path not found again Very interesting, we went from almost minutes to 30 seconds, i also tweaked a few things in startup, but the difference was when i dropped the NAS drive, like i said doesnt help but now i know, and explains why it was a mystery, rarely would anyone think to check that area, most of us would go for startup problems, or disk issues, or malware, at least i did! One of the interesting things about the sort of third party tools mentioned earlier, is that many of them actually have built-in windows versions that are oftentimes better. EDIT: I guess since it's mostly solved now it's not as useful, but I thought I'd post it anyways). Windows Performance Analyzer and Windows Performance Recorder is a Windows 7+ Tool that can be used to record and analyze all sorts of information about Boot-up, shutdown, reboot, standby/resume ,etc. You can get a very useful set of statistics and information on Boot about CPU usage, Network usage, what processes are using the system, etc. with it, which might be helpful in trying to determine the cause of this delay you are experiencing. The first step is to configure the Windows Performance Recorder- for obvious reasons Windows doesn't record traces all the time. I search for it with the start menu ("Windows Performance" and both the Recorder and Analyzer show up) Within the Recorder configure it- For your case setting Performance Scenario to "Boot", Detail Level to Verbose, and Logging mode to File. Also set the "Additional Profiles" and check off the CPU, Disk I/O, File I/O, Registry I/O, and Networking I/O options, which are in the "Resource Analysis" drop-down. You might also want Scenario Analysis->Minifilter I/O activity selected. Once Selected, I believe you Press "Start" and then close Windows Performance Recorder. Reboot, and when you get back to the desktop you can start Windows Performance Recorder again. This time, it will allow you to stop the trace and save it to a file. This file will be massive- ~3-4GB. Once it is saved, you can start Windows Performance Analyzer to open the created trace file. The amount of information recorded is massive and will hopefully provide some insight into things. It gives you a few basic graphs to start off with that don't seem super useful, but you can actually drill down- for example, let's say during that long pause the CPU is throttled at 100%. Surely that would indicate a process hogging CPU time. You can grab and view all sorts of graphs and even view a breakdown of CPU usage over time by individual processes, same for Disk I/O and other similar resources. Quote from: needsomehelp on February 26, 2014, 11:22:21 AM i have found that a good product rarely stays free, they build it, test it, develop it, sign people up, then raise prices, which causes all but a few to go to the next "free thing" and those that stay keep the company afloatYeah, I literally just discovered LogMeIn Free - which I've been using to remotely manage my "home network" from the road for nearly ten years - does not exist anymore.Logmein hasnt been free for awhile now, we use a software called Dolphin, its a complete IT ticketing, purchasing, accounting, and remote support suite, however you will never find it on any website for sale, it is one of the most comprehensive IT suites out there (well not out THERE) i was pleased that the solution was so handy, all had good input, even the first replys that were such an enigma GOod show by all (As they say in england) lol |
|