RSOD - Crossfire and 15.7, 15.7.1, 15.7.1 Hotfix1 and 15.7.1 Hotfix2 drivers

Nospheratu

Member
Joined
Aug 29, 2015
Posts
11
· OS - Windows 10 x64
· OEM version of Windows 7 upgraded to Windows 10. Now on clean install on Windows 10.
· System age: +- 5 years
· New OS install: > 1 month


· CPU
· 2x Clevo AMD Radeon 7970M in Crossfire
· Power Supply - Dell 330W manufactured by Delta


· System Manufacturer - Dell (Alienware)
· M17X R2


· Laptop


I know with some certainty through my troubleshooting that AMD's Windows 10 drivers that are giving me these red screen of death errors. I'm hoping an experienced Windows debugger can go through my dump file to determine whether my hardware isn't at fault as I'm running a very customised hardware configuration. I have WinDBG installed although my attempts to get to the root of the problem were futile due to the fact that there are no publicly available symbols for the atikmdag.sys driver and my lack of Windows debugging skills. My PerfMon and SysNativeFileCollectionApp reports were done while running on the stable 14.12 Catalyst drivers with more apps and drivers installed. My BSOD/RSOD dumps linked below were run on a much leaner OS install to rule out potential conflicts.

TL;DR: Red Screen of Death occurs immediately when 3Dmark, Crysis 3, Metro Last Light, Grid Autosport, Project Cars and Alien Isolation launch into fullscreen mode when Crossfire is enabled and running the 15.7, 15.7.1, 15.7.1 Hotfix1 and 15.7.1 Hotfix2 drivers. If I create a custom profile for Metro Last Light with AFR Friendly Crossfire Mode, Metro Last Light does not BSOD/RSOD on startup and plays without issue. Crysis 3 works with an AFR Friendly Crossfile Profile as well with no BSOD/RSOD but certain textures are dark. 3Dmark still crashes with an AFR Friendly profile. The BSOD/RSOD does not occur when playing the following games Thief(2014), Sniper Elite 3, Tomb Raider(2013), Mortal Kombat X and Unreal Tournament 3 (both cards confirmed working flawlessly in Crossfire by using "Show AMD CrossireX status Icon" from the Catalyst System tray icon). These Crossfire RSOD's do not occur at all when running the 15.6 beta's for Windows 8.1.
/TL;DR

On Windows 10 Pro x64, when I start select 3D applications/games with 7970M Crossfire enabled and the application/game launches to fullscreen mode from the Windows desktop, my laptop immediately crashes with a blank red screen of death (RSOD) and then reboots after Windows has completed creating the dump file. Usually there is a millisecond of what looks like corrupted textures before the blank red screen comes up.

- Only occurs when Crossfire is enabled with drivers 15.7, 15.7.1, 15.7.1 Hotfix1 and 15.7.1 Hotfix2.
- Does not occur with 15.6 beta for Windows 8.1 x64 (14.502.1014.1001)
- If I create a custom profile for Metro Last Light with AFR Friendly Crossfire Mode, Metro Last Light does not BSOD/RSOD on startup and plays without issue. Crysis 3 works with an AFR Friendly Crossfile Profile as well with no BSOD/RSOD but certain textures are dark. 3Dmark still crashes with an AFR Friendly profile. I have not tested the other games with the different Crossfire Modes.
- These BSOD/RSOD's occur on the following applications that I am able to test with 3Dmark Firestrike, Crysis 3, Metro Last Light, Grid Autosport, Project Cars and Alien Isolation.
- The BSOD/RSOD does not occur when playing the following games Thief(2014), Sniper Elite 3, Tomb Raider(2013), Mortal Kombat X and Unreal Tournament 3 (both cards confirmed working flawlessly in Crossfire by using "Show AMD CrossireX status Icon" from the Catalyst System tray icon).
- The BSOD/RSOD does not occur when Crossfire is disabled or if the application/game is run in window mode.

