Drivers & Software

[ralfthomas]

Hallo,

mein Windows 10 lief vor Creators mit August Blockchain Treiber 17.30 perfekt und schnell ! Dann kam Creators. Meine Karten haben lediglich Timing Straps vom Polaris Editor.

Mit Creators lauft der PC mit August Blockchain nonstop in Bluescreens. Mit dem 17.40 lauft es nicht gut. Aber mit 5 x booten und Bluescreen atikmpag.sys halbwegs.

Wann kommt der Blockchain 17.50 ?

Scheinbar ist der Creators echt Bull.... Lade ich einen Treiber 17.12.2 dann kommt TDR Video Failure

Gruss

Ralf

Message was edited by: Matt B

We have updated the title of this discussion with relevant details to better describe your issue.

[elstaci]

Please translate your post into English since AMD Forum is a English Only forum. Also you need to post your computer specs. Current Windows version, Make and model of CPU/APU, GPU's, PSU, and Motherboard.

[ralfthomas]

Hello,

my Windows 10 ran before Creators with August Blockchain drivers 17.30 perfect and fast! Then came Creators. My maps only have timing straps from Polaris Editor.

With Creators, the PC with August Blockchain runs non-stop in blue screens. It does not go well with the 17.40. But with 5 x boot and bluescreen atikmpag.sys halfway.

When is the blockchain Driver 17.50?
Apparently the Creators is real Bull .... I load a driver 17.12.2 then comes TDR Video Failure

Computer ASROCK 110+ Mining Pro Board. windows 10 Enterprise Creators. Graphics RX580  8*

Greeting

Ralf

[elstaci]

I don't know much about Computer mining setups. Hopefully, someone that is a Miner here at the Forum can assist you.

[ralfthomas]

This is Memory Dump

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Kernel Version 16299 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 16299.15.amd64fre.rs3_release.170928-1534 Machine Name: Kernel base = 0xfffff802`5768c000 PsLoadedModuleList = 0xfffff802`579edff0 Debug session time: Mon Jan 15 13:21:31.163 2018 (UTC - 5:00) System Uptime: 0 days 1:01:40.817 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: ffffdb8b9feea080, 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 OVERLAPPED_MODULE: Address regions for 'dump_iaStorA' and 'dump_storpor' overlap FAULTING_THREAD: ffffdb8b9feea080 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0xEA PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff809166e6d33 to fffff802577f00e0 STACK_TEXT: fffff10d`b7fc6758 fffff809`166e6d33 : 00000000`000000ea ffffdb8b`9feea080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx fffff10d`b7fc6760 fffff809`166e6dfe : fffff10d`b7fc6838 fffff809`1c483808 fffff10d`b7fc6838 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f fffff10d`b7fc67d0 fffff809`1c409e00 : ffffdb8b`9f126000 00000000`00000000 fffff10d`b7fc6920 fffff809`1c4837f4 : dxgkrnl!TdrTimedOperationDelay+0xbe fffff10d`b7fc6810 ffffdb8b`9f126000 : 00000000`00000000 fffff10d`b7fc6920 fffff809`1c4837f4 00000000`00002710 : atikmdag+0x59e00 fffff10d`b7fc6818 00000000`00000000 : fffff10d`b7fc6920 fffff809`1c4837f4 00000000`00002710 00000000`00020028 : 0xffffdb8b`9f126000 STACK_COMMAND: .thread 0xffffdb8b9feea080 ; kb FOLLOWUP_IP: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f

[elstaci]

As I mentioned before, I am not a miner.

It does sound as Windows Update screwed something with the mining software or AMD driver when it upgraded to the latest version 1709. Are there any newer versions of the Mining software you use?

There is a new BIOS (BETA) update for your motherboard (12/18/2017): ASRock > H110 Pro BTC+  and BETA VGA driver (12/05/2017): ASRock > H110 Pro BTC+

Try disconnecting all your RX580's and just leave one on your Motherboard. See if it works correctly. If it does. Add another RX580 and continue until the problem occurs. This method will just eliminate any failing RX580 or Risers you may have connected.

Your problem really is out of my league. I can only suggest basic troubleshooting. Hopefully, someone that is experience in Mining will respond to your post.

Have you gone to any Mining Forum with your problems. They may have a fix or work around for the same problems you are having.

Found this website Bitcoin Forum. Maybe they have some information from the posters that may help guide you in resolving your issues.: https://bitcointalk.org/index.php?topic=2092279.260​

This is a copy from one of the posters in the link I gave you. seems to be similar to your problem:

Gunna01 Sr. Member Activity: 267 Re: AMD Releases Driver for DAG Issue !!! November 06, 2017, 12:11:00 AM #257 SO my drivers have recently started crashing as of yesterday, cannot get my machine stable. Using the August block chain drivers. atikmdag.sys and dxgkrnl.sys crash. Reports that THREAD_STUCK_IN_DEVICE_DRIVER

Marvell2 Full Member Online Activity: 140 Re: AMD Releases Driver for DAG Issue !!! November 06, 2017, 12:45:52 AM #258 Quote from: Gunna01 on November 06, 2017, 12:11:00 AM SO my drivers have recently started crashing as of yesterday, cannot get my machine stable. Using the August block chain drivers. atikmdag.sys and dxgkrnl.sys crash. Reports that THREAD_STUCK_IN_DEVICE_DRIVER bad card or riser

