Unexpected Error Recovery - Catalyst 10.3 issue?

Hi,

I am having issues with windows 7 64-bit. It crashes repeatedly when recovering from hibernation state and other times when idle. I do not have problems when at the machine actively doing anything.

From my investigation:

1. Only started since I installed my HD 5850 (Running catalyst 10.3)
2. I have disabled Hibernate/sleep and it still happens
3.I don't know how to analyse the minidump files!

I know some issues existed with the low voltage level of the HD5XXX cards when at idle so I edited this in the profile.xml for the card to increase it slightly - I wonder if the profile is activating properly when the computer resumes... so potentially this could be a part of the problem (or a red herring!).

I have attached a .rar file with 3 of the minidump files for assistance.

I hope someone can help!

Hello again,

after doing more reading I have performed a few extra checks.

I ran the file check (sfc /scannow) as an admin and no issues were raised.

Also I have uploaded the full list of minidump files I have. Some were cleaned out when I did a file cleanup but I hope the extras assist in finding what is at fault.

Hi mr grobins


Start at the beginning - make sure your BIOS is set correctly and you are using DEFAULTS. Slow down your RAM for the time being. NO overclocks anywhere. Check everything.

Test

Look at the power supply - make sure you are using different power feed lines from the supply.
Most mb's need an aux power connector for PCI cards and the 5850 needs 2 additional power feeds.

If all is good I would start by testing your RAM with memtest

Look at the CPU - 3d mode kicks them all into a higher voltage and temperature state. 2d does not stress at all. Voltage and fan all good?

Hope this helps

Thanks for the tips.

The hardware works rock solid - the only unknown being the HD5850 (which I run at stock clockspeeds).

The issues only began after I swapped out my 8800GT for the HD5850. I never have problems with it running under load.

I have the latest Bios for my m/b (it was specifically updated to enable hybrid sleep to function properly).

I have already used memtest to determine if RAM is at fault - all ok.

Drivers were removed with drivercleaner and freshly installed to minimise any issues there.

I think it is a compatibility issue introduced with the catalyst driver.... hopefully someone can confirm/deny this and point me more directly toward the problem by viewing the dump files :).

Have you tried a catalyst version other than 10.3 (I'm aware that there have been issues with previous catalyst versions)?
Could be a good way to try and isolate if it is the graphics hardware or the software.

Hope this helps

Yes :). Tried that option as well...

I read another thread on here regarding a conflict with some of the MS updates and ATI. I uninstalled KB974332/974331/976098 and am monitoring how the PC runs with sleep mode on and doing the things that normally provoke an error.

If I can get some analysis of the dump file I hope to find a more specific solution.

mgrobins said:

Yes :). Tried that option as well...

I read another thread on here regarding a conflict with some of the MS updates and ATI. I uninstalled KB974332/974331/976098 and am monitoring how the PC runs with sleep mode on and doing the things that normally provoke an error.

If I can get some analysis of the dump file I hope to find a more specific solution.

These crashes were caused by dxgmms1.sys which is the direct x part of your video driver.
Go to the manufacturer to get the uninstall tool, uninstall then reinstall a fresh copy.
If you need help let us know.

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\New folder (3)\040510-27440-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`01e49000 PsLoadedModuleList = 0xfffff800`02086e50
Debug session time: Sun Apr  4 18:10:36.010 2010 (GMT-4)
System Uptime: 0 days 0:10:11.886
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {60, 0, 0, 0}

*** 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_DMA_POOL::RemoveDmaBufferFromPool+12b )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000060, Attempt to free an invalid contiguous memory address (ie: caller of MmFreeContiguousMemory is passing a bad pointer).
Arg2: 0000000000000000, Starting address
Arg3: 0000000000000000, 0
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0xc2_60

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001fb1c3a to fffff80001ebaf00

STACK_TEXT:  
fffff880`0688e4a8 fffff800`01fb1c3a : 00000000`000000c2 00000000`00000060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0688e4b0 fffff880`029be7cb : fffffa80`07a1a010 fffffa80`07150740 fffffa80`6d4d6956 fffff880`00000000 : nt!MmFreeContiguousMemory+0x10a
fffff880`0688e4f0 fffff880`0299824b : fffffa80`071506e0 00000000`00000001 fffffa80`071506e0 fffff880`0688e5a0 : dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+0x12b
fffff880`0688e540 fffff880`029981d3 : fffff8a0`0312c3e0 fffff8a0`0317c058 00000000`00000000 00000000`00000001 : dxgmms1!VIDMM_DMA_POOL::`scalar deleting destructor'+0x6b
fffff880`0688e570 fffff880`028ea3f9 : fffff8a0`00000001 fffff8a0`0312c3e0 00000000`00000000 fffff8a0`0317c058 : dxgmms1!VidMmDestoryDmaPool+0x13
fffff880`0688e5a0 fffff8a0`00000001 : fffff8a0`0312c3e0 00000000`00000000 fffff8a0`0317c058 fffffa80`073528c0 : dxgkrnl+0x493f9
fffff880`0688e5a8 fffff8a0`0312c3e0 : 00000000`00000000 fffff8a0`0317c058 fffffa80`073528c0 00000000`00000000 : 0xfffff8a0`00000001
fffff880`0688e5b0 00000000`00000000 : fffff8a0`0317c058 fffffa80`073528c0 00000000`00000000 00000000`00000000 : 0xfffff8a0`0312c3e0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+12b
fffff880`029be7cb 837f5c02        cmp     dword ptr [rdi+5Ch],2

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+12b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xc2_60_dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+12b

BUCKET_ID:  X64_0xc2_60_dxgmms1!VIDMM_DMA_POOL::RemoveDmaBufferFromPool+12b

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

Awesome thanks :).

If I uninstall the driver and use drivercleaner (eg from guru3d.com) will that be sufficient?

SHould I manually check the removal of the .sys file?

I reinstalled the catalyst drivers.

I note that the dxgmms1.sys file is not part of the driver installation.

dxdiag shows no errors.

Will see how things go.

mgrobins said:

Awesome thanks :).

If I uninstall the driver and use drivercleaner (eg from guru3d.com) will that be sufficient?

SHould I manually check the removal of the .sys file?

Re your questions -
Driver Cleaner - I wouldn't recommend you use it however it is your choice.
Yes to your second question.
Good luck.