BSOD ntkrnlmp.exe

[Criz213]

Hello,

I have been having BSOD Problems a very long time. My computer has been shutting down frequently almost every day about 7 times a day. First I had problems with Ntfs.sys but I think that problem got fixed after posting another thread on this website. Also to mention someone told me to use Seatools For Windows, to examine my driver if it had problems but after I ran that examiner it said my driver passed the test which meaning that I do not have problems on my driver, but I don't know if that is true because I think my driver is having problems or I dont know if something else is wrong. But anyways now my computer has another problem I think, after my computer shut down a dialog box came up Saying Microsoft Recovered From an Unexpected Shutdown, I clicked view problem details and here are the details it said:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80001E66D07
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\Mini073112-01.dmp
C:\Users\cortez\AppData\Local\Temp\WER-215000-0.sysdata.xml
C:\Users\cortez\AppData\Local\Temp\WERADAC.tmp.version.txt

Read our privacy statement:
Privacy Statement for the Microsoft Error Reporting Service

Also I ran the JCGriffith Windows NT6 program, I have attached the minidumpfile below.

I also debugged my Vista to see more closely is my problem, I also have attached that. The image name problem is the one I typed in the title which is ntkrnlmp.exe

Also I have included .txt file of all the debugged info which is attached.

If you need anymore details please tell me :D!

My computer is a Windows Vista Home Premium x64 bit.. I need help please, ive been having this problem about 2 months already! :l

Thank you!

 

[richc46]

Welcome
Your report is corrupt, this is what we received

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp2_Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\Mini080712-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 , Win32 error 0n2
*** WARNING: Unable to verify timestamp for 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 
*** ERROR: Module load completed but symbols could not be loaded for 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`01e16000 PsLoadedModuleList = 0xfffff800`01fdadd0
Debug session time: Tue Aug  7 17:09:38.162 2012 (GMT-4)
System Uptime: 0 days 3:18:20.200
Unable to load image 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 , Win32 error 0n2
*** WARNING: Unable to verify timestamp for 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 
*** ERROR: Module load completed but symbols could not be loaded for 밑` 䈰Ƽ褐 䀸Ƽ褐 䑰ష婢 
Loading Kernel Symbols
.........................................
Loading User Symbols
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
....Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff80001e66d07, 0, ffffffffffffffff}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ?_?????????????? ( nt+50d07 )
Followup: MachineOwner
---------

The information provided is not enough to make an educated guess. If you get others submit to us.

Your other reports indicate a possible driver problem, we can begin with the driver verifier test, but Im not that hopeful.


Driver Verifier

I'd suggest that you firstbackup your data and then make sure you've got access to another computer soyou can contact us if problems arise. Then make a System Restore point (so youcan restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....AllPrograms...Maintenance...Create a System Repair Disc - with Windows Vistayou'll have to use your installation disk or the "Repair your computer"option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click"Next"
- Select "Select individual settings from a full list" and click"Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click"Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to useyour system normally, and if you know what causes the crash, do thatrepeatedly. The objective here is to get the system to crash because Driver Verifier isstressing the drivers out. If it doesn't crash for you, then let it run for atleast 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from yourinstallation DVD to set the system back to the previous restore point that youcreated.

DriverVerifier - Enable and Disable

 

[Criz213]

Hello Richc46 to figure out the ntkrnlmp.exe I reinstalled my Vista from scratch that problem is fixed. I updated to Windows Vista SP2 Pack, and updated my network adapter driver. But now sometimes it crashes and says this.

A problem has been detected and Windows has been shut down to prevent damage to your computer.

BAD_POOL_CALLER

If this is the first time you've seen this Stop screen error. Restart your computer check to make sure any hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer, for any Windows Updated you might need.

If problems continue, disable or remove any newly installed hardware or software, Disable BIOS memory options such as caching or shadowing. If you need to use Safe mode to remove or disable computer, press F8 to select advanced startup options and than select Safe Mode.

Than when I restarted my computer and booted it up, a Microsoft Windows Windows came up saying Windows has recovered from an unexpected shut down. Windows can check online for a solution, so I clicked problem details and here are the details it said:


Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 1033

Additional information about the problem:

BCCode: c2

BCP1: 0000000000000007

BCP2: 000000000000110B

BCP3: 0000000000000000

BCP4: FFFFFA800409CC20

OS Version: 6_0_6002

Service Pack: 2_0

Product: 768_1

Files that help describe the problem:

C:\Windows\Minidump\Mini081612-01.dmp

C:\Users\Cortez\AppData\Local\Temp\WER-99123-0.sysdata.xml

C:\Users\Cortez\AppData\Local\Temp\WER3E37.tmp.version.txt

Read our privacy statement:


Privacy Statement for the Microsoft Error Reporting Service



Please can you help me..

 

[Criz213]

And in when it turned to the bluescreen thing it also said this Technical Information:

***STOP : 0x000000c2 (0x0000000000000007, 0x000000000000110B, 0x0000000000000000, 0xFFFFFA800409cc20)

 

[richc46]

I truly want to give you the most help that I can, and to do so I need the information that was uploaded in your first post, for each BSOD.

 

[Criz213]

Okay I have attached the Seven Forums thing on here, right now.

 

[richc46]

Thank you for the two reports. Each was different, (but this is common), but were similar in certain respects.
The common elelments suggest.
That you:
Test your hard drive run a full chkdsk (that corrects errors) and the test below.
Run a full anti virus scan and then download and make a full scan with malwarebytes
be sure both are updated
Make sure that you have SP2 and all updates.

Test Hard Drive

Hard drive scan usings SeaTools - SeaToolsfor Windows | Seagate - Both long and shorttests