Blue Screen crashes

[tim967]

A friend of mine is having some real issues with his PC. He is running win 7 home 64 bit and is experiencing regular BSOD's/crashes.

He has provided me with the attached images of what comes up after the error. I have also uploaded the zip file that I have generated on his pc with the DM Log Collector.

He said previously it was happening when playing games and watching youtube videos but can also occasionally happen randomly. So i uninstalled and re-installed his graphics card drivers (he has an amd r9 200 series graphics card) and also ran amd driver autodetect and it says he has the latest drivers.

I ran a stress test via furmark for 5 minutes yesterday and it was fine and temperatures were fine so I doubt it's overheating.

Anyone know what else I could try?

Thanks in advance!

Tim967

 

[Hacb]

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


from what i can see there is a hardware problem which in turn has caused an issue with directX