Re: BSOD Stop 0x00000019

What are your answers to my questions?

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Virgilijus wrote:
I ran the memtest for way over 2 hours and there were NO errors at
all. Any other suggestions??

Thanks for all of the help.



"Paul" wrote:

Gerry wrote:
Does the computer boot? Do the errors occuring during or after the
boot process? How often are these errors occuring? Do the errors
occur in safe mode as well as normal mode?

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793223.aspx

A pool header issue is a problem with Windows memory allocation.
Device driver issues are probably the most common, but this can
have diverse causes including bad sectors or other disk write
issues, and problems with some routers. (By theory, RAM problems
would be suspect for memory pool issues, but I haven't been able to
confirm this as a cause.) Source: http://aumha.org/a/stop.htm

Are there any yellow question marks in Device Manager? Right click
on the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not
checked.

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Virgilijus wrote:
I have been getting a BSOD with Stop 0x00000019 with the
parameters of (0x00000020,0xE38B5740,0xE38B5760,0x0C040201). I
have not installed any new hardware in the last 3 months and this
has only started in the last week. Any suggestions as to what is
causing this??

Thanks



You can get memtest86+ from memtest.org . Versions of the program
are available to make a boot floppy or a boot CD. Memtest will run
forever, until you press <esc> to stop it, and reboot the machine.
At which time, you remove the Memtest floppy or CD from the drive.

Chances are, there is a single stubborn bit in one of the sticks
of memory, which can no longer be written. In which case, when you
examine the error log on the memtest screen, the same address
should be involved with each error reported.

The only parts of memory, which memtest cannot test, is the parts
reserved by the BIOS.

Paul


.

Relevant Pages

  • Re: Problem with 865PE chipset and Dual Channel DDR
    ... I assume that your boot partition is not FAT? ... It runs fine with 1GB memory in everything ... It's when you set the RAM sticks in the Dual Channel configuration. ... > memtest upon the new 1 GB memory configuration to see if the new ...
    (comp.os.os2.misc)
  • Re: memtest+ wont load SOLVED
    ... causing random hard-locks of my debian sid machine. ... I've tried to boot into memtest from ... Download and Burn the ultimate boot cd: ... Run the memory tests tests from it. ...
    (Debian-User)
  • Re: system crash
    ... "rudy" wrote ... from cd boot and it will not make it thru an entire run. ... the computer is 3 years old, not sure of memory life expectancy. ...
    (microsoft.public.windowsxp.general)
  • Re: System_service_exception error on vista
    ... Unless there is a limit to the memtest capability, you do have memory ... and i hit yes to display crash log and it doesn't pop anything up. ... I used the registry mechanic to look through my event logs. ...
    (microsoft.public.windows.vista.performance_maintenance)
  • Re: Can someone else help? Was changing partition size.
    ... I tried the supposed fix to make Windows 98SE boot up with more ... than a gig of memory but that has not worked either. ... The last time I did that set of changes, it was done by using a Linux LiveCD ... and finish the Win98 install. ...
    (microsoft.public.windowsxp.general)