New
#1
Help!! Bsod t_t
can anyone help me? im having problem with my PC..
it always get BSOD..
i uploaded the zip file of my minidump.:
help please..
can anyone help me? im having problem with my PC..
it always get BSOD..
i uploaded the zip file of my minidump.:
help please..
Hi,
It seems you have drivers issue, so I recommend you to update these drivers:
And two dmp files point to your Graphic driver as the cause, so you must update the Graphic Card driver as well.Code:ASACPI.sys Thu Aug 12 19:52:52 2004 → Asus ATK0110 ACPI Utility sisagpx.sys Tue Jan 23 23:01:26 2007 → SIS AGP driver smserial.sys Fri Sep 26 01:23:38 2008 → Motorola SM56 voice modem driver
Before update, better to remove current driver with driversweeper then install the fresh copy of your ATI drivers.
Guru3D - Driver Sweeper
AMD.com | Support & Downloads
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 8f632f44, 961a09ac, 0} Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for dxgkrnl.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 ) 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: 8f632f44, The address that the exception occurred at Arg3: 961a09ac, 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: dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 8f632f44 890a mov dword ptr [edx],ecx TRAP_FRAME: 961a09ac -- (.trap 0xffffffff961a09ac) ErrCode = 00000002 eax=8622e998 ebx=8240cf78 ecx=8240cf78 edx=7dbfcf78 esi=8240cf78 edi=00000000 eip=8f632f44 esp=961a0a20 ebp=961a0a30 iopl=0 nv up ei pl nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x28: 8f632f44 890a mov dword ptr [edx],ecx ds:0023:7dbfcf78=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: danceclient.ex CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 8f61632b to 8f632f44 STACK_TEXT: 961a0a30 8f61632b 8240cf78 00000000 961a0abc dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x28 961a0a40 8e36b4aa 85e8f000 8240cf78 00000000 dxgmms1!VidMmCloseAllocation+0x13 WARNING: Stack unwind information not available. Following frames may be wrong. 961a0abc 8e369481 00000000 00000000 a716f100 dxgkrnl+0x244aa 961a0ae4 8e36b95e 00000001 00000000 00000000 dxgkrnl+0x22481 961a0b08 8e36bd6e 00000000 00000000 a5d314b0 dxgkrnl+0x2495e 961a0b64 8e36c594 961a0b98 00000001 182c1f00 dxgkrnl+0x24d6e 961a0d28 8285844a 0012f3d0 0012f3e0 777464f4 dxgkrnl+0x25594 961a0d28 777464f4 0012f3d0 0012f3e0 777464f4 nt!KiFastCallEntry+0x12a 0012f3e0 00000000 00000000 00000000 00000000 0x777464f4 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 8f632f44 890a mov dword ptr [edx],ecx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc265 FAILURE_BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 BUCKET_ID: 0x8E_dxgmms1!VIDMM_GLOBAL::CloseAllocation+28 Followup: MachineOwner ---------
oh.. tnx.. ill just follow recommendations..
and hope it will help.. =)