Not sure which is broken

[legalize101]

Hey all, haven’t been here in ages, couldn’t even remember my username! I’ve been having a bit of an issue lately, and I can’t seem to pinpoint it, however I am leaning to either the mobo or video card failing, or of course drivers ruining my life.

I built a PC about 2-3 years ago: i5 2500k, 8gb RAM, Radeon r9 380, ASrock mobo (b75m-dgs whose model doesn’t show in msinfo, and a Netgear wifi usb stick. I have some speakers plugged into the back and a headset into the front jacks.

Not sure if related, but I’ll start with the issues I’ve been having for a while, which didn’t bother me too much. Occasionally on boot, the wifi USB stick wouldn’t work (either steady light which indicates no activity, and no internet connection on the desktop, or would just stay off), it would require a restart or pulling it out and plugging it back in… no biggie. When the computer is off, my mouse or keyboard lights would come on and stay on… also no biggie, however weird. Otherwise, everything would work just fine.

Recently however, maybe a month or two or so, my internet started to lag. I play counter strike, and my ping would just go through the roof, for prolonged periods of time and momentarily come back down to normal for a short while. I have a bunch of things on my wifi, I pondered the possibility of the router not being able to handle it… but pinging it from my phone I get responses and no loss, pinging from the desktop I get slow responses and losing packets. Maybe interference… changed the channel and same issue. This isn’t constant though, so I am at a slight loss.

Now for the newest and biggest issue, my game started to freeze. I would get a black screen or the ingame screen would just freeze. No response from the computer what so ever. It did BSOD a couple times, one of them was “THREAD STUCK IN DEVICE DRIVER”. I can’t recall what the other was, but it was different. Now I can’t pinpoint if this started happening after a Radeon driver update, and I tried rolling the drivers back and updating again.

I’m hoping someone can help me narrow down the culprit, I’m really hoping the mobo is taking a dump because I don’t want to buy a new video card.
Thanks in advance!

[TwitchisMental]

Hello Legalize101, I am sorry to hear about the issues you are having. We can certainly assist you with that.

First let us get some basic information.

Please download MINITOOLBOX and run it.

Checkmark following boxes:

Flush DNS
Reset FF proxy Settings
Reset Ie Proxy Settings
Report IE Proxy Settings
Report FF Proxy Settings
List content of Hosts
List IP configuration
List Winsock Entries
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size
List Devices (problems only)

Please attach the results in your next reply. This will help us help you .

[legalize101]

Thanks for the reply, I attached the log here

[legalize101]

Got another BSOD today… “VIDEO SCHEDULER INTERNAL ERROR”
Ran that program after restarting, in case it shows something new.

[TwitchisMental]

If you are also getting BSODs, please attach the dump files.

1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
3. Upload the zip folder using the More Reply Options tab, Choose File then the Attach This File tab., bottom left of the dialogue input box.

[legalize101]

Here they are

[TwitchisMental]

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000005, The subtype of the bugcheck:
Arg2: ffffd50106438000
Arg3: ffffd5010648dad0
Arg4: 00000000000007f4

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  6

LAST_CONTROL_TRANSFER:  from fffff8058a0c355e to fffff801393fc580

STACK_TEXT:
fffff801`3a4b59e8 fffff805`8a0c355e : 00000000`00000119 00000000`00000005 ffffd501`06438000 ffffd501`0648dad0 : nt!KeBugCheckEx
fffff801`3a4b59f0 fffff805`8c376962 : ffffd501`0643a000 ffffd501`06438000 00000000`000007f2 fffff805`8c35ae0e : watchdog!WdLogEvent5_WdCriticalError+0xce
fffff801`3a4b5a30 fffff805`8c36b17a : ffffd501`0624f010 ffffd501`064ea010 ffffd501`06438000 fffff805`8b87b874 : dxgmms2!VidSchiProcessIsrFaultedPacket+0x23e
fffff801`3a4b5ab0 fffff805`8c35ad0d : fffff801`000007f4 ffffd501`054e9030 ffffd501`0624f010 ffffd501`06101aa0 : dxgmms2!VidSchDdiNotifyInterruptWorker+0x1044a
fffff801`3a4b5b00 fffff805`8b87b874 : ffffd501`054e9030 00000005`000007f3 ffffd501`00000000 fffff805`00000000 : dxgmms2!VidSchDdiNotifyInterrupt+0x8d
fffff801`3a4b5b30 fffff805`8b708ac3 : ffffd501`054ff758 fffff805`8eba2864 fffff801`3a4b5c90 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x74
fffff801`3a4b5b60 ffffd501`054ff758 : fffff805`8eba2864 fffff801`3a4b5c90 00000000`00000000 00000000`00000002 : atikmpag+0x48ac3
fffff801`3a4b5b68 fffff805`8eba2864 : fffff801`3a4b5c90 00000000`00000000 00000000`00000002 00000005`00000000 : 0xffffd501`054ff758
fffff801`3a4b5b70 fffff801`3a4b5c90 : 00000000`00000000 00000000`00000002 00000005`00000000 00000000`00000009 : atikmdag+0x102864
fffff801`3a4b5b78 00000000`00000000 : 00000000`00000002 00000005`00000000 00000000`00000009 00000000`000007f4 : 0xfffff801`3a4b5c90


STACK_COMMAND:  kb

FOLLOWUP_IP:
dxgmms2!VidSchiProcessIsrFaultedPacket+23e
fffff805`8c376962 cc              int     3

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms2!VidSchiProcessIsrFaultedPacket+23e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  6109c19a

FAILURE_BUCKET_ID:  X64_0x119_dxgmms2!VidSchiProcessIsrFaultedPacket+23e

BUCKET_ID:  X64_0x119_dxgmms2!VidSchiProcessIsrFaultedPacket+23e

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
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 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: ffffb9083d0e9240, 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 "intercepted" bugcheck 0xEA was hit (see notes).

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_THREAD:  ffffb9083d0e9240

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80f487960bb to fffff80277f76580

STACK_TEXT:
ffff9380`496e5168 fffff80f`487960bb : 00000000`000000ea ffffb908`3d0e9240 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9380`496e5170 fffff80f`4879618e : ffff9380`496e5248 fffff80f`4e68b1f0 ffff9380`496e5248 ffff9380`496e5330 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffff9380`496e51e0 fffff80f`4e619ea0 : ffffb908`39d08000 00000000`00000000 ffff9380`496e5330 fffff80f`4e68b1dc : dxgkrnl!TdrTimedOperationDelay+0xbe
ffff9380`496e5220 ffffb908`39d08000 : 00000000`00000000 ffff9380`496e5330 fffff80f`4e68b1dc 00000000`00002710 : atikmdag+0x59ea0
ffff9380`496e5228 00000000`00000000 : ffff9380`496e5330 fffff80f`4e68b1dc 00000000`00002710 ffffb908`39ab0028 : 0xffffb908`39d08000


STACK_COMMAND:  .thread 0xffffb9083d0e9240 ; kb

FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff80f`487960bb cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

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

Both of the above BSODs log indicate that something may be wrong with the graphics/video driver or related.

Lets go ahead and do a full clean uninstall and reinstall of the graphics driver.

You can download the AMD Clean Uninstall Utility and see how to run the tool here - https://support.amd.com/en-us/kb-art...l-Utility.aspx

Once you have completed that and rebooted your computer, go ahead and get the latest driver here - https://support.amd.com/en-us/download/auto-detect-tool

That tool will detect your graphics card and download the latest correct driver for you.

Also, do you know if you have the latest UEFI/BIOS update installed?

[legalize101]

Funny enough, I used some Driver delete utility or something of that name right after I posted the dumps, then reinstalled the drivers. Even more interestingly, my Wifi was bridged with some other connection, it might’ve been the vlan, but I didn’t get a look before disabling in rage haha. The BIOS is up to date, they haven’t maintained this thing in ages.
I guess we’ll see how it goes going forward.

[TwitchisMental]

Funny enough, I used some Driver delete utility or something of that name right after I posted the dumps, then reinstalled the drivers. Even more interestingly, my Wifi was bridged with some other connection, it might’ve been the vlan, but I didn’t get a look before disabling in rage haha. The BIOS is up to date, they haven’t maintained this thing in ages.
I guess we’ll see how it goes going forward.

So just to confirm, you are currently on the latest BIOS version of 1.40?

If you have already completely removed and reinstalled the graphics driver, you will need to basically play wait and see to know if the BSOD will occur again.

In relation to the reported usb wifi device not working all of the time, what is the make and model of the device? Have you installed the latest driver?

[phillpower2]

Any update for us legalize101?

[legalize101]

Was waiting a little to see what happens. After my last post the pc crashed again, I actually got artifacts one time… Took the video card out, uninstalled the drivers again, did a chkdsk in case something was corrupt, and reinstalled. It’s been a few days now and so far so good, I think my frame rate isn’t even suffering any more. I’ll keep my fingers crossed for now and see what happens a few days down the road. Thanks for the help thus far fellas!

[phillpower2]

Thanks for the update, would give it a week or so and if all is still well mark your thread as solved (y)

[legalize101]

Everything seems to be working fine now… Very weird. Thank you all for the help!

[phillpower2]

Glad to hear it and thanks for the follow up (y)