|
|
|
Question : Bluescreens on shutdown with XP SP1
|
|
Hi,
I'm running Windows XP Pro SP1 on my system and whenever I shut down I get a bluescreen.
There are two different ones which I have recorded:
IRQL_NOT_LESS_OR_EQUAL
* STOP: 0x0000000A (0x99AB5B14, 0x00000002, 0x00000000, 0x804E8785)
and
IRQL_NOT_LESS_OR_EQUAL
* STOP: 0x0000000A (0x8000000B, 0x00000002, 0x00000000, 0x804DF6AC)
I have been resorting to holding the off button on the front of my computer, but that eventually caused bad sectors which I had to fix (took about 6 hours with chkdsk).
I used WinDbg to read the MEMORY.DMP file generated by the second BSOD:
-------------------------------------------------------------
*******************************************************************************
* *
* 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: 8000000b, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804df6ac, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 8000000b
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEvent+d
804df6ac 8b7904 mov edi,[ecx+0x4]
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
TRAP_FRAME: f008da70 -- (.trap fffffffff008da70)
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=80000007 edx=00000003 esi=8226cc48 edi=8226cc48
eip=804df6ac esp=f008dae4 ebp=f008db18 iopl=0 nv up ei pl nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010217
nt!KeSetEvent+0xd:
804df6ac 8b7904 mov edi,[ecx+0x4] ds:0023:8000000b=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 8051adc6 to 804df6ac
STACK_TEXT:
f008daec 8051adc6 80000007 00000000 00000000 nt!KeSetEvent+0xd
f008db18 804f024d 8226cc48 821ca5d0 821ca501 nt!MiCheckControlArea+0x148
f008dbc0 804fbf7f 821ca5d0 8226cc30 821ca5d0 nt!MiRemoveMappedView+0x253
f008dbfc 805757a5 011ca5d0 82992020 82992268 nt!MmCleanProcessAddressSpace+0x266
f008dca4 80558bc5 00000001 82992020 00000000 nt!PspExitThread+0x668
f008dca8 00000001 82992020 00000000 fff0bdc0 nt!ExWaitForRundownProtectionRelease
FOLLOWUP_IP:
nt!KeSetEvent+d
804df6ac 8b7904 mov edi,[ecx+0x4]
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KeSetEvent+d
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 422517e4
STACK_COMMAND: .trap fffffffff008da70 ; kb
BUCKET_ID: 0xA_nt!KeSetEvent+d
Followup: MachineOwner
-------------------------------------------------------------
I've tried removing non-necsesary hardware and updating drivers, but have had no luck.
It's odd, the bluescreens just started to happen one day without any new hardware being added or updates being done.
Hope somebody can help,
Graham Sutherland.
|
Answer : Bluescreens on shutdown with XP SP1
|
|
Corrupt memory dump is the indication of hardware problem. When windows encounter sever problem, it writes the memory to the paging space and hardware occurs. Windows cannot writes the dump complete and reboot to occur recursive error recovery loop. (ie example of recursive error : hardware error --> taking dump --> hardware error --> dump taking)
Either the ram or m/b is faulty.
|
|
|
|
|
|
|
