Quote: Originally Posted by MrFeenee
Ok that worked too. I'm now running selective startup. Is there anything I should look out for?
Just to clarify, this particular troubleshooting strategy is based on the premise that what is described as a "crash" in the thread's title is actually a lockup. Otherwise, if it really does crash - in the BSOD sense - it would be better to analyse minidumps.
Lockups are nasty to troubleshoot because it's hard to extract info from the OS at the point where everything is locked up. What you've done, so far, is to prove that the issue doesn't happen in safe mode, and doesn't happen in MSCONFIG's "diagnostic" mode either, which is about as close as you can get to a safe mode boot - without actually being in safe mode.
Now, you'd use "selective" to enable some components and test what happens (reboot before testing each time). For example, you could choose to start all "services" while keeping the "Startup items" all disabled. If that still works (no lockups), swap it around so that all startup items are enabled but services are disabled. Then half of each. Then the remaining quarter. Then an eigth... Eventually you'll be down to the lone item whose presence appears to alter the outcome and lead to lockups.
It's a pain, but it'll get you to the answer.