Archived from groups: microsoft.public.windowsxp.customize (
More info?)
Ok, Errors aren't errors you should care about.
Type minidump in Start Run. If nothing set your options to create one.
--
----------------------------------------------------------
"Bruce Roberson" <Bruceroberson@cox-internet.com> wrote in message news:w_f_d.39246$3z.17536@okepread03...
> There is not file or folder anywhere with the name minidump so maybe that
> file goes away if you have a successful bootup? I don't know.
>
> Also, you're saying "Errors aren't errors". I thought that was what I was
> looking for in Event Viewer?
>
> Bruce
> "David Candy" <.> wrote in message
> news:uqdupJvKFHA.3640@TK2MSFTNGP12.phx.gbl...
> Possibly because you don't use MS Messenger. Errors aren't errors.
>
> %SystemRoot%\Minidump = c:\windows\minidump
> --
> ----------------------------------------------------------
>
> "Bruce Roberson" <Bruceroberson@cox-internet.com> wrote in message
> news:89f_d.39243$3z.8594@okepread03...
>> David:
>>
>> I did all that and it says something about a small memory dump, and the
>> location being :%SystemRoot%\Minidump. I didn't find such a file in the
>> search. But for now, I'm not doing anything else with that until I see if
>> I
>> have fixed the problem already.
>>
>> I did see one other consistent error that happens independently of the
>> bootup process. The server {F3A614DC-ABE0-11D2-A441-00C04F795683} did not
>> register with DCOM within the required timeout. I traced this on the to
>> the
>> program "c:\programs\messenger\msmsgs.exe" on the above server by
>> 1.. Using Regedit, navigate to the following registry value
>> HKCR\Clsid\clsid value\localserver32
>> The clsid value is the information displayed in the message.
>> 2.. In the right pane, double-click Default. The Edit String dialog box
>> is
>> displayed. Leave this dialog box open.
>> Ok, so what is wrong with windows messenger, because I don't even use that
>> and I don't see it listed in the processes and I don't have it start when
>> Windows starts. So why the heck does it have an error like that that is
>> separate from bootup if it shouldn't be on unless I open the program
>> myself?
>>
>> I don't think that pertains to the bootup problem I mentioned, but at
>> least
>> while I'm learning I'd like to see why this error occured.
>>
>> Thanks,
>>
>>
>> Bruce
>>
>>
>>
>>
>> "David Candy" <.> wrote in message
>> news:O4BvdgqKFHA.3340@TK2MSFTNGP14.phx.gbl...
>> Just get the error message from event viewer if you have to post back.
>> Windows will tell you what is erroring. Programs in MSConfig can't cause
>> Stop errors, at least not directly, though they may use a function that
>> triggers the stop error. Services can cause Stop errors.
>>
>> For speed reasons windows can't catch the full details of every error, but
>> it has modes it can switch to where it can (but it trades off speed).
>>
>> From Help
>> We need error messages in full. If Write an event to the system log is on
>> then look in Event Viewer (type it in help). Most people have it display
>> the
>> screen and write (you know a pen) down the message. See if they are all
>> the
>> same number and details.
>> If Write an event to the system log is on then look in Event Viewer (type
>> it
>> in help).
>>
>> From Help
>>
>> To specify what Windows does if the system stops unexpectedly.
>>
>> You must be logged on as an administrator or a member of the
>> Administrators
>> group in order to complete this procedure. If your computer is connected
>> to
>> a network, network policy settings might also prevent you from completing
>> this procedure.
>>
>> 1.. Open System in Control Panel.
>> 2.. On the Advanced tab, under Startup and Recovery, click Settings.
>> 3.. Under System Failure, select the check boxes that correspond to the
>> actions you want Windows to perform if a Stop error occurs:
>> a.. Write an event to the system log specifies that event information
>> will be recorded in the system log.
>> b.. Send an administrative alert specifies that your system
>> administrator will be notified.
>> c.. Automatically reboot specifies that Windows will automatically
>> restart your computer.
>> 4.. Under Write Debugging Information, choose the type of information you
>> want Windows to record when the system stops unexpectedly:
>> a.. Small Memory Dump records the smallest amount of information that
>> will help identify the problem. This option requires a paging file of at
>> least 2 MB on the boot volume of your computer and specifies that Windows
>> will create a new file each time the system stops unexpectedly. A history
>> of
>> these files is stored in the directory listed under Small Dump Directory.
>> b.. Kernel Memory Dump records only kernel memory, which speeds up the
>> process of recording information in a log when the system stops
>> unexpectedly. Depending on the amount of RAM in your computer, you must
>> have
>> 50 MB to 800 MB available for the paging file on the boot volume. The file
>> is stored in the directory listed under Dump File.
>> c.. Complete Memory Dump records the entire contents of system memory
>> when the system stops unexpectedly. If you choose this option you must
>> have
>> a paging file on the boot volume large enough to hold all of the physical
>> RAM plus one megabyte (MB). The file is stored in the directory listed
>> under
>> Dump File.
>> Notes
>>
>> a.. To open System, click Start, click Control Panel, and then
>> double-click System.
>> b.. You must have at least a 2-MB paging file on the computer's boot
>> volume if you select Write an event to the system log or Send an
>> administrative alert.
>> c.. If you choose either Kernel Memory Dump or Complete Memory Dump and
>> select the Overwrite any existing file check box, Windows always writes to
>> the same file name. To save individual dump files, clear the Overwrite any
>> existing file check box and change the file name after each Stop error.
>> d.. You can save some memory if you clear the Write an event to the
>> system
>> log and Send an administrative alert check boxes. The memory saved depends
>> on the computer, but typically about 60 KB to 70 KB are required by these
>> features.
>> e.. If you contact Microsoft Product Support Services about a Stop error,
>> they might ask for the system-memory dump file generated by the Write
>> Debugging Information option.
>> Related Topics
>>
>>
>> We want either the error message, AND if that doesn't have enough info, a
>> minidump file. And if that doesn't have enough info we switch into a
>> driver
>> debugging mode, and then do the above again. Type verifier in Start Run
>> and
>> follow the wizard. This will do two things.
>>
>> 1. Be very strict with drivers and generate a stop error whenever a driver
>> misbehaves.
>> 2. Some drivers are written to be buggy and fast so they can win magazine
>> benchmark competitions. If verifier is turned on they may become well
>> behaved and slower. That is some drivers have two drivers in the file, one
>> for magazines and users and one for MS testing - what happens depend on
>> how
>> the driver decides it's at an MS test lab (who only care about crashes) or
>> on a magazine/user's machine.
>> --
>> ----------------------------------------------------------
>>
>> "Bruce Roberson" <Bruceroberson@cox-internet.com> wrote in message
>> news:te7_d.39226$3z.9722@okepread03...
>>> Thanks David, I may have isolated the problem, by seeing the message that
>>> a
>>> service called mrtrate service failed to start due to the following
>>> error:
>>> The system cannot find the file specified. Then, I went out and did a
>>> search
>>> for this condition; it was apparently related to Quicken 2004 Deluxe
>>> which
>>> I've been running for some time. There was a fix to change a value in the
>>> registry for it after backing it up which I did. Then, I rebooted and the
>>> error did not reoccur.
>>>
>>> What gets me is the erratic behavior of this error. If this is the real
>>> culprit, then sometimes the system booted into windows fine the first
>>> time,
>>> and other times, it stopped with the sorry message, and its various
>>> options
>>> for continuing. I've been screwing with MSconfig options now probably for
>>> a
>>> month, with still this intermittent situation.
>>>
>>> I probably won't know for three or four days for sure if this was the fix
>>> or
>>> not. I sure hope so after all this effort.
>>>
>>> Thanks again,
>>>
>>>
>>> Bruce
>>>
>>>
>>> "David Candy" <.> wrote in message
>>> news:OnyK9upKFHA.3652@TK2MSFTNGP10.phx.gbl...
>>> The error messages. Nothing else matters but the error messages. Event
>>> Viewer should have the Stop error involved.
>>>
>>> --
>>> ----------------------------------------------------------
>>>
>>> "Bruce Roberson" <bruceroberson@cox.net> wrote in message
>>> news
😛G4_d.39215$3z.24464@okepread03...
>>>> None of the hardware components are malfunctioning at all.. It just
>>>> gives
>>>> that stupid screen at bootup on a random, not continuous basis. I have
>>>> experimented now for a month almost.
>>>>
>>>> I have gone into the device manager and checked for hardware conflicts
>>>> using
>>>> msinfo32 or whatever that is. It did not show any conflicts. Again, this
>>>> happens randomly at bootup, and then the computer behaves fine after it
>>>> gets
>>>> into Windows.
>>>>
>>>> I would just like to figure out an approach to solve the problem.
>>>>
>>>> Any other ideas?
>>>>
>>>> Bruce
>>>> "Walter Clayton" <w-claytonNO@SPmvps.AMorg> wrote in message
>>>> news:u$HClOoKFHA.4092@tk2msftngp13.phx.gbl...
>>>>> You're looking in the wrong place.
>>>>>
>>>>> It's perfectly normal for the system to decide not to load a driver if
>>>>> the
>>>>> hardware doesn't need the driver or some other function doesn't need
>>>>> the
>>>>> driver.
>>>>>
>>>>> Look to your hardware first. Suspect, although not in any particular
>>>>> order, power supply, memory, processor; don't rule out other components
>>>>> either.
>>>>>
>>>>> --
>>>>> Walter Clayton
>>>>> Any technology distinguishable from magic is insufficiently advanced.
>>>>>
http://www.dts-l.org
>>>>>
>>>>>
>>>>> "Bruce Roberson" <Bruceroberson@cox-internet.com> wrote in message
>>>>> news:lMVZd.38174$3z.25652@okepread03...
>>>>>> This is an excerpt from the file ntbtlog.txt showing the drivers not
>>>>>> loaded. How can I figure how to eliminate these specific problem
>>>>>> areas.
>>>>>> Once every two or three days, I get the screen at bootup saying
>>>>>> Windows
>>>>>> faile to load normally, and I get to choose between using the "last
>>>>>> known
>>>>>> good configuration" or a normal windows load. Its a black screen with
>>>>>> white text etc. I figured out how to find the bootlog file
>>>>>> ntbtlog.txt,
>>>>>> but now that I see the offending drivers, I don't know what they are
>>>>>> to
>>>>>> know what to do to keep them from being a problem.
>>>>>>
>>>>>> Here are the offending lines:
>>>>>>
>>>>>> Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
>>>>>> Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
>>>>>> Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
>>>>>> Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
>>>>>> Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
>>>>>> Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\kbdhid.sys
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\serial.sys
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\processr.sys
>>>>>> Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\rdbss.sys
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
>>>>>> Did not load driver \SystemRoot\System32\Drivers\mrtRate.SYS
>>>>>> Did not load driver \SystemRoot\System32\DRIVERS\ipnat.sys
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Facebook
Twitter
Instagram