Thanks for that info, can you please click on the BSOD link, below in my signature and follow the process. Attach the logs back here and one of our BSOD experts will help you further.

Apologies for the delay, Grosvenor. I'll get your thread relocated to the BSOD forum for review by the BSOD techs.

While you wait, you might want to review the PCHF tutorial for a Clean Video Driver Installation. Chances are good that you have already followed this procedure, but you never know - something might have been missed.

Hi there,

Seems like it might be the Hardware itself because the stacks are pointing to "hal!HalpQueryPerformanceCounter+0x1f" mich most of time used to be Hardware related.

Run the following Test:

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select “Stability Test” and “Log GPU Temperature”
Click “Go” to start the test
- Run the test until the GPU temperature maxes out – or until you start having problems (whichever comes first).
- Click “Quit” to exit
Try this free stress test: Free Software – GIMPS
Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select “Just stress testing”
- select the “Blend” test. If you’ve already run MemTest overnight you may want to run the “Small FFTs” test instead.
- “Number of torture test threads to run” should equal the number of CPU’s times 2 (if you’re using hyperthreading).
The easiest way to figure this out is to go to Task Manager…Performance tab – and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours – or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Code:

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: 89f7d020, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 8a886558, Pointer to a DEFERRED_WATCHDOG object.
Arg3: ba4ebcbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

Version too small

FAULTING_THREAD:  89f7d020

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  firefox.exe

LAST_CONTROL_TRANSFER:  from 806ecfa0 to 806ecf73

STACK_TEXT:  
8ec28d98 806ecfa0 8ec28dec bf8198f2 00000000 hal!HalpQueryPerformanceCounter+0x1f
8ec28da0 bf8198f2 00000000 bf8198e5 bf077d27 hal!HalpPmTimerQueryPerfCount+0x8
8ec28dac bf077d27 8ec28dd0 e2800ba4 e2a414a0 win32k!EngQueryPerformanceCounter+0xd
WARNING: Stack unwind information not available. Following frames may be wrong.
8ec28e9c 80505f97 c0e0003c c0e00000 80561ee0 ati2cqag+0x17d27
8ec28eb8 804ffca1 00000002 8ec28f80 00000002 nt!MiLocateAndReserveWsle+0xb1
8ec28f68 804fb442 00000002 804fb20a 00000001 nt!KiIpiSendPacket+0x85
8ec28f98 805238a9 00000003 8ec29020 00000001 nt!KeFlushMultipleTb+0xc8
8ec28fc0 80510368 8ec28fe0 00000001 00000300 nt!MiFlushPteList+0x33
8ec29090 00000000 80561b80 8ec290d4 805491e8 nt!MiDeleteSystemPagableVm+0x4b2


STACK_COMMAND:  .thread 0xffffffff89f7d020 ; kb

FOLLOWUP_IP: 
ati2cqag+17d27
bf077d27 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  ati2cqag+17d27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME:  ati2cqag.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4cef18e7

FAILURE_BUCKET_ID:  0xEA_IMAGE_ati2cqag.dll_DATE_2010_11_26

BUCKET_ID:  0xEA_IMAGE_ati2cqag.dll_DATE_2010_11_26

Followup: MachineOwner