BSOD (Please look at my minidumps)

[Jomox]

Hi,

Getting some minidumps the last few days, restarted 3 times on it's own when I've been away from the PC. I don't know whats causing it, but I've uploaded the minidumps for someone to look at. Hopefully you can help me find what is causing it, as it's been fine for a few months untill the last few days.

 

[Jonathan_King]

The bugcheck on the one I could open is equivalent to 8E:

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

BSOD Index

Look through those causes and see if anything matches up. Try updating your video card drivers.

Now I could only open 1 of them; that's not enough to make a very accurate analysis. If you get more BSODs, could you please upload the dmps?

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp4_dumps.zip\040710-17893-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82e3b000 PsLoadedModuleList = 0x82f83810
Debug session time: Wed Apr  7 07:53:03.547 2010 (GMT-4)
System Uptime: 4 days 10:56:23.076
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 83080349, 91bbfc10, 0}

Probably caused by : hardware ( nt!ExDestroyHandle+d )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 83080349, The address that the exception occurred at
Arg3: 91bbfc10, 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: 
nt!ExDestroyHandle+d
83080349 8b3d24010000    mov     edi,dword ptr ds:[124h]

TRAP_FRAME:  91bbfc10 -- (.trap 0xffffffff91bbfc10)
ErrCode = 00000000
eax=a58215c8 ebx=a8fffa20 ecx=02000000 edx=85885548 esi=85885548 edi=866da838
eip=83080349 esp=91bbfc84 ebp=91bbfc90 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!ExDestroyHandle+0xd:
83080349 8b3d24010000    mov     edi,dword ptr ds:[124h] ds:0023:00000124=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!ExDestroyHandle+d
83080349 8b3d24010000    mov     edi,dword ptr ds:[124h]

LAST_CONTROL_TRANSFER:  from 8308072c to 83080349

STACK_TEXT:  
91bbfc90 8308072c a8fffa20 000002e5 a8fffa20 nt!ExDestroyHandle+0xd
91bbfcdc 83081f72 a8fffa20 a58215c8 84e51408 nt!ObpCloseHandleTableEntry+0x1bd
91bbfd0c 830820ea 84e51408 866da801 01b3f5f0 nt!ObpCloseHandle+0x7f
91bbfd28 82e7e47a 000002e5 01b3f5f4 776e64f4 nt!NtClose+0x4e
91bbfd28 776e64f4 000002e5 01b3f5f4 776e64f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01b3f5f4 00000000 00000000 00000000 00000000 0x776e64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDestroyHandle+d
83080349 8b3d24010000    mov     edi,dword ptr ds:[124h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDestroyHandle+d

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

 

[Jomox]

Thanks. AM hoping I don't get any more again but If I do I will upload them for you to look at.

 

[Jomox]

Actually am sorry I got another not long ago, it's attached.

 

[Jomox]

Could you open the last one?

 

[Jonathan_King]

Could you open the last one?

Sorry, I can't open that one.

 

[Jomox]

Instead of making a new thread I will post on here.

I've had a few more minidumps since I made this topic. They are attached. I hope you can open some of them and we can see what could potentially be causing this issue.

Thanks in advance.

 

[Jonathan_King]

Looks like hardware. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.