1 (edited by giacomopasquali 2021-06-10 15:12:40)

Topic: BSOD changing buffer size / hdsp_64.sys

Hi, I'm experiencing blue screens of death when changing buffer size.
I've an HDSPe RayDat, I'm on 44.1 but I've tested it on others sample rates too.

As soon as I boot the PC I've no problems changing it, I start working and after an "X" amount of time changing buffer size freeze the PC and makes this BSOD.

https://i.ibb.co/Pm2NDqj/BSOD-hdsp-64.jpg

Do someone experienced something like this?

I wrote to RME Support but they only suggested me tried different PCI ports, and I did It without this having influence on the problem.
They asked me to try in a different PC but I can't at this moment.

I've tested other PCI cards in those same slots and everything worked perfectly so I assume It's something HDSPe Raydat related.

I've an Intel i9-9900K, Gigabyte Z390 Aorus Pro, 64 Gb Ram DDR4, Nvidia 1050 Ti, all M.2 Drives. Pretty rock solid machine on which I've never had any problem except this.

Re: BSOD changing buffer size / hdsp_64.sys

Not a known issue of the card or driver. That said, which driver and firmware have you got installed here?
Are all PCIe related power savings options deactivated?

Regards
Daniel Fuchs
RME

Re: BSOD changing buffer size / hdsp_64.sys

All power saving options disabled.
Last driver and last firmware.

Re: BSOD changing buffer size / hdsp_64.sys

Does this happen with or without audio software runnning? How long does it take for the BSOD to occur?

Regards
Daniel Fuchs
RME

Re: BSOD changing buffer size / hdsp_64.sys

Instantly.
Both running or not.

The system freeze for 2/3 seconds and then the blue screen occurs.

Re: BSOD changing buffer size / hdsp_64.sys

Can you test this without the nVidia? What other hardware is installed?

Regards
Daniel Fuchs
RME

Re: BSOD changing buffer size / hdsp_64.sys

I have the same issue, since recently. I also get a "System_service_exception" BSOD in addition to the one you experience. I also have issues in Cakewalk that always mute output to the Multiface if I'm recording from a channel on the Digiface. I have Multiface on Cardbus + Digiface on PCI v1.8 card.

giacomopasquali wrote:

Hi, I'm experiencing blue screens of death when changing buffer size.
I've an HDSPe RayDat, I'm on 44.1 but I've tested it on others sample rates too.

As soon as I boot the PC I've no problems changing it, I start working and after an "X" amount of time changing buffer size freeze the PC and makes this BSOD.

https://i.ibb.co/Pm2NDqj/BSOD-hdsp-64.jpg

Do someone experienced something like this?

I wrote to RME Support but they only suggested me tried different PCI ports, and I did It without this having influence on the problem.
They asked me to try in a different PC but I can't at this moment.

I've tested other PCI cards in those same slots and everything worked perfectly so I assume It's something HDSPe Raydat related.

I've an Intel i9-9900K, Gigabyte Z390 Aorus Pro, 64 Gb Ram DDR4, Nvidia 1050 Ti, all M.2 Drives. Pretty rock solid machine on which I've never had any problem except this.

Re: BSOD changing buffer size / hdsp_64.sys

