lol that was suppose to be do not haha. should have proof read
Sorry, what? I don'T get that.
it was suppose to read as If i stay on the game and do not fiddle with full screen or do not click over to the other screen I can play all day and not get a BSOD =)
Oh, yeah. That is actually what I was reading out of it. :D
Fullscreen, not touching anything else -> works fine.
Do something else while game is running -> BSOD.
Yeah, that is why I'm not sure about the GPU. Maybe it is just a software thing.
On the other hand when I read the reviews on newegg... maybe returning it isn't a bad idea.
You getting event 219? That's from asus's garbage software and apparently can't be uninstalled unless you completely wipe everything. I've removed AMD00 multiple times in multple ways and literally every time I turn my computer off and on again it's back. Total garbage, I have no idea how people recommend them.
Yeah I am also getting that Warning. I did the fix from Tomshardware hopefully that fixes it.
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffe000b0c9b080, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
FAULT_INSTR_CODE: ccccccccSYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5775e290
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2016-07-23T18:31:09.000Z
OSBUILD: 10586
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-06-30 23:26:45
BUILDDATESTAMP_STR: 160630-1736
BUILDLAB_STR: th2_release_sec
BUILDOSVER_STR: 10.0.10586.494.amd64fre.th2_release_sec.160630-1736
ANALYSIS_SESSION_ELAPSED_TIME: 3891
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
Here is part of my memory dump. If you want the whole thing just let me know.
Reinstall Windows and then ONLY install the latest graphics driver with no extra software. If you have an extra HDD you could certainly try this without going through all the hassle of backing up and restoring your files and applications.
Sometimes the windows Driverstore will hold corrupt data in such a way that it takes a monumental effort to remove the corrupt instance.
Looks like it was my card. ASUS wanted me to send it in for RMA. I took out the card and I haven't had an issue with Freezes or BSOD. Sucks I'm only running on iGPU, but I have been playing Dark Souls 1 and iGPU can handle it. =) not very well but it is playable.