	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.0

IRQL BSOD caused by ntkrpamp.exe

Asked by jtiernan2008 in Debugging Software for Development, Assembly Programming Language, Windows Vista

Please find the results of the kernal dump below.
The user has a laptop that keeps trowing this BSOD. Clean OEM system, new RAM and hdd.
RAM check done via memory diagnostics.
Can someone please advise :(

View the Solution FREE for 30 Days

         
           
             1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:
39:
40:
41:
42:
43:
44:
45:
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63:
64:
65:
66:
67:
68:
69:
70:
71:
72:
73:
74:
75:
76:
77:
78:
79:
80:
81:
82:
83:
84:
85:
86:
87:
88:
89:
90:
91:
92:
93:
94:
95:
96:
97:
98:
99:
100:
101:
102:
103:
104:
105:
106:
107:
108:
109:
110:
111:
112:
113:
114:
115:
116:
117:

           
           
             oading Dump File [C:\Users\Justin\Desktop\work\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
 
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81e42000 PsLoadedModuleList = 0x81f59c70
Debug session time: Wed May 27 12:30:54.771 2009 (GMT+1)
System Uptime: 0 days 23:29:16.564
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
 
Loading unloaded module list
..
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck A, {48f9f9cf, ff, 0, 81efdde2}
 
Probably caused by : ntkrpamp.exe ( nt!PpmCallIdleHandler+2c )
 
Followup: MachineOwner
---------
 
1: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 48f9f9cf, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 81efdde2, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS:  48f9f9cf 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
nt!PpmCallIdleHandler+2c
81efdde2 ff17            call    dword ptr [edi]
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0xA
 
PROCESS_NAME:  System
 
TRAP_FRAME:  803ecc7c -- (.trap 0xffffffff803ecc7c)
ErrCode = 00000000
eax=869c9b70 ebx=0003709c ecx=869c9d00 edx=00000000 esi=869c9ac0 edi=869c9bcc
eip=81efdde2 esp=803eccf0 ebp=803eccf8 iopl=0         nv up di ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010093
nt!PpmCallIdleHandler+0x2c:
81efdde2 ff17            call    dword ptr [edi]      ds:0023:869c9bcc={intelppm!MWaitIdle (8d6e74c0)}
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from 81efdde2 to 81e9cd24
 
STACK_TEXT:  
803ecc7c 81efdde2 badb0d00 00000000 00000f43 nt!KiTrap0E+0x2ac
803eccf8 81efdd32 869c9ac0 00000000 85c26568 nt!PpmCallIdleHandler+0x2c
803ecd50 81ef6ea1 00000000 0000000e 00000000 nt!PoIdle+0x2d1
803ecd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0xd
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!PpmCallIdleHandler+2c
81efdde2 ff17            call    dword ptr [edi]
 
SYMBOL_STACK_INDEX:  1
 
SYMBOL_NAME:  nt!PpmCallIdleHandler+2c
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrpamp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4
 
FAILURE_BUCKET_ID:  0xA_nt!PpmCallIdleHandler+2c
 
BUCKET_ID:  0xA_nt!PpmCallIdleHandler+2c
 
Followup: MachineOwner
---------

           
         

IRQL BSOD caused by ntkrpamp.exe

Asked by jtiernan2008 in Debugging Software for Development, Assembly Programming Language, Windows Vista

About this solution