I had a blue screen also once with the Babyface. I also see problems when changing the buffer size -- although others. It seems that the driver can crash / hang up / react unwanted when changing the buffer size (see my thread "Knistern / Knacken.... Windows 10). Maybe this is related!?

Re: BSOD changing buffer size / hdsp_64.sys

I tried:
- reflashing the bios with the latest version
- switching pci socket
- clean Windows install from 0
- using HDSPe without NVidia graphic card

Nothing helped.
Quite frustrating.

Re: BSOD changing buffer size / hdsp_64.sys

This is what I usually see connected to the BSOD.

https://i.ibb.co/6HLfVnQ/EventLog.png

XML:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Eventlog" Guid="{fc65ddd8-d6ef-4962-83d5-6e5cfe9ce148}" />
  <EventID>1101</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>101</Task>
  <Opcode>0</Opcode>
  <Keywords>0x4020000000000000</Keywords>
  <TimeCreated SystemTime="2022-01-27T08:32:09.6049459Z" />
  <EventRecordID>26424</EventRecordID>
  <Correlation />
  <Execution ProcessID="1496" ThreadID="1936" />
  <Channel>Security</Channel>
  <Computer>GIACOMO</Computer>
  <Security />
  </System>
- <UserData>
- <AuditEventsDropped xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">
  <Reason>0</Reason>
  </AuditEventsDropped>
  </UserData>
  </Event>

Re: BSOD changing buffer size / hdsp_64.sys

And here it is the dump analysis:

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`34400000 PsLoadedModuleList = 0xfffff805`3502a2b0
Debug session time: Thu Jan 27 09:31:22.053 2022 (UTC + 1:00)
System Uptime: 1 days 17:53:15.691
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols

Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`347f72e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff805`3a6a1ba0=000000000000000a
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffb9fcb7a40000, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8055113de50, address which referenced memory

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

Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page 8a68e3 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page ff8de2 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page 3976e1 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page a961e0 not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details
Page 902cdf not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2061

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6726

    Key  : Analysis.Init.CPU.mSec
    Value: 484

    Key  : Analysis.Init.Elapsed.mSec
    Value: 39002

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 92

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  d1

BUGCHECK_P1: ffffb9fcb7a40000

BUGCHECK_P2: 9

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8055113de50

WRITE_ADDRESS:  ffffb9fcb7a40000 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8053a6a1ce0 -- (.trap 0xfffff8053a6a1ce0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb9fcb7a3fa00 rbx=0000000000000000 rcx=ffffb9fcb7a40000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8055113de50 rsp=fffff8053a6a1e78 rbp=000000000008c000
 r8=0000000000000000  r9=0000000000000008 r10=0000000000000000
r11=0000000000003e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
hdsp_64+0xde50:
fffff805`5113de50 488911          mov     qword ptr [rcx],rdx ds:ffffb9fc`b7a40000=????????????????
Resetting default scope

STACK_TEXT:  
fffff805`3a6a1b98 fffff805`34809269     : 00000000`0000000a ffffb9fc`b7a40000 00000000`00000009 00000000`00000001 : nt!KeBugCheckEx
fffff805`3a6a1ba0 fffff805`34805569     : fffff805`3a6a1d00 00000000`00000000 00000000`00000000 fffff805`511b066c : nt!KiBugCheckDispatch+0x69
fffff805`3a6a1ce0 fffff805`5113de50     : fffff805`5113ae56 ffff968a`4b9531a0 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x469
fffff805`3a6a1e78 fffff805`5113ae56     : ffff968a`4b9531a0 00000000`00000000 00000000`00000000 00014c81`b9832731 : hdsp_64+0xde50
fffff805`3a6a1e80 fffff805`53eabacf     : 00000000`e0000000 ffff968a`4b39a950 fffff805`4d811ef0 00000000`00e00000 : hdsp_64+0xae56
fffff805`3a6a1f10 fffff805`346de195     : ffffaa00`3c40bc80 ffff968a`4bc93600 ffffaa00`3c40bd30 fffff805`32033180 : portcls!CInterruptSyncServiceRoutine+0x3f
fffff805`3a6a1f40 fffff805`347f8b0f     : fffff805`3a692a50 ffffaa00`3c40bc80 00000000`00000392 00014c81`b8095a67 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`3a6a1f90 fffff805`347f8dd7     : fffff805`3a692af0 00000000`00000001 00000000`00040046 fffff805`34617138 : nt!KiInterruptSubDispatch+0x11f
fffff805`3a6929d0 fffff805`347fae0a     : 00000000`00000000 fffff805`35127a00 ffff968a`4b257040 00000000`00000392 : nt!KiInterruptDispatch+0x37
fffff805`3a692b60 00000000`00000000     : fffff805`3a693000 fffff805`3a68c000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


SYMBOL_NAME:  hdsp_64+de50

MODULE_NAME: hdsp_64

IMAGE_NAME:  hdsp_64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  de50

FAILURE_BUCKET_ID:  AV_hdsp_64!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8679ed58-8520-3b87-6f98-a4779c52a48d}

Followup:     MachineOwner

   

12

Re: BSOD changing buffer size / hdsp_64.sys

giacomopasquali wrote:

Hi, I'm experiencing blue screens of death when changing buffer size.
I've an HDSPe RayDat, I'm on 44.1 but I've tested it on others sample rates too.

As soon as I boot the PC I've no problems changing it, I start working and after an "X" amount of time changing buffer size freeze the PC and makes this BSOD.

Questions to clarify the situation:

- which DAW is used?

- does the BSOD also happen when just switching the buffer size in the card's Settings dialog, with no DAW running? (we think that will work without BSOD)

- ASIO in use? WDM also in use? If WDM is not used set the number of WDM devices in the Settings dialog to 0, reboot, try again.

Regards
Matthias Carstens
RME

13 (edited by giacomopasquali 2022-01-28 01:54:07)

Re: BSOD changing buffer size / hdsp_64.sys

MC wrote:

Questions to clarify the situation:

- which DAW is used?

- does the BSOD also happen when just switching the buffer size in the card's Settings dialog, with no DAW running? (we think that will work withput BSOD)

- ASIO in use? WDM also in use? If WDM is not used set the number of WDM devices in the Settings dialog to 0, reboot, try again.

- Cubase Pro 11

- BSOD occurs randomly both with or without the daw opened

- Hammerfall ASIO in use of course. WDM useful for communication apps like Zoom, Skype, etc. SoundID running too.

The fact is that it’s the same Pc configuration (specs in my first post), same programs, everything it’s the same but I started having these problem 1 year ago. Before that everything was just perfect.

I’m leaving for some day of studio work in another city, when I’ll come back I’ll try changing buffer size specifically closing the daw but as said its happened before in that same scenario.

Also uploading a video I made some days ago of this strange cycle sound happening sometimes too on changing buffer that stops when coming back to the first selected size.

www.giacomopasquali.it/__resources/temp/2022-01-14.mov

14 (edited by tonehustle 2023-02-28 07:52:53)

Re: BSOD changing buffer size / hdsp_64.sys

giacomopasquali wrote:
MC wrote:

Questions to clarify the situation:

- which DAW is used?

- does the BSOD also happen when just switching the buffer size in the card's Settings dialog, with no DAW running? (we think that will work withput BSOD)

- ASIO in use? WDM also in use? If WDM is not used set the number of WDM devices in the Settings dialog to 0, reboot, try again.

- Cubase Pro 11

- BSOD occurs randomly both with or without the daw opened

- Hammerfall ASIO in use of course. WDM useful for communication apps like Zoom, Skype, etc. SoundID running too.

The fact is that it’s the same Pc configuration (specs in my first post), same programs, everything it’s the same but I started having these problem 1 year ago. Before that everything was just perfect.

I’m leaving for some day of studio work in another city, when I’ll come back I’ll try changing buffer size specifically closing the daw but as said its happened before in that same scenario.

Also uploading a video I made some days ago of this strange cycle sound happening sometimes too on changing buffer that stops when coming back to the first selected size.

www.giacomopasquali.it/__resources/temp/2022-01-14.mov

Sorry to raise this thread from the dead, but I googled to see if anyone else was having this issue with RayDATs; low and behold...

Same BSOD as you, also running an i9 9900k build.

It started happening last year on a new Windows 11 install (moved from OSX) and hadn't happened for months... its back again, periodically.

Did you ever manage to solve this or find the "culprit"?

It seems to happen more often when switching buffer sizes whilst audio playback is running in Ableton Live 11. I've got out of that habit! But it's still happening now and then when I've made sure the audio playback has stopped.

It's happening even when I'm using the internal clock, with none of my ADAT rack gear on, just using the SPDIF out, routed to my monitor controller.

RME Hammerfall DSP
Driver: 4.40 (01/10/23)
RayDAT Firmware: Revision=18
running at 48000 Hz

Ableton Live Standard 11.2.10

PC Specs:

Intel i9 9900k
Gigabyte Z390 Gaming X-CF motherboard
32GB DD4 RAM
NVIDIA GeForce GT710 (ASUS - Fanless)
Windows 11 Professional 64-bit - Build 22621)

EDIT: (all power-saving options are disabled).

Any help would be much appreciated!

15

Re: BSOD changing buffer size / hdsp_64.sys

Remove the RAYDAT, carefully clean its golden bus contacts with a rubber eraser, put it back in, check.

Regards
Matthias Carstens
RME

Re: BSOD changing buffer size / hdsp_64.sys

MC wrote:

Remove the RAYDAT, carefully clean its golden bus contacts with a rubber eraser, put it back in, check.

Thanks, I'll do that and report back.