New PC suddenly freezes with no warning

Generally a freeze like that will be caused by something that has to operate fast and does that by not doing error checking.
Your top candidates for this are firmware inside of solid state drive or more likely your graphics driver.
Your graphics driver has to run fast. The people that write the driver strip out error checking because they have almost full control of the device and can get away with it most of the time.

generally, update the graphics device driver takes care of the problem. Now, there is another issue with the device driver that can cause a hang.
The device driver for the graphics card has to support sound for HDMI and display port. Sound drivers for other sound devices can mess with each other and cause the whole graphics card to get "confused" and stop responding. What you want to do in this case is go into
control panel, find device manger under the hardware section. look at the high definition sound sources and disable the ones you don't use.
I turn off the one in my graphics card because I don't have speakers in my monitor. I think I have 5 sound sources and disabled 4 of them, I use the one on my mother board for most things.

give the update a shot (and disable the extra HD sound) and see if that solves your problem.

I can think of other possible causes but try the easy fixes first

I had that too, but it usually happened in the first 15 minutes or less of using the computer. After that, reboot, and it was good for the whole day. Then for days it wouldn't happen at all and out the blue, happened again. I rarely got a BSOD about a Kernel or IRQL problem too, but not often.

I tried all sorts of stuff, even going so far as to delete unneeded startup programs and replacing my Video card as the driver for it didn't exist for Win8.1 and I was using the W8 driver.

In ALL instances it seemed to clear the problem only to have it come back again.

What seems to have cleared it now for 2 weeks was something I saw on a web search that was obscure.

You, like me, have an SSD, and my OS is on the SSD. The suggestion was to run CHKDSK on the drives (I have 3, 1 SSD and 2 Mechanical). All had to be set to run on the next boot. Did that and rebooted. First the SSD and then the 2 other drives were run. No error messages, only normal stage messages. Then it said it was rebooting, and on the reboot it ran the SSD again, and it took longer than the first one. I feared I'd be in a continuous loop of CHKDSK running, but it wasn't the case. After the SSD was run Windows booted. I searched all over for CHKDSK error reports and couldn't find anything, nothing, no log, no FOUND.000 folders, nothing.

However, since that was done, no more problems. Give it a try. One thing I did notice, when booting, those circular dots... after a crash they took longer to appear on the Windows Flag first start screen. Occasionally they also took longer, but I didn't see a pattern. Now it is ALWAYS fast. Possible a lock/freeze or self-inflicted reboot I had caused some bad pointers on the SSD which loaded back code and poof, when you branched to it, the result was a freeze?

Well, off hand, no?

I'd suggest a few more things that you might not have tried. A new machine, I assume a month or so old? If it started immediately since you have it, I'd call the purchase point and return it or get warranty service.

I you can't, the next best thing is to open the case and check ALL connections and the heat sinks to make sure they are making proper contact. Must be done with the power OFF and the power plug removed and I'd ground yourself too. Also reseat the memory.

Lastly, how is your power? Is it stable? Are you connected to a surge protector or UPS? I'll assume you've had a computer prior to this without these problems, so that might not be the cause?

Can you see anything in the Event Viewer matching the time it locked up?

Was anything open when it was idle, that might have triggered it?

Locking up and then shutting down with doing the SHUTDOWN can still cause problems. Once rebooted, open MY COMPUTER and right click on all your drives and select PROPERTIES. Then the TOOLS and SCAN DRIVES for errors, see if that finds anything?

-make sure you get your system as up to date as you can, update all of the windows patches

I would update my BIOS next and make sure I pick up any updated device drivers for my motherboard.
particularly any chipset drivers,
get your chipset drivers from intel

https://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Software+Products&ProductLine=Chipset+Software&ProductProduct=Intel%C2%AE+Chipset+Software+Installation+Utility


Then I would enable my machine to do a memory dump on request
http://www.novell.com/support/kb/doc.php?id=7004093

if you get a hang you would try to force a memory dump. using the keyboard

if you want you can force a memory dump while your system is working and I will take a quick look at in the debugger to see if I can see a problem before you system even hangs.
you would just have to put the memory dump on a cloud share with public access (like on skydrive)

based on you symptoms, I would also enable hotswapping on the SSD drive port if you have that option in BIOS.
I would also look at event viewer for any drive resets done by windows. (might not show up if hotswap was not enabled)

