Help with a STOP 000000D1 dump

[davetest]

Hello,
this system is very stable. However, I'm getting a repeatable
STOP error - here's the summary:
Filename . . . . . . .i:\winnt\minidump\mini072404-02.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x0407b000
PfnDataBase. . . . . .0x818d7000
PsLoadedModuleList . .0x8046e8f0
PsActiveProcessHead. .0x8046e728
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x000000d1
BugCheckParameter1 . .0x00000000
BugCheckParameter2 . .0x00000014
BugCheckParameter3 . .0x00000000
BugCheckParameter4 . .0x00000000

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x804690f3

This occurs when I attempt to use the Nero Infotool.
This is a tool included with Nero's burning program
that gives info on the drives and media.

According to the resource kit:
Interpreting the Message
This Stop message has four parameters:
Memory referenced.
1)IRQL at time of reference.
2)Type of access (0x00000000 = read operation, 0x00000001 = write
3)operation).
4)Address that referenced memory.

I suppose I could update Nero and see if it goes away,
but what's the general approach with a dump like this?
Particularly since bugcheckparameters 1 and 4 both contain zero.

Dave

 

[GHalleck]

davetest wrote:

I suppose I could update Nero and see if it goes away,
but what's the general approach with a dump like this?
Particularly since bugcheckparameters 1 and 4 both contain zero.

Dave

There has to be a starting point for everything. Just
what had been installed prior to the onset of this stop
error? It is usually a poorly written driver or one that
was improperly installed, esp. for a different OS. For
additional troubleshooting, see if there is a corresponding
Dr. Watson log file. It might indicate the application that
tripped the stop error.

 

[davetest]

davetest wrote:




There has to be a starting point for everything. Just
what had been installed prior to the onset of this stop
error? It is usually a poorly written driver or one that
was improperly installed, esp. for a different OS. For
additional troubleshooting, see if there is a corresponding
Dr. Watson log file. It might indicate the application that
tripped the stop error.

Hello - nothing was installed recently.
However, Nero was installed about 3 months ago, and this bugcheck
occurred the very first time I ran Nero's infotool - a couple
of days ago, and as I mentioned is repeatable.


I will look into drwatson -- I'd forgotten about it completely.

Dave

 

[davetest]

Hello - nothing was installed recently.
However, Nero was installed about 3 months ago, and this bugcheck
occurred the very first time I ran Nero's infotool - a couple
of days ago, and as I mentioned is repeatable.


I will look into drwatson -- I'd forgotten about it completely.

Dave

Well updating Nero to the latest didn't help.
I've used dumpchk to process the minidump, but so far,
looking at it, nothing obvious stands out.

Any tips appreciated.
Dave