Feb 18, 2016 Windows 7: BSOD THREAD_STUCK_IN_DEVICE_DRIVER ATI (dxgkrnl.sys + hal.dll + atikm. The 1st argument is a pointer to the stuck thread object, so we need to force it as the implicit thread and dump its contents. 0: kd>.thread fffffa80127cfa00 Implicit thread is now fffffa80`127cfa00.
Hi guys, so unfortunately I am having a really annoying issue with my computer. It is constantly crashing and I am always being greeted by the 'Thread stuck in device driver issue' I've tried everything that I can to fix it but nothing is working. I have tried:
Wiping computer and just using the AMD driver that came with the motherboard disc
Completely uninstalling all drivers using driver uninstall programs and then using the auto detect tool from AMD
Completely uninstalling all drivers using driver uninstall programs and then selecting a specific driver for my computer
Nothing seems to be working at all, please help I will attach the whocrashed file if it helps. Thank you.
System Information (local)
Computer name: DESKTOP-AVVUPLF
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:WINDOWS
Hardware: Gigabyte Technology Co., Ltd., F2A68HM-HD2
CPU: AuthenticAMD AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 16050548736 bytes total
Crash Dump Analysis
Crash dump directory: C:WINDOWSMinidump
Crash dumps are enabled on your computer.
On Mon 08/08/2016 18:41:27 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-24390-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFB787C65FF080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 08/08/2016 18:41:27 GMT your computer crashed
crash dump file: C:WINDOWSmemory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4DBE0)
Bugcheck code: 0xEA (0xFFFFB787C65FF080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:WINDOWSsystem32driversatikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER
On Mon 08/08/2016 18:15:34 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-16265-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFD98267578080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 08/08/2016 07:19:36 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-21203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x109 (0xA3A0145E10DCB9FC, 0xB3B720E4635D9E66, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 08/08/2016 05:54:13 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-17750-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFA90B6FFFD740, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Rtl2832u driver.
On Sat 06/08/2016 13:50:20 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080616-34031-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFE70D42B82800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Message was edited by: Lee AucoteBUMP.Still having this issue unfortunately :(
The cracked version of this software comes embedded with improved standard and improved quality. Quite interesting to talk about is its enhances tool for wavetable synthesis. With this tool, users can, with the software, use periodic waveforms to produce musical notes. This feature is well woven into Omnisphere 2 Crack for users to enjoy. The total number of effects available on this software was. How to install omnisphere 2 crack mac. Omnisphere 2 Crack is a best hacking tool. The omnisphere download is a free, powerful standalone plugin VSTi RTAS compatible for Ableton live, Fl Studio, and other popular software. Omnisphere is a crack tool for giving an extraordinary power and versatility to the other software.
Hello there.
Description of problem:
I'm having BSOD problem over a year, which I could not fix. You are probably asking, why am I tolerating it for over a year? Well, It may be more correctly said, that I have been avoiding it for a year, and now I decided to fight it. How was I avoiding this BSOD? Well it appears, that BSOD only happens when I'm running games, which seems to be very graphic demanding? I do no know if and when it was first time it happened or where, but it was occurring a lot when I played' Dragon Age Inquisition', which in the end i stopped because I could not fix the problem and was affraid that I will trash my graphic card which could run other games just fine. In course of years, I played without problems whole set of other games including 'CS:GO' which I played daily for more then a hour - without any problems at all, so that I even forgot that this BSOD even exists. Lately I bought RUST and this bastard is again hunting me! Sometimes it shows after hour of gameplay, yet sometimes after 10 min and it happened that it came same minute I entered 3d world, by now, I think it never happened on main menu.
What does Furmark say:
I run a furmark for about an hour and there was no BSOD or any thing similar or unusual. Temperature while doing furmark test does not go beyond: GPU1 max temp: 64c, GPU2 mtemp: 83c (is that too high?) and GPU3 maxtemp: 66c.
update: I run some kind of a video memory test (russian one) and there was no error.
Tried things:
For solution I tried a lot of things. I uninstalled all drivers and installed them again. I tried installing new windows. Played with catalyst option (turning off various settings). Putting out sound card.
Final word:
I'm not looking for 'final solution', just a solution which will enable to bypass said problem, even it means that I have to sacrifice performance or quality (disabling some features which card enables, but it seems is not able to do due something being faulty) and I do not have money at all for new graphic card
Technical info:
Even tho I think all technical info is inside attachment, for better view I will provide some basic information here:
Operating System: Windows 7 (64x) M-audio uno driver.
Processor: AMD PHENOM II X6 1090T
Graphic Card: AMD Radeon HD 5850
Installed memory: 8GB
More technical information about system is attached to the thread. (minidump and etc.)
Looking forward for the answer.
& until solution is found, I will go play some cs:go
Attached Files
- SysnativeFileCollectionApp.zip334.21KB1 downloads
- Perfmon report.zip132KB1 downloads
Crash dumps are enabled on your computer.
On Mon 08/08/2016 18:41:27 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-24390-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFB787C65FF080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 08/08/2016 18:41:27 GMT your computer crashed
crash dump file: C:WINDOWSmemory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4DBE0)
Bugcheck code: 0xEA (0xFFFFB787C65FF080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:WINDOWSsystem32driversatikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER
On Mon 08/08/2016 18:15:34 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-16265-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFD98267578080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Mon 08/08/2016 07:19:36 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-21203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x109 (0xA3A0145E10DCB9FC, 0xB3B720E4635D9E66, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:WINDOWSsystem32ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 08/08/2016 05:54:13 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080816-17750-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFA90B6FFFD740, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. Rtl2832u driver.
On Sat 06/08/2016 13:50:20 GMT your computer crashed
crash dump file: C:WINDOWSMinidump080616-34031-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22E0F)
Bugcheck code: 0x100000EA (0xFFFFE70D42B82800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:WINDOWSsystem32driversdxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Conclusion
6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Message was edited by: Lee AucoteBUMP.Still having this issue unfortunately :(
The cracked version of this software comes embedded with improved standard and improved quality. Quite interesting to talk about is its enhances tool for wavetable synthesis. With this tool, users can, with the software, use periodic waveforms to produce musical notes. This feature is well woven into Omnisphere 2 Crack for users to enjoy. The total number of effects available on this software was. How to install omnisphere 2 crack mac. Omnisphere 2 Crack is a best hacking tool. The omnisphere download is a free, powerful standalone plugin VSTi RTAS compatible for Ableton live, Fl Studio, and other popular software. Omnisphere is a crack tool for giving an extraordinary power and versatility to the other software.
Hello there.
Description of problem:
I'm having BSOD problem over a year, which I could not fix. You are probably asking, why am I tolerating it for over a year? Well, It may be more correctly said, that I have been avoiding it for a year, and now I decided to fight it. How was I avoiding this BSOD? Well it appears, that BSOD only happens when I'm running games, which seems to be very graphic demanding? I do no know if and when it was first time it happened or where, but it was occurring a lot when I played' Dragon Age Inquisition', which in the end i stopped because I could not fix the problem and was affraid that I will trash my graphic card which could run other games just fine. In course of years, I played without problems whole set of other games including 'CS:GO' which I played daily for more then a hour - without any problems at all, so that I even forgot that this BSOD even exists. Lately I bought RUST and this bastard is again hunting me! Sometimes it shows after hour of gameplay, yet sometimes after 10 min and it happened that it came same minute I entered 3d world, by now, I think it never happened on main menu.
What does Furmark say:
I run a furmark for about an hour and there was no BSOD or any thing similar or unusual. Temperature while doing furmark test does not go beyond: GPU1 max temp: 64c, GPU2 mtemp: 83c (is that too high?) and GPU3 maxtemp: 66c.
update: I run some kind of a video memory test (russian one) and there was no error.
Tried things:
For solution I tried a lot of things. I uninstalled all drivers and installed them again. I tried installing new windows. Played with catalyst option (turning off various settings). Putting out sound card.
Final word:
I'm not looking for 'final solution', just a solution which will enable to bypass said problem, even it means that I have to sacrifice performance or quality (disabling some features which card enables, but it seems is not able to do due something being faulty) and I do not have money at all for new graphic card
Technical info:
Even tho I think all technical info is inside attachment, for better view I will provide some basic information here:
Operating System: Windows 7 (64x) M-audio uno driver.
Processor: AMD PHENOM II X6 1090T
Graphic Card: AMD Radeon HD 5850
Installed memory: 8GB
More technical information about system is attached to the thread. (minidump and etc.)
Looking forward for the answer.
& until solution is found, I will go play some cs:go
Attached Files
- SysnativeFileCollectionApp.zip334.21KB1 downloads
- Perfmon report.zip132KB1 downloads
Stop Code Thread Stuck In Device Driver
Edited by Vlad0153, 28 April 2016 - 11:30 AM.
