 | |
| |
| 08 Jun 2012 | #1 |
| | BSOD ntkrnlmp.exe : IRQL_NOT_LESS_OR_EQUAL (a) I have a BSOD of Death that seems to occur all the time on a Windows 7 Machine. The Machine is Microsoft Windows 7 Professional x64 SP1 I have 4GB of ram installed DDR3, Nothing has been installed new wise, however since this has been happening i have Updated Drivers. HP ProBook 4530s Please see the Mini.Dmp file. Please can someone help me Code: Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Ticket 64624\New\060812-14211-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`03095650 Debug session time: Fri Jun 8 15:33:29.919 2012 (UTC + 1:00) System Uptime: 0 days 6:13:07.965 Loading Kernel Symbols ............................................................... ................................................................ ................................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {40, 2, 1, fffff80002edc188} Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000040, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff80002edc188, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ff100 0000000000000040 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTryUnwaitThread+28 fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff8800318c230 -- (.trap 0xfffff8800318c230) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000003 rbx=0000000000000000 rcx=fffff88003164180 rdx=fffffa80045f04d8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002edc188 rsp=fffff8800318c3c0 rbp=0000000000000000 r8=0000000000000100 r9=0000000000000000 r10=00000000000000ec r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiTryUnwaitThread+0x28: fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:9dc0:00000000`00000040=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecd229 to fffff80002ecdc80 STACK_TEXT: fffff880`0318c0e8 fffff800`02ecd229 : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0318c0f0 fffff800`02ecbea0 : 00000000`00000002 fffffa80`0ce90080 fffffa80`041696c0 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0318c230 fffff800`02edc188 : 00000000`0022275c 00000000`00222696 fffff880`03164180 fffff880`03164100 : nt!KiPageFault+0x260 fffff880`0318c3c0 fffff800`02f2707b : fffffa80`045f66d8 00000000`00000000 00000000`00000000 fffffa80`045f66d0 : nt!KiTryUnwaitThread+0x28 fffff880`0318c420 fffff800`02ed879d : fffffa80`045f66d0 fffffa80`04310c68 fffffa80`04310c68 00000000`00004202 : nt! ?? ::FNODOBFM::`string'+0xb510 fffff880`0318c4a0 fffff800`02ed86de : 00000034`20446814 fffff880`0318cb18 00000000`0015e5ec fffff880`03168308 : nt!KiProcessExpiredTimerList+0x6d fffff880`0318caf0 fffff800`02ed84c7 : 0000000b`add9e1c7 0000000b`0015e5ec 0000000b`add9e17c 00000000`000000ec : nt!KiTimerExpiration+0x1be fffff880`0318cb90 fffff800`02ec598a : fffff880`03164180 fffff880`0316efc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff880`0318cc40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTryUnwaitThread+28 fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiTryUnwaitThread+28 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55 FAILURE_BUCKET_ID: X64_0xA_nt!KiTryUnwaitThread+28 BUCKET_ID: X64_0xA_nt!KiTryUnwaitThread+28 Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * 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: 0000000000000040, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, 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: fffff80002edc188, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: 0000000000000040 CURRENT_IRQL: 2 FAULTING_IP: nt!KiTryUnwaitThread+28 fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff8800318c230 -- (.trap 0xfffff8800318c230) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000003 rbx=0000000000000000 rcx=fffff88003164180 rdx=fffffa80045f04d8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002edc188 rsp=fffff8800318c3c0 rbp=0000000000000000 r8=0000000000000100 r9=0000000000000000 r10=00000000000000ec r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiTryUnwaitThread+0x28: fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:9dc0:00000000`00000040=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002ecd229 to fffff80002ecdc80 STACK_TEXT: fffff880`0318c0e8 fffff800`02ecd229 : 00000000`0000000a 00000000`00000040 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`0318c0f0 fffff800`02ecbea0 : 00000000`00000002 fffffa80`0ce90080 fffffa80`041696c0 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`0318c230 fffff800`02edc188 : 00000000`0022275c 00000000`00222696 fffff880`03164180 fffff880`03164100 : nt!KiPageFault+0x260 fffff880`0318c3c0 fffff800`02f2707b : fffffa80`045f66d8 00000000`00000000 00000000`00000000 fffffa80`045f66d0 : nt!KiTryUnwaitThread+0x28 fffff880`0318c420 fffff800`02ed879d : fffffa80`045f66d0 fffffa80`04310c68 fffffa80`04310c68 00000000`00004202 : nt! ?? ::FNODOBFM::`string'+0xb510 fffff880`0318c4a0 fffff800`02ed86de : 00000034`20446814 fffff880`0318cb18 00000000`0015e5ec fffff880`03168308 : nt!KiProcessExpiredTimerList+0x6d fffff880`0318caf0 fffff800`02ed84c7 : 0000000b`add9e1c7 0000000b`0015e5ec 0000000b`add9e17c 00000000`000000ec : nt!KiTimerExpiration+0x1be fffff880`0318cb90 fffff800`02ec598a : fffff880`03164180 fffff880`0316efc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff880`0318cc40 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiTryUnwaitThread+28 fffff800`02edc188 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KiTryUnwaitThread+28 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f558b55 FAILURE_BUCKET_ID: X64_0xA_nt!KiTryUnwaitThread+28 BUCKET_ID: X64_0xA_nt!KiTryUnwaitThread+28 Followup: MachineOwner --------- Last edited by Brink; 08 Jun 2012 at 11:13 AM.. Reason: code box |
My System Specs | |
| 08 Jun 2012 | #2 |
| | I recommend turning on Driver Verifier. Do not select the following checks: Force Pending I/O Requests, IRP Logging, and Low Resource Sim. Select all other checks. Make sure to restart system after you finish setup. If you experience a boot loop afterwards, go into Safe Mode by pressing F8 prior to Windows logo and disable DV there. When you happen to get a few crashes in afterwards, provide us a JCGriff Report as instructed here. |
| My System Specs |
 |
BSOD ntkrnlmp.exe : IRQL_NOT_LESS_OR_EQUAL (a) problems?
« BSOD in almost every action that i do Please read these dump files
|
BSOD occuring daily at random times »
| Thread Tools | |
| Similar help and support threads for: BSOD ntkrnlmp.exe : IRQL_NOT_LESS_OR_EQUAL (a) | ||||
| Thread | Forum | |||
 BSOD cause by ntkrnlmp.exe | BSOD Help and Support | |||
| bsod ntkrnlmp.exe | BSOD Help and Support | |||
| BSOD - ntkrnlmp.exe | BSOD Help and Support | |||
| BSOD ntkrnlmp.exe ??? HELP! | BSOD Help and Support | |||
All times are GMT -5. The time now is 06:09 AM.
