Prev: Audio cassette to PC convertor
Next: USB keyboard
From: geoff on 19 Jan 2010 09:31
> The "faded" appearance at startup, could be how the Windows logo is done.
> I
> think it fades in from black. So the first frame of the logo which is
> non-black,
> would be a faded image.

I see what you mean about the logo fading in. I'm real sensitive about it
now and that very first frame, which is barely visible, is where it stops.

I also tried the boot logging and the beginning of the file is:

Service Pack 3 1 19 2010 02:42:49.125
Loaded driver \WINDOWS\system32\ntkrnlpa.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver ohci1394.sys
Loaded driver \WINDOWS\system32\DRIVERS\1394BUS.SYS
Loaded driver compbatt.sys
etc.

.. . . but if it stopped on a driver, say 'wmilib.sys', what would be your
next step?

Thanks.

--g


From: geoff on 19 Jan 2010 09:37
> Any driver conflict can cause the boot to stop, as can any hardware
> failure.

The reason I ask is my documentation says scanning for legacy USB ports is a
BIOS function, so, if that were to stop the boot, it seems it would be in
the BIOS, before the computer even gets to Windows.

--g


From: TVeblen on 19 Jan 2010 10:28
On 1/19/2010 9:37 AM, geoff wrote:
>> Any driver conflict can cause the boot to stop, as can any hardware
>> failure.
>
> The reason I ask is my documentation says scanning for legacy USB ports is a
> BIOS function, so, if that were to stop the boot, it seems it would be in
> the BIOS, before the computer even gets to Windows.
>
> --g
>
>
But it may be that once the legacy drivers are initiated (in BIOS) then
as soon as Windows tries to load it hits a conflict and freezes. You
just want to eliminate that as a possibility. Turn it off, see if it
changes anything. If it doesn't, then turn it back on.
From: Paul on 19 Jan 2010 18:55
geoff wrote:
>> The "faded" appearance at startup, could be how the Windows logo is done.
>> I
>> think it fades in from black. So the first frame of the logo which is
>> non-black,
>> would be a faded image.
>
> I see what you mean about the logo fading in. I'm real sensitive about it
> now and that very first frame, which is barely visible, is where it stops.
>
> I also tried the boot logging and the beginning of the file is:
>
> Service Pack 3 1 19 2010 02:42:49.125
> Loaded driver \WINDOWS\system32\ntkrnlpa.exe
> Loaded driver \WINDOWS\system32\hal.dll
> Loaded driver \WINDOWS\system32\KDCOM.DLL
> Loaded driver \WINDOWS\system32\BOOTVID.dll
> Loaded driver ACPI.sys
> Loaded driver \WINDOWS\system32\DRIVERS\WMILIB.SYS
> Loaded driver pci.sys
> Loaded driver isapnp.sys
> Loaded driver ohci1394.sys
> Loaded driver \WINDOWS\system32\DRIVERS\1394BUS.SYS
> Loaded driver compbatt.sys
> etc.
>
> . . . but if it stopped on a driver, say 'wmilib.sys', what would be your
> next step?
>
> Thanks.
>
> --g
>

There might not be any value to it :-) But in your example, it is possible
something is happening to pci.sys . I don't understand enough of the boot
process, to know whether any initialization code runs when a driver loads.
I thought there was a whole lot of initialization activity, just as the
desktop appears. But perhaps each driver executes its initialization
code at the point of loading. The "pci.sys" would be used for something
related to the system busses, and perhaps you could imply some kind of hardware
failure.

The scary thing about your issue, is I experienced the same kind of thing
just yesterday, and for the first time. But my WinXP logo screen got close
to the end of the driver load sequence before the machine froze. And the
problem so far is not reproducible. What is weird is, at the end of the
ntbtlog I collected on the *next* boot attempt, shows this at the end.

Loaded driver \SystemRoot\System32\Drivers\HTTP.sys
Loaded driver \SystemRoot\system32\drivers\npf.sys
Loaded driver \SystemRoot\system32\DRIVERS\NMnt.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys

I guess kmixer is very popular this year :-) I don't know what is up
with that, but my guess is that is what froze the machine yesterday.

Paul
From: geoff on 24 Jan 2010 12:21
Resolved the issue. These two items:

> GIGABYTE GA-MA78GM-S2H (rev 1.1)
> AMD Phenom II X4 955 Black Edition Deneb 3.2GHz

.. . . are not compatible. The processor is listed on their compatibility
list to let you know it is not compatible. That is kind of like making a
grocery list by writing down the things you don't want.

However, I was thinking of upgrading the graphics card but noticed that
GigaByte had a board similar to mine but with integrated Radeon HD 4200 for
$80. I went for that and it all seems to be working well.

I'm a GigaByte fan now. I like ASUS and built one machine with ASRock. All
good boards.

--g


First  |  Prev  | 
Pages: 1 2 3
Prev: Audio cassette to PC convertor
Next: USB keyboard