Windows 7: BSoD Help - Friend has been having similar problems as me

Tbab · 23 Jul 2010

I posted about a series of BSoD issue a while ago on here and because of some of the amazing analyzers here, it fixed my problem, thanks again. But my friend has been having similar issues for quite some time now, since I found help here, I thought it's worth a shot.

I've attached his dumps, thanks in advance!

zigzag3143 · 23 Jul 2010

Quote: Originally Posted by Tbab

I posted about a series of BSoD issue a while ago on here and because of some of the amazing analyzers here, it fixed my problem, thanks again. But my friend has been having similar issues for quite some time now, since I found help here, I thought it's worth a shot.

I've attached his dumps, thanks in advance!

In an effort to expedite a reply I analyzed the most recent crash. It was caused by his video driver. he needs to remove all traces of it (they have an uninstall tool) before installing a new copy.

I am analyzing the 21 crashes now.

Code:

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


Loading Dump File [C:\Users\K\Desktop\072310-34632-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a4b000 PsLoadedModuleList = 0x82b93810
Debug session time: Fri Jul 23 15:45:08.459 2010 (GMT-4)
System Uptime: 0 days 6:27:52.503
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {d, 0, 0, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+3bb83 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82a17700 to 82a91f6b

STACK_TEXT:  
8dcfb94c 82a17700 badb0d00 857982a0 00000380 nt!KiSystemFatalException+0xf
8dcfb9bc 9205bb83 8dcfba6c 920e2665 8dcfba24 hal!KfAcquireSpinLock
WARNING: Stack unwind information not available. Following frames may be wrong.
8dcfb9c4 920e2665 8dcfba24 869f4608 8dcfbaf0 nvlddmkm+0x3bb83
8dcfba6c 92034174 8dcfbaf0 82a196ee 8dcfbaf0 nvlddmkm+0xc2665
8dcfba94 92a9ee50 868d6000 920340f6 87e218d8 nvlddmkm+0x14174
8dcfbabc 92a9f018 8dcfbaf0 8dcfbad8 92b550d5 dxgkrnl+0x1e50
8dcfbac8 92b550d5 87cfe000 8dcfbaf0 8dcfbb64 dxgkrnl+0x2018
8dcfbad8 92b5e4ea 8dcfbaf0 87e21940 87e21000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
8dcfbb64 92b85617 00000006 869f4b48 87e21940 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
8dcfbbdc 92b85f87 87e26788 00000001 869f4b48 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
8dcfbd18 92b8622f 009f4b48 882aadd0 8dcfbd3c dxgmms1!VidSchiSubmitRenderCommand+0x809
8dcfbd28 92b864cc 869f4b48 82a873f1 87e26788 dxgmms1!VidSchiSubmitQueueCommand+0x61
8dcfbd3c 92b86573 87e26788 00000000 87e22c48 dxgmms1!VidSchiRun_PriorityTable+0x24
8dcfbd50 82c596bb 87e26788 a7fb531a 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8dcfbd90 82b0b0f9 92b864f4 87e26788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+3bb83
9205bb83 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvlddmkm+3bb83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c23264b

FAILURE_BUCKET_ID:  0x7f_d_nvlddmkm+3bb83

BUCKET_ID:  0x7f_d_nvlddmkm+3bb83

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82a17700 to 82a91f6b

STACK_TEXT:  
8dcfb94c 82a17700 badb0d00 857982a0 00000380 nt!KiSystemFatalException+0xf
8dcfb9bc 9205bb83 8dcfba6c 920e2665 8dcfba24 hal!KfAcquireSpinLock
WARNING: Stack unwind information not available. Following frames may be wrong.
8dcfb9c4 920e2665 8dcfba24 869f4608 8dcfbaf0 nvlddmkm+0x3bb83
8dcfba6c 92034174 8dcfbaf0 82a196ee 8dcfbaf0 nvlddmkm+0xc2665
8dcfba94 92a9ee50 868d6000 920340f6 87e218d8 nvlddmkm+0x14174
8dcfbabc 92a9f018 8dcfbaf0 8dcfbad8 92b550d5 dxgkrnl+0x1e50
8dcfbac8 92b550d5 87cfe000 8dcfbaf0 8dcfbb64 dxgkrnl+0x2018
8dcfbad8 92b5e4ea 8dcfbaf0 87e21940 87e21000 dxgmms1!DXGADAPTER::DdiSubmitCommand+0x11
8dcfbb64 92b85617 00000006 869f4b48 87e21940 dxgmms1!VidSchiSendToExecutionQueue+0x7d6
8dcfbbdc 92b85f87 87e26788 00000001 869f4b48 dxgmms1!VidSchiSendToExecutionQueueWithWait+0x115
8dcfbd18 92b8622f 009f4b48 882aadd0 8dcfbd3c dxgmms1!VidSchiSubmitRenderCommand+0x809
8dcfbd28 92b864cc 869f4b48 82a873f1 87e26788 dxgmms1!VidSchiSubmitQueueCommand+0x61
8dcfbd3c 92b86573 87e26788 00000000 87e22c48 dxgmms1!VidSchiRun_PriorityTable+0x24
8dcfbd50 82c596bb 87e26788 a7fb531a 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8dcfbd90 82b0b0f9 92b864f4 87e26788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+3bb83
9205bb83 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nvlddmkm+3bb83

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c23264b

FAILURE_BUCKET_ID:  0x7f_d_nvlddmkm+3bb83

BUCKET_ID:  0x7f_d_nvlddmkm+3bb83

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

EDIT: MOST OF THE OTHERS WERE ALSO CAUSED BY THE VIDEO DRIVER

Tbab · 31 Jul 2010

He's been having troubles again, not that much as before though, so thanks a don.

I attached the last two.

Thanks in advance again! You guys are great.

ttran · 31 Jul 2010

Does he has another graphic card that he can try? Both of the crash dump have stop code that contain graphic card related

Quote:

STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

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
STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

Tell him to update directx:
Download details: DirectX End-User Runtime

Exception code c000005 is memory access violation occurred. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

BUGCHECK SUMMARY:

Code:

BugCheck 1000007E, {c0000005, 92b8febd, 8dcebb84, 8dceb760}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_DEVICE::RemoveCommitment+27 )

Followup: MachineOwner
---------
BugCheck 1000008E, {c0000005, 82c46f70, 9d85fbb0, 0}

Probably caused by : ntkrpamp.exe ( nt!ObDereferenceSecurityDescriptor+11 )

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

Also please these driver ASAP:

Code:

 ASACPI   ASACPI.sys   Fri Aug 13 09:52:52 2004 (411C2D04)
 AmdLLD   AmdLLD.sys   Sat Jun 30 02:47:32 2007 (468561D4)
ATITool  ATITool.sys  Fri Nov 10 20:08:51 2006 (455479E3)
voclock nvoclock.sys Wed Sep 05 09:26:31 2007 (46DE13D7)

Update the ASACPI.sys following this instruction, that driver is guaranteed to cause BSODs. Pay attention on that one please

BSOD + Minidumps, please help

For other driver, following this instruction:
How To Find Drivers:

Quote:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Let us know if you need help

Tuan

Windows 7: BSoD Help - Friend has been having similar problems as me

BSoD Help - Friend has been having similar problems as me problems?