Music causes non-BSOD system halt

[ebb]

Here's where I'm at:

When I play audio (i.e. music) on my new Windows 7 UE/64 installation, my system intermittently hangs up. When this happens, the last 1/2 second or so of audio in the buffer repeats over and over again, the screen goes black (or occasionally a black-snow looking effect), and the system ceases to respond over the network.

The intermittent period seems to be affected by the overall processor utilization. The more the system is loaded down, the more often it happens. When running a game while playing music, it happens perhaps once per 10 minutes.

Any help is greatly appreciated.

 

[zigzag3143]

Here's where I'm at:

When I play audio (i.e. music) on my new Windows 7 UE/64 installation, my system intermittently hangs up. When this happens, the last 1/2 second or so of audio in the buffer repeats over and over again, the screen goes black (or occasionally a black-snow looking effect), and the system ceases to respond over the network.

The intermittent period seems to be affected by the overall processor utilization. The more the system is loaded down, the more often it happens. When running a game while playing music, it happens perhaps once per 10 minutes.

Any help is greatly appreciated.

This was probably caused by your video card driver atipmdag.sys
I suggest that you uninstall the old driver. Go to the ATI web page & use the uninstaller. Then download the appropriate driver for your system
Post back your results please.

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


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

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Sat Mar 13 00:11:31.250 2010 (GMT-4)
System Uptime: 2 days 3:29:51.780
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000094, fffff88004bc80f5, fffff88005da9f78, fffff88005da97d0}
[B]
Probably caused by : atipmdag.sys[/B] ( atipmdag+38c0f5 )

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

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

[I]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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004bc80f5, The address that the exception occurred at
Arg3: fffff88005da9f78, Exception Record Address
Arg4: fffff88005da97d0, Context Record Address[/I]

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
atipmdag+38c0f5
fffff880`04bc80f5 41f7f0          div     eax,r8d

EXCEPTION_RECORD:  fffff88005da9f78 -- (.exr 0xfffff88005da9f78)
ExceptionAddress: fffff88004bc80f5 (atipmdag+0x000000000038c0f5)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff88005da97d0 -- (.cxr 0xfffff88005da97d0)
rax=00000000002a1d40 rbx=fffff88005daa200 rcx=00000000002a1d40
rdx=0000000000000000 rsi=fffffa8005436400 rdi=fffff8800483c000
rip=fffff88004bc80f5 rsp=fffff88005daa1b0 rbp=0000000000000026
 r8=0000000000000000  r9=00000000000076a0 r10=fffff88005daa200
r11=fffff88004dc2c00 r12=0000000000000000 r13=fffffa800543d014
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
atipmdag+0x38c0f5:
fffff880`04bc80f5 41f7f0          div     eax,r8d
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

LAST_CONTROL_TRANSFER:  from fffffa8005552864 to fffff88004bc80f5

STACK_TEXT:  
fffff880`05daa1b0 fffffa80`05552864 : 00000000`00000000 fffff880`04c52378 fffff880`bebe002f fffff880`05daa290 : atipmdag+0x38c0f5
fffff880`05daa1b8 00000000`00000000 : fffff880`04c52378 fffff880`bebe002f fffff880`05daa290 fffff880`04bc7251 : 0xfffffa80`05552864


FOLLOWUP_IP: 
atipmdag+38c0f5
fffff880`04bc80f5 41f7f0          div     eax,r8d

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  atipmdag+38c0f5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atipmdag
[B]
IMAGE_NAME:  atipmdag.sys[/B]

DEBUG_FLR_IMAGE_TIMESTAMP:  4b68f9c4

STACK_COMMAND:  .cxr 0xfffff88005da97d0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atipmdag+38c0f5

BUCKET_ID:  X64_0x7E_atipmdag+38c0f5

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

 

[ebb]

Thanks for the advise. Interesting note however, is that the full driver + CCC package didn't solve the problem, but installing the driver-only package did.

Cheers,
EB

 

[zigzag3143]

Thanks for the advise. Interesting note however, is that the full driver + CCC package didn't solve the problem, but installing the driver-only package did.

Cheers,
EB

Sometimes the additional junk causes to most grief.
K

 

[ebb]

As it turns out, I still have the extra fluff installed. I installed the 'driver only' package after the 'driver + CCC' package, it it worked.

 

[ebb]

Update: after several week or so of running with the new driver-only configuration, there symptoms still manifest. However, the frequency with which the halt happens is much diminished. Before, it would halt every few minutes (20-30). Now, it only happens every few hours.

Any other thoughts?