Been having BSOD problems for a while and whenever I think I figure it out, it comes back again. Here is my last dumpcheck.
With the IRQL not less or equal I tried going in to my bios and changed the setting to allow XP to assign IRQ and thought that would fix it. Was that worth a shot or is that screwing it up more? This problem occured after I tried that. Please help! Thanks, Mike
*******************************************************************************
* *
* 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: 00000001, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e5e03, address which referenced memory
Debugging Details:
------------------
WORKER_ROUTINE:
+1
00000001 ?? ???
WORK_ITEM: 804e5e03
CURRENT_IRQL: 1c
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: csrss.exe
MISALIGNED_IP:
nt!KeSetEvent+40
804e5e03 00ff add bh,bh
LAST_CONTROL_TRANSFER: from bf874614 to 804e5e03
STACK_TEXT:
f60db938 bf874614 00000000 00000000 00000000 nt!KeSetEvent+0x40
f60db97c bf873536 004d5cfe 85c5eda8 f60db9d4 win32k!ProcessMouseInput+0x1b1
f60db98c 804f6784 e1252b98 e1252bc0 00000000 win32k!InputApc+0x4e
f60db9d4 804f2df4 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f60db9ec 804e1b83 804e1a13 e120c008 00000000 nt!KiSwapThread+0xa8
f60dba24 bf807c70 00000003 85e4f9c0 00000001 nt!KeWaitForMultipleObjects+0x284
f60dba5c bf88964e 00000002 85e4f9c0 bf88c5dd win32k!xxxMsgWaitForMultipleObjects+0xb0
f60dbd30 bf87264d bf9aa5a0 00000001 f60dbd54 win32k!xxxDesktopThread+0x333
f60dbd40 bf80109a bf9aa5a0 f60dbd64 0074fff4 win32k!xxxCreateSystemThreads+0x6a
f60dbd54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f60dbd54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!ProcessMouseInput+1b1
bf874614 85db test ebx,ebx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k!ProcessMouseInput+1b1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
With the IRQL not less or equal I tried going in to my bios and changed the setting to allow XP to assign IRQ and thought that would fix it. Was that worth a shot or is that screwing it up more? This problem occured after I tried that. Please help! Thanks, Mike
*******************************************************************************
* *
* 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: 00000001, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e5e03, address which referenced memory
Debugging Details:
------------------
WORKER_ROUTINE:
+1
00000001 ?? ???
WORK_ITEM: 804e5e03
CURRENT_IRQL: 1c
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: csrss.exe
MISALIGNED_IP:
nt!KeSetEvent+40
804e5e03 00ff add bh,bh
LAST_CONTROL_TRANSFER: from bf874614 to 804e5e03
STACK_TEXT:
f60db938 bf874614 00000000 00000000 00000000 nt!KeSetEvent+0x40
f60db97c bf873536 004d5cfe 85c5eda8 f60db9d4 win32k!ProcessMouseInput+0x1b1
f60db98c 804f6784 e1252b98 e1252bc0 00000000 win32k!InputApc+0x4e
f60db9d4 804f2df4 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f60db9ec 804e1b83 804e1a13 e120c008 00000000 nt!KiSwapThread+0xa8
f60dba24 bf807c70 00000003 85e4f9c0 00000001 nt!KeWaitForMultipleObjects+0x284
f60dba5c bf88964e 00000002 85e4f9c0 bf88c5dd win32k!xxxMsgWaitForMultipleObjects+0xb0
f60dbd30 bf87264d bf9aa5a0 00000001 f60dbd54 win32k!xxxDesktopThread+0x333
f60dbd40 bf80109a bf9aa5a0 f60dbd64 0074fff4 win32k!xxxCreateSystemThreads+0x6a
f60dbd54 804dd99f 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f60dbd54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!ProcessMouseInput+1b1
bf874614 85db test ebx,ebx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: win32k!ProcessMouseInput+1b1
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------