I have tested each graphic card independantly in the first pci-express slot and I receive no errors. I have tried another set of 4gb DIMM's as well with the same result. I have also tried another crossfire cable to rule out that as a possible cause but since I dont receive the error with 15.6 Beta's and I'm able to workaround the error in Metro Last Light and Crysis 3 with a custom Crossfire profile using AFR, I dont think its hardware related.

My hardware is not overclocked. I have stress tested my RAM using Memtest at boot for 11 passes, my CPU using Prime95 for 12 hours with the blend setting and GPU's using 15.6 beta's for Windows 8.1 with 3Dmark's "Run Primary Test's" which runs all tests including their demo's consecutively. No errors occured in any of these tests. I know running 3Dmark is not an ideal GPU stress test but since I do not experience the RSOD's with earlier drivers I am not going to submit my cards to the torture that is FurMark.

As I mentioned the RSOD does not occur after a period of time when gaming, it occurs immediately when select applications/games launch into fullscreen mode when Crossfire is enabled and running the 15.7, 15.7.1, 15.7.1 Hotfix1 and 15.7.1 Hotfix2 drivers. I do not have an integrated GPU, the 7970M's are dedicated cards in my machine.

Please find Windows 10 memory dumps at the link below. It includes minidumps as well as two full memory dumps, hence the size. I have used WinRAR to compress the files using RAR5 in order to reduce the file size from 19GB to 2GB.

https://drive.google.com/file/d/0B8IDXugAxTo-QkJvR2N6Z0lOejA/view?usp=sharing
MD5: CDAF44E9EF2CF8533D0B2B87CEBAAA6A

I'm sure you will be able to retrieve some of my system specifications from the Windows dump files as well as the attached files but I have included the core components below in the interests of being thorough.

Alienware M17X R2
CPU: Intel Core i7 920XM
RAM: 2 x 4GB Samsung DDR3 1600Mhz running at 1333Mhz
GPU: 2 x Clevo AMD Radeon 7970M
HDD: 256GB Samsung 830 Series SSD
MB Chipset: PM55 Express

Your help would be greatly appreciated :smile9:
 

Attachments

Missing drivers for what seems to be a Ricoh Card Reader. Please install the latest, W10 compatible version.

No memory dumps in the uploaded reports.
KernelDumpList report shows C:\Windows\MEMORY.dmp
Please zip it up and upload it to a free file-hosting service (like OneDrive or DropBox), share it, and then post a link to it here.

Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump
More info on dump file options here: http://support.microsoft.com/kb/254649

Your UEFI/BIOS (version A10) dates from 2011. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.

Lot's of crashes with SearchUI.exe Could be problems with Cortana: https://www.reddit.com/r/Windows10/comments/3ay8h1/how_to_completely_disabled_cortana_searchuiexe/

I'm uncertain about Stardock - but have to wonder about adding it to a system that's not stable - it'll interfere (IMO) with the troubleshooting.
I'd also suggest uninstalling the Radeon Pro stuff.
In short, start with a plain install of W10, then update and try new things one-by-one.
 
Attempted to download and open the 1.9 gB .rar file
Cannot open it.

I'd suggest:
1) Use .zip rather than .rar
2) Zip the minidumps separately and upload them here
3) If needed, you can zip the MEMORY.dmp files separately and upload them separately
 
Thanks for your response @usasma, its much appreciated.

I have attached the minidumps. I have zipped them rather than using WinRAR as requested.

Unfortunately my A10 BIOS is the latest available for my machine.

Thanks for the info on Cortana I have disabled it.

The minidump files attached were taken on a much leaner OS install without Stardock, RadeonPro or anything that I didnt really need to replicate the RSOD. Thats the reason my Ricoh Card Reader drivers have not been installed as yet, I havent gotten around to it.

I will zip a full memory dump and upload it shortly.
 

Attachments

I have uploaded the full memory dump (657MB). Please find the link below.

