windbg.info
Home Search
 You are here: arrow Home Forum

Search Our Site

www.windbg.info
Welcome, Guest
Please Login or Register.    Lost Password?
Help with crash dump
(1 viewing) 1 Guest
Go to bottom
TOPIC: Help with crash dump
#88
Liam (User)
Posts: 1
User Offline

Help with crash dump 03 Feb 2011 - 12:03
Hi, I am have a regular crash of my machine every 2-3 days.

below is the analysis of the problem "Open Crash Dump ...".

Can anyone suggest the problem? Is it faulty memory or a driver fault?

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: 00000140, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804eb5b9, address which referenced memory

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


OVERLAPPED_MODULE: tmcomm

READ_ADDRESS: 00000140

CURRENT_IRQL: 2

FAULTING_IP:
nt!PsReturnProcessNonPagedPoolQuota+19
804eb5b9 8bb040010000 mov esi,[eax+0x140]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80673470 to 804eb5b9

IRP_ADDRESS: 8aa22f00

DEVICE_OBJECT: 89fbf030

TRAP_FRAME: a909db50 -- (.trap ffffffffa909db50)
ErrCode = 00000000
eax=00000000 ebx=8aa22f00 ecx=89c5dbd0 edx=00000000 esi=89c5dbd0 edi=a909dc23
eip=804eb5b9 esp=a909dbc4 ebp=a909dbe4 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
nt!PsReturnProcessNonPagedPoolQuota+0x19:
804eb5b9 8bb040010000 mov esi,[eax+0x140] ds:0023:00000140=????????
Resetting default scope

STACK_TEXT:
a909dbe4 80673470 00000000 00000000 89bc2a20 nt!PsReturnProcessNonPagedPoolQuota+0x19
a909dc08 8066be88 00000000 8aa22f00 a909dc68 nt!VerifierIoFreeIrp+0x109
a909dc18 804ec9cb 8aa22f00 00000103 806f02d0 nt!IovFreeIrpPrivate+0x41
a909dc68 80568065 8aa22f40 a909dcac a909dc98 nt!IopCompleteRequest+0x316
a909dc90 80576703 89fbf030 00000000 89bc2a20 nt!IopSynchronousServiceTail+0xb8
a909dd38 804de7ec 00000228 00000000 00000000 nt!NtReadFile+0x580
a909dd38 7c90e514 00000228 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f5b0 00000000 00000000 00000000 00000000 0x7c90e514


FOLLOWUP_IP:
nt!PsReturnProcessNonPagedPoolQuota+19
804eb5b9 8bb040010000 mov esi,[eax+0x140]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!PsReturnProcessNonPagedPoolQuota+19

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a78505a

STACK_COMMAND: .trap ffffffffa909db50 ; kb

FAILURE_BUCKET_ID: 0xA_nt!PsReturnProcessNonPagedPoolQuota+19

BUCKET_ID: 0xA_nt!PsReturnProcessNonPagedPoolQuota+19

Followup: MachineOwner
 
  Logged IP
  The administrator has disabled public write access.
Go to top
  up top of page up  
 

Copyright © 2017 WinDbg.info. All Rights Reserved.
Page generated in 0.0009 seconds.