If you cannot find an update for the drivers, try uninstalling the drivers for the keyboard and see if your system stabilizes. You will not be able to utilize the advanced functions of the keyboard like macro keys and whatnot, but typical keyboard usage will still function normally.
They do have an updated driver, straight from the TT Esports website:
http://usa.ttesports.com/download_FAQ.aspx
Anyways, I dumped the raw stack on the crashdump and I see what's most certainly stack overflow occurring here. Modules that looked to be involved were your ATI video drivers and your AMD motherboard chipset's SATA drivers (
amd_sata.sys). All your motherboard drivers look pretty out of date, including your BIOS, so you will want to go to the page listed
here and update any existing drivers you have on your system (chipset, sata, BIOS, etc.). Please make sure your system is relatively stable when updating your BIOS by closing any and all applications before running it. If your system crashes during BIOS flash update, there's the potential you may brick your motherboard. It's recommended you proceed with the driver updates before updating your BIOS unless the updates for the drivers somehow manages to make things worse (doubtful).
Analysts:
Dumped raw stack. 3rd-party drivers are highlighted:
Code:
4: kd> !thread
GetPointerFromAddress: unable to read from fffff80003103000
THREAD fffffa801130bb60 Cid 150c.10ac Teb: 000000007efdb000 Win32Thread: fffff900c3547c20 RUNNING on processor 4
Not impersonating
GetUlongFromAddress: unable to read from fffff80003042ba4
Owning Process fffffa80112558a0 Image: chrome.exe
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 10006620
Context Switch Count 456285 IdealProcessor: 5 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x0000000000c640ea
Stack Init fffff88008b0ac70 Current fffff88008b0a960
Base fffff88008b0b000 Limit fffff88008b02000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`03062538 fffff800`02ed12e9 : 00000000`0000000a 00000000`401b0033 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03062540 fffff800`02ecff60 : 00000000`00000000 fffff800`02f20306 fffffa80`1066bc60 00000000`401b0008 : nt!KiBugCheckDispatch+0x69
fffff880`03062680 fffff800`02edc943 : fffffa80`0d4ccc20 fffffa80`1034c3b0 fffffa80`1034c3b0 00000000`00000102 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`03062680)
fffff880`03062810 fffff800`02edc7ee : 0000016c`09ea8fac fffff880`03062e88 00000000`0098b05c fffff880`009b6108 : nt!KiProcessExpiredTimerList+0x103
fffff880`03062e60 fffff800`02edc5d7 : fffff880`009b31c1 fffffa80`0098b05c fffffa80`0e9c7d40 00000000`0000005c : nt!KiTimerExpiration+0x1be
fffff880`03062f00 fffff800`02ed4f15 : 070c0105`0a010508 fffffa80`1130bb60 00000000`00000000 fffff880`04809588 : nt!KiRetireDpcList+0x277
fffff880`03062fb0 fffff800`02ed4d2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5 (TrapFrame @ fffff880`03062e70)
fffff880`08b0aaa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
4: kd> dps fffff88008b02000 fffff88008b0b000 < Stack ranges, remember stacks grow backwards so have Limit as start and Base as end.
fffff880`08b02000 7f72918a`52fd72f2
fffff880`08b02008 38fcad5a`47b65c5f
fffff880`08b02010 edc41d33`c27fc772
fffff880`08b02018 b04978f2`bd087bf3
fffff880`08b02020 0acdeef3`10769e5b
fffff880`08b02028 ecc3336a`d619dd20
fffff880`08b02030 fe40c826`d96e91b3
fffff880`08b02038 e2b3ced0`bef5d832
fffff880`08b02040 835ed2b7`64fc7bfe
fffff880`08b02048 bf36aace`c6bd7b30 < all of this is trash. Notice it fills up the stack all the way to the limit.
fffff880`08b02050 4f5ffce7`4c7bf54b
fffff880`08b02058 1568eedf`eb5f9563
fffff880`08b02060 cd1faf91`35bc0eac
fffff880`08b02068 67f4bc37`3b47fa35
fffff880`08b02070 7dd9d3d8`3ea8db41
fffff880`08b02078 afbf5c6f`fb248d73
fffff880`08b02080 dad6bc8c`c6ca6f50
fffff880`08b02088 e3b3fc23`47dfb4e2
fffff880`08b02090 9a0599fc`7eb7bfb6
fffff880`08b02098 959f946d`7dfafb5f
fffff880`08b020a0 9760f4f0`49cdeaa7
fffff880`08b020a8 330ccbf5`acfabfec
fffff880`08b020b0 d2de0e40`cd2e351e
fffff880`08b020b8 8db29662`4e197bb3
...
fffff880`08b086d8 fffff880`00e523dbUnable to load image amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
amd_sata+0xd3db
...
fffff880`08b08d38 fffff880`010988fdUnable to load image amd_xata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_xata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys
amd_xata+0x18fd
...
fffff880`08b098e8 fffff880`04d08f0bUnable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
atikmdag+0x413f0b
...
I tried dumping the stack using
dc to see if the trash had any strings in it that could clue into cause but it all just looks like data. I cannot ascertain what it is right now. I could try and align it to see fi that will work, or try and see if it's code by disassembling it, but I feel it may not be worth the effort, given that this is a minidump, and therefore I could be running into a wall regardless.