I took a quick look of the dump from the working system.
I would remove a few drivers
start with
gdrv.sys Thu Mar 12 20:22:29 2009 \C:\Windows\gdrv.sys i think is a old gigabyte easytune driver
next suspect drivers would be the USB charger drivers
AppleCharger.sys Sun Oct 27 18:59:21 2013
UsbCharger.sys Thu Oct 24 02:26:43 2013


I would also confirm that your SSD drive has up to date firmware, I would also boot into BIOS and leave the system powered on to allow the SSD drive to run its trim and garbage collection routines (do this now, and always before you attempt to update SSD firmware)


here are my debug notes on the working system:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
BIOS Version F7
BIOS Release Date 08/03/2013
Manufacturer Gigabyte Technology Co., Ltd.
Product Name Z87X-UD3H
Product Z87X-UD3H-CF
Processor ID c3060300fffbebbf

Processor Version Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Processor Voltage 8ah - 1.0V
External Clock 100MHz
Max Speed 7000MHz
Current Speed 3400MHz


memory
bank 0 none
bank 1 ChannelA 4096MB 1600MHz Part Number F3-12800CL9-4GBXL
bnak 2 none
bank 3 ChannelB 4096MB 1600MHz Part Number F3-12800CL9-4GBXL

drivers of interest: (just the list of drivers that the debugger did not confirm that their memory image was not corrupt)
SamsungRapidFSFltr.sys Mon Jul 29 11:55:39 2013
SamsungRapidDiskFltr.sys Mon Jul 29 11:55:38 2013
mvs91xx.sys Mon Jul 29 23:52:22 2013
mvxxmm.sys Mon Jul 29 23:51:32 2013
iaStorA.sys Thu Aug 01 18:39:52 2013
dtsoftbus01.sys Thu Jun 20 00:22:51 2013
AppleCharger.sys Sun Oct 27 18:59:21 2013
UsbCharger.sys Thu Oct 24 02:26:43 2013
atikmpag.sys Fri Dec 06 12:21:45 2013
Dot4.sys Mon Aug 06 10:01:00 2012
dc3d.sys Mon Aug 05 23:07:46 2013
dot4usb.sys Mon Jul 13 17:00:20 2009
e1d64x64.sys Thu Aug 29 16:55:45 2013
igdkmd64.sys Wed Dec 18 12:49:12 2013
TeeDriverx64 Thu Sep 05 11:02:18 2013
iwdbus.sys Thu Sep 26 14:38:04 2013
RTKVHD64.sys Tue Sep 10 06:37:35 2013 Realtek(r) High Definition Audio Function Driver
Dot4Prt.sys Thu Aug 02 10:35:46 2012
gdrv.sys Thu Mar 12 20:22:29 2009 *** image path not in drivers directory \??\C:\Windows\gdrv.sys
gigabyte device driver?

Note: how did you install windows on this machine? install program or image software?

