Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD caused by ntkrnlpa.exe


  • Please log in to reply

#1
Relemar

Relemar

    Member

  • Member
  • PipPipPip
  • 108 posts
Im getting regular BSOD's from the file ntkrnlpa.exe. It sometimes happens on other files too, but mostly ntkrnlpa.exe. Im getting ever increasingly worried due to the fact this OS install is brand new (3 days) I formatted my XP and installed Vista Ultimate SP1.

I also built this sytem at Christmas, XFX 9800GTX+, Quad core q6600 2.4 ghz, 4gbram, new PSU and new mobo.

ive ran chkdsk
defrag
memtest86

cant seem to see the problem

Edited by Relemar, 13 January 2009 - 03:56 PM.

  • 0

Advertisements


#2
jcgriff2

jcgriff2

    Member

  • Expert
  • 90 posts
  • MVP

Im getting regular BSOD's from the file ntkrnlpa.exe. It sometimes happens on other files too, but mostly ntkrnlpa.exe. Im getting ever increasingly worried due to the fact this OS install is brand new (3 days) I formatted my XP and installed Vista Ultimate SP1.

I also built this sytem at Christmas, XFX 9800GTX+, Quad core q6600 2.4 ghz, 4gbram, new PSU and new mobo.

ive ran chkdsk
defrag
memtest86

cant seem to see the problem


Hi -

Sorry to hear of your BSOD situation.

A few questions first, please:
1. Since the approx 2-3 weeks since Christmas week when XP was running were there any problems at all?
2. Had you always planned to run Vista Ultimate on it (i.e., why run XP and not Vista 2-3 weeks ago)?
3. Was XP --> Vista Ultimate SP1 an upgrade from XP - or do you own full retail copy of Vista?
4. Are you running Vista x86 or x64?
5. What version XP were you running - XP Pro x64 or Home/Pro x86?
6. What XP Service Pack - SP3?
7. Did you obtain Vista compatible drivers for all devices?

The module that you mentioned ntkrnlpa.exe is a core component of the Vista NT Kernel. Unless the possibility exists that the Vista install is corrupt or your system is infected, the NT Kernel is not the actual cause of your BSODs. Potential hardware causes aside, the crashes are most likely the result of a rogue 3rd party driver that is hiding under the memory address range of NT at BSOD time.

I can take a look at the mini kernel dumps left behind by the BSODs and see what clues they yield. I'll need them and system information. Please follow THESE instructions. The max size for a single attachment is 500k. You should have ~1.5 - 2MB after they are zipped. Go into the resulting folder and split the files up - make 3 or 4 zip files and see if you can attach multiple zips to one post. If not, please send me a PM for my email address.

Regards. . .

jcgriff2

.
  • 0

#3
Relemar

Relemar

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 108 posts
1. I had a few BSODs while in game (Grand theft auto 4) but I believe that was just the game, as it didn't happen in any other game or while in windows.
2. No, I just wanted a change and wanted to be up to date (DX10 ftw)
3. I formatted and installed Windows Vista Ultimate.
4. 32bit (x84)
5. I was running XP Home.
6. SP3.
7. Yep, got all the right drivers.

I ran Ccleaner earlier today (or diskcleanup) so they've gone, when I next BSOD I will send you them.

PS: I've also noticed I BSOD when I run ConvertXtoDVD.......

i think its that application you know.. im not sure because I think ive had one before (but it happens when Im converting or defragging)

thanks for your reply, highly appreciate your professionalism and helpfulness mate :)

Edited by Relemar, 14 January 2009 - 03:29 PM.

  • 0

#4
jcgriff2

jcgriff2

    Member

  • Expert
  • 90 posts
  • MVP
Hi -

You're welcome - nothing except some typing done here yet, though!

Glad to hear that BSODs may be an isolated incident related to the one app. It was the mention of the NT Kernel core that caught my attention - and several BSODs. It very well could be this one app. I doubt that CCleaner (a product that I use) could do anything for a < week-old system to scare the BSODs away.

It is your call on what the next step is here. I don't think this is the end of them. If you would like to know what the bugchecks (STOP error codes) were, which may lead to an easy software fix (like a driver update) or it could lead no where, I can try and locate them within the info that I requested. Even w/o the dumps, they should be recorded elsewhere - the Event Viewer, WERCON (Problem Rpts & Solutions), or maybe another file gives us a clue to a more definitive cause.

Since no dumps available, you can try and create some by running the driver verifier, which will stress-test your non-MS drivers. If the verifier flags a driver, it will BSOD the system. To re-start, it may be necessary to run Windows System Restore or Vista System Repair. If this were my system and I had the chance to have it looked over - I would do it. No guarantees of course. But one never knows what another set of eyes can see.

To run the driver verifier - bring up an elevated administrative cmd/DOS prompt:
START | type cmd.exe | right-click on cmd.exe uptop under programs | Run as Administrator | type verifier & hit enter - the Verifier screen will appear | do the following:
1. Select 2nd option - Create custom settings (for code developers)
2. Select 2nd option - Select individual settings from a full list.
3. Check the boxes
	• Special Pool 
	• Pool Tracking 
	• Force IRQL checking
4. Select last option - Select driver names from a list 
5. Click on the Provider heading - sorts list by Provider
6. Check ALL boxes where Microsoft is not the Provider
7. Click on Finish 
8. Re-boot


Again... if the Driver Verifier (DV) finds a violation (flags a driver), it will result in a BSOD. To see the status of the D/Verifier, bring up an elevated cmd/DOS prompt and type verifier - select the last option on the first screen - "Display information about the currently verified drivers..". If your system becomes too unstable (the d/v utilizes CPU & RAM), turn d/v off - type verifier /reset then re-boot.

If you get a verifier-enabled BSOD, get the mini dump - go to \windows\minidump - copy it out, zip it up and attach.

Regards. . .

jcgriff2

.
  • 1

#5
Relemar

Relemar

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 108 posts
Crash dump from WhoCrashed;


On Thu 15/01/2009 07:37:50 your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xFFFFFFE8, 0x1, 0x81CA381C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.


I ran verifier, take a look;

Posted Image
  • 0

#6
Russ_T

Russ_T

    New Member

  • Member
  • Pip
  • 1 posts
Just wanted to thank you jcgriff2, I had never heard of verifier before.

You have save my colleague and I countless hours on a nightly blue screen. Turned out to be an old driver for a laser machine we emulate under windows 7.

I have passed your test on to my other friends in IT, I'm amazed we've never come across the driver verification process before.

Thank you again!
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP