"I have used the Driver verifier and the above driver has a probelm, since it keeps crashing when I test it using the verifier...."

I think you've drawn the wrong conclusions there as ntkrnlpa.exe is not a driver. Therefore, its integrity is not checked when you run the Microsoft Driver Verifier utility. What's probably happening is that when it encounters a corrupt driver, it crashes ntkrnlpa.exe. If ntkrnlpa.exe was corrupt then it's likely that Windows wouldn't work at all.

If you're talking about a different driver verifier then let us know which one it is.

Anyhow, regarding your random BSODs, download and run BlueScreenView which is a tool that'll hopefully identify the cause of your problem. In the top pane, double-click on the most recent entry to view the details in a new window. Copy and paste the following details:

Bug Check String

Parameters 1, 2, 3, and 4

Caused by driver

Check the other recent BSODs, and if they're not identical, post details for the last three occurrences.

"The system seems to crash with a "dump of physical memory " message. Any ideas?.."

When Windows suffers a catastrophic failure and displays a BSOD, information about the event is written to a file - that's what it's doing when you see the "dump of physical memory" message. That file is then saved on your PC so you can view the details with tools such as BlueScreenView.

......apologies for my previous post. I don't know how I missed it but ntkrnlpa.exe is listed as an XP driver in Driver Verifier so you can move on to the other parts of my post. Hopefully the information you provide will help determine the cause of your troublesome BSODs.

Thanks for all the advice, but I would add that you do not appear to be able to reove service pack 3 by the remove prog in the control panel, or am I missing something?.
I have downloaded the BlueScreenview and I will check the same once another dreaded BSOD oocurs

"I have downloaded the BlueScreenview and I will check the same once another dreaded BSOD oocurs"

There's no need to wait for a new BSOD as the previous ones should have been automatically saved on your PC ready for you to view at any time. Or are you saying that on opening BlueScreenView, its top pane is empty?

ntoskrnl is a core XP system file. If it was corrupt then your PC wouldn't work at all, so even though it's mentioned as the culprit, I think something else is causing your problems.

Because your problems started again after re-installing Windows, it could be a hardware problem. Here are a couple of things to try:

1) Do an XP disk check by right-clicking your C: drive icon in My Computer -> Properties -> "Tools" tab -> "Check Now" button. Tick both boxes and answer yes when it asks if you want to schedule the check for the next boot. Restart your PC and the check should start automatically. It could take a couple of hours or so on a large drive so be patient.

2) Check your PC's RAM. You can use Microsoft's Windows Memory Diagnostic bootable CD if you don't have any tools of your own. After creating your own CD, start the PC with it and the memory check will start automatically. Allow it to complete at least two passes. If it doesn't find anything then run the extended tests.