BSOD in Enterprise x64, multiple causes?

Posted originally in this thread ( https://www.sevenforums.com/general-d...bsod-help.html ), in case a resolution is found that might help others. New thread started by request.

I'm experiencing the same BSODs on Windows 7 Enterprise x64 RTM. It seems to be aggrivated by 3D gaming, though I've had it crash and restart while perfoming virus scans or even sitting idle. Since I can almost guarantee that it will crash while playing Call of Duty: World at War, I've been using that to test for results.

I've had at least 5 different reported drivers as the culprit, but atikmdag.sys seems to be the most prevalent. The latest showed ks.sys to have caused the crash. (Actually the latest is now dxgmms1.sys). My system had been completely stable since built, and I had made no change before I started experiencing the crashes.

I was using Avast av when I first started experiencing the crashes. I tried running with AVG, BitDefender and even with no av. Each change made little difference. I had also been running the 9.7 ATI drivers for my HD4870 gfx card. After the crashes started, I tried upgrading to 9.8, then adding the 9.8 hotfix, to no avail. The most significant difference was when I tried running with no driver, instead letting it revert back to the Windows 7 drivers. I was able to play for about 30 minutes before it finally crashed, right about the time I thought I had figured it out.

I've also run the Windows memory test and it showed no faults. I've tried various BIOS settings starting from default and working back to where I had adjusted/tweaked. Mind you, this system was perfectly stable with slight overclocking on the CPU.

I'm in process of unistalling drivers until I hit something that seems to stabilize it again. I've just done the Audigy SE sound card drivers but have yet to stress test it (now tested, still crashing), and the only thing left would be the motherboard drivers. When I get home this evening, I'll post my dumps if someone would care to compare them to pearcie's to see if there's some common link here. I get the feeling that something got buggy, perhaps with an update? I could be grasping at straws though...

I've attached the first and last dump files. I tried to review them myself in WinDBG tool, but I believe I'm not using the correct symbol pack. I have more that I can attach if needed.

BTW, you've got a wonderful community here. I'm glad to be part of it.

EDIT: I just noticed the dump summary for pearcie's crashes has alot of references to codwaw.exe/codwawmp.exe. Hmmmmm.......

Much better and a dump file, i will take a quick look at it

Ken

last dump file caused by dxgmms1.sys

Ms recommends here Windows 7 crashdump issue. It involves paid for services.


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


Loading Dump File [C:\Users\K\Desktop\091009-14500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
Debug session time: Thu Sep 10 18:21:28.869 2009 (GMT-4)
System Uptime: 0 days 3:00:38.603
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004d73d6d, fffff880051276a8, fffff88005126f00}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSendToExecutionQueue+879 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88004d73d6d, The address that the exception occurred at
Arg3: fffff880051276a8, Exception Record Address
Arg4: fffff88005126f00, Context Record Address

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!VidSchiSendToExecutionQueue+879
fffff880`04d73d6d ff5058 call qword ptr [rax+58h]

EXCEPTION_RECORD: fffff880051276a8 -- (.exr 0xfffff880051276a8)
ExceptionAddress: fffff88004d73d6d (dxgmms1!VidSchiSendToExecutionQueue+0x0000000000000879)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff88005126f00 -- (.cxr 0xfffff88005126f00)
rax=fffff88004c8fd90 rbx=0000000000000000 rcx=fffffa80055ca000
rdx=fffff88005127940 rsi=fffffa80055d31a0 rdi=0000000000000000
rip=fffff88004d73d6d rsp=fffff880051278e0 rbp=fffffa80055d2000
r8=0000000000000000 r9=0000000000000000 r10=0000000000020000
r11=fffffa80055d2a58 r12=fffffa80055c8010 r13=0000000000000000
r14=fffffa8003a37290 r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
dxgmms1!VidSchiSendToExecutionQueue+0x879:
fffff880`04d73d6d ff5058 call qword ptr [rax+58h] ds:002b:fffff880`04c8fde8={dxgkrnl!DXGADAPTER_DdiSubmitCommand (fffff880`04c7b4dc)}
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc0e0
ffffffffffffffff

FOLLOWUP_IP:
dxgmms1!VidSchiSendToExecutionQueue+879
fffff880`04d73d6d ff5058 call qword ptr [rax+58h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff88004da5e65 to fffff88004d73d6d

STACK_TEXT:
fffff880`051278e0 fffff880`04da5e65 : fffffa80`055d2001 fffffa80`00000001 00000000`00000000 fffffa80`055d2000 : dxgmms1!VidSchiSendToExecutionQueue+0x879
fffff880`051279e0 fffff880`04da4d3c : 00000000`00000713 00000000`0003ec59 fffffa80`04471470 fffffa80`055c8010 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x179
fffff880`05127ae0 fffff880`04da4398 : fffff800`03fab000 fffff880`04da3d00 fffffa80`00000000 fffffa80`0001f6a0 : dxgmms1!VidSchiSubmitRenderCommand+0x920
fffff880`05127cd0 fffff880`04da3e96 : 00000000`00000000 fffffa80`03e7fb00 00000000`00000080 fffffa80`055c8010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05127d00 fffff800`02d69166 : 00000000`028dc77c fffffa80`05523b60 fffffa80`0396c990 fffffa80`05523b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05127d40 fffff800`02aa4486 : fffff800`02c3ee80 fffffa80`05523b60 fffff800`02c4cc40 fffff880`01022534 : nt!PspSystemThreadStartup+0x5a
fffff880`05127d80 00000000`00000000 : fffff880`05128000 fffff880`05122000 fffff880`05127690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VidSchiSendToExecutionQueue+879

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff88005126f00 ; kb

FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VidSchiSendToExecutionQueue+879

BUCKET_ID: X64_0x7E_dxgmms1!VidSchiSendToExecutionQueue+879

Followup: MachineOwner

First dump caused by portcls.sys This is a sound driver file for realtek AC95/97. Your sound driver should be re-installed with the newest one available


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


Loading Dump File [C:\Users\K\Desktop\082709-18984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02818000 PsLoadedModuleList = 0xfffff800`02a55e50
Debug session time: Fri Aug 28 00:14:37.076 2009 (GMT-4)
System Uptime: 0 days 5:13:12.810
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88003faff17, fffff88007faec30, 0}

Probably caused by : portcls.sys ( portcls!CPortPinWaveCyclic::GetPosition+47 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff88003faff17, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007faec30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
portcls!CPortPinWaveCyclic::GetPosition+47
fffff880`03faff17 41ff5040 call qword ptr [r8+40h]

CONTEXT: fffff88007faec30 -- (.cxr 0xfffff88007faec30)
rax=0000000000000000 rbx=fffffa8004ddb128 rcx=fffffa8003d9fd88
rdx=0000000000002000 rsi=fffff88007faf700 rdi=0000000000000000
rip=fffff88003faff17 rsp=fffff88007faf610 rbp=fffffa8005695430
r8=ffaaf88003eeab90 r9=0000000000000000 r10=0000120000001e00
r11=000000005dd02000 r12=0000000000000002 r13=0000000000000001
r14=fffff88003fbef40 r15=0000000000000028
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
portcls!CPortPinWaveCyclic::GetPosition+0x47:
fffff880`03faff17 41ff5040 call qword ptr [r8+40h] ds:002b:ffaaf880`03eeabd0=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88003faff17

STACK_TEXT:
fffff880`07faf610 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : portcls!CPortPinWaveCyclic::GetPosition+0x47


FOLLOWUP_IP:
portcls!CPortPinWaveCyclic::GetPosition+47
fffff880`03faff17 41ff5040 call qword ptr [r8+40h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: portcls!CPortPinWaveCyclic::GetPosition+47

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: portcls

IMAGE_NAME: portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc03

STACK_COMMAND: .cxr 0xfffff88007faec30 ; kb

FAILURE_BUCKET_ID: X64_0x3B_portcls!CPortPinWaveCyclic::GetPosition+47

BUCKET_ID: X64_0x3B_portcls!CPortPinWaveCyclic::GetPosition+47

Followup: MachineOwner

So one blue screen was caused by a sound driver and another by a file used in gaming (maybe video driver). Has this happened for a long rime or just started happening? when/what are you doing when it BSOD?

Ken

H

Its easier to explain without quotes. I think both of these were caused by driver issues. If I were you I would update my sound driver and video driver. I would also see if there is a bios upgrade available. Im waiting of r one of our debugging Guru's to look thru the dumps as they have alot more experience than I do. while you're waiting you can do the driver upgrades

edit: i Pm'ed one of our best with the link to this thread

hope this helps

Ken

Interesting thing, I so wish I had looked into the reliability monitor sooner...I would have seen the degradation in performance. And what likely caused it. It looks as if installing the mobo drivers might be the issue.

I installed the Vista x64 drivers under Vista-compatibility ( MSI Global – Computer, Laptop, Notebook, Desktop, Mainboard, Graphics and more ). So much for me saying I had made no changes!

So what would seem the best course? Uninstall everything motherboard-related from device manager? Perhaps I should just rebuild entirely? Suggestions?

I have the latest BIOS already installed. I did that before I started testing Win7. I do believe you're correct about this being driver-related though.

Get the latest chipset drivers and install them.

jfar said:

Get the latest chipset drivers and install them.

Yeah, I did that but thanks for the advice. That's the link I have above. Unless you know of anything more recent?

I've done a rebuild with the x86 version and found that I still get crashes. It's beginning to look alot like hardware I'm including the dumps from right after I rebuilt.

I took my PC to work with me today to try some things. I got to step one - re-enable onboard sound and disable my Audigy SE card. So far it seems to have done the trick. I've been running CoD:WaW now for about 20 minutes...it's usually failed within the first 10 minutes of play. So I'm hopeful. I'll let it run the rest of the day and post any updates.

The other variable is that I'm using the onboard LAN connection instead of the Linksys wireless card. But if I take it home tonight and it starts crashing again, that should be an indicator.

Again, thanks for all the help.

That's good news, kind of, at least it might narrow it down a bit, talk to you later.