O
Ozo
I get frequent blue screens with a message like that:
Stop 0x0000001e (c000009a xxxxxxx xxxxxxxx xxxxxxxx)
Unhandled Kernel exception xxxxxxxx from xxxxxxx
Address has base at xxxxxxxx ntoskrnl.exe
From what I can find on Microsoft website, the c000009a code means
STATUS_INSUFFICIENT_RESOURCES. If I understand correctly, that means
ntoskrnl.exe tried to allocate some memory in kernel space and ran out
of memory. However, I have problems getting more precise details (ex:
what type of memory?). Is there something useful to do with the other
hexadecimal numbers? Ate the other 3 numbers in the parenthesis any
useful?
I am running Windows 2000 SP4 on a dual Xeons system. I get this
problem way after everything is booted; Sometimes my application is
running for 30 minutes (or more) when the blue screen occurs. Since I
have one custom designed device drivers installed, I guess one
possibility is that this driver is leaking. But assuming the drivers
are OK, is it possible that using Win32 alone makes Windows leak by
itself?
Note that all numbers that I can not remember are replaced with x's (I
do not have access to this computer today).
Any help is welcome,
Thanks.
Ozo.
Stop 0x0000001e (c000009a xxxxxxx xxxxxxxx xxxxxxxx)
Unhandled Kernel exception xxxxxxxx from xxxxxxx
Address has base at xxxxxxxx ntoskrnl.exe
From what I can find on Microsoft website, the c000009a code means
STATUS_INSUFFICIENT_RESOURCES. If I understand correctly, that means
ntoskrnl.exe tried to allocate some memory in kernel space and ran out
of memory. However, I have problems getting more precise details (ex:
what type of memory?). Is there something useful to do with the other
hexadecimal numbers? Ate the other 3 numbers in the parenthesis any
useful?
I am running Windows 2000 SP4 on a dual Xeons system. I get this
problem way after everything is booted; Sometimes my application is
running for 30 minutes (or more) when the blue screen occurs. Since I
have one custom designed device drivers installed, I guess one
possibility is that this driver is leaking. But assuming the drivers
are OK, is it possible that using Win32 alone makes Windows leak by
itself?
Note that all numbers that I can not remember are replaced with x's (I
do not have access to this computer today).
Any help is welcome,
Thanks.
Ozo.