Link to home
Start Free TrialLog in
Avatar of ethernet69
ethernet69

asked on

Windows XP ntoskrnl.exe BSOD

Hello Everyone,
One of my clients got a BSOD and I was able to get this out of the minidump:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Wed Feb 16 07:43:23.437 2011 (UTC - 5:00)
System Uptime: 0 days 0:07:44.011


Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Has anyone seen this particular error before?
I would like to avoid reloading the OS if at all possible.

Avatar of pasolo
pasolo

ntoskrnl is for single processor machines, ntkrnlmp is for multiple processors machines. Hope this brings some light. Has the user upgraded the hardware?
Yes I have seen that error before. It may result from OS corruption and also may result from a hardware error causing OS corruption. I have not seen any way to fix this except to verify hardware and re-install the operating system.

You should be able to boot with a bootable CD and recover your data, but even this is not a given if there is a hardware problem.

... Thinkpads_User
That dump analysis is incomplete and close to useless. Could you please attach the minidump file itself here?
ASKER CERTIFIED SOLUTION
Avatar of davy999
davy999
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It kan also be a driver problem like video or wirelees netcard driver go into safemode and test for
a while.
Avatar of ethernet69

ASKER

these comments helped me narrow down what the potential issues are. The computer is very old and will probably be replaced.