Ellusive BSODs

[TheMainMan]

Hi All,
I have been having fairly consistent BSODs on my main rig and have been unable to determine the cause through typical troubleshooting. I'm running a MSDN copy of W7 Pro 64 with SP1 installed. I've had a lot more crashes than the 7 dump files attached would suggest as my latest troubleshooting attempt involved getting a new install disc with SP1 and doing a clean install. I've run memory tests and they've come back clean, there is no overclock or overheating, nor any obvious pattern to when it BSODs. System specs are for this machine.
Thanks for the help,
TheMainMan

 

[zigzag3143]

Hi All,
I have been having fairly consistent BSODs on my main rig and have been unable to determine the cause through typical troubleshooting. I'm running a MSDN copy of W7 Pro 64 with SP1 installed. I've had a lot more crashes than the 7 dump files attached would suggest as my latest troubleshooting attempt involved getting a new install disc with SP1 and doing a clean install. I've run memory tests and they've come back clean, there is no overclock or overheating, nor any obvious pattern to when it BSODs. System specs are for this machine.
Thanks for the help,
TheMainMan

There are two problems

1-asacpi.sys (yours from 2005) is a huge cause of BSOD's



The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).

Download and install it.

Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT before).


2-your video drivers dirextx re-install using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\032711-14617-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e4ce90
Debug session time: Sun Mar 27 12:26:12.340 2011 (GMT-4)
System Uptime: 0 days 11:26:27.012
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {81, 2, 0, fffff80002c8b616}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessCompletedQueuePacketInternal+423 )

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

0: 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: 0000000000000081, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c8b616, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb80e8
 0000000000000081 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+16
fffff800`02c8b616 f6037f          test    byte ptr [rbx],7Fh

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  FahCore_a3.exe

TRAP_FRAME:  fffff80000ba28c0 -- (.trap 0xfffff80000ba28c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8b616 rsp=fffff80000ba2a50 rbp=fffffa8008ed7010
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002c07000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeSetEvent+0x16:
fffff800`02c8b616 f6037f          test    byte ptr [rbx],7Fh ds:00000000`00000000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c86be9 to fffff80002c87640

STACK_TEXT:  
fffff800`00ba2778 fffff800`02c86be9 : 00000000`0000000a 00000000`00000081 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00ba2780 fffff800`02c85860 : fffff800`02df9e80 fffff800`02c8b790 00000000`00000002 00000000`00000081 : nt!KiBugCheckDispatch+0x69
fffff800`00ba28c0 fffff800`02c8b616 : fffffa80`09137010 fffffa80`08742010 fffffa80`08742780 fffff880`0471547f : nt!KiPageFault+0x260
fffff800`00ba2a50 fffff880`0471334b : fffffa80`00000000 fffffa80`00000000 fffffa80`08750000 fffffa80`08750000 : nt!KeSetEvent+0x16
fffff800`00ba2ac0 fffff880`047127da : fffffa80`00000001 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x423
fffff800`00ba2b80 fffff880`04711e00 : fffffa80`00000000 fffffa80`08742010 00000000`00000000 fffff880`0f2d9c00 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff800`00ba2c20 fffff880`04711c4c : 00000000`00000000 fffffa80`08742010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff800`00ba2c70 fffff880`046181cf : fffffa80`070f2040 fffff880`0f372d3d 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff800`00ba2cc0 fffff880`0f31d4ed : fffffa80`0763a000 fffffa80`0763a000 00000000`00000000 fffff880`0f40157d : dxgkrnl!DxgNotifyDpcCB+0x77
fffff800`00ba2cf0 fffffa80`0763a000 : fffffa80`0763a000 00000000`00000000 fffff880`0f40157d fffffa80`0763a000 : nvlddmkm+0xa34ed
fffff800`00ba2cf8 fffffa80`0763a000 : 00000000`00000000 fffff880`0f40157d fffffa80`0763a000 00000000`00000000 : 0xfffffa80`0763a000
fffff800`00ba2d00 00000000`00000000 : fffff880`0f40157d fffffa80`0763a000 00000000`00000000 00000000`00000000 : 0xfffffa80`0763a000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessCompletedQueuePacketInternal+423
fffff880`0471334b 488b8bd8000000  mov     rcx,qword ptr [rbx+0D8h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgmms1!VidSchiProcessCompletedQueuePacketInternal+423

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+423

BUCKET_ID:  X64_0xA_dxgmms1!VidSchiProcessCompletedQueuePacketInternal+423

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

0: kd> lmvm dxgmms1
start             end                 module name
fffff880`04709000 fffff880`0474f000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: C:\Symbols\dxgmms1.sys\4CE799C146000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Sat Nov 20 04:49:53 2010 (4CE799C1)
    CheckSum:         00047A89
    ImageSize:        00046000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[TheMainMan]

Hi Zigzag,
Thanks for the quick response, I've tried both of those suggestions and will leave my computer Folding to see how stable it is. I did have another BSOD but it was due to me messing around with the Folding clients on my GPU.
Thanks again,
TheMainMan

 

[TheMainMan]

More issues

So I'm still having issues after trying the two steps above.
I've attached an updated zip of the error reports. I do have MSE installed as my antivirus although the system health report says otherwise. The only other information I have that may be useful is that my USB wired keyboard will often not respond when the computer comes out of sleep mode. To fix it I have to unplug and re-plug in the keyboard.
Thanks for the help.
TheMainMan

 

[TheMainMan]

Not only am I still having BSODs but now they always hang at 75% and will never complete the dump. How can I fix that? I've tried deleting all the old files in the minidump folder but that didn't change anything.