J
J.Fenton
I ran into a 0xA stop error at the very end of a w2k pro
boot cycle after installing W2K-SP4 on my cpu. The error
doesn't name a specific file as the problem. It does name
the memory address, and that ntoskrnl.exe with datestamp
3ee6c002 (a stamp reflecting an sp4 updated ntoskrnl.exe)
is affected. I did a kernel-dump and read it with latest
WinDBG. It would not show me the thread where the bugcheck
executed to narrow down what driver/process is faultering.
Any advice/ideas would be greatly appreciated.
JF
boot cycle after installing W2K-SP4 on my cpu. The error
doesn't name a specific file as the problem. It does name
the memory address, and that ntoskrnl.exe with datestamp
3ee6c002 (a stamp reflecting an sp4 updated ntoskrnl.exe)
is affected. I did a kernel-dump and read it with latest
WinDBG. It would not show me the thread where the bugcheck
executed to narrow down what driver/process is faultering.
Any advice/ideas would be greatly appreciated.
JF