Need help with BSOD mainly at startup, ntkrnlpa.exe error.

[cookie9123]

Hi,
Being new to this type of fix I am hoping that someone can help with debugging a BSOD error that keeps occurring on a laptop.

The laptop is a HP 250 Notebook PC running Windows 7 Professional 32bit. Full system details and minidump files are attached below.

I have tried using the Blue Screen View to diagnose the issue and it shows as a ntkrnlpa.exe error, but no other driver or explanation as to the cause/fix and SFC with no results.

Thanks in advance for any help that can be given.

Lee Cook.

 

[essenbe]

Hello, cookie9123 and welcome to Seven Forums. I will try to help you if I can. Unfortunately, you have a lot of dump files and none that I have checked is giving very much information. Fortunately, almost every one is the same, which means we most likely are looking for 1 problem and not several.

First I would like you to fill in your System Specs as completely as possible. I realize you are using an OEM laptop and system specs are a little more difficulkt to find, but as good as you can please, it helps us to be able to help you.

Please fill out your System Specs​

   Information

Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.

If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html​

If you can provide any further details, please do. If there is any program or activity that causes the BSOD please let me know.

Please run http://www.sevenforums.com/tutorials/433-disk-check.html
also Please run Seatools to check your Hard Drive.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Please let me know the results.

 

[cookie9123]

Hi,
Thank you for your help. I will update the Specs asap and run the checks requested. With regards to the check disk, does this just need to be the check only option or attempt recovery option etc.

Lee Cook

 

[essenbe]

I think just run the check first. Until we find out and you have backed up all of your personal files to an external source, I don't want to risk loss of files. The recovery does not usually do that, but better safe than sorry. So, first let's just see if there are any errors.

 

[cookie9123]

Hi ,
Sorry for the delay, it's been very hard to get access to the laptop over the last few days.

Regards,
Lee Cook

 

[cookie9123]

Hello,
I've run a check disk and no issues have been found. I will now run the sea tools and update the system info.

Regards,
Lee

 

[cookie9123]

Updated the specs, run the short and long check on the sea tools and no errors found.

 

[essenbe]

OK, are you still having BSODs? If so, please run the www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html#option2 again and please make sure your computer is configured for Small Memory Dumps. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

I apologize for being so late in responding, but we had leftover Thanksgiving dinner and someone spiked mine with sleeping pills.

 

[cookie9123]

No problem. I have amended the dump file settings and am now trying some restarts to try and get it to BS.

Regards,
Lee

 

[essenbe]

cookie9123, You have a whole bunch of dump files dating back to May. Every one of them is the same.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck F4[/COLOR], {3, 87dc4518, 87dc4684, 82e6dec0}
----- ETW minidump data unavailable-----
Probably caused by : [COLOR=red]csrss.exe[/COLOR]
Followup: MachineOwner

I know you ran Seatools and it said you passed. But, in my experience every time I have ever had a stop code of F4 blaming csrss.exe it has always been a storage device. I may suggest you run check disk http://www.sevenforums.com/tutorials/433-disk-check.html

This may be a first for me, but that is the way I see it. also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

 

[cookie9123]

Hi, I've been having difficulties getting access to the PC. I will update asap.

Regards,
Lee

 

[essenbe]

No problem, Lee. Just let us know whenever you can.

 

[cookie9123]

HI, I have run several SFC /scannow and check disk tests with all results showing no errors. The machine has crashed again since the 5th December. I have attached the new dump files, these are a little larger than the previous files has the laptop has been configured for small dump files.

Regards,
Lee

 

[essenbe]

Lee, the file you uploaded contain only files which are older than the first ones you sent. The one you uploaded, the latest dump file was 9-24,I believe. In the first dumps you uploaded, there were dumps in late November. Have you run some type of disk cleanup tool? most of them clean out error reports by default. Please make sure uour computer is configured for small memory dumps, http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

also, please run the BSOD posting instructions again. Try option 2 and press the 'grab all' button.
http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[cookie9123]

Hi,
The dump files were used using option one on that page. I will try the option 2. The latest dump files are attached as I copied them to my machine to make sure I had a copy.

Regards,
Lee

 

[essenbe]

This dump file had 3 dumps later than the original, however there was little new information I could get out of them because of the particular problem. The dumps were pretty much the same as the original ones.

CRITICAL_OBJECT_TERMINATION [COLOR=red](f4)[/COLOR]
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 87c07d40, Terminating object
Arg3: 87c07eac, Process image file name
Arg4: 82e60ec0, Explanatory message (ascii)

Do I understand correctly you ran checkdisk f/r and no errors were found and ran sfc /scannow and no integrity violations were forum?

I know you sais you ran Seatools, did you run the short and the long test? If not, please do so from a DOD bootable disk or USB flask drive. You will need to boot into the media you choose. These are the instructions http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

maybe it is just me, but I cannot believe it is anything other than a hard drive problem or possibly a virus. If this turns up nothing we will take a different course, but it will take time with the computer.

 

[cookie9123]

Hi,
What I'm going to do is start again with the testing. Just to confirm that all tests have been carried out. Can you confirm that the tests required are as below.
1. Check disk with the f/r switch.
2. SFC /scannow
3. Short Seatools test
4. Long seatools test

Just so you know, I have run several malware and AV scans with different products with no significant results.

I will post the results from the tests once I have them.

Thanks your help and time so far.

Regards,
Lee

 

[essenbe]

Lee some online scanners that I use. There may be more:

Kaspersky TDSSKiller:
Anti-rootkit utility TDSSKiller

ESET online scanner:
Free Virus Scan | Online Virus Scanner from ESET
Free Online Virus Scanner | ESET

Microsoft's Windows Defender Offline
http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html

I apologize if I am off base, but I have always said that a stop F4 was a storage problem. I just may be wrong. Here is something else you may try. Before doing anything, create a restore point, it may be your only way back. The tutorial of how to do it is in the link below. I would like you to run it for 24 hours of actual use, doing anything and everything you normally do. If there is anything that causes a BSOD Normally, do it a lot. The idea is to put stress on all Non-Microsoft drivers in hopes of causing the problematic one to cause a BSOD and catch it in the dump file. When you set it up, sort the drivers by provider. Select all drivers not provided by Microsoft. It will make the PC seem slow and sluggish, that is normal.

   Warning

Be sure to create a System Restore point before proceeding further http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[NoelDP]

The Event Logs show BIG problems with SOPHOS.

I would recommend uninstalling all Sophos software, and using the company's removal tools.
How to uninstall the Sophos Control Center
How to remove Sophos Endpoint Security and Control from client computers

As a temporary measure, install MSE as your AV - Microsoft Security Essentials - Microsoft Windows

 

[essenbe]

Thank you Noel, I guess I owe you again.