Need help on minidump info

Status
Not open for further replies.

nsf42

Beta member
Messages
5
I am trying to help a friend fix his frequent bsods but I am fairly new at debugging the minidump info, if anybody can tell me what the following means I would be very grateful thanks in advance.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfae521f, The address that the exception occurred at
Arg3: b4cbfad0, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
nv4_disp+11021f
bfae521f 8b8884000000    mov     ecx,dword ptr [eax+84h]

TRAP_FRAME:  b4cbfad0 -- (.trap 0xffffffffb4cbfad0)
ErrCode = 00000000
eax=69536972 ebx=00200000 ecx=e68841e8 edx=77beef00 esi=e68840c0 edi=00000000
eip=bfae521f esp=b4cbfb44 ebp=e68841e8 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nv4_disp+0x11021f:
bfae521f 8b8884000000    mov     ecx,dword ptr [eax+84h] ds:0023:695369f6=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  left4dead.exe

LAST_CONTROL_TRANSFER:  from bf819804 to bfae521f

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
b4cbfb78 bf819804 b4cbfc64 bfdd2540 bfa8e2d1 nv4_disp+0x11021f
b4cbfc3c bf8f7441 b4cbfcfc e170b714 e2cf1590 win32k!EngSaveFloatingPointState+0x2a
b4cbfc74 bf9cc530 b4cbfcfc bf8f74dc e170b714 win32k!WatchdogDdDestroySurface+0x38
b4cbfd30 bf9ce3a4 e170b008 e2cf1590 b4cbfd50 dxg!vDdDisableSurfaceObject+0x294
b4cbfd54 8054162c e170b008 00000001 0012e5a0 dxg!DxDdDestroySurface+0x42
b4cbfd54 7c90e4f4 e170b008 00000001 0012e5a0 nt!KiFastCallEntry+0xfc
0012e5a0 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nv4_disp+11021f
bfae521f 8b8884000000    mov     ecx,dword ptr [eax+84h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nv4_disp+11021f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  48ebd26f

FAILURE_BUCKET_ID:  0x8E_nv4_disp+11021f

BUCKET_ID:  0x8E_nv4_disp+11021f

Followup: MachineOwner
 
Your nVidia Display Adapter failed.

MODULE_NAME: nv4_disp

That is the line you look for. Check for a updated GFX Driver.
 
Thanks for the quick response guys. I actually saw that too, but the problem is this will be the third time we have formatted my friends hd and installed windows with a fresh install. Every time we do the computer runs fine for a week or so but then it starts with the bsods again and again more and more frequently. Could a faulty graphics card be the cause? I just dont see the drivers constantly being bad ever time I re-download them. Again thanks for the responses guys.
 
How do you format when you reinstall? If you only use the quick format then you dont really get rid of the old data. You just basically send it to the recycle bin. A full format would be the way to go. That way if there are bad sectors they can be marked.

Also are you getting the drivers right from nvidia or Windows Update?
 
Thanks for the quick response guys. I actually saw that too, but the problem is this will be the third time we have formatted my friends hd and installed windows with a fresh install. Every time we do the computer runs fine for a week or so but then it starts with the bsods again and again more and more frequently. Could a faulty graphics card be the cause? I just dont see the drivers constantly being bad ever time I re-download them. Again thanks for the responses guys.

They'er not the same driver version, are they? Have you tried a different version? Possibly BETA drivers or even an older stable version? Maybe even Omega drivers off of Guru3D.

When you reformat, are you doing a full or quick format?

You could also try doing a Memtest86+ run.

Download it from here: Memtest86+ - Advanced Memory Diagnostic Tool and burn the ISO to a blank CD, and run it for at least 4 hours. If there are any errors reported, that means there is bad system RAM.
 
I just checked his previous bsod and its completely different. Seems to be a memory error. Any thoughts on that guys? Nuke and boot might be a good idea but I would just like to be positive that it would fix the problem. Heres the previous bsod:

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 7c946001, bc, c0883000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c1 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 7c946001
Arg3: 000000bc
Arg4: c0883000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  MemeoBackup.exe

LAST_CONTROL_TRANSFER:  from 80523319 to 804f9f43

STACK_TEXT:  
b6b48a4c 80523319 0000001a 00041284 7c946001 nt!KeBugCheckEx+0x1b
b6b48a84 80523b9f 000000bc 7c946000 c0601f20 nt!MiLocateWsle+0xc1
b6b48ab8 80523fb8 c03e4a30 7c946000 00000000 nt!MiDeletePte+0x1fd
b6b48b80 8051a1dd e15677c0 7c9aefff 00000000 nt!MiDeleteVirtualAddresses+0x164
b6b48c30 80513563 89a2eda0 894712b0 89a2eed8 nt!MiRemoveMappedView+0x237
b6b48c68 805d2712 01a2eda0 89a40790 89a409d8 nt!MmCleanProcessAddressSpace+0x1ff
b6b48d08 805d28d4 00000000 89a40790 00000000 nt!PspExitThread+0x680
b6b48d28 805d2aaf 89a40790 00000000 b6b48d64 nt!PspTerminateThreadByPointer+0x52
b6b48d54 8054162c 00000000 00000000 0012fd24 nt!NtTerminateProcess+0x105
b6b48d54 7c90e4f4 00000000 00000000 0012fd24 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fd24 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiLocateWsle+c1
80523319 2b45f0          sub     eax,dword ptr [ebp-10h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiLocateWsle+c1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  48a3fbd9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x1a_41284_nt!MiLocateWsle+c1

BUCKET_ID:  0x1a_41284_nt!MiLocateWsle+c1

Followup: MachineOwner
 
Status
Not open for further replies.
Back
Top Bottom