Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

ATI Radeon Video Card issues to blue screen errors


  • Please log in to reply
1 reply to this topic

#1 maheshdj

maheshdj

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:03:15 PM

Posted 17 November 2013 - 12:59 PM

RogueKiller V8.7.8 [Nov 14 2013] by Tigzy
mail : tigzyRK<at>gmail<dot>com
Feedback : http://www.adlice.com/forum/
Website : http://www.adlice.com/softwares/roguekiller/
Blog : http://tigzyrk.blogspot.com/

Operating System : Windows 7 (6.1.7601 Service Pack 1) 64 bits version
Started in : Normal mode
User : MaheshKJ [Admin rights]
Mode : Scan -- Date : 11/17/2013 02:38:06
| ARK || FAK || MBR |

¤¤¤ Bad processes : 1 ¤¤¤
[SUSP PATH] DellSystemDetect.exe -- C:\Users\MaheshKJ\AppData\Local\Apps\2.0\VTYP32NR.NJR\488DE7NM.J6C\dell..tion_0f612f649c4a10af_0005.0003_d2152cbf7ce307ec\DellSystemDetect.exe [7] -> KILLED [TermProc]

¤¤¤ Registry Entries : 8 ¤¤¤
[RUN][SUSP PATH] HKCU\[...]\Run : DellSystemDetect (C:\Users\MaheshKJ\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Dell\Dell System Detect.appref-ms [-]) -> FOUND
[RUN][SUSP PATH] HKUS\S-1-5-21-1018963560-2741143563-1530177602-1000\[...]\Run : DellSystemDetect (C:\Users\MaheshKJ\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Dell\Dell System Detect.appref-ms [-]) -> FOUND
[HJ POL][PUM] HKLM\[...]\System : DisableTaskMgr (0) -> FOUND
[HJ POL][PUM] HKLM\[...]\System : DisableRegistryTools (0) -> FOUND
[HJ POL][PUM] HKLM\[...]\Wow6432Node\[...]\System : DisableTaskMgr (0) -> FOUND
[HJ POL][PUM] HKLM\[...]\Wow6432Node\[...]\System : DisableRegistryTools (0) -> FOUND
[HJ DESK][PUM] HKLM\[...]\NewStartPanel : {59031a47-3f72-44a7-89c5-5595fe6b30ee} (1) -> FOUND
[HJ DESK][PUM] HKLM\[...]\NewStartPanel : {20D04FE0-3AEA-1069-A2D8-08002B30309D} (1) -> FOUND

¤¤¤ Scheduled tasks : 0 ¤¤¤

¤¤¤ Startup Entries : 0 ¤¤¤

¤¤¤ Web browsers : 3 ¤¤¤
[FF][PROXY] hwwmnhtu.default : user_pref("network.proxy.hxxp", "p-de1.biscience.com"); -> FOUND
[FF][PROXY] hwwmnhtu.default : user_pref("network.proxy.hxxp_port", 80); -> FOUND
[FF][PROXY] hwwmnhtu.default : user_pref("network.proxy.type", 4); -> FOUND

¤¤¤ Particular Files / Folders: ¤¤¤

¤¤¤ Driver : [NOT LOADED 0x0] ¤¤¤

¤¤¤ External Hives: ¤¤¤

¤¤¤ Infection :  ¤¤¤

¤¤¤ HOSTS File: ¤¤¤
--> %SystemRoot%\System32\drivers\etc\hosts




¤¤¤ MBR Check: ¤¤¤

+++++ PhysicalDrive0: (\\.\PHYSICALDRIVE0 @ IDE) ST9500420ASG ATA Device +++++
--- User ---
[MBR] a7cfa856d0acf7a3181380d4ce260162
[BSP] 36980062a8f9247c97b77433f7e1859f : Windows 7/8 MBR Code
Partition table:
0 - [XXXXXX] DELL-UTIL (0xde) [VISIBLE] Offset (sectors): 63 | Size: 133 Mo
1 - [ACTIVE] NTFS (0x07) [VISIBLE] Offset (sectors): 274432 | Size: 9842 Mo
2 - [XXXXXX] NTFS (0x07) [VISIBLE] Offset (sectors): 20430848 | Size: 200000 Mo
3 - [XXXXXX] NTFS (0x07) [VISIBLE] Offset (sectors): 430030848 | Size: 200963 Mo
User = LL1 ... OK!
User = LL2 ... OK!

Finished : << RKreport[0]_S_11172013_023806.txt >>



**********************************************************

 

 

System Information (local)


computer name: MAHESHKJ-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Studio XPS 1645, Dell Inc., 0Y507R
CPU: GenuineIntel Intel® Core™ i7 CPU Q 720 @ 1.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4282908672 total
VM: 2147352576, free: 1923657728





Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 11/11/2013 10:55:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-19406-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8003DB9750, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 11/11/2013 10:55:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x3109A)
Bugcheck code: 0xEA (0xFFFFFA8003DB9750, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies 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, ATI Technologies Inc.).
Google query: ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER



On Mon 11/11/2013 10:44:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-19843-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8008D138B0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 11/11/2013 10:38:18 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-16832-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8009DB3B50, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 11/11/2013 10:31:43 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-25740-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8008A86B50, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 11/11/2013 8:37:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111113-25396-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA800875A460, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 Sat 11/9/2013 10:30:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111013-17815-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA80064881F0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 Fri 11/8/2013 9:34:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110913-21450-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8008932B50, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 Fri 11/8/2013 8:25:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110913-21980-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA80042FC210, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.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 Wed 10/16/2013 1:12:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101613-22713-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8005A49B30, 0xFFFFFA8005A49E10, 0xFFFFF800039D17B0)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion

13 crash dumps have been found and analyzed. Only 10 are included in this report. 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, ATI Technologies Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


 

I HAVE ALREADY UNISTALLED THE VIDEO CARD DRIVER AND RE INSTALLED THE SOFTWARE STILL THEY CRASH ALSO I HAVE A GREAT ISSUE OF THE FLASH DRIVERS  NOT WORKING EACH TIME ANY OBJECT IS USED WHICH HAS FLASH CONTROL MY SYSTEM FREEZES DOESNT RESPOND SO I NEED TO HARD REBOOT TO GET BACK TO NORMAL SYSTEM.

 

PLEASE HELP ME

 

http://www.bleepingcomputer.com/forums/t/480723/skyware-or-malware-infection/page-2 well i posted in to check for malware but they suggested to get video card and hardware issues checked.



BC AdBot (Login to Remove)

 


#2 jhayz

jhayz

  • BC Advisor
  • 6,922 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:15 AM

Posted 21 November 2013 - 10:06 PM

Do you still need help?


Tekken
 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users