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.


BSOD issue

  • Please log in to reply
1 reply to this topic

#1 dialout


  • Members
  • 118 posts
  • Local time:07:50 AM

Posted 12 October 2011 - 07:14 AM


Trying to fix the kids old desktop again. They have been complaining that it hangs, and freezes...then takes an extended time to start-up. I fixed a DSOD issue earlier this year by burning a linux cd from my laptop, and booting this computer with it. Took some playing but eventually got windows to boot again.

I got up this morning and the computer was hung on the shutdown screen. I hard booted it, and it hung at the black screen...another boot, and it went to splash screen...another boot and after a looooong pause at each screen it came up. If I remember correctly this is what it started doing before locking up with the BSOD last time...

so the question is...is there any way to check for a coming problem? is there a "tune-up" I can preform to try and avoid it?

Just trying to put off buying a new computer as long as I can since this one is used by the kids, and all the online games they play put lots of little nasties on it.

BC AdBot (Login to Remove)


#2 Allan


  • BC Advisor
  • 8,627 posts
  • Gender:Male
  • Location:New Jersey
  • Local time:08:50 AM

Posted 12 October 2011 - 07:15 AM

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.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users