BSOD STOP 0x0000001A before Logon

Hi!

Here is what I observe just after I have the logon screen (without
logonning)
During the first 10 seconds, there is no activity on the C: drive.
After these 10 seconds, the light of the C: drive begins to flash a lot.
So, many activities happen on the C: drive.
And, usually, 30 seconds later, I get BSOD STOP 0x0000001A.

Do you have the same problem?
What would be the process doing these activities on the C: drive before the
Logon?
Could it be the Search Process or the Defragment process or . . . ?

Merci beaucoup! Roger

Hi Roger,

0x1A is a Memory Management error, generally indicating a faulty driver or
incompatible hardware. Did you run the compatibility check before
installing? Have you installed supporting drivers for all hardware? Has this
happened since day 1 or did it just start? Did it happen in previous builds?
Does the BSOD indicate a module? Have you tried logging into safe mode and
checking the event viewer for more details?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org

"rogerlebo" <no.spam@no.spam> wrote in message
news:ufSb1iY2GHA.4976@TK2MSFTNGP02.phx.gbl...
> Hi!
>
> Here is what I observe just after I have the logon screen (without
> logonning)
> During the first 10 seconds, there is no activity on the C: drive.
> After these 10 seconds, the light of the C: drive begins to flash a lot.
> So, many activities happen on the C: drive.
> And, usually, 30 seconds later, I get BSOD STOP 0x0000001A.
>
> Do you have the same problem?
> What would be the process doing these activities on the C: drive before
> the Logon?
> Could it be the Search Process or the Defragment process or . . . ?
>
> Merci beaucoup! Roger
>
>

Hi Rick!

First, thanks a lor for all your ideas.

Yes, I ran the compatibility check before installing and many times since
then.
Yes, I installed supporting drivers for all hardwares.
No, it dit not happen neither with Build 5384 32-bits, nor with Build 5384
64-bits, nor with RC1 64-bits nor with Windows XP.
It just happened with RC1 32-bits.
No, the BSOD dit not indicate a module.
In safe mode, it did not happen.
In the event viewer, there is nothing special.

Maybe, it is the Search process.
I know it is started automatically before Logon.
I will set it to Manual.

Merci encore! Roger

"Rick Rogers" <rick@mvps.org> wrote in message
news:ezzGvuY2GHA.4924@TK2MSFTNGP05.phx.gbl...
> Hi Roger,
>
> 0x1A is a Memory Management error, generally indicating a faulty driver or
> incompatible hardware. Did you run the compatibility check before
> installing? Have you installed supporting drivers for all hardware? Has
> this happened since day 1 or did it just start? Did it happen in previous
> builds? Does the BSOD indicate a module? Have you tried logging into safe
> mode and checking the event viewer for more details?
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org

Hi Roger,

> In safe mode, it did not happen.

There is a big clue. It likely means that a device driver loading in normal
mode is causing the problem. In safe mode, only limited drivers are loaded,
so there is no conflict. Is it creating a memory dump? We might be able to
analyze it for clues.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org

"rogerlebo" <no.spam@no.spam> wrote in message
news:OS1zYzm2GHA.5048@TK2MSFTNGP05.phx.gbl...
> Hi Rick!
>
> First, thanks a lor for all your ideas.
>
> Yes, I ran the compatibility check before installing and many times since
> then.
> Yes, I installed supporting drivers for all hardwares.
> No, it dit not happen neither with Build 5384 32-bits, nor with Build 5384
> 64-bits, nor with RC1 64-bits nor with Windows XP.
> It just happened with RC1 32-bits.
> No, the BSOD dit not indicate a module.
> In safe mode, it did not happen.
> In the event viewer, there is nothing special.
>
> Maybe, it is the Search process.
> I know it is started automatically before Logon.
> I will set it to Manual.
>
> Merci encore! Roger
>
> "Rick Rogers" <rick@mvps.org> wrote in message
> news:ezzGvuY2GHA.4924@TK2MSFTNGP05.phx.gbl...
>> Hi Roger,
>>
>> 0x1A is a Memory Management error, generally indicating a faulty driver
>> or
>> incompatible hardware. Did you run the compatibility check before
>> installing? Have you installed supporting drivers for all hardware? Has
>> this happened since day 1 or did it just start? Did it happen in previous
>> builds? Does the BSOD indicate a module? Have you tried logging into safe
>> mode and checking the event viewer for more details?
>>
>> --
>> Best of Luck,
>>
>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>> http://mvp.support.microsoft.com/
>> Windows help - www.rickrogers.org
>

Hourra!

I've just received this message in "Problem Reports ans Solutions" :

Error is being researched


--------------------------------------------------------------------------------

Thank you for submitting an error report to Microsoft Online Crash Analysis.
Unfortunately, we cannot provide you with specific information about how to
resolve this problem at this time. The information that you and other users
submit will be used to investigate this problem.


Analysis

This error is currently being researched.


Je suis très content!

Bonne journée! Roger

"Rick Rogers" <rick@mvps.org> wrote in message
news:urB3cAq2GHA.600@TK2MSFTNGP05.phx.gbl...
> Hi Roger,
>
>> In safe mode, it did not happen.
>
> There is a big clue. It likely means that a device driver loading in
> normal mode is causing the problem. In safe mode, only limited drivers are
> loaded, so there is no conflict. Is it creating a memory dump? We might be
> able to analyze it for clues.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Windows help - www.rickrogers.org
>
> "rogerlebo" <no.spam@no.spam> wrote in message
> news:OS1zYzm2GHA.5048@TK2MSFTNGP05.phx.gbl...
>> Hi Rick!
>>
>> First, thanks a lor for all your ideas.
>>
>> Yes, I ran the compatibility check before installing and many times since
>> then.
>> Yes, I installed supporting drivers for all hardwares.
>> No, it dit not happen neither with Build 5384 32-bits, nor with Build
>> 5384
>> 64-bits, nor with RC1 64-bits nor with Windows XP.
>> It just happened with RC1 32-bits.
>> No, the BSOD dit not indicate a module.
>> In safe mode, it did not happen.
>> In the event viewer, there is nothing special.
>>
>> Maybe, it is the Search process.
>> I know it is started automatically before Logon.
>> I will set it to Manual.
>>
>> Merci encore! Roger
>>
>> "Rick Rogers" <rick@mvps.org> wrote in message
>> news:ezzGvuY2GHA.4924@TK2MSFTNGP05.phx.gbl...
>>> Hi Roger,
>>>
>>> 0x1A is a Memory Management error, generally indicating a faulty driver
>>> or
>>> incompatible hardware. Did you run the compatibility check before
>>> installing? Have you installed supporting drivers for all hardware? Has
>>> this happened since day 1 or did it just start? Did it happen in
>>> previous
>>> builds? Does the BSOD indicate a module? Have you tried logging into
>>> safe
>>> mode and checking the event viewer for more details?
>>>
>>> --
>>> Best of Luck,
>>>
>>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>>> http://mvp.support.microsoft.com/
>>> Windows help - www.rickrogers.org
>>
>