The firmware inside a SSD will have to do a bunch of clean up functions, some of these will be triggered by the operating system as various files are deleted. (basic TRIM functions) other are done internal to the Solid state drive and are used to substitute bad blocks when write errors occur (each block on a solid state drive can only be written to 2k to 3k times before the block starts to fail. When this happens the internal firmware has to move the data to a reserved block and mark the original block as bad. If this process takes more than 30 seconds windows will issue a reset to the SATA port the device is on. It does this in order the hope that the port reset will start the device communications working again. I have seen SSD do this and basically freeze a system for several minutes without causing a bugcheck. In the cases I actually looked at they turned out to be firmware bugs.
Given the fact that you have updated the firmware, and your machine looks like it has two different SATA chips, I would move the drives sata port to a port on the other chip and see if the problem still occurs.

Also, how much free space on the SSD drive do you have?
In windows 8 you can trigger the TRIM commands to do the TRIM cleanup on the SSD by running the defrag program. It is smart enough not to attempt to defrag a SSD but it will run TRIM for you. After you do that
You can boot into BIOS and leave the system powered on for a hour or two and the SSD internal firmware routines will start after a few minutes do its garbage collection. If the cause of the hang is due to starvation of the internal routines in the firmware of the SSD this will cause a delay in the occurrence of the next hang.
(it will all depend on how much IO is being done on the drive)

second note: why does the system not bugcheck in this condition. Normally, if the SSD gets hung up in its firmware, windows will reset its port. after a period of time it should bugcheck just like you unplugged the data cable on the SSD. But, it will not bugcheck until the system needs to page in a critical data from the pagefile.
If you have plenty of memory in your system, it might go several hours at idle before something is scheduled to run that is not all ready in memory. Then you would get your bugcheck, but it won't be able to write it to the disk and the data will be gone, no logs will be written for the entire time the drive was "disconnected"

So what you might do is limit the systems access to memory when you boot to see if you get the hang faster.
run msconfig.exe
select boot, advanced options and click the memory box and type in a reduced amount of memory, hit ok and reboot. (just in case you care to try)

-if you can get the system to reproduce the problem quickly then you could boot the system in safe mode with VGA only and you would know that it is not the graphics drivers that caused the problem.

that would do it. now you know it is in the ATI graphics drivers or ATI sound driver

I just looked at the first dump. it does indicate a deadlock in the graphics driver.
you have the same graphics driver as I have installed, I have the amd high def audio driver installed but
and it looks like you don't have it installed.
your build: Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
you have the newer 7790, i have the older 6870 card.

I could not dump the memory structures because it was a mini dump. you need a full kernel dump to look at the locks.
the second dump looks like a kernel dump, will look at in the morning

note: running ASGT.exe in memory ASUS GPU Tweak, tweaking and clocking tool for ASUS graphics cards
note: you can report the bug about the deadlock in Display Driver ver. 13.251 to amd
http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64
(and get the new beta driver at the same place)

edit: here is a good description of what a deadlock is(just fyi)
http://www.codeproject.com/Articles/7919/Debug-Tutorial-Part-7-Locks-and-Synchronization-Ob

Note: amd has new beta drivers posted on 2/1/2114 I would give them a shot in the hope it has a fix for the deadlock problem in your current driver

here is the debug output for the second freeze.
It is a deadlock in the graphics driver. (program error)
your system is up to date, no corruption in you OS files
all you can really do is talk to AMD and see if you can get a fixed driver.
You can provide them the second memory dump and it will be very easy for them to debug because you have verifier flags turned on.
You might be able to avoid hitting this problem if you change the timing of the hardware (slow it down) or install the audio portion of the graphics driver (will slow the driver down).

other than that, you just have to wait for new drivers from amd


--------------------
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\john\Downloads\MEMORY (3)\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred http://msdl.microsoft.com/download/symbols
Deferred srv*d:\symbols
*http://msdl.microsoft.com/download/symbols
Symbol search path is: http://msdl.microsoft.com/download/symbols;srv*d:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
Machine Name:
Kernel base = 0xfffff803`3ce06000 PsLoadedModuleList = 0xfffff803`3d0ca990
Debug session time: Sun Feb 2 22:34:41.107 2014 (UTC - 8:00)
System Uptime: 0 days 1:35:55.789
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {1001, ffffe000069701e0, ffffe0003bd6dd70, 0}

*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+9e43b7 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000001001, Verifier predicted potential deadlock.
Arg2: ffffe000069701e0, Lock address.
Arg3: ffffe0003bd6dd70, Verifier internal data.
Arg4: 0000000000000000

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


BUGCHECK_STR: 0xc4_1001

DRIVER_DEADLOCK: issue: 0000000000001001 ffffe000069701e0 ffffe0003bd6dd70 0000000000000000

Deadlock detected (4 locks in 3 threads):

=================================================
Thread 0: TERMINATED took locks in the following order:

Lock A = ffffe000069701e0 (+0xffffe000069701e0) - Type 'Fast Mutex'.

Stack: fffff80002bf29fe atikmdag+0x00000000009e59fe
fffff8000295bd69 atikmdag+0x000000000074ed69
fffff8000222a845 atikmdag+0x000000000001d845
fffff80002945d53 atikmdag+0x0000000000738d53
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
fffff800020f6b01 atikmpag+0x0000000000005b01
fffff8000214ab66 atikmpag+0x0000000000059b66
fffff80001d4ab94 dxgkrnl!DpiDxgkDdiStartDevice+0x0000000000000058
fffff80001d48ea0 dxgkrnl!DpiFdoStartAdapter+0x0000000000000358

Lock B = ffffcf8002c48fc0 (+0xffffcf8002c48fc0) - Type 'Mutex'.

Stack: fffff8033d479f4c nt!VerifierKeWaitForSingleObject+0x0000000000000180
fffff80002245239 atikmdag+0x0000000000038239
fffff80002c0bd96 atikmdag+0x00000000009fed96
fffff80002395fd8 atikmdag+0x0000000000188fd8
fffff80002c03a75 atikmdag+0x00000000009f6a75
fffff80002bf2a25 atikmdag+0x00000000009e5a25
fffff8000295bd69 atikmdag+0x000000000074ed69
fffff8000222a845 atikmdag+0x000000000001d845

=================================================
Thread 1: TERMINATED took locks in the following order:

Lock B = ffffcf8002c48fc0 (+0xffffcf8002c48fc0) - Type 'Mutex'.

Stack: fffff8033d479f4c nt!VerifierKeWaitForSingleObject+0x0000000000000180
fffff80002245239 atikmdag+0x0000000000038239
fffff80002c0bd96 atikmdag+0x00000000009fed96
fffff80002396331 atikmdag+0x0000000000189331
fffff80002c03be6 atikmdag+0x00000000009f6be6
fffff80002bf2a25 atikmdag+0x00000000009e5a25
fffff8000295bd69 atikmdag+0x000000000074ed69
fffff8000222a845 atikmdag+0x000000000001d845

Lock C = ffffcf8001e20f68 (+0xffffcf8001e20f68) - Type 'Mutex'.

Stack: fffff8033d479f4c nt!VerifierKeWaitForSingleObject+0x0000000000000180
fffff80002308102 atikmdag+0x00000000000fb102
fffff80002307e68 atikmdag+0x00000000000fae68
fffff8000221cdc0 atikmdag+0x000000000000fdc0
fffff80002c0cc18 atikmdag+0x00000000009ffc18
fffff80002396364 atikmdag+0x0000000000189364
fffff80002c03be6 atikmdag+0x00000000009f6be6
fffff80002bf2a25 atikmdag+0x00000000009e5a25

Lock D = ffffcf8001ef0fc4 (+0xffffcf8001ef0fc4) - Type 'Mutex'.

Stack: fffff8033d479f4c nt!VerifierKeWaitForSingleObject+0x0000000000000180
fffff80002245239 atikmdag+0x0000000000038239
fffff80002b76272 atikmdag+0x0000000000969272
fffff80002b6f201 atikmdag+0x0000000000962201
fffff80002b72840 atikmdag+0x0000000000965840
fffff8000225afab atikmdag+0x000000000004dfab
fffff8000225b01c atikmdag+0x000000000004e01c
fffff80002308185 atikmdag+0x00000000000fb185

=================================================
Thread 2: ffffe000000de700 took locks in the following order:

Lock D = ffffcf8001ef0fc4 (+0xffffcf8001ef0fc4) - Type 'Mutex'.

Stack: fffff8033d479f4c nt!VerifierKeWaitForSingleObject+0x0000000000000180
fffff80002245239 atikmdag+0x0000000000038239
fffff80002b76272 atikmdag+0x0000000000969272
fffff80002b81d19 atikmdag+0x0000000000974d19
fffff80002b6e31c atikmdag+0x000000000096131c
fffff80002b72840 atikmdag+0x0000000000965840
fffff8000225b2a3 atikmdag+0x000000000004e2a3
fffff8000225bb64 atikmdag+0x000000000004eb64

Lock A = ffffe000069701e0 (+0xffffe000069701e0) - Type 'Fast Mutex'.

Stack: << Current stack trace - use kb to display it >>


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER: from fffff8033d4726a8 to fffff8033cf53ca0

STACK_TEXT:
ffffd000`21abf328 fffff803`3d4726a8 : 00000000`000000c4 00000000`00001001 ffffe000`069701e0 ffffe000`3bd6dd70 : nt!KeBugCheckEx
ffffd000`21abf330 fffff803`3d02d75b : 00000000`00000065 00000000`00000000 ffffe000`069701e0 ffffe000`3bd6dd70 : nt!VerifierBugCheckIfAppropriate+0x3c
ffffd000`21abf370 fffff803`3d480fef : fffff803`3d0a4a88 00000000`00001001 ffffe000`3bd6dd70 ffffe000`069701e0 : nt!VfReportIssueWithOptions+0xe3
ffffd000`21abf3b0 fffff803`3d47fabd : ffffe000`069701e0 ffffe000`06952c88 00000000`00000001 00000000`00000000 : nt!ViDeadlockAnalyze+0x243
ffffd000`21abf420 fffff803`3d482210 : ffffe000`069701e0 ffffd000`21abf601 fffff803`3ce06000 00000000`00000000 : nt!VfDeadlockAcquireResource+0x399
ffffd000`21abf520 fffff800`02bf13b7 : 00000000`00000010 00000000`00010282 fffff800`02ebb620 00000000`00000000 : nt!VerifierExAcquireFastMutex+0x3c
ffffd000`21abf560 fffff800`02bf3869 : ffffd000`21abf5f0 00000000`00000000 00000000`00000000 00000000`00000018 : atikmdag+0x9e43b7
ffffd000`21abf590 fffff800`02b767a9 : ffffcf80`01eeadf8 ffffcf80`01eeadf8 00000000`00000001 ffffcf80`01fd4fdc : atikmdag+0x9e6869
ffffd000`21abf5c0 fffff800`02b83b05 : ffffcf80`01fd4fdc 00000000`00000001 ffffcf80`01fd4b14 00000000`00010282 : atikmdag+0x9697a9
ffffd000`21abf630 fffff800`022a134a : 00000000`00000001 fffff800`0256ccb0 fffff800`024006f8 fffff800`02400440 : atikmdag+0x976b05
ffffd000`21abf670 fffff800`02b81d26 : ffffcf80`01fd4b14 ffffd000`21abf719 ffffd000`21abf700 00000000`00000043 : atikmdag+0x9434a
ffffd000`21abf6b0 fffff800`02b6e31c : 00000000`00000043 ffffd000`21abf7c0 ffffd000`21abf7c0 00000000`00000433 : atikmdag+0x974d26
ffffd000`21abf6e0 fffff800`02b72840 : ffffcf80`01f26554 fffff800`00000043 ffffd000`21abf858 ffffcf80`01ee6a01 : atikmdag+0x96131c
ffffd000`21abf780 fffff800`0225b2a3 : 00000000`00000000 00000000`00000018 00000000`00000004 fffff800`022bdf1b : atikmdag+0x965840
ffffd000`21abf800 fffff800`0225bb64 : 00000000`08050107 ffffe000`06904000 ffffe000`069102e8 00000000`08050107 : atikmdag+0x4e2a3
ffffd000`21abf880 fffff800`02259567 : ffffcf80`01ee6a60 ffffe000`06904000 ffffcf80`01ee6a60 00000000`00000000 : atikmdag+0x4eb64
ffffd000`21abf8b0 fffff800`02259176 : ffffe000`06904000 ffffcf80`01ee6a40 ffffe000`06904000 fffff803`3ce06000 : atikmdag+0x4c567
ffffd000`21abf8f0 fffff800`02243880 : 00000000`00000282 ffffe000`06904000 00000000`00000000 ffffd000`21abfb10 : atikmdag+0x4c176
ffffd000`21abf990 fffff800`0228d4f5 : ffffe000`06905010 fffff800`0229443c ffffe000`06904000 fffff800`0228d1b1 : atikmdag+0x36880
ffffd000`21abf9c0 fffff800`0228efa8 : 00000000`00000001 00000003`00000030 00000000`00000006 fffff800`0229459e : atikmdag+0x804f5
ffffd000`21abfa40 fffff800`022916f1 : ffffe000`06905008 ffffd000`21abfb69 00000000`00000001 00000000`00000001 : atikmdag+0x81fa8
ffffd000`21abfac0 fffff800`0228e105 : 00000000`00000008 ffffe000`06904000 ffffe000`000de700 ffffe000`06905008 : atikmdag+0x846f1
ffffd000`21abfbd0 fffff803`3ce932e4 : ffffe000`000de700 ffffe000`000de700 ffffd000`21abfc90 fffff803`3cf5707d : atikmdag+0x81105
ffffd000`21abfc00 fffff803`3cf5a2c6 : ffffd000`20743180 ffffe000`000de700 ffffd000`2074f240 00000000`00000002 : nt!PspSystemThreadStartup+0x58
ffffd000`21abfc60 00000000`00000000 : ffffd000`21ac0000 ffffd000`21aba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+9e43b7
fffff800`02bf13b7 3937 cmp dword ptr [rdi],esi

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: atikmdag+9e43b7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52a23f6f

FAILURE_BUCKET_ID: 0xc4_1001_VRF_atikmdag+9e43b7

BUCKET_ID: 0xc4_1001_VRF_atikmdag+9e43b7

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc4_1001_vrf_atikmdag+9e43b7

FAILURE_ID_HASH: {99b6d4c1-9fc4-ff20-b247-23a30f16a4e2}

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

2: kd> lmvm atikmpag
start end module name
fffff800`020f1000 fffff800`02191000 atikmpag (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Dec 06 12:21:45 2013 (52A231D9)
CheckSum: 0009FEFF
ImageSize: 000A0000
File version: 8.14.1.6354
Product version: 8.14.1.6354
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Advanced Micro Devices, Inc.
ProductName: AMD driver
InternalName: atikmpag.sys
OriginalFilename: atikmpag.sys
ProductVersion: 8.14.01.6354
FileVersion: 8.14.01.6354
FileDescription: AMD multi-vendor Miniport Driver
LegalCopyright: Copyright (C) 2007 Advanced Micro Devices, Inc.
2: kd> lmvm atikmdag
start end module name
fffff800`0220d000 fffff800`02efd000 atikmdag (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Dec 06 13:19:43 2013 (52A23F6F)
CheckSum: 00CA856E
ImageSize: 00CF0000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
2: kd> !deadlock
issue: 0000000000001001 ffffe000069701e0 ffffe0003bd6dd70 0000000000000000

Deadlock detected (4 locks in 3 threads):

Thread 0: A B.
Thread 1: B C D.
Thread 2: D A.

Where:

Thread 0 = TERMINATED.
Thread 1 = TERMINATED.
Thread 2 = ffffe000000de700.

Lock A = ffffe000069701e0 (+0xffffe000069701e0) - Type 'Fast Mutex'.
Lock B = ffffcf8002c48fc0 (+0xffffcf8002c48fc0) - Type 'Mutex'.
Lock C = ffffcf8001e20f68 (+0xffffcf8001e20f68) - Type 'Mutex'.
Lock D = ffffcf8001ef0fc4 (+0xffffcf8001ef0fc4) - Type 'Mutex'.

windows 8.x enables low power management by default. if there is a bug in the driver related to low power states you might just disable the link state transitions in the power management for the driver. just make it run in high performance mode using control panel power management and see if you still get the problem.

cause:
windows asked for some graphics memory and was not given it and just started waiting for the memory.
14 threads were blocked waiting for the first process request to complete, ( process just keep waiting, 1.4 million times )
Basically, the Window system just keeps checking if it is ok to up up its new windows put never gets permission from the graphics adapter.
it could be a bug in windows (direct x or in CDD.dll) but more likely a bug in the graphics driver as it failed to respond as it was expected.
Most likely if Microsoft did a fix they would just force try to reset the graphics adapter and if that failed they would bugcheck.
You have to determine why the graphics adapter did not respond and only AMD would be able to do that. (driver problem or hardware problem, or did they get a incorrect request from the OS)

I would report this to AMD. It has all the required debugging info in the memory dump and the files are up to date and no memory corruption.

What I would try:
- maybe change hardware graphics acceleration used by the OS or browser until the problem is worked out.
- Maybe disable any themes or screen savers or if you do have one don't let it change to an new background automatically.




more info:


It looks like windows wanted to create a window, did its allocations, set it location, then wanted to use the hardware acceleration provided by the graphics adapter. To do this it then called its CDD.dll (canonical display driver) which called the directx kernel driver which talks to the vendors graphics driver. The directx driver wants a lock on a section of memory in the graphics driver and the graphic driver never gave it a lock. This
resulted in 14 threads getting backed up waiting for access to the graphic card memory. Basically, there are 1.4 million attempts to gain access which caused your system to hang.
------

here is the debug info:

Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505

System Uptime: 0 days 2:07:41.725


0: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks.........................

Resource @ 0xffffe00007ffb438 Exclusively owned
Threads: ffffe00000287080-01<*>
KD: Scanning for held locks....

Resource @ 0xffffe0000812b9f0 Exclusively owned
Contention Count = 1427973
NumberOfSharedWaiters = 1
NumberOfExclusiveWaiters = 10
Threads: ffffe000090ba080-01<*> ffffe00008995080-01
Threads Waiting On Exclusive Access:
ffffe000093e5880 ffffe00009375080 ffffe00008632080 ffffe00009924880
ffffe00009816880 ffffe000093a3880 ffffe00008509880 ffffe000006a4080
ffffe00009717880 ffffe00009765880



0: kd> .thread ffffe000090ba080
Implicit thread is now ffffe000`090ba080
0: kd> kv
*** Stack trace for last set context - .thread/.cxr resets it
Child-SP RetAddr : Args to Child : Call Site
ffffd000`248e6900 fffff802`01f2990e : ffffd000`20889180 ffffe000`090ba080 00000000`fffffffe 00000000`fffffffe : nt!KiSwapContext+0x76
ffffd000`248e6a40 fffff802`01f293a7 : ffffe000`090ba080 00000000`00000000 00000000`00000000 ffffe000`098739f0 : nt!KiSwapThread+0x14e
ffffd000`248e6ae0 fffff802`01f26af2 : fffff680`0dc1f801 00000000`00000001 00000000`00000004 ffffe000`0973fdf0 : nt!KiCommitThreadWait+0x127
ffffd000`248e6b40 fffff802`01ef8bde : ffffe000`09873990 ffffe000`0973fdf0 00000000`00000000 00000000`00000002 : nt!ExpWaitForResource+0x282
ffffd000`248e6c00 fffff800`01cd24c9 : 00000000`00000002 ffffc000`0c36d000 ffffd000`248e6db0 00000000`40001200 : nt!ExAcquireResourceExclusiveLite+0x1de
ffffd000`248e6c70 fffff800`01d2445e : 00000000`00000000 00000000`40001200 00000000`40001200 ffffd000`248e6ee8 : dxgkrnl!DXGDEVICEACCESSLOCKEXCLUSIVECDD:XGDEVICEACCESSLOCKEXCLUSIVECDD+0x91
ffffd000`248e6cb0 fffff960`00a53dda : fffff901`451de020 fffff901`45d69b80 00000000`000005c5 00000000`00000000 : dxgkrnl!DxgkCddCreateAllocation+0xca
ffffd000`248e6e60 fffff960`00a53a12 : 00000000`00000001 ffffe000`0814c3d0 ffffd000`248e7200 fffff802`01ef7ec2 : cdd!CDDPDEV::CreateAllocation+0x13e
ffffd000`248e6fb0 fffff960`00a538d1 : fffff901`00000000 00000000`00000000 fffff901`45d69b80 00000000`0000007f : cdd!CddBitmapHw::RecreateDeviceAllocations+0xae
ffffd000`248e7040 fffff960`00a522d6 : fffff901`451de020 fffff901`45d69b80 00000000`00000000 00000000`00000000 : cdd!CddBitmapHw::InitBitmap+0x85
ffffd000`248e7070 fffff960`000e78a8 : 00000000`00000000 00000405`000005c5 ffffd000`248e7209 ffffc000`0aa48560 : cdd!DrvCreateDeviceBitmapEx+0x226
ffffd000`248e7140 fffff960`000e3a18 : 00000000`00000000 00000000`00000405 00000000`00000000 00000000`00000000 : win32k!hsurfCreateCompatibleSurface+0x158
ffffd000`248e7250 fffff960`001d04c5 : 00000000`04000000 00000000`00000000 fffff901`00000001 00000000`00000000 : win32k!GreCreateCompatibleBitmap+0x1c0
ffffd000`248e7390 fffff960`001ce14a : 00000000`00000000 00000000`00000001 ffffd000`248e7440 fffff901`430780a0 : win32k!CreateOrGetRedirectionBitmap+0xf5
ffffd000`248e7410 fffff960`001cdf6e : 00000000`00000000 00000000`00000014 00000000`00000000 fffff960`001ceece : win32k!SetRedirectedWindow+0x7a
ffffd000`248e7470 fffff960`001cb70f : 00000000`00000000 fffff901`430780a0 00000000`00000000 00120674`40000018 : win32k!_SetLayeredWindowAttributes+0x8e
ffffd000`248e7540 fffff960`000c7026 : fffff901`430780a0 ffffd000`248e76e0 ffffffff`ac0f29d7 00000000`fffffff0 : win32k!ComposeWindow+0xcf
ffffd000`248e7580 fffff960`000c6cf0 : fffff901`430780a0 ffffd000`248e76e0 00000000`00000000 fffff901`42d682a0 : win32k!ComposeWindowIfNeeded+0x4e
ffffd000`248e75b0 fffff960`000dc583 : 00000000`00000000 fffff901`4514bd80 fffff901`4514bd80 00000000`00000000 : win32k!SetVisible+0xd8
ffffd000`248e75e0 fffff960`000fe94e : fffff901`4514bd80 ffffd000`248e77f9 fffff901`4514be20 fffff901`465feb70 : win32k!zzzChangeStates+0x5eb
ffffd000`248e7740 fffff960`000fdc50 : fffff901`42d682a0 fffff901`42d682a0 00000000`00000000 fffff901`465feb70 : win32k!zzzBltValidBits+0x10e
ffffd000`248e7860 fffff960`000ea290 : fffff901`00000001 fffff901`430780a0 00000000`00000000 fffff960`00000000 : win32k!xxxEndDeferWindowPosEx+0x1b4
ffffd000`248e7920 fffff960`000d5735 : fffff901`4306e330 00000000`06ff0000 fffff901`00000000 00000000`00000000 : win32k!xxxSetWindowPosAndBand+0xc0
ffffd000`248e79b0 fffff960`0029df61 : fffff901`4306e330 00000000`00000001 00000000`00000000 00000000`00000000 : win32k!xxxSetWindowPos+0x29
ffffd000`248e7a00 fffff960`0029d395 : fffff901`4306e330 00000000`00120674 00000000`00000000 fffff901`430780a0 : win32k!xxxShowGhostWindow+0x1d1
ffffd000`248e7a60 fffff960`001bf934 : 00000000`00000079 ffffd000`248e7b80 00000000`00120674 00000000`00000005 : win32k!xxxRegisterGhostWindow+0x165
ffffd000`248e7ad0 fffff802`01fde4b3 : ffffe000`090ba080 00000000`00120674 0000001b`ffd8b901 ffffd000`248e7b00 : win32k!NtUserCallTwoParam+0x44
ffffd000`248e7b00 00007ffd`40d89b2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ ffffd000`248e7b00)
0000001b`83f1f848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`40d89b2a
0: kd> .thread ffffe000090ba080
Implicit thread is now ffffe000`090ba080
0: kd> lmvm cdd
start end module name
fffff960`00a49000 fffff960`00a84000 cdd (pdb symbols) C:\ProgramData\dbg\sym\cdd.pdb\B566E9962A1D441F8F8DBCDA303243B81\cdd.pdb
Loaded symbol image file: cdd.dll
Mapped memory image file: C:\ProgramData\dbg\sym\cdd.dll\521605D03b000\cdd.dll
Image path: \SystemRoot\System32\cdd.dll
Image name: cdd.dll
Timestamp: Thu Aug 22 05:36:32 2013 (521605D0)
CheckSum: 0003D112
ImageSize: 0003B000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm dxgkrnl
start end module name
fffff800`01ccf000 fffff800`01e49000 dxgkrnl (pdb symbols) C:\ProgramData\dbg\sym\dxgkrnl.pdb\E086B2EA9F604B3AA1AAA5D13E77E4401\dxgkrnl.pdb
Loaded symbol image file: dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
Timestamp: Mon Nov 04 06:44:38 2013 (5277B2D6)
CheckSum: 00184A1C
ImageSize: 0017A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm win32k
start end module name
fffff960`000b4000 fffff960`004cd000 win32k (pdb symbols) C:\ProgramData\dbg\sym\win32k.pdb\BDE51F8DC20142DDB4CC8E26945610AF2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file: C:\ProgramData\dbg\sym\win32k.sys\52947414419000\win32k.sys
Image path: \SystemRoot\System32\win32k.sys
Image name: win32k.sys
Timestamp: Tue Nov 26 02:12:36 2013 (52947414)
CheckSum: 0040387C
ImageSize: 00419000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm nt
start end module name
fffff802`01e85000 fffff802`02606000 nt (pdb symbols) C:\ProgramData\dbg\sym\ntkrnlmp.pdb\A32C55CDEBC1441DAC80552A86F5F11F1\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Wed Oct 30 15:52:12 2013 (52718D9C)
CheckSum: 007120D6
ImageSize: 00781000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lmvm atikmdag
start end module name
fffff800`022b7000 fffff800`02fa7000 atikmdag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Fri Dec 06 13:19:43 2013 (52A23F6F)
CheckSum: 00CA856E
ImageSize: 00CF0000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm atikmpag
start end module name
fffff800`0204b000 fffff800`020eb000 atikmpag (deferred)
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Dec 06 12:21:45 2013 (52A231D9)
CheckSum: 0009FEFF
ImageSize: 000A0000
File version: 8.14.1.6354
Product version: 8.14.1.6354
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Advanced Micro Devices, Inc.
ProductName: AMD driver
InternalName: atikmpag.sys
OriginalFilename: atikmpag.sys
ProductVersion: 8.14.01.6354
FileVersion: 8.14.01.6354
FileDescription: AMD multi-vendor Miniport Driver
LegalCopyright: Copyright (C) 2007 Advanced Micro Devices, Inc.

------
0: kd> !chkimg -lo 50 -d !dxgkrnl
0 errors : !dxgkrnl
0: kd> !chkimg -lo 50 -d !nt
0 errors : !nt
0: kd> !chkimg -lo 50 -d !cdd
0 errors : !cdd
0: kd> !chkimg -lo 50 -d !win32k.sys
0 errors : !win32k.sys

I think it is a timing related issue in the driver, I would reduce the cards memory and GPU clock by 25MHz and see if it reduces how often it hits the problem.