Gunna01 Sr. Member Activity: 267 Re: AMD Releases Driver for DAG Issue !!! November 06, 2017, 01:05:51 AM #259 Quote from: Marvell2 on November 06, 2017, 12:45:52 AM Quote from: Gunna01 on November 06, 2017, 12:11:00 AM SO my drivers have recently started crashing as of yesterday, cannot get my machine stable. Using the August block chain drivers. atikmdag.sys and dxgkrnl.sys crash. Reports that THREAD_STUCK_IN_DEVICE_DRIVER bad card or riser SGMINER mines fine I just discovered. Switching back to Claymore now to see if it crashes again.

0xcosmos Member Activity: 112 Re: AMD Releases Driver for DAG Issue !!! November 06, 2017, 01:50:57 PM #260 Quote from: Gunna01 on November 06, 2017, 01:05:51 AM Quote from: Marvell2 on November 06, 2017, 12:45:52 AM Quote from: Gunna01 on November 06, 2017, 12:11:00 AM SO my drivers have recently started crashing as of yesterday, cannot get my machine stable. Using the August block chain drivers. atikmdag.sys and dxgkrnl.sys crash. Reports that THREAD_STUCK_IN_DEVICE_DRIVER bad card or riser SGMINER mines fine I just discovered. Switching back to Claymore now to see if it crashes again. new drivers have mode to switch between graphics and compute test with them

[elstaci]

Here two links that can help guide you in troubleshooting "Thread Stuck in Device Drive":

this is from Tom's Hardware concerning your BSOD error. It has some helpful tips on resolving the problem , It is about a year old but I believe still valid: How to fix Windows 10 Thread Stuck In Device Driver error - Windows 10

This link is even better than the above. It goes into more depth troubleshooting your problem: http://troubleshooter.xyz/wiki/fix-thread-stuck-in-device-driver-windows-10/

This a copied from the last link:

Few of the cause which can lead to Thread Stuck In Device Driver error are:

• Corrupt or old device drivers
• Driver conflict after installing new hardware.
• Error 0xEA blue screen caused by damaged video card. (your DUMP file mentions error (100000ea)
• Old BIOS
• Bad Memory

[ralfthomas]

Hello,

i installed now August Blockchain Driver . Than from all 8 Cards. I disabled 7.

Got error

Log Name:      Application
Source:        Windows Error Reporting
Date:          16.01.2018 10:39:00
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Cryptominer1
Description:
Fault bucket 0xEA_IMAGE_atikmdag.sys, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 100000ea
P2: ffff9009f8d23700
P3: 0
P4: 0
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\Minidump\011418-45296-01.dmp
\\?\C:\WINDOWS\TEMP\WER-63218-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23E.tmp.txt
\\?\C:\Windows\Temp\WERE923.tmp.WERDataCollectionStatus.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_5cf3c909416cc98638e28551a863f8951b0b7_00000000_cab_03a5023d

Analysis symbol:
Rechecking for solution: 0
Report Id: 8b33807d-3f74-4bdf-b68e-a3add26d1b00
Report Status: 388
Hashed bucket:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-01-16T09:39:00.031676600Z" />
    <EventRecordID>29054</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Cryptominer1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0xEA_IMAGE_atikmdag.sys</Data>
    <Data>0</Data>
    <Data>BlueScreen</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>100000ea</Data>
    <Data>ffff9009f8d23700</Data>
    <Data>0</Data>
    <Data>0</Data>
    <Data>0</Data>
    <Data>10_0_16299</Data>
    <Data>0_0</Data>
    <Data>256_1</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\WINDOWS\Minidump\011418-45296-01.dmp
\\?\C:\WINDOWS\TEMP\WER-63218-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22D.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER23E.tmp.txt
\\?\C:\Windows\Temp\WERE923.tmp.WERDataCollectionStatus.txt</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_100000ea_5cf3c909416cc98638e28551a863f8951b0b7_00000000_cab_03a5023d</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>8b33807d-3f74-4bdf-b68e-a3add26d1b00</Data>
    <Data>388</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Than i diabled all Cards. And enabled other Card.

Still the same error.

Bios is updatet

Greets

Ralf

[elstaci]

I googled all your errors and seemed to indicate a bad or uncompatible GPU driver or at Tom's Hardware a bad PSU. Most mention to use an Older version.

Thread Stuck in Device Driver - atikmdag.sys - Windows Crashes, BSOD, and Hangs Help and Support

Thread stuck in device driver - [Solved] - Graphics Cards  This link said a bad PSU resolved the issue.

atikmdag.sys error BSOD on startup - [Solved] - Graphics Cards  This might help even though its for Windows 7.

I am sorry I can't be more of a help. I would check your PSU outputs to be sure they are with tolerances. Also check your CPU and GPU temperature that they aren't overheating. Otherwise I am out of suggestions except try to find an Older version and just install the GPU driver and nothing else.

Go here and open a Ticket with AMD Support. They may respond back on your issue plus it lets them know there is a problem: AMD Issue Reporting Form or contact AMD Support by Telephone in the country you reside in: Call