<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[RME User Forum — RME RayDAT Strangeness - Invalid Serial Number]]></title>
		<link>https://forum.rme-audio.de/viewtopic.php?id=36584</link>
		<atom:link href="https://forum.rme-audio.de/extern.php?action=feed&amp;tid=36584&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in RME RayDAT Strangeness - Invalid Serial Number.]]></description>
		<lastBuildDate>Wed, 11 Jan 2023 04:27:03 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=196174#p196174</link>
			<description><![CDATA[<p>Yes, driver v4.40 and firmware v2.48 works in both legacy and DriverKit modes. Thanks.</p>]]></description>
			<author><![CDATA[null@example.com (jreinhard)]]></author>
			<pubDate>Wed, 11 Jan 2023 04:27:03 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=196174#p196174</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=196167#p196167</link>
			<description><![CDATA[<p>Nope, that&#039;s the driver. V 4.40 will be up in an hour.</p>]]></description>
			<author><![CDATA[null@example.com (MC)]]></author>
			<pubDate>Wed, 11 Jan 2023 01:27:11 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=196167#p196167</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=196155#p196155</link>
			<description><![CDATA[<p>I just tried fut_wdm_dspe version 2.48, and it has the same issues as 2.47.</p>]]></description>
			<author><![CDATA[null@example.com (jreinhard)]]></author>
			<pubDate>Tue, 10 Jan 2023 20:31:13 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=196155#p196155</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195853#p195853</link>
			<description><![CDATA[<p>Thanks guys, this is a very unexpected and unusual side effect of the new FUT. We hope to be able to fix this on Monday.</p>]]></description>
			<author><![CDATA[null@example.com (MC)]]></author>
			<pubDate>Fri, 06 Jan 2023 03:35:37 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195853#p195853</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195840#p195840</link>
			<description><![CDATA[<div class="quotebox"><cite>weezul wrote:</cite><blockquote><p>Have you two had same stability etc since being on 18 after the XXXXX?</p></blockquote></div><p>Yes, it seems to be ok with the v18 Legacy, but I haven&#039;t had much time to test it thoroughly yet. However, to say the truth, my RayDat has also been working fine for almost a week with the &quot;bad&quot; v19 DriverKit firmware installed, so I don&#039;t really know if this is more a cosmetic rather than a functional issue.</p>]]></description>
			<author><![CDATA[null@example.com (Jorge Ruiz)]]></author>
			<pubDate>Thu, 05 Jan 2023 18:51:11 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195840#p195840</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195839#p195839</link>
			<description><![CDATA[<div class="quotebox"><cite>Jorge Ruiz wrote:</cite><blockquote><div class="quotebox"><cite>jreinhard wrote:</cite><blockquote><p>The same thing happened to my Raydat when I updated with version 2.47 of the Flash update tool when selecting &quot;DriverKit compatible&quot;. I was able to restore the Raydat to normal behavior by using version 2.36 of the Flash update tool. I then tried 2.47 again with &quot;DriverKit compatible&quot; unselected and it worked. My Raydat now shows Revision=18 and the serial number is correct.</p></blockquote></div><p>Thanks a lot. I had the same issue (empty serial number after flashing my RayDat to v19 DriverKit). Following your suggestion I could restore the card back to v16, and then upgrade it to v18 Legacy. By the way, the Flash Update Tool v2.36 can be downloaded here: <a href="https://archiv.rme-audio.de/download/fut_wdm_dspe.zip">https://archiv.rme-audio.de/download/fut_wdm_dspe.zip</a></p></blockquote></div><p>Well I&#039;ll Be Damned</p><p><span class="postimg"><img src="https://i.imgur.com/zh53no3.png" alt="https://i.imgur.com/zh53no3.png" /></span></p><p>going back to 16 worked and i saw the SN again.<br />going then to 19 driver kit resulted in XXXXXX<br />back to 16, then to 18 legacy has worked.</p><p>Have you two had same stability etc since being on 18 after the XXXXX?</p><p>One for the team maybe? Thanks all.</p>]]></description>
			<author><![CDATA[null@example.com (weezul)]]></author>
			<pubDate>Thu, 05 Jan 2023 18:07:13 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195839#p195839</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195834#p195834</link>
			<description><![CDATA[<div class="quotebox"><cite>jreinhard wrote:</cite><blockquote><p>The same thing happened to my Raydat when I updated with version 2.47 of the Flash update tool when selecting &quot;DriverKit compatible&quot;. I was able to restore the Raydat to normal behavior by using version 2.36 of the Flash update tool. I then tried 2.47 again with &quot;DriverKit compatible&quot; unselected and it worked. My Raydat now shows Revision=18 and the serial number is correct.</p></blockquote></div><p>Thanks a lot. I had the same issue (empty serial number after flashing my RayDat to v19 DriverKit). Following your suggestion I could restore the card back to v16, and then upgrade it to v18 Legacy. By the way, the Flash Update Tool v2.36 can be downloaded here: <a href="https://archiv.rme-audio.de/download/fut_wdm_dspe.zip">https://archiv.rme-audio.de/download/fut_wdm_dspe.zip</a></p>]]></description>
			<author><![CDATA[null@example.com (Jorge Ruiz)]]></author>
			<pubDate>Thu, 05 Jan 2023 16:48:18 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195834#p195834</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195833#p195833</link>
			<description><![CDATA[<p>The same thing happened to my Raydat when I updated with version 2.47 of the Flash update tool when selecting &quot;DriverKit compatible&quot;. I was able to restore the Raydat to normal behavior by using version 2.36 of the Flash update tool. I then tried 2.47 again with &quot;DriverKit compatible&quot; unselected and it worked. My Raydat now shows Revision=18 and the serial number is correct.</p>]]></description>
			<author><![CDATA[null@example.com (jreinhard)]]></author>
			<pubDate>Thu, 05 Jan 2023 16:04:27 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195833#p195833</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195818#p195818</link>
			<description><![CDATA[<div class="quotebox"><cite>MC wrote:</cite><blockquote><p>No serial number means the card must be sent in. This is not repairable by a flash tool, sorry.</p></blockquote></div><p>It&#039;s all good. Just seems like a stream of bad luck, as we also had an old blackmagic decklink which was not being recognised on every boot either.... Hence the worries about PCIe lanes before looking at an upgrade. That decklink has been through the ringer though, and it&#039;s bent.... It&#039;s likely he would prefer MADI in the machine anyhow, so it&#039;s worth knowing that it should in theory be fine.</p><p>It&#039;s unlikely he&#039;ll bother sending it back but I will let him know. I&#039;ll pour one out for the little guy. Thanks for your swift responses both of you, it&#039;s appreciated.</p>]]></description>
			<author><![CDATA[null@example.com (weezul)]]></author>
			<pubDate>Thu, 05 Jan 2023 11:56:28 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195818#p195818</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195794#p195794</link>
			<description><![CDATA[<p>Hey Jeff</p><p>Those screenshots are from my working computer.<br />Sorry I know it&#039;s a bit confusing.</p><p>Original machine with problems: Client&#039;s 8700 with RayDAT pulled from old old pyramix machine</p><p>My spare machine where that old RayDAT still has XXXXX serial: mini itx 4th gen intel, where screenshots are from.</p><p>My other machine where my own RayDAT has worked for years: 6700k machine</p><p>As an update, I put my own RayDAT confirmed working into the 8700k client machine, and RayDAT works fine, serial number and flasher tool looks normal again, so I would assume the card is maybe done? Or maybe the dodgy PCIe slots in his computer ended in a dodgy flash that broke it. Pic:<br /><span class="postimg"><img src="https://i.imgur.com/ltVB9R4.png" alt="https://i.imgur.com/ltVB9R4.png" /></span></p><p>The last thing I could try would be to put the broken RayDAT into my 6700k build. It&#039;s a hackintosh machine, but currently dualbooting with Windows IIRC, so could try flashing from either. I never had problems flashing over the years in MacOS on that machine.</p><br /><br /><p>Cheers</p>]]></description>
			<author><![CDATA[null@example.com (weezul)]]></author>
			<pubDate>Wed, 04 Jan 2023 23:24:04 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195794#p195794</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195789#p195789</link>
			<description><![CDATA[<p>The XXXXXXX serial number is a bad sign, could you put the card into the working PC and try to flash update it there?</p>]]></description>
			<author><![CDATA[null@example.com (Jeff)]]></author>
			<pubDate>Wed, 04 Jan 2023 22:37:36 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195789#p195789</guid>
		</item>
		<item>
			<title><![CDATA[Re: RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195776#p195776</link>
			<description><![CDATA[<p>Update: I clicked flash....</p><p><span class="postimg"><img src="https://i.imgur.com/DtHS3zk.png" alt="https://i.imgur.com/DtHS3zk.png" /></span></p><p>Uh oh. The flasher got stuck where you see here with an error... This is on Windows 10 box, 4th gen intel , MSI H81i motherboard. Only has one PCIe slot.<br />After a restart, totalmix works, WDM devices seem to work, signal makes it to Totalmix software inputs still.<br />I have one more computer I could try the card in, my current RayDAT machine. I could swap the cards and check the behaviour.</p>]]></description>
			<author><![CDATA[null@example.com (weezul)]]></author>
			<pubDate>Wed, 04 Jan 2023 20:56:16 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195776#p195776</guid>
		</item>
		<item>
			<title><![CDATA[RME RayDAT Strangeness - Invalid Serial Number]]></title>
			<link>https://forum.rme-audio.de/viewtopic.php?pid=195774#p195774</link>
			<description><![CDATA[<p>Hey there.<br />I&#039;ve been a happy RayDAT user for years. Today I was helping a friend with a Windows machine, and we took an old RayDAT from his old Pyramix machine and put it in his build (8th Gen intel). </p><p>We&#039;re troubleshooting some PCIe wierdness with his rig (he uses it for vMix) which we&#039;re still not happy with. Anyway, amongst this we tried this RayDAT. In a 1x slot he gets a blue screen with hdsp.dll, but moving it to x4 slot worked so we could update firmware. The strange thing is, the firmware update would freeze. It couldn&#039;t see a serial number, and clicking start just made it freeze. After a reboot, and putting it in the x16 slot, moving GFX to x4 slot, the computer booted fine, no dll crash and we could see the serial number, and updated the firmware. Now, the card seems to work but the serial number is still now XXXXXXXX.</p><p>I brought the card home and plopped it in a different machine. Drivers install fine, but still strange things going on:<br /><span class="postimg"><img src="https://i.imgur.com/UvtMXyZ.png" alt="https://i.imgur.com/UvtMXyZ.png" /></span></p><p>Device Info... in TotalMix is also blank but the card did seem to work in vMix.</p><p>Just wondering if this is a hardware problem, or if another flash could help. The current flash screen I&#039;m seeing looks a little corrupted so just wondering what you&#039;d suggest.</p><p>Thanks</p>]]></description>
			<author><![CDATA[null@example.com (weezul)]]></author>
			<pubDate>Wed, 04 Jan 2023 20:36:38 +0000</pubDate>
			<guid>https://forum.rme-audio.de/viewtopic.php?pid=195774#p195774</guid>
		</item>
	</channel>
</rss>
