System crashing with driver errors

Joined
Oct 12, 2003
Messages
2
Reaction score
0
I have been suffering with system crahes for some time now. To be honest I was putting up with it because I couldnt be bothered to do anything about it. They have become more frequent and I should really do something about it.

I followed the information in this post in order to be able to examine the error dumps. I seem to be getting many different programs as the cause of the problem and am not sure how to proceed. I am not very experienced at debugging these sorts of problems and so I was hoping someone may be able to help.

I have included a sample of one of the crash dumps in the hope that someone can help. I can provide many more (there are currently 146 in my \Windows\Minidump folder :blush:) if needed.

Many thanks for any possible help.

*******************************************************************************
* *
* 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: fffe4080, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 806ee2dc, address which referenced memory

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


WRITE_ADDRESS: fffe4080

CURRENT_IRQL: 2

FAULTING_IP:
hal!HalpStopOhciInterrupt+5c
806ee2dc 890d8000feff mov dword ptr ds:[0FFFE0080h],ecx

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Civ4Warlords.ex

LAST_CONTROL_TRANSFER: from 80565674 to 806ee2dc

STACK_TEXT:
ae043cf0 80565674 00000000 00000001 00000000 hal!HalpStopOhciInterrupt+0x5c
ae043d54 804de7ec 00000054 00000000 1863fe24 nt!ObpReferenceSecurityDescriptor+0x35
ae043d64 7c90eb94 badb0d00 1863fe1c ae043d98 nt!KiUnexpectedInterrupt65+0x2
WARNING: Frame IP not in any known module. Following frames may be wrong.
ae043d68 badb0d00 1863fe1c ae043d98 ae043dcc 0x7c90eb94
ae043d6c 1863fe1c ae043d98 ae043dcc 00000000 0xbadb0d00
ae043d70 ae043d98 ae043dcc 00000000 00000000 0x1863fe1c
ae043d74 ae043dcc 00000000 00000000 00000000 0xae043d98
ae043d98 00000000 0f2d5eac 1863fd48 1863fd48 0xae043dcc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ObpReferenceSecurityDescriptor+35
80565674 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ObpReferenceSecurityDescriptor+35

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9

FAILURE_BUCKET_ID: 0xA_W_nt!ObpReferenceSecurityDescriptor+35

BUCKET_ID: 0xA_W_nt!ObpReferenceSecurityDescriptor+35

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

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top