https://drive.google.com/file/d/0B8IDXugAxTo-V18tM0pYTWl6aGs/view?usp=sharing
Zipped MEMORY.zip MD5: 3E52638752B520C53755661F485CC89C
Extracted MEMORY.DMP MD5: D3B273F6AE6733467B9A865466697AEE

I also have WinDBG installed if you would like me to execute any commands on the full memory dump if you experience any problems downloading or opening the file.

Thank you for your help.
 
First off, you have to keep in mind that this problem may not be fixable.
It may simply be that the system is not compatible w/W10.
But, we'll continue to try and fix things for as long as you want.

Please note that these minidumps are all STOP 0x7E errors.
The significance of this is that they are more likely to be hardware/compatibility problems than a lot of other errors.
The fact that they all blame video drivers implies that it's a video issue (either hardware or software).

Are you able to run the system with only 1 video card at a time?
If so, please do so - for long enough to see if either card indivually experiences BSOD's.
If not, then we can assume that the problem is due to Crossfire (either hardware or software).

Get rid of the program associated with WinRing0x64.sys It is a known cause of BSOD's on some Windows systems - and is especially suspect as the driver itself dates from 2008.
This is most likely a component of a program named Throttle Stop - please uninstall it.

Also uninstall the program associated with ssgdio64.sys (it dates from 2005). Showshock Softnology Generic Driver
It's most likely associated with ATI Diagnostics Hardware Abstraction Sys
I would really wonder about this one!!!
Please make sure that this one is uninstalled!

Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Mon Aug 10 12:58:18.073 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\081015-8343-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: [B]1024[/B]0.16412.amd64fre.th1.150729-1800
System Uptime:[B]0 days 0:02:37.745[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+329fa )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff80103fc29fa, ffffd00020db58b8, ffffd00020db50d0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80103fc29fa, The address that the exception occurred at
Arg3: ffffd00020db58b8, Exception Record Address
Arg4: ffffd00020db50d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: [B]AV_atikmdag+329fa[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU       X 920  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A10
  BIOS Release Date             01/17/2011
  Manufacturer                  Alienware
  Product Name                  M17x
  Baseboard Product                   
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 10 12:55:10.255 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\081015-8453-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: [B]1024[/B]0.16412.amd64fre.th1.150729-1800
System Uptime:[B]0 days 0:02:20.926[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+329fa )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff8008d0d29fa, ffffd00020d568b8, ffffd00020d560d0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8008d0d29fa, The address that the exception occurred at
Arg3: ffffd00020d568b8, Exception Record Address
Arg4: ffffd00020d560d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: [B]AV_atikmdag+329fa[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU       X 920  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A10
  BIOS Release Date             01/17/2011
  Manufacturer                  Alienware
  Product Name                  M17x
  Baseboard Product                   
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Aug 10 12:52:17.073 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\081015-8265-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: [B]1024[/B]0.16412.amd64fre.th1.150729-1800
System Uptime:[B]0 days 0:12:56.745[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+329fa )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff800e87f29fa, ffffd001636fe8b8, ffffd001636fe0d0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800e87f29fa, The address that the exception occurred at
Arg3: ffffd001636fe8b8, Exception Record Address
Arg4: ffffd001636fe0d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: [B]AV_atikmdag+329fa[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU       X 920  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A10
  BIOS Release Date             01/17/2011
  Manufacturer                  Alienware
  Product Name                  M17x
  Baseboard Product                   
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug  9 11:39:30.376 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080915-9687-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: [B]1024[/B]0.16412.amd64fre.th1.150729-1800
System Uptime:[B]0 days 0:10:50.047[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+329fa )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff8013fc729fa, ffffd0002097e8b8, ffffd0002097e0d0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8013fc729fa, The address that the exception occurred at
Arg3: ffffd0002097e8b8, Exception Record Address
Arg4: ffffd0002097e0d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: [B]AV_atikmdag+329fa[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU       X 920  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A10
  BIOS Release Date             01/17/2011
  Manufacturer                  Alienware
  Product Name                  M17x
  Baseboard Product                   
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug  9 10:16:36.956 2015 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\080915-7750-01.dmp]
Windows 8 Kernel Version 10240 MP (8 procs) Free x64
Built by: [B]1024[/B]0.16393.amd64fre.th1_st1.150717-1719
System Uptime:[B]0 days 0:51:42.627[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+329aa )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff801fd9e29aa, ffffd00020b558b8, ffffd00020b550d0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff801fd9e29aa, The address that the exception occurred at
Arg3: ffffd00020b558b8, Exception Record Address
Arg4: ffffd00020b550d0, Context Record Address
PROCESS_NAME:  System
BUGCHECK_STR:  AV
FAILURE_BUCKET_ID: [B]AV_atikmdag+329aa[/B]
CPUID:        "Intel(R) Core(TM) i7 CPU       X 920  @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: [B]1995[/B]
  BIOS Version                  A10
  BIOS Release Date             01/17/2011
  Manufacturer                  Alienware
  Product Name                  M17x
  Baseboard Product                   
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Mon Aug 10 12:58:18.073 2015 (UTC - 4:00)**************************
ssgdio64.sys                Fri Sep  9 14:40:54 2005 (4321D736)
itecir.sys                  Thu Apr 28 06:11:05 2011 (4DB93D39)
stdcfltn.sys                Fri Jul 13 19:30:14 2012 (5000AF86)
ST_Accel.sys                Tue Aug  6 13:08:21 2013 (52012D85)
ITECIRfilter.sys            Wed May 14 03:45:04 2014 (53731F00)
NETwew01.sys                Tue Jan  6 11:19:19 2015 (54AC0B07)
e1i63x64.sys                Thu Mar 26 16:24:57 2015 (55146B19)
intelppm.sys                Thu Jul  9 23:12:59 2015 (559F383B)
atikmpag.sys                Tue Jul 28 22:22:05 2015 (55B838CD)
atikmdag.sys                Tue Jul 28 22:46:46 2015 (55B83E96)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug  9 11:39:30.376 2015 (UTC - 4:00)**************************
GPUZ.sys                    Wed Oct  6 12:14:37 2010 (4CACA06D)
cpuz138_x64.sys             Thu Feb 26 02:04:34 2015 (54EEC582)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Aug  9 10:16:36.956 2015 (UTC - 4:00)**************************
WinRing0x64.sys             Sat Jul 26 09:29:37 2008 (488B26C1)
atikmpag.sys                Wed Jul 15 21:13:26 2015 (55A70536)
atikmdag.sys                Wed Jul 15 21:37:09 2015 (55A70AC5)
[/font]
ssgdio64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=itecir.sys
http://www.carrona.org/drivers/driver.php?id=stdcfltn.sys
http://www.carrona.org/drivers/driver.php?id=ST_Accel.sys
http://www.carrona.org/drivers/driver.php?id=ITECIRfilter.sys
http://www.carrona.org/drivers/driver.php?id=NETwew01.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=GPUZ.sys
http://www.carrona.org/drivers/driver.php?id=cpuz138_x64.sys
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
 
Thank you for your analysis @usasma. I will remove ThrottleStop (WinRing0x64.sys). I am unsure about ssgdio64.sys but I have a feeling it is either GPU-Z or GPUShark which I run occasionally. They aren't installed programs but I will delete them as well as the ssgdio64.sys file.

I understand it could be a hardware incompatibility that I cannot avoid and I am fine with that. The thing is, I dont experience this error with any of the AMD Catalyst drivers from 15.6 or earlier. If I use 15.7 or 15.7.1 (Hotfix1 and Hotfix2) I experience the 0x7E bugchecks. I am able to run other applications and games with the 15.7 or 15.7.1 drivers. I can even workaround the bugcheck by creating my own crossfire application profile and it works without error for some of the apps/games that I experience the error with. I was hoping you could provide a more detailed analysis to determine if is a hardware fault or the if the GPU driver is at fault. From my troubleshooting I'm leaning towards the game/application specific profile for Crossfire created by AMD.

The furthest I got was analysing the trapframe below but I dont know how to trace backwards to figure out how the virtual address 10 got into the rbx+rax registers. It doesnt seem to contain a valid value and I want to figure out why the CPU tried to execute code at this address.

Code:
0: kd> .trap ffffd000`2097e960NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe001705e1000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8013fc729fa rsp=ffffd0002097eaf0 rbp=0000000000000001
 r8=0000000000000000  r9=ffffd0002097ebb0 r10=ffffe0016d668020
r11=ffffd0002097ebc8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
atikmdag+0x329fa:
fffff801`3fc729fa 488b5cc310      mov     rbx,qword ptr [rbx+rax*8+10h] ds:00000000`00000010=????????????????


0: kd> !pool fffff801`3fc729fa
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
Pool page fffff8013fc729fa region is unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
Unknown
fffff8013fc72000 is not a valid large pool allocation, checking large session pool...
Unable to read large session pool table (Session data is not present in mini and kernel-only dumps)
fffff8013fc72000 is not valid pool. Checking for freed (or corrupt) pool
Bad previous allocation size @fffff8013fc72000, last size was 0

I honestly dont know if I'm even on the right track here as I'm totally out of my depth and am using info from various posts/blogs that seem to be relevant.
 
A BSOD/memory dump doesn't provide an exact determination of hardware or software.
Even in the instances where it does point to hardware, there's still a possibility of it actually being software.

A broken piece of hardware can act the same as an incompatible piece of hardware.
And either can be mimicked by a problem with a driver that operates on lower level OS functions.

To determine this we use various troubleshooting techniques - but they all boil down to hardware and software tests/checks.
Stability is the key here - so we generally only mess with the latest version of the drivers - presuming that AMD has done sufficient testing to ensure that the drivers work well.

Next, we don't usually bother determining exactly where the problem lies - simply because we can't do anything to fix problems at that level.
We are not driver developers, and the skills required to do this are more suited to driver developers.
I will ask a friend to have a look at this as he's more adept at this sort of memory dump analysis than I am.

Also, as you're going more in depth that we usually do here, you may want to consider posting over at OSROnline in their WinDbg list: ListServer/Forum
They will have the in-depth experience with WinDbg that you seem to want.
 
Thank you for the information and advice @usasma. I will post over at OSROnline as well. I appreciate you referring this to your friend, hopefully they can shed more light on the matter. I'm also hoping AMD release a newer revision of the GPU drivers soon that resolves this as it seems a lot a of users are experiencing various Crossfire issues on Windows 10.

On a side note I did enable Driver Verifier and it was unable to catch the crash. I still get the normal 0x7E bugcheck without any reference to Driver Verifier. I had all options ticked apart from the code integrity check which apparently is only usable if the driver was built using Windows 10 WDK.
 
Thanks for taking the time to analyse the memory dump @xBlueRobot :smile9:

Just to clarify, are you saying that the AMD driver requested an instruction from invalid memory? I know it might be more complex than face value but that would mean the AMD driver is at fault?

The new beta driver was released today which I was pinning all my hopes on and sadly theres no change. I have made another discovery though, I dont get the bugchecks if I create an application profile for the offending app/game in the AMD catalyst driver control panel and specify AFR (Alternate frame rendering) friendly mode.

I have no hope of getting the AMD driver team to fix this though as I havent found any reports of this particular behaviour elsewhere. I'll keep reporting it in the hopes they fix it to shut me up :grin1:
 
Just an update on the situation, I did post about my issue on the AMD support forums as well and two members came forth today with exactly the same symptoms! I can actually replicate one of the members symptoms on my laptop and that particular member is running a desktop. So its fairly safe to assume my hardware is not to blame! :dance:
 
If anyone stumbles across this thread while troubleshooting, I'm glad to report that this issue has been resolved with AMD's latest Crimson driver 16.5.2.

I'd like to thank all the members who provided support and advice and spent time analyzing the issue, it's greatly appreciated :smile9:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top