General discussion

Locked

bsod

By jackorama ·
it started last week ... couple times a day, on our PDC we receive BSOD with 0x0a and ntoskrnl.exe. there are no errors logged except that the shutdown was unexpected. i have researched Technet with no successful solution. majority of the search results for 0x0a with ntoskrnl.exe errors had the solution to upgrade to latest service pack. when the error started last week, we were at SP4 and i have upgraded to the latest SP6a, but the problem has not been resolved. i ran a quick diagnostics on the hardware and it came up clean. i didn't perform an exhaustive diagnostics as it would take a very long time. i am going to swap memory tonight to rule out bad memory, but in the meantime, i would appreciate any other ideas and pointers.

Compaq Proliant 5500, 2 Pentium Pro processors at 200 Mhz., NT 4.0, SP6a, DHCP, WINS, file server, print server (mostly HP printers, about 50 Intel Netports, and two Lexmarks setup on LPR print queue), Legato Networker backup and Trend ServerProtect. no new hardware has been add

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

bsod

by calves In reply to bsod

It seems you're on top of things there.

A couple ideas from past experience, might help.
Did you unistall any software that might run as a service in the past?
Is your IE up-to-date with all the patches? (IE is an integral part of the OS)
Is your WINS working OK? do you cleanup on a regular basis?
Is the Printer Spooler doing OK? Does it give trouble often and lately?
One other thing I would check is my NIC(s), this little guys can cause more trouble than often we realize. If you can, try a different NIC too.

Good Luck, and feel free to email me, I don't know if I can help, but...

Collapse -

bsod

by jackorama In reply to bsod

The question was auto-closed by TechRepublic

Collapse -

bsod

by Steve Cody In reply to bsod

I haven't researched the STOP 0x0a error, but, maybe this will help.

You might be having a heat problem. Since it is a dual proc. system, there's can be some serious heat in the case. Check out the fan(s) inside the case, and also CPU fans if it has them.

The Microsoft KB article Q183169 is for "Possible resolutions for Stop 0x0a errors". You may have some bad RAM, but heat is the first thing I would check.

Hope this helps.

- Steve

Collapse -

bsod

by jackorama In reply to bsod

The question was auto-closed by TechRepublic

Collapse -

bsod

by jackorama In reply to bsod

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums