Windows 7 BSOD with error ACPI.sys drive DRIVER_IRQL_NOT_LESS_OR_EQUAL

[Sam1886]

Hi Support,

My system BSOD with error "DRIVER_IRQL_NOT_LESS_OR_EQUAL", below is the debug report of dump file. Any advise?


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Stephen_Jamison_MEMORY_DUMP\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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4d6d0
Debug session time: Mon Sep 9 08:37:04.831 2013 (UTC - 4:00)
System Uptime: 3 days 16:57:38.180
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {5b8b3e, 2, 0, 8004}

Probably caused by : ACPI.sys ( ACPI!ACPIDeviceWorkerThread+b7 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000005b8b3e, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: 0000000000008004, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 00000000005b8b3e

CURRENT_IRQL: 2

FAULTING_IP:
+3336646334353561
00000000`00008004 ?? ???

PROCESS_NAME: System

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff80002a7f129 to fffff80002a7fb80

STACK_TEXT:
fffff880`037bf8c8 fffff800`02a7f129 : 00000000`0000000a 00000000`005b8b3e 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`037bf8d0 fffff800`02bb3d0e : fffff880`03375f40 00000000`00008004 fffff880`00fc0f00 00000000`00000801 : nt!KiBugCheckDispatch+0x69
fffff880`037bfa10 5254535f`000007ff : fffff880`00fc0f7c fffffa80`0de55355 fffffa80`0fa71400 00000000`00000801 : nt!ExAllocatePoolWithTag+0xfe
fffff880`037bfb00 fffff880`00fc0f7b : fffffa80`0de55355 fffffa80`0fa71400 00000000`00000801 fffff880`03375f40 : 0x5254535f`000007ff
fffff880`037bfb08 fffffa80`0de55355 : fffffa80`0fa71400 00000000`00000801 fffff880`03375f40 5254535f`000007ff : ACPI!ACPIDeviceWorkerThread+0xb7
fffff880`037bfb10 fffffa80`0fa71400 : 00000000`00000801 fffff880`03375f40 5254535f`000007ff fffff880`00fc0f7c : 0xfffffa80`0de55355
fffff880`037bfb18 00000000`00000801 : fffff880`03375f40 5254535f`000007ff fffff880`00fc0f7c fffffa80`0d7325da : 0xfffffa80`0fa71400
fffff880`037bfb20 fffff880`03375f40 : 5254535f`000007ff fffff880`00fc0f7c fffffa80`0d7325da 00000000`00008000 : 0x801
fffff880`037bfb28 5254535f`000007ff : fffff880`00fc0f7c fffffa80`0d7325da 00000000`00008000 fffffa80`0d7325d0 : 0xfffff880`03375f40
fffff880`037bfb30 fffff880`00fc0f7b : fffffa80`0d7325da 00000000`00008000 fffffa80`0d7325d0 fffff880`03375f40 : 0x5254535f`000007ff
fffff880`037bfb38 fffffa80`0d7325da : 00000000`00008000 fffffa80`0d7325d0 fffff880`03375f40 00000000`00008004 : ACPI!ACPIDeviceWorkerThread+0xb7
fffff880`037bfb40 00000000`00008000 : fffffa80`0d7325d0 fffff880`03375f40 00000000`00008004 fffff880`00fc0f7c : 0xfffffa80`0d7325da
fffff880`037bfb48 fffffa80`0d7325d0 : fffff880`03375f40 00000000`00008004 fffff880`00fc0f7c fffffa80`0fa713fe : 0x8000
fffff880`037bfb50 fffff880`03375f40 : 00000000`00008004 fffff880`00fc0f7c fffffa80`0fa713fe 00000000`00008000 : 0xfffffa80`0d7325d0
fffff880`037bfb58 00000000`00008004 : fffff880`00fc0f7c fffffa80`0fa713fe 00000000`00008000 fffffa80`0fa713f0 : 0xfffff880`03375f40
fffff880`037bfb60 fffff880`00fc0f7b : fffffa80`0fa713fe 00000000`00008000 fffffa80`0fa713f0 00000000`00008004 : 0x8004
fffff880`037bfb68 fffffa80`0fa713fe : 00000000`00008000 fffffa80`0fa713f0 00000000`00008004 fffff880`00fc0f7c : ACPI!ACPIDeviceWorkerThread+0xb7
fffff880`037bfb70 00000000`00008000 : fffffa80`0fa713f0 00000000`00008004 fffff880`00fc0f7c 00000000`00000000 : 0xfffffa80`0fa713fe
fffff880`037bfb78 fffffa80`0fa713f0 : 00000000`00008004 fffff880`00fc0f7c 00000000`00000000 00000000`00008000 : 0x8000
fffff880`037bfb80 00000000`00008004 : fffff880`00fc0f7c 00000000`00000000 00000000`00008000 fffff880`03375f40 : 0xfffffa80`0fa713f0
fffff880`037bfb88 fffff880`00fc0f7b : 00000000`00000000 00000000`00008000 fffff880`03375f40 fffffa80`0b8fb123 : 0x8004
fffff880`037bfb90 00000000`00000000 : 00000000`00008000 fffff880`03375f40 fffffa80`0b8fb123 fffffa80`0b8fb110 : ACPI!ACPIDeviceWorkerThread+0xb7


STACK_COMMAND: kb

FOLLOWUP_IP:
ACPI!ACPIDeviceWorkerThread+b7
fffff880`00fc0f7b cc int 3

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: ACPI!ACPIDeviceWorkerThread+b7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ACPI

IMAGE_NAME: ACPI.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79294

FAILURE_BUCKET_ID: X64_0xD1_ACPI!ACPIDeviceWorkerThread+b7

BUCKET_ID: X64_0xD1_ACPI!ACPIDeviceWorkerThread+b7

Followup: MachineOwner
---------

2: kd> lmvm ACPI
start end module name
fffff880`00fa6000 fffff880`00ffd000 ACPI (pdb symbols) c:\websymbols\acpi.pdb\4CCAFC55779D45F49D63AD1C8D245D701\acpi.pdb
Loaded symbol image file: ACPI.sys
Image path: \SystemRoot\system32\drivers\ACPI.sys
Image name: ACPI.sys
Timestamp: Sat Nov 20 04:19:16 2010 (4CE79294)
CheckSum: 0005ACF6
ImageSize: 00057000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[hairlessupportmonkey]

Firstly, we are not your support We are professionals that give up a bit of free time helping other professionals out.

Any advise for the above?

You havent really told us much. the last time I saw this ACPI blue screen was when I installed slysofts virtual clone drive.

what is new on your PC recently? if nothing, I suggest re-installing SP1 and that sometimes restores broken files.

ACSS - SME
General Geek

 

[Sam1886]

Hi,

Thanks for your time and reply, i will going to re-apply SP1 again after taking backup of all my IMP stuff, thank I will keep posting.