I'm running a Windows Server 2003 on pretty much standard HW (Dell PE1850
server connected to a RAID array) for the purpose of file serving. The server
had been running fine for almost a year, and still is, but other day it
crashed (rebooted) leaving this message in the Event Log.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e
(0xc0000005, 0x00000014, 0xf7906c5c, 0xf7906958). A dump was saved in:
C:\WINDOWS\MEMORY.DMP.

Also an error report on the first logon said: "You received this message
because a device driver installed on your computer caused the Windows
operating system to stop unexpectedly. This type of error is referred to as a
"stop error." A stop error requires you to restart your computer"

Following the advice of some KB articles I used the Windows DebuggingTools
(specifically the WinDbg GUI) to analyze my memory dump after having
installed the latest symbols from the Microsoft Website. The analysis report
said in the end:

Probably caused by : EraserUtilDrv1061.sys ( EraserUtilDrv1061+ea1e )

I could not find any info on this Driver on the Web. Can anyone help?

Also do you know of any tools I can run to make sure all my drivers are OK
and stable.

Any help is greatly appreciated.

Thank you,

--
James

According to Google that's a Symantec driver. If you have any Symantec
software on this system check for driver updates for Win2K3, and make
sure these apps are compatible with Win2K3.

"James McGill" <(E-Mail Removed)> wrote in message news:3FA22B11-9549-4E72-A5EF-(E-Mail Removed)...
> I'm running a Windows Server 2003 on pretty much standard HW (Dell PE1850
> server connected to a RAID array) for the purpose of file serving. The server
> had been running fine for almost a year, and still is, but other day it
> crashed (rebooted) leaving this message in the Event Log.
>
> The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e
> (0xc0000005, 0x00000014, 0xf7906c5c, 0xf7906958). A dump was saved in:
> C:\WINDOWS\MEMORY.DMP.
>
> Also an error report on the first logon said: "You received this message
> because a device driver installed on your computer caused the Windows
> operating system to stop unexpectedly. This type of error is referred to as a
> "stop error." A stop error requires you to restart your computer"
>
> Following the advice of some KB articles I used the Windows DebuggingTools
> (specifically the WinDbg GUI) to analyze my memory dump after having
> installed the latest symbols from the Microsoft Website. The analysis report
> said in the end:
>
> Probably caused by : EraserUtilDrv1061.sys ( EraserUtilDrv1061+ea1e )
>
> I could not find any info on this Driver on the Web. Can anyone help?
>
> Also do you know of any tools I can run to make sure all my drivers are OK
> and stable.
>
> Any help is greatly appreciated.
>
> Thank you,
>
> --
> James

Thank you. The strange thing is that the file "EraserUtilDrv1061.sys" does
not exist on my machine, even though I have SAV client security installed on
it. I am now doubting the results of the crash analysis.

Either way, I updated the SAV client to the latest version, but I don't
think that changed the drivers. I'll try to contact Symantec about this.

Ok but what about tools that can check the drivers and warn about poteential
problems? Do you know of any?

Thanks
--
James


"Glen" wrote:

> According to Google that's a Symantec driver. If you have any Symantec
> software on this system check for driver updates for Win2K3, and make
> sure these apps are compatible with Win2K3.
>
> "James McGill" <(E-Mail Removed)> wrote in message news:3FA22B11-9549-4E72-A5EF-(E-Mail Removed)...
> > I'm running a Windows Server 2003 on pretty much standard HW (Dell PE1850
> > server connected to a RAID array) for the purpose of file serving. The server
> > had been running fine for almost a year, and still is, but other day it
> > crashed (rebooted) leaving this message in the Event Log.
> >
> > The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e
> > (0xc0000005, 0x00000014, 0xf7906c5c, 0xf7906958). A dump was saved in:
> > C:\WINDOWS\MEMORY.DMP.
> >
> > Also an error report on the first logon said: "You received this message
> > because a device driver installed on your computer caused the Windows
> > operating system to stop unexpectedly. This type of error is referred to as a
> > "stop error." A stop error requires you to restart your computer"
> >
> > Following the advice of some KB articles I used the Windows DebuggingTools
> > (specifically the WinDbg GUI) to analyze my memory dump after having
> > installed the latest symbols from the Microsoft Website. The analysis report
> > said in the end:
> >
> > Probably caused by : EraserUtilDrv1061.sys ( EraserUtilDrv1061+ea1e )
> >
> > I could not find any info on this Driver on the Web. Can anyone help?
> >
> > Also do you know of any tools I can run to make sure all my drivers are OK
> > and stable.
> >
> > Any help is greatly appreciated.
> >
> > Thank you,
> >
> > --
> > James
>
>
>

A generic one? No. There's such a bewildering array of possible hardware
and drivers I doubt a utility like that exists. There are registry checkers, but
they cause more problems than they solve most of the time.

"James McGill" <(E-Mail Removed)> wrote in message news20CA178-7D1E-4081-A1B8-(E-Mail Removed)...
> Thank you. The strange thing is that the file "EraserUtilDrv1061.sys" does
> not exist on my machine, even though I have SAV client security installed on
> it. I am now doubting the results of the crash analysis.
>
> Either way, I updated the SAV client to the latest version, but I don't
> think that changed the drivers. I'll try to contact Symantec about this.
>
> Ok but what about tools that can check the drivers and warn about poteential
> problems? Do you know of any?
>
> Thanks
> --
> James
>
>
> "Glen" wrote:
>
> > According to Google that's a Symantec driver. If you have any Symantec
> > software on this system check for driver updates for Win2K3, and make
> > sure these apps are compatible with Win2K3.
> >
> > "James McGill" <(E-Mail Removed)> wrote in message news:3FA22B11-9549-4E72-A5EF-(E-Mail Removed)...
> > > I'm running a Windows Server 2003 on pretty much standard HW (Dell PE1850
> > > server connected to a RAID array) for the purpose of file serving. The server
> > > had been running fine for almost a year, and still is, but other day it
> > > crashed (rebooted) leaving this message in the Event Log.
> > >
> > > The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e
> > > (0xc0000005, 0x00000014, 0xf7906c5c, 0xf7906958). A dump was saved in:
> > > C:\WINDOWS\MEMORY.DMP.
> > >
> > > Also an error report on the first logon said: "You received this message
> > > because a device driver installed on your computer caused the Windows
> > > operating system to stop unexpectedly. This type of error is referred to as a
> > > "stop error." A stop error requires you to restart your computer"
> > >
> > > Following the advice of some KB articles I used the Windows DebuggingTools
> > > (specifically the WinDbg GUI) to analyze my memory dump after having
> > > installed the latest symbols from the Microsoft Website. The analysis report
> > > said in the end:
> > >
> > > Probably caused by : EraserUtilDrv1061.sys ( EraserUtilDrv1061+ea1e )
> > >
> > > I could not find any info on this Driver on the Web. Can anyone help?
> > >
> > > Also do you know of any tools I can run to make sure all my drivers are OK
> > > and stable.
> > >
> > > Any help is greatly appreciated.
> > >
> > > Thank you,
> > >
> > > --
> > > James
> >
> >
> >