Ben,
Good enough - we now know that it is most likely (99%) driver related. Now
comes the fun part - narrowing it down by adding back one thing at a time.
Bring the system up normally and then in the Start box where it says Search,
type in msconfig
That brings up a window that has a tab called "Startup", click on it. Now
uncheck all the entries, you will add them back later - one at a time.
Turn off the system and connect any hardware that was connected. You can do
this one at a time and test each but I prefer to do the divide and conquer
method.
Go back into BIOS and turn everything back on that you turned off or set to
defaults - however the system was configured.
Now bring the system up normally. Windows may complain about something not
starting up (we've disabled all startup items which includes applications
(if any) and maybe a driver or two.) Acknowledge or cancel (whatever it
takes) to get rid of any window messages.
Exercise the system - and if it works okay, go back into msconfig and enable
1/2 of the items (top to bottom).
Repeat reboot and test. If it goes south, you now it was one of the items
you just enabled. If not, enable the other 1/2 of items unchecked - and
this time when you reboot something should fail.
Back to msconfig and turn off one item that you enabled and test after
rebooting. Remember that turning something off in msconfig has no effect
until you reboot.
This "should" narrow down what is causing the problem. If not, we'll try a
different tact but I think this should nail it since everything ran in Safe
Mode. If you can't determine what the item is for that you turned off (and
the computer didn't freeze) post the entry here and we'll look it up or you
can do a Google search.
There may not be a new driver available yet or a fix for what is bothering
your system - so be prepared for that. And, it may be more than one item
that is at issue here so don't let it frustrate you. Need you to keep track
of what you're doing so you know exactly what you're chasing down even if
you don't understand what it is. It's a bug - that's all you need to
know...........;-)
Post back to this thread and I'll keep an eye open for your response.
Bob S.
"lockup" <lockup@discussions.microsoft.com> wrote in message
news
858F55B-D784-4628-9571-6DA2481D3FF2@microsoft.com...
> "BobS" wrote:
>>
>> ...lots of handy stuff...
>
> Hi Bob,
>
> I've disabled everything I can. Unfortunately I can't install to an IDE
> disk
> as I only have SATA disks here which means I need to have the SATA
> controller
> enabled.
>
> I'm stuck on graphics cards as well. I've got a hatful of AGP and nothing
> else. This system only has two PCI-E slots.
>
> Everything that can be disabled has been and I'm only running with one
> stick
> of memory as described. In safe mode (with or without networking),
> everything
> is fine. I've run 4 concurrent 32M place SuperPi's for half an hour, so
> really stretched the CPU and memory without any issues whatsoever.
>
> This certainly seems to be a driver related issue. Is there a way to
> enable
> drivers selectively at boot to narrow things down?
>
> Cheers,
>
> Ben
>
Linear Mode
