Windows XP Error crash

[homey76]

I was wondering if anyone can explain this BSOD for me. Here is the dump file:

BugCheck 1000000A, {c072d7d8, 2, 0, 8051cefa}

Probably caused by : Unknown_Image ( nt!KiTrap0E+cc )

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

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: c072d7d8, memory referenced
Arg2: 00000002, 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: 8051cefa, address which referenced memory

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


READ_ADDRESS: c072d7d8

CURRENT_IRQL: 2

FAULTING_IP:
nt!MmAccessFault+b82
8051cefa 8b07 mov eax,dword ptr [edi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: lsass.exe

TRAP_FRAME: a99bfd64 -- (.trap 0xffffffffa99bfd64)
ErrCode = 00000004
eax=0000000e ebx=000ee498 ecx=00000003 edx=0000004a esi=7444ee7c edi=00143040
eip=74444f0f esp=00b8f670 ebp=00b8f680 iopl=0 nv up ei pl nz na pe cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010207
001b:74444f0f ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8054052c to 8051cefa

STACK_TEXT:
a99bfd4c 8054052c 00000000 7444ee7c 00000001 nt!MmAccessFault+0xb82
a99bfd4c 74444f0f 00000000 7444ee7c 00000001 nt!KiTrap0E+0xcc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b8f680 00000000 00000000 00000000 00000000 0x74444f0f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+cc
8054052c 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+cc

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: RAISED_IRQL_USER_FAULT

MODULE_NAME: Unknown_Module

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

 

[Bobbye]

I don't do the minidumps, but if you find the corresponding Error in the Event Viewer, I might be able to assist.

I would like more information on the BSOD:

1. When do you get the BSOD? Starting up? Program? What are you doing?
2. What is the Error message?
3. What problem are you having with the system at the time of the BSOD?
4. What operating system are you using?

Start> Run> type in eventvwr

Do this on each the System and the Applications logs:
1. Click to open the log>
2. Look for the Error>
3 .Right click on the Error> Properties>
4. Click on Copy button, top right, below the down arrow

NOTE: Please ignore Warnings & Information Events. You do not need to include the lines of code-if any-in the box below the Description. Please do not paste the entire Event log here.

The tags you will be looking for are:
1. nt!KiTrap0E+cc
2. IRQL_NOT_LESS_OR_EQUAL
3. PROCESS_NAME: lsass.exe
(Desc. of lsass.exe: Local Security Authentication Server. It verifies the validity of user logons to your PC/Server.)

 

[homey76]

Bobbye,

Thanks for replying to my issue.

I was printing some set of pictures to our Laserjet when this happened. This machine is a windows xp pro machine with all current windows updates. It connects to a Domain so that the user can log into the software that stores pictures for printing. This is the first time i got this BSOD. I have never gotten this before nor has it happened again. As soon as she sent the job to the printer the machine rebooted itself. When restarting and logging in i received a windows has recovered from a serious error. I went to the event log and this was logged.

The error message is as follows:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 4/16/2009
Time: 5:17:53 PM
User: N/A
Computer: DAISYPC4D
Description:
Error code 1000000a, parameter1 c072d7d8, parameter2 00000002, parameter3 00000000, parameter4 8051cefa.


Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 30 1000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 63 30 eters c0
0030: 37 32 64 37 64 38 2c 20 72d7d8,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 35 31 00, 8051
0050: 63 65 66 61 cefa


After seeing this I retrieved the dump file and opened it up to see what process or applications caused this error which i initially posted.

Thanks for all your help in advance,

-Homey76

 

[Bobbye]

This is the first time i got this BSOD. I have never gotten this before nor has it happened again.

???
If this was a one time message and the problem has resolved, don't worry about it. IF this continues to happen, use the troubleshooting in the quote box:
Event #1003, Source System Error, Description: Error Code 0000000a = "IRQL_NOT_LESS_OR_EQUAL" - The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

1. Disable any newly installed drivers and remove any newly added programs.
2. If the computer will not start normally, try starting it in Last Known Good Configuration.
Boot into Safe Mode: by pressing F8 during startup after the logo loads, before Windows begins to load. Continue tapping the F8 key until Safe Mode comes up..
3. If the current hardware settings prevent the computer from starting> choose Last Known Good Configuration can allow you to start the computer and examine the configuration. This allows you to start your computer when a problem prevents it from starting normally., and then remove or disable newly added programs or drivers.
4. Remove any newly installed hardware (RAM, adapters, hard disks, modems, and so on).
5. Ensure that you have updated drivers for your hardware devices. Also, ensure that you have the latest system BIOS.
6. Run system diagnostics supplied by your hardware vendor, especially a memory check.
7. Disable memory caching in the BIOS.

Further instruction depending on these results.