Topic: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I love my FF800. Had it for years, bought it used, and it's still kicking!

I am running windows 11, latest drivers -

via word clock connected to a focusrite octopre

and I use REAPER.

some plugins and projects really don't like my lowest latency settings (I can get down to 64 samples sometimes), so I have to change the buffers here and there.

problem is, when I go to the reaper preference screen and then the ASIO settings which opens up the Firepod control panel, I get unusable audio, constantly dropped buffers.

I've tried to shut down reaper, and THEN change the buffer settings, and reopen reaper, nope. Same thing seems to happen when I change the sample rate.

I've tried shutting off the octopre while reaper is closed, turning it back on and restarting reaper, nope.

So right now I've tried to close reaper, change the buffer length, restart the FF800, and i THINK that works. The problem is, I remember just being able to change the samplerate/buffer on the fly - and other Reaper users are reporting this, too:

forum.cockos.com/showthread.php?p=2535256#post2535256

So why can't I? What could be getting in the way? Maybe it comes down to some other thing I have installed?

Also, when reaper is using the ASIO driver, if I shut off my RME, I get a BSOD/crashdump/restart. If I change reaper to "dummy audio" or close REAPER, it doesn't do this. Only when REAPER has the driver does it crash.

I am also not 100 percent sure if I am wiring the RME to the Focusrite correctly. I have word clock and ADAT wired up. This is the only time I've attempted to sync two devices like this. I feel like I'm not doing it right.

here are screengrabs of my current settings. On the thread above, you can see how I was trying to approach this months ago and those settings, too.

I kinda just gave up.

https://www.dropbox.com/s/g81ep8svmc91drm/Screenshot%202023-06-06%20120853.png?dl=1

https://www.dropbox.com/s/mrexm72d6m0h9sn/Screenshot%202023-06-06%20120948.png?dl=1

https://www.dropbox.com/s/y7atp0882yvxri5/Screenshot%202023-06-06%20121007.png?dl=1

2 (edited by MetalHeadKeys 2023-06-07 08:47:04)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Hello!

What happens if you set 'WDM Devices' to zero? Do you, still, get the same behaviour?
(You will loose Windows Audio, but it's only for testing. You can, later, set it to 1)

Also, which Octopre are you using? Can you post a link?

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Focusrite OctoPre MkII 8-Channel Microphone Preamp

https://www.bhphotovideo.com/c/product/ … phone.html

I will try that after I post this in case it shuts down.

But what you seem to be saying is that maybe since windows is using the driver (also why 14 devices? haha), it causes an error when I shut it down? Still seems weird but what a great approach! thank you!!!

4 (edited by jasonbrianmerrill 2023-06-08 16:08:00)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Ok, so it did BSOD. hah.

also, I sometimes need a couple of different WDM drivers as I have a separate one I used for zoom calls that I route things to - but I definitely don't need FOURTEEN ha.

here's a dump from it, no idea why it says my OS is windows 10 when it's windows 11 but...

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


Loading Dump File [C:\Windows\Minidump\060823-24406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff804`61c00000 PsLoadedModuleList = 0xfffff804`628134d0
Debug session time: Thu Jun  8 10:48:12.966 2023 (UTC - 4:00)
System Uptime: 0 days 9:31:19.562
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`6202c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9182`ed8bf210=000000000000004e
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a, 
Arg2: 0000000000fcc468
Arg3: 0000000000000006
Arg4: 0000000000000002

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4640

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19080

    Key  : Analysis.IO.Other.Mb
    Value: 3

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 33

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x4e

    Key  : Bugcheck.Code.Register
    Value: 0x4e

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  060823-24406-01.dmp

BUGCHECK_CODE:  4e

BUGCHECK_P1: 9a

BUGCHECK_P2: fcc468

BUGCHECK_P3: 6

BUGCHECK_P4: 2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff9182`ed8bf208 fffff804`6224da4a     : 00000000`0000004e 00000000`0000009a 00000000`00fcc468 00000000`00000006 : nt!KeBugCheckEx
ffff9182`ed8bf210 fffff804`620afa14     : 1a000001`525dd863 00000000`00000000 00000000`00000000 fffff804`61e4009b : nt!MiBadRefCount+0x42
ffff9182`ed8bf250 fffff804`61ea7400     : ffffa785`1c0fb000 00000000`00000000 00000000`00000002 0a00000f`cc468863 : nt!MiDeleteNonPagedPoolPte+0x2084e4
ffff9182`ed8bf2c0 fffff804`61ea7147     : 00000000`00000000 00000000`00000000 ffff9182`ed8bf760 fffff804`620355f6 : nt!MiClearNonPagedPtes+0x16c
ffff9182`ed8bf500 fffff804`61ea7072     : 00000000`00000000 ffff9182`ed8bf691 ffffffff`ffffffff 00000000`00000000 : nt!MmFreePoolMemory+0xa3
ffff9182`ed8bf590 fffff804`61ea7012     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpEnvFreeVA+0x12
ffff9182`ed8bf5c0 fffff804`61e4bb64     : ffff36bd`6d8e642b fffff804`61eea219 ffffa785`0b302080 00000000`00000000 : nt!RtlpHpFreeVA+0x3a
ffff9182`ed8bf610 fffff804`61e4aecb     : 00000000`00000000 ffffa785`1c000000 00000000`ffffffff fffff804`61ea9a3d : nt!RtlpHpSegMgrCommit+0x334
ffff9182`ed8bf6e0 fffff804`61e4b5fa     : 00000000`00000000 ffffa785`1c001600 00000000`0000004b ffffa785`00000001 : nt!RtlpHpSegPageRangeCommit+0x29b
ffff9182`ed8bf780 fffff804`61f28bca     : ffffa785`00000000 ffffa785`1c000000 ffffa785`1c001600 ffffa785`0ae00140 : nt!RtlpHpSegPageRangeCoalesce+0x28a
ffff9182`ed8bf7e0 fffff804`61f28a48     : 00000000`00000000 00000000`00000000 ffff9182`ed8bfa00 ffffa785`0ae002c0 : nt!RtlpHpSegContextCompact+0x14a
ffff9182`ed8bf840 fffff804`61f289b5     : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : nt!RtlpHpHeapCompact+0x74
ffff9182`ed8bf870 fffff804`61ebd625     : 00000000`00000001 ffff9182`ed8bfa00 ffffa785`00000001 fffff804`00000000 : nt!ExpHpCompactionRoutine+0x205
ffff9182`ed8bf900 fffff804`61eccfd7     : ffffa785`25895040 00000000`00000900 ffffa785`25895040 fffff804`61ebd4d0 : nt!ExpWorkerThread+0x155
ffff9182`ed8bfaf0 fffff804`62031054     : ffffcd81`1a591180 ffffa785`25895040 fffff804`61eccf80 5f000004`7cc60000 : nt!PspSystemThreadStartup+0x57
ffff9182`ed8bfb40 00000000`00000000     : ffff9182`ed8c0000 ffff9182`ed8b9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiBadRefCount+42

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.1830

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  42

FAILURE_BUCKET_ID:  0x4E_9a_nt!MiBadRefCount

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4c6c82ad-5a0e-fdfd-2072-9de1e8578958}

Followup:     MachineOwner
---------

But here's the one from last night when my power went out:

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


Loading Dump File [C:\Windows\Minidump\060823-21390-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff804`58a00000 PsLoadedModuleList = 0xfffff804`596134d0
Debug session time: Thu Jun  8 01:15:18.020 2023 (UTC - 4:00)
System Uptime: 0 days 23:58:28.401
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`58e2c0f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffe8f`51ca7210=000000000000004e
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 000000000000009a, 
Arg2: 0000000000721204
Arg3: 0000000000000006
Arg4: 0000000000000002

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3656

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14288

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 10

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x4e

    Key  : Bugcheck.Code.Register
    Value: 0x4e

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  060823-21390-01.dmp

BUGCHECK_CODE:  4e

BUGCHECK_P1: 9a

BUGCHECK_P2: 721204

BUGCHECK_P3: 6

BUGCHECK_P4: 2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffffe8f`51ca7208 fffff804`5904da4a     : 00000000`0000004e 00000000`0000009a 00000000`00721204 00000000`00000006 : nt!KeBugCheckEx
fffffe8f`51ca7210 fffff804`58eafa14     : 1a000001`818e7863 00000000`00000000 00000000`00000000 fffff804`58c4009b : nt!MiBadRefCount+0x42
fffffe8f`51ca7250 fffff804`58ca7400     : ffffd289`cdcfb000 00000000`00000000 00000000`00000002 0a000007`21204863 : nt!MiDeleteNonPagedPoolPte+0x2084e4
fffffe8f`51ca72c0 fffff804`58ca7147     : 00000000`00000000 00000000`00000000 fffffe8f`51ca7760 fffff804`58e355f6 : nt!MiClearNonPagedPtes+0x16c
fffffe8f`51ca7500 fffff804`58ca7072     : 00000000`00000000 fffffe8f`51ca7691 ffffffff`ffffffff 00000000`00000000 : nt!MmFreePoolMemory+0xa3
fffffe8f`51ca7590 fffff804`58ca7012     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpEnvFreeVA+0x12
fffffe8f`51ca75c0 fffff804`58c4bb64     : ffffa7a2`293fb019 ffffd28a`00000001 ffffd289`bb802080 00000000`00000000 : nt!RtlpHpFreeVA+0x3a
fffffe8f`51ca7610 fffff804`58c4aecb     : 00000000`00000000 ffffd289`cdc00000 00000000`ffffffff fffff804`58ca9a3d : nt!RtlpHpSegMgrCommit+0x334
fffffe8f`51ca76e0 fffff804`58c4b5fa     : 00000000`00000000 ffffd289`cdc01f60 00000000`00000000 ffffd289`00000001 : nt!RtlpHpSegPageRangeCommit+0x29b
fffffe8f`51ca7780 fffff804`58d28bca     : ffffd289`00000000 ffffd289`cdc00000 ffffd289`cdc01f60 ffffd289`bb200140 : nt!RtlpHpSegPageRangeCoalesce+0x28a
fffffe8f`51ca77e0 fffff804`58d28a48     : 00000000`00000000 00000000`00000000 fffffe8f`51ca7a00 ffffd289`bb2002c0 : nt!RtlpHpSegContextCompact+0x14a
fffffe8f`51ca7840 fffff804`58d289b5     : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : nt!RtlpHpHeapCompact+0x74
fffffe8f`51ca7870 fffff804`58cbd625     : 00000000`00000001 ffffd289`f89ec000 ffffd289`00000001 fffff804`00000000 : nt!ExpHpCompactionRoutine+0x205
fffffe8f`51ca7900 fffff804`58cccfd7     : ffffd289`f89ec040 00000000`000001ac ffffd289`f89ec040 fffff804`58cbd4d0 : nt!ExpWorkerThread+0x155
fffffe8f`51ca7af0 fffff804`58e31054     : ffffbf00`dfcd1180 ffffd289`f89ec040 fffff804`58cccf80 00000000`00000008 : nt!PspSystemThreadStartup+0x57
fffffe8f`51ca7b40 00000000`00000000     : fffffe8f`51ca8000 fffffe8f`51ca1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiBadRefCount+42

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.1830

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  42

FAILURE_BUCKET_ID:  0x4E_9a_nt!MiBadRefCount

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4c6c82ad-5a0e-fdfd-2072-9de1e8578958}

Followup:     MachineOwner
---------

http://www.dropbox.com/s/8vd2lab6498l585/20230608_104826.jpg?dl=1

5

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Any WDM background app can cause buffer size change issues. Some apps are even known for that (Sonarworks). Reagrdsing the BSOD it might go away by using a different FireWire driver in Windows.

Regards
Matthias Carstens
RME

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

No tengo mucha experiencia y puede que algo de lo que diga no sea correcto. Me he registrado expresamente por si mi caso puede ayudar a otras personas. Escribo en Español y luego traduciré al Inglés por lo que puede haber alguna inconsistencia.

Estoy muy contento con mi nueva adquisición, RME fireface UCX II. Soy propietario de una RME fireface UC desde hace unos 10 años…ahora tengo las dos…soy un afortunado.

Problema resuelto con la UCX II nueva.

Cada vez que cambiaba el buffer en la configuración (settings) de la UCX II, la reproducción, grabación…variaba la velocidad de reproducción dentro de Reaper acelerándola o ralentizándola dependiendo de si el cambio de buffer era de menos a más o de más a menos respectivamente…haciendo además todo tipo de artefactos distorsionados…una vez que fallaba, hasta alimentar con phantom 48V una pista hacia un pitido distorsionado con una cola sin fin…esto está roto pensé…parecía como cuando hay discrepancia entre varios samples rates 48000/44100 entre dispositivos o software…pero además distorsión, clics, ecos, artefactos de todo tipo…una desgracia. Apagaba la UCX II sin reiniciar el ordenador y todo volvía a la normalidad. Un día entero cambiando configuraciones aquí y allá…nada…esto está roto volvía a pensar una y otra vez…hasta que ayer por la noche, agotado y desilusionado…se me ocurrió volver a mirar la configuración de Windows, panel de control/sonido/reproducción/grabación y demás…y resulta que ahí, en opciones avanzadas del dispositivo predeterminado, hay una opción que suelo dejar deseleccionado por consejo de muchos tutoriales de optimización de Windows para audio, me refiero a la de “Permitir que las aplicaciones tomen el control exclusivo de este dispositivo” y la de abajo “ Dar prioridad a las aplicaciones en modo exclusivo”, las seleccione las dos y…voilà…desde ese momento todo volvió a la normalidad. Nunca me había pasado, en unos ordenadores lo tengo marcado y en otros no…en ese mismo ordenador con la RME UC da igual si lo marcas o lo desmarcas…en este caso con la UCX II, en ese ordenador (Windows 10) por lo menos, es necesario marcarlo. Bueno, pues eso, si a alguien le pasa lo mismo (davidlaijiajun), aunque sea otro modelo RME, que pruebe esta solución por si es el mismo caso. A mí es la primera vez que me pasa.
(No uso Sonarworks, y todo está actualizado en la nueva UCX II. USB 105/DSP 26/USB CC 104)

Saludos a todos y Gracias a RME.


(traducido)


I don't have much experience and some of what I say may not be correct. I have registered expressly in case my case can help other people. I write in Spanish and then I will translate into English so there may be some inconsistencies. I am very happy with my new purchase, RME fireface UCX II. I have owned an RME fireface UC for about 10 years…now I have both…I am lucky.

Fixed issue with the new UCX II.

Every time I changed the buffer in the settings (settings) of the UCX II, the playback, recording... I varied the playback speed within Reaper speeding it up or slowing it down depending on whether the buffer change was from less to more or from more to less respectively…plus making all sorts of distorted artifacts…once it failed, even 48V phantom powering a track to a distorted beep with an endless tail…this is broken I thought…it seemed like when there is a discrepancy between various 48000/44100 sample rates between devices or software... but also distortion, clicks, echoes, artifacts of all kinds... a misfortune. I turned off the UCX II without restarting the computer and everything was back to normal. A whole day changing settings here and there...nothing...this is broken I kept thinking again and again...until last night, exhausted and disappointed...it occurred to me to look again in Windows settings, control panel/sound/ playback/recording and so on... and it turns out that there, in the advanced options of the default device, there is an option that I usually leave deselected on the advice of many Windows audio optimization tutorials, I mean the "Allow applications to take control exclusive to this device” and the one below “Give priority to apps in exclusive mode”, I selected them both and…voilà…from that moment everything went back to normal. It had never happened to me, on some computers I have it checked and on others I don't... on that same computer with the RME UC it doesn't matter if you check it or uncheck it... in this case with the UCX II, on that computer (Windows 10) so less, it is necessary to mark it. Well, that's it, if the same thing happens to someone (davidlaijiajun), even if it's another RME model, try this solution in case it's the same case. It's the first time it's happened to me.

(I don't use Sonarworks, and everything is up to date on the new UCX II. USB 105/DSP 26/USB CC 104)

Greetings to all and Thanks to RME.

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Lo siento, me he confundido de hilo/foro. la respuesta era para otro hilo/foro.

https://forum.rme-audio.de/viewtopic.php?id=37585

Soy nuevo. Disculpen las molestias.





Sorry, I got the wrong thread/forum. the answer was for another thread/forum.

https://forum.rme-audio.de/viewtopic.php?id=37585

I'm new. Sorry for the inconvenience.

8 (edited by jasonbrianmerrill 2023-06-11 15:28:20)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

MC wrote:

Any WDM background app can cause buffer size change issues. Some apps are even known for that (Sonarworks). Reagrdsing the BSOD it might go away by using a different FireWire driver in Windows.

Thing is, it only does this when the ASIO driver is activated on REAPER.

When reaper is closed, it doesn't matter what else is open on the PC. It doesnt BSOD. Also happens w FLStudio.

what firewire driver do you recommend?

9

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Are you using the Legacy 1394 (Firewire) Driver?

Frank Lockwood
https://LockwoodARS.com
Fireface 800, Firmware 2.77
Drivers: Win10, 3.125; Mac, 3.36

10 (edited by jasonbrianmerrill 2023-06-12 03:00:48)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

It keeps defaulting to:

Texas Instruments 1394 OHCI Compliant Host Controller

---

I will try and change it again.

I've been trying to change it to other drivers - I have these other ones:

1394 OHCI Compliant Host Controller (Legacy)
and
1394 OHCI Compliant Host Controller

11

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Yes the 1394 OHCI Compliant Host Controller (Legacy) driver is the one you want to use. I have no clue why the setting doesn't "take". Perhaps a Win11 permissions thing?

Frank Lockwood
https://LockwoodARS.com
Fireface 800, Firmware 2.77
Drivers: Win10, 3.125; Mac, 3.36

12 (edited by jasonbrianmerrill 2023-06-12 14:36:15)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I got it to take. Same issue. sad



I basically had to delete the other driver.

Although, I have to say I am now able to change sample rate and latency without glitches!

Could it be something about how the octopre is connected?

https://www.dropbox.com/s/3zsc7qyy10nq3f1/Screenshot%202023-06-12%20093545.png?dl=1

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Then how about people like me using the Babyface Pro / Pro FS and can't adjust buffer size on the fly? I admire you firewire users, haha.

14 (edited by MetalHeadKeys 2023-06-12 15:57:14)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

jasonbrianmerrill wrote:

Could it be something about how the octopre is connected?

If the driver reports "Sync" and it doesn't change between "Lock" and "Sync", then it 's, properly, clocked!
Nevertheless, I 'll describe the connections and settings you need, so you can check!

So, you need a Word Clock cable from FF800 'Word Out' to Octopre 'Word In'
and ADAT Cable(s) from Octopre 'ADAT Out' to FF800 'ADAT In'

Set 'Clock Source' to "Internal" on the FF800, and 'Clock Source' to "WordClock" on the Octopre.
That 's all on the Clocking side!

Now, if you, still, get glitches you need to "tune" your PC for Audio related work!
Some steps are:
- Disable C States in the Bios
- Use "Highest" or "Ultimate" Power plan on Windows
- Optimize Windows for "Background Tasks"
- Disable unnecessary Windows Services

If you 're using an NVidia GPU, choose highest Power Settings, as well, or try their "Studio" Driver Version (if your card is supported)
If all of the above, don 't work, you can try another PCI port for your FireWire Card!

You can, also, run this: https://www.resplendence.com/latencymon
to check if there is any other software that occupies the CPU, for too long.
Run it with a fresh restart, and let it run for 5-10 minutes, on an idle system!

Then, please, post an update! smile

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

My current settings:

- octopre is on wordclock and the "locked" light is lit.

https://www.dropbox.com/s/oci3h9lwtkkcq36/Screenshot%202023-06-12%20132738.png?dl=1

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

more settings changes next big_smile

here's my power plan:

https://www.dropbox.com/s/fxlrlyx9chn2vff/Screenshot%202023-06-12%20132917.png?dl=1

https://www.dropbox.com/s/v2kglzv9kawecbs/Screenshot%202023-06-12%20132945.png?dl=1

https://www.dropbox.com/s/6ycdswd6vlsed5h/Screenshot%202023-06-12%20133025.png?dl=1

https://www.dropbox.com/s/76zx88ip5d5m1kc/Screenshot%202023-06-12%20133040.png?dl=1

17 (edited by jasonbrianmerrill 2023-06-12 19:35:31)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

aaaaaannnnd this

https://www.dropbox.com/s/9hnfgf18d6coapg/20230612_133556.jpg?dl=1

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

seems decent here, even with all my startup programs loaded. I typically turn them off during recording sessions.

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts. 
LatencyMon has been analyzing your system for  0:08:47  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BASEMENTSTUDIO
OS version:                                           Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware:                                             System Product Name, System manufacturer
BIOS:                                                 2801
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors:                                   12
Processor groups:                                     1
Processor group size:                                 12
RAM:                                                  65471 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             3696 MHz
Reported CPU speed (registry):                        3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   363.80
Average measured interrupt to process latency (µs):   4.698855

Highest measured interrupt to DPC latency (µs):       358.80
Average measured interrupt to DPC latency (µs):       2.366083


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              123.969156
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.016022
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.021935

ISR count (execution time <250 µs):                   289761
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               0
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              474.834957
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.017806
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.059749

DPC count (execution time <250 µs):                   711709
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              232
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 msmpeng.exe

Total number of hard pagefaults                       1409
Hard pagefault count of hardest hit process:          1054
Number of processes hit:                              21


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       11.924730
CPU 0 ISR highest execution time (µs):                123.969156
CPU 0 ISR total execution time (s):                   1.387153
CPU 0 ISR count:                                      288835
CPU 0 DPC highest execution time (µs):                474.834957
CPU 0 DPC total execution time (s):                   3.547743
CPU 0 DPC count:                                      657760
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       1.635916
CPU 1 ISR highest execution time (µs):                66.407468
CPU 1 ISR total execution time (s):                   0.000959
CPU 1 ISR count:                                      926
CPU 1 DPC highest execution time (µs):                179.519481
CPU 1 DPC total execution time (s):                   0.044127
CPU 1 DPC count:                                      15005
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       1.795748
CPU 2 ISR highest execution time (µs):                0.0
CPU 2 ISR total execution time (s):                   0.0
CPU 2 ISR count:                                      0
CPU 2 DPC highest execution time (µs):                76.845238
CPU 2 DPC total execution time (s):                   0.032618
CPU 2 DPC count:                                      7396
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       1.256118
CPU 3 ISR highest execution time (µs):                0.0
CPU 3 ISR total execution time (s):                   0.0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                74.640693
CPU 3 DPC total execution time (s):                   0.007407
CPU 3 DPC count:                                      1803
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       1.913337
CPU 4 ISR highest execution time (µs):                0.0
CPU 4 ISR total execution time (s):                   0.0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                89.823593
CPU 4 DPC total execution time (s):                   0.036211
CPU 4 DPC count:                                      7712
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       4.174322
CPU 5 ISR highest execution time (µs):                0.0
CPU 5 ISR total execution time (s):                   0.0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                97.522727
CPU 5 DPC total execution time (s):                   0.006481
CPU 5 DPC count:                                      1406
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       2.610285
CPU 6 ISR highest execution time (µs):                0.0
CPU 6 ISR total execution time (s):                   0.0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                83.583333
CPU 6 DPC total execution time (s):                   0.029181
CPU 6 DPC count:                                      6297
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       1.076660
CPU 7 ISR highest execution time (µs):                0.0
CPU 7 ISR total execution time (s):                   0.0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                65.876623
CPU 7 DPC total execution time (s):                   0.002715
CPU 7 DPC count:                                      526
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       2.334410
CPU 8 ISR highest execution time (µs):                0.0
CPU 8 ISR total execution time (s):                   0.0
CPU 8 ISR count:                                      0
CPU 8 DPC highest execution time (µs):                74.396104
CPU 8 DPC total execution time (s):                   0.029540
CPU 8 DPC count:                                      6006
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       0.978627
CPU 9 ISR highest execution time (µs):                0.0
CPU 9 ISR total execution time (s):                   0.0
CPU 9 ISR count:                                      0
CPU 9 DPC highest execution time (µs):                66.529221
CPU 9 DPC total execution time (s):                   0.002443
CPU 9 DPC count:                                      432
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       2.138369
CPU 10 ISR highest execution time (µs):                0.0
CPU 10 ISR total execution time (s):                   0.0
CPU 10 ISR count:                                      0
CPU 10 DPC highest execution time (µs):                71.871212
CPU 10 DPC total execution time (s):                   0.032483
CPU 10 DPC count:                                      6052
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       1.563813
CPU 11 ISR highest execution time (µs):                0.0
CPU 11 ISR total execution time (s):                   0.0
CPU 11 ISR count:                                      0
CPU 11 DPC highest execution time (µs):                75.667749
CPU 11 DPC total execution time (s):                   0.010175
CPU 11 DPC count:                                      1546
_________________________________________________________________________________________________________

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Hi, again!

Yes, latencyMon report seems very good, except of the Hard Pagefaults Count.
Here's a good article I found on msmpeng.exe, that you can try: https://www.freecodecamp.org/news/what- … isk-usage/

Now, here is another on how to optimize Windows for "Background Services": https://www.thewindowsclub.com/processo … indows-7-8

Also, on the same "Advanced" Tab, there is a "Virtual Memory" Setting. Set that to half of your physical RAM! So, for 64gigs -> 32768.
If you click on the "Change..." button, you will be presented with a few additional options.
Set both Minimum and Maximum value to "32768". If it's too much space for your hard drive set it to "16384".

Also, I would disable "Intel SpeedStep" and "Intel Speedshift Technology", in the BIOS.
Try these tweaks, and please, report back! smile

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

My findings in my blog

https://www.tonstudio-forum.de/blog/Ent … es-or-not/

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13

21 (edited by jasonbrianmerrill 2023-06-14 15:38:06)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

MetalHeadKeys wrote:

Hi,

Also, I would disable "Intel SpeedStep" and "Intel Speedshift Technology", in the BIOS.
Try these tweaks, and please, report back! smile

Hey there, the reason that I wouldn't want to do this in the BIOS it's because if I wanted to have power savings later on, this isn't able to be changed unless I reboot the system.

Would this send disable the power management when it comes to minimum and maximum processor state in the control panel?

Obviously though if I have to do this I'm going to do it.

Also I don't think this would be related to the BSOD, but I certainly appreciate whatever tweeks I can make

As far as that first process which seems to be related to Windows defender, it could be that upon boot up it is doing a lot of work. Next time after I boot up I'll wait about 15 minutes for everything to have loaded and initialize and then I'll run a latency scan again

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Thank you for this I'll check it out. I don't like doing a ton of two weeks but if there are some that seem reasonable and won't affect other usage, because I also use the computer for lots of typical user stuff.

I have this razor cortex program that actually disables a bunch of unnecessary stuff when needed and then re-enables it when I want to use it

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

jasonbrianmerrill wrote:

Would this send disable the power management when it comes to minimum and maximum processor state in the control panel?

No, I don't think so! It' s on a MoBo level. Windows can, still, manage minimum and maximum processor states. At least, you can try! You can re-enable them, if you want, later!

Thing is that firewire is kind of a bottleneck, in your situation, so we need to relieve the CPU as much as possible!
The number of logical processors doesn't matter. Even if only one processor reaches 100 per cent usage, you will have dropouts!
And with processes running in the background (apps constantly checking for updates, OneDrive, Xbox Gaming etc), it becomes harder to achieve the required CPU stability.

Did you try the other tweaks? (optimize for background services, and virtual memory)
Also, yes, do check Ramses' suggestions!!

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

MetalHeadKeys wrote:

Hi, again!

Yes, latencyMon report seems very good, except of the Hard Pagefaults Count.
Here's a good article I found on msmpeng.exe, that you can try: https://www.freecodecamp.org/news/what- … isk-usage/

Well, I do wonder about one thing. My DAW is always connected to the net, so i always need realtime protection on, I think - I am not totally up on stuff these days but I wouldn't want a worm or something to make its way into my pc - I don't click on any risky links, and actually I scan every exe or suspicious or potentially harmful file with windefender as it is.. but I am not sure I should disable realtime scanning.

The exclusion thing, however - WHY does windows defender scan its own folder? That's odd. I'll try it. Maybe its a place it puts files that are downloaded to scan?

anyway, that's all done.

MetalHeadKeys wrote:

Now, here is another on how to optimize Windows for "Background Services": https://www.thewindowsclub.com/processo … indows-7-8

Also, on the same "Advanced" Tab, there is a "Virtual Memory" Setting. Set that to half of your physical RAM! So, for 64gigs -> 32768.
If you click on the "Change..." button, you will be presented with a few additional options.
Set both Minimum and Maximum value to "32768". If it's too much space for your hard drive set it to "16384".

done!

MetalHeadKeys wrote:

Also, I would disable "Intel SpeedStep" and "Intel Speedshift Technology", in the BIOS.
Try these tweaks, and please, report back! smile

next reboot this will also be done!

25 (edited by jasonbrianmerrill 2023-06-15 18:50:15)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

https://www.dropbox.com/s/6hcfol50l0x2bub/20230615_114414.jpg?dl=1

https://www.dropbox.com/s/go05h1hlh9m0o4e/Screenshot%202023-06-15%20130419.png?dl=1

at first, that highest one was quite a bit lower.

second one, forgot to get the report copied:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts. 
LatencyMon has been analyzing your system for  0:18:20  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BASEMENTSTUDIO
OS version:                                           Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware:                                             System Product Name, System manufacturer
BIOS:                                                 2801
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors:                                   12
Processor groups:                                     1
Processor group size:                                 12
RAM:                                                  65471 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             3701 MHz
Reported CPU speed (registry):                        3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   881.50
Average measured interrupt to process latency (µs):   4.012617

Highest measured interrupt to DPC latency (µs):       609.40
Average measured interrupt to DPC latency (µs):       1.756958


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              610.125541
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.009904
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.015290

ISR count (execution time <250 µs):                   553980
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               4
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              362.396104
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.009490
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.040376

DPC count (execution time <250 µs):                   1406348
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              221
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 svchost.exe

Total number of hard pagefaults                       94510
Hard pagefault count of hardest hit process:          94241
Number of processes hit:                              14


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       18.328678
CPU 0 ISR highest execution time (µs):                610.125541
CPU 0 ISR total execution time (s):                   1.979274
CPU 0 ISR count:                                      474499
CPU 0 DPC highest execution time (µs):                362.396104
CPU 0 DPC total execution time (s):                   4.525069
CPU 0 DPC count:                                      1182708
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       2.662068
CPU 1 ISR highest execution time (µs):                74.113095
CPU 1 ISR total execution time (s):                   0.036005
CPU 1 ISR count:                                      72506
CPU 1 DPC highest execution time (µs):                271.226732
CPU 1 DPC total execution time (s):                   0.283515
CPU 1 DPC count:                                      87492
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       3.319582
CPU 2 ISR highest execution time (µs):                67.734307
CPU 2 ISR total execution time (s):                   0.003356
CPU 2 ISR count:                                      6979
CPU 2 DPC highest execution time (µs):                268.969156
CPU 2 DPC total execution time (s):                   0.094097
CPU 2 DPC count:                                      26192
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       2.996907
CPU 3 ISR highest execution time (µs):                0.0
CPU 3 ISR total execution time (s):                   0.0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                271.727814
CPU 3 DPC total execution time (s):                   0.011806
CPU 3 DPC count:                                      3061
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       2.983428
CPU 4 ISR highest execution time (µs):                0.0
CPU 4 ISR total execution time (s):                   0.0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                85.340368
CPU 4 DPC total execution time (s):                   0.053684
CPU 4 DPC count:                                      15804
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       1.777362
CPU 5 ISR highest execution time (µs):                0.0
CPU 5 ISR total execution time (s):                   0.0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                270.576299
CPU 5 DPC total execution time (s):                   0.008044
CPU 5 DPC count:                                      1887
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       3.692718
CPU 6 ISR highest execution time (µs):                0.0
CPU 6 ISR total execution time (s):                   0.0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                315.672078
CPU 6 DPC total execution time (s):                   0.148561
CPU 6 DPC count:                                      37763
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       1.956192
CPU 7 ISR highest execution time (µs):                0.0
CPU 7 ISR total execution time (s):                   0.0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                280.426407
CPU 7 DPC total execution time (s):                   0.011010
CPU 7 DPC count:                                      2810
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       3.079173
CPU 8 ISR highest execution time (µs):                0.0
CPU 8 ISR total execution time (s):                   0.0
CPU 8 ISR count:                                      0
CPU 8 DPC highest execution time (µs):                313.786797
CPU 8 DPC total execution time (s):                   0.083087
CPU 8 DPC count:                                      22668
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       1.665293
CPU 9 ISR highest execution time (µs):                0.0
CPU 9 ISR total execution time (s):                   0.0
CPU 9 ISR count:                                      0
CPU 9 DPC highest execution time (µs):                91.693182
CPU 9 DPC total execution time (s):                   0.014628
CPU 9 DPC count:                                      4309
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       3.520651
CPU 10 ISR highest execution time (µs):                0.0
CPU 10 ISR total execution time (s):                   0.0
CPU 10 ISR count:                                      0
CPU 10 DPC highest execution time (µs):                85.451299
CPU 10 DPC total execution time (s):                   0.085229
CPU 10 DPC count:                                      19735
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       2.088539
CPU 11 ISR highest execution time (µs):                0.0
CPU 11 ISR total execution time (s):                   0.0
CPU 11 ISR count:                                      0
CPU 11 DPC highest execution time (µs):                63.284091
CPU 11 DPC total execution time (s):                   0.011837
CPU 11 DPC count:                                      2140
_________________________________________________________________________________________________________

ok this is strange. I did it again after using "razer cortex" to disable unneeded stuff... maybe I need to tweak that...

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. 
LatencyMon has been analyzing your system for  0:16:36  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BASEMENTSTUDIO
OS version:                                           Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware:                                             System Product Name, System manufacturer
BIOS:                                                 2801
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors:                                   12
Processor groups:                                     1
Processor group size:                                 12
RAM:                                                  65471 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             3701 MHz
Reported CPU speed (registry):                        3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   1192.50
Average measured interrupt to process latency (µs):   4.709173

Highest measured interrupt to DPC latency (µs):       1188.60
Average measured interrupt to DPC latency (µs):       2.237028


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              896.378247
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.012631
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.016399

ISR count (execution time <250 µs):                   268092
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               11
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              593.422619
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.01010
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.039251

DPC count (execution time <250 µs):                   1021058
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              161
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 searchindexer.exe

Total number of hard pagefaults                       22503
Hard pagefault count of hardest hit process:          8743
Number of processes hit:                              179


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       21.368938
CPU 0 ISR highest execution time (µs):                896.378247
CPU 0 ISR total execution time (s):                   1.953839
CPU 0 ISR count:                                      262124
CPU 0 DPC highest execution time (µs):                593.422619
CPU 0 DPC total execution time (s):                   3.800844
CPU 0 DPC count:                                      779252
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       7.242489
CPU 1 ISR highest execution time (µs):                74.077381
CPU 1 ISR total execution time (s):                   0.007540
CPU 1 ISR count:                                      5979
CPU 1 DPC highest execution time (µs):                202.989719
CPU 1 DPC total execution time (s):                   0.369423
CPU 1 DPC count:                                      117106
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       4.542551
CPU 2 ISR highest execution time (µs):                0.0
CPU 2 ISR total execution time (s):                   0.0
CPU 2 ISR count:                                      0
CPU 2 DPC highest execution time (µs):                270.946429
CPU 2 DPC total execution time (s):                   0.094464
CPU 2 DPC count:                                      22016
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       2.218992
CPU 3 ISR highest execution time (µs):                0.0
CPU 3 ISR total execution time (s):                   0.0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                81.711039
CPU 3 DPC total execution time (s):                   0.016715
CPU 3 DPC count:                                      5398
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       5.815833
CPU 4 ISR highest execution time (µs):                0.0
CPU 4 ISR total execution time (s):                   0.0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                162.614177
CPU 4 DPC total execution time (s):                   0.072689
CPU 4 DPC count:                                      21847
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       2.121128
CPU 5 ISR highest execution time (µs):                0.0
CPU 5 ISR total execution time (s):                   0.0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                323.810606
CPU 5 DPC total execution time (s):                   0.015642
CPU 5 DPC count:                                      3446
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       4.451018
CPU 6 ISR highest execution time (µs):                0.0
CPU 6 ISR total execution time (s):                   0.0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                320.856602
CPU 6 DPC total execution time (s):                   0.125068
CPU 6 DPC count:                                      28967
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       2.082449
CPU 7 ISR highest execution time (µs):                0.0
CPU 7 ISR total execution time (s):                   0.0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                77.760281
CPU 7 DPC total execution time (s):                   0.007871
CPU 7 DPC count:                                      1647
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       3.787380
CPU 8 ISR highest execution time (µs):                0.0
CPU 8 ISR total execution time (s):                   0.0
CPU 8 ISR count:                                      0
CPU 8 DPC highest execution time (µs):                276.388528
CPU 8 DPC total execution time (s):                   0.091390
CPU 8 DPC count:                                      24042
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       2.031297
CPU 9 ISR highest execution time (µs):                0.0
CPU 9 ISR total execution time (s):                   0.0
CPU 9 ISR count:                                      0
CPU 9 DPC highest execution time (µs):                84.982684
CPU 9 DPC total execution time (s):                   0.007808
CPU 9 DPC count:                                      1548
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       4.119929
CPU 10 ISR highest execution time (µs):                0.0
CPU 10 ISR total execution time (s):                   0.0
CPU 10 ISR count:                                      0
CPU 10 DPC highest execution time (µs):                291.866342
CPU 10 DPC total execution time (s):                   0.078449
CPU 10 DPC count:                                      13704
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       2.164257
CPU 11 ISR highest execution time (µs):                0.0
CPU 11 ISR total execution time (s):                   0.0
CPU 11 ISR count:                                      0
CPU 11 DPC highest execution time (µs):                75.966991
CPU 11 DPC total execution time (s):                   0.014275
CPU 11 DPC count:                                      2246
_________________________________________________________________________________________________________

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

Well, I think you know the next step! smile

Disable Windows Search Service: https://www.makeuseof.com/windows-search-indexer-guide/
It's described on the lower half of the article, labeled " Is It Safe to Stop Windows Search Indexing? ".

Then check with LatencyMon, again, and post an update! smile

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts. 
LatencyMon has been analyzing your system for  0:10:01  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BASEMENTSTUDIO
OS version:                                           Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware:                                             System Product Name, System manufacturer
BIOS:                                                 2801
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors:                                   12
Processor groups:                                     1
Processor group size:                                 12
RAM:                                                  65471 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             3701 MHz
Reported CPU speed (registry):                        3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   327.50
Average measured interrupt to process latency (µs):   3.970567

Highest measured interrupt to DPC latency (µs):       321.90
Average measured interrupt to DPC latency (µs):       1.820054


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              350.922619
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.009474
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.012956

ISR count (execution time <250 µs):                   112831
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               2
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              726.200216
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.008645
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 531.61 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.032780

DPC count (execution time <250 µs):                   553261
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              138
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 searchprotocolhost.exe

Total number of hard pagefaults                       28944
Hard pagefault count of hardest hit process:          10681
Number of processes hit:                              41


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       10.349617
CPU 0 ISR highest execution time (µs):                350.922619
CPU 0 ISR total execution time (s):                   0.934691
CPU 0 ISR count:                                      112716
CPU 0 DPC highest execution time (µs):                726.200216
CPU 0 DPC total execution time (s):                   1.897374
CPU 0 DPC count:                                      429730
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       3.358877
CPU 1 ISR highest execution time (µs):                61.985390
CPU 1 ISR total execution time (s):                   0.001166
CPU 1 ISR count:                                      117
CPU 1 DPC highest execution time (µs):                97.935606
CPU 1 DPC total execution time (s):                   0.209064
CPU 1 DPC count:                                      66085
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       1.646025
CPU 2 ISR highest execution time (µs):                0.0
CPU 2 ISR total execution time (s):                   0.0
CPU 2 ISR count:                                      0
CPU 2 DPC highest execution time (µs):                122.450216
CPU 2 DPC total execution time (s):                   0.035746
CPU 2 DPC count:                                      7528
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       0.979537
CPU 3 ISR highest execution time (µs):                0.0
CPU 3 ISR total execution time (s):                   0.0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                77.588203
CPU 3 DPC total execution time (s):                   0.006873
CPU 3 DPC count:                                      1441
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       2.798441
CPU 4 ISR highest execution time (µs):                0.0
CPU 4 ISR total execution time (s):                   0.0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                77.530844
CPU 4 DPC total execution time (s):                   0.074819
CPU 4 DPC count:                                      19188
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       0.988106
CPU 5 ISR highest execution time (µs):                0.0
CPU 5 ISR total execution time (s):                   0.0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                66.126082
CPU 5 DPC total execution time (s):                   0.008129
CPU 5 DPC count:                                      2297
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       1.777264
CPU 6 ISR highest execution time (µs):                0.0
CPU 6 ISR total execution time (s):                   0.0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                107.199134
CPU 6 DPC total execution time (s):                   0.019981
CPU 6 DPC count:                                      4325
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       0.891734
CPU 7 ISR highest execution time (µs):                0.0
CPU 7 ISR total execution time (s):                   0.0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                56.826299
CPU 7 DPC total execution time (s):                   0.003014
CPU 7 DPC count:                                      625
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       1.67830
CPU 8 ISR highest execution time (µs):                0.0
CPU 8 ISR total execution time (s):                   0.0
CPU 8 ISR count:                                      0
CPU 8 DPC highest execution time (µs):                92.240801
CPU 8 DPC total execution time (s):                   0.067536
CPU 8 DPC count:                                      14224
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       0.829701
CPU 9 ISR highest execution time (µs):                0.0
CPU 9 ISR total execution time (s):                   0.0
CPU 9 ISR count:                                      0
CPU 9 DPC highest execution time (µs):                85.093074
CPU 9 DPC total execution time (s):                   0.004338
CPU 9 DPC count:                                      779
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       1.822307
CPU 10 ISR highest execution time (µs):                0.0
CPU 10 ISR total execution time (s):                   0.0
CPU 10 ISR count:                                      0
CPU 10 DPC highest execution time (µs):                86.107143
CPU 10 DPC total execution time (s):                   0.032346
CPU 10 DPC count:                                      5747
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       0.955199
CPU 11 ISR highest execution time (µs):                0.0
CPU 11 ISR total execution time (s):                   0.0
CPU 11 ISR count:                                      0
CPU 11 DPC highest execution time (µs):                71.699675
CPU 11 DPC total execution time (s):                   0.008542
CPU 11 DPC count:                                      1430
_________________________________________________________________________________________________________

28 (edited by MetalHeadKeys 2023-06-16 14:57:18)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I just noticed, your previous power settings' screenshot!

You need to set minimum processor state to '100 percent', as well, and 'Turn off Hard Disk' to "Never".
Save that as your power plan, and you can change power plans depending on your PC usage, if you don't want to keep the CPU to 100%!
Also, disable any on-board Sound card!
Also, you should consider disabling Cortana and OneDrive, or at least stop the services from running when you 're using Reaper
You can, also, check the Studio Drivers for nVidia GPUs, if your card is supported :https://www.nvidia.com/Download/driverR … 730/en-us/


Also, check your BIOS PCI settings and disable any power-management setting for the port where you have the Firewire card connected!
Restart and check with Reaper! Do you, still, get BSOD or dropouts? Has performance improved?

RME Gear: Digiface USB, HDSP 9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

ok, all of this is done!

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts. 
LatencyMon has been analyzing your system for  0:17:45  (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:                                        BASEMENTSTUDIO
OS version:                                           Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware:                                             System Product Name, System manufacturer
BIOS:                                                 2801
CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
Logical processors:                                   12
Processor groups:                                     1
Processor group size:                                 12
RAM:                                                  65471 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI):                             3701 MHz
Reported CPU speed (registry):                        3696 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.


_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs):   373.60
Average measured interrupt to process latency (µs):   4.696670

Highest measured interrupt to DPC latency (µs):       365.30
Average measured interrupt to DPC latency (µs):       2.364757


_________________________________________________________________________________________________________
 REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs):              191.560065
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.005904
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.008277

ISR count (execution time <250 µs):                   130633
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-1000 µs):               0
ISR count (execution time 1000-2000 µs):              0
ISR count (execution time 2000-4000 µs):              0
ISR count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs):              357.550325
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 528.24 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.005597
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 528.24 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.020554

DPC count (execution time <250 µs):                   551748
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-10000 µs):              119
DPC count (execution time 1000-2000 µs):              0
DPC count (execution time 2000-4000 µs):              0
DPC count (execution time >=4000 µs):                 0


_________________________________________________________________________________________________________
 REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count:                 searchindexer.exe

Total number of hard pagefaults                       4396
Hard pagefault count of hardest hit process:          3266
Number of processes hit:                              16


_________________________________________________________________________________________________________
 PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s):                       17.759017
CPU 0 ISR highest execution time (µs):                191.560065
CPU 0 ISR total execution time (s):                   1.058106
CPU 0 ISR count:                                      130633
CPU 0 DPC highest execution time (µs):                357.550325
CPU 0 DPC total execution time (s):                   1.849945
CPU 0 DPC count:                                      310190
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s):                       7.607782
CPU 1 ISR highest execution time (µs):                0.0
CPU 1 ISR total execution time (s):                   0.0
CPU 1 ISR count:                                      0
CPU 1 DPC highest execution time (µs):                321.134740
CPU 1 DPC total execution time (s):                   0.352861
CPU 1 DPC count:                                      122622
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s):                       3.482581
CPU 2 ISR highest execution time (µs):                0.0
CPU 2 ISR total execution time (s):                   0.0
CPU 2 ISR count:                                      0
CPU 2 DPC highest execution time (µs):                62.815476
CPU 2 DPC total execution time (s):                   0.088005
CPU 2 DPC count:                                      26938
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s):                       3.728290
CPU 3 ISR highest execution time (µs):                0.0
CPU 3 ISR total execution time (s):                   0.0
CPU 3 ISR count:                                      0
CPU 3 DPC highest execution time (µs):                37.586580
CPU 3 DPC total execution time (s):                   0.026480
CPU 3 DPC count:                                      8628
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s):                       6.046079
CPU 4 ISR highest execution time (µs):                0.0
CPU 4 ISR total execution time (s):                   0.0
CPU 4 ISR count:                                      0
CPU 4 DPC highest execution time (µs):                40.412338
CPU 4 DPC total execution time (s):                   0.044688
CPU 4 DPC count:                                      11544
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s):                       1.902120
CPU 5 ISR highest execution time (µs):                0.0
CPU 5 ISR total execution time (s):                   0.0
CPU 5 ISR count:                                      0
CPU 5 DPC highest execution time (µs):                34.152056
CPU 5 DPC total execution time (s):                   0.010935
CPU 5 DPC count:                                      2773
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s):                       4.066272
CPU 6 ISR highest execution time (µs):                0.0
CPU 6 ISR total execution time (s):                   0.0
CPU 6 ISR count:                                      0
CPU 6 DPC highest execution time (µs):                61.617424
CPU 6 DPC total execution time (s):                   0.103783
CPU 6 DPC count:                                      22999
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s):                       2.002249
CPU 7 ISR highest execution time (µs):                0.0
CPU 7 ISR total execution time (s):                   0.0
CPU 7 ISR count:                                      0
CPU 7 DPC highest execution time (µs):                32.609307
CPU 7 DPC total execution time (s):                   0.006462
CPU 7 DPC count:                                      1621
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s):                       2.813155
CPU 8 ISR highest execution time (µs):                0.0
CPU 8 ISR total execution time (s):                   0.0
CPU 8 ISR count:                                      0
CPU 8 DPC highest execution time (µs):                56.419372
CPU 8 DPC total execution time (s):                   0.039177
CPU 8 DPC count:                                      11027
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s):                       1.994826
CPU 9 ISR highest execution time (µs):                0.0
CPU 9 ISR total execution time (s):                   0.0
CPU 9 ISR count:                                      0
CPU 9 DPC highest execution time (µs):                36.118506
CPU 9 DPC total execution time (s):                   0.020901
CPU 9 DPC count:                                      7237
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s):                       3.638034
CPU 10 ISR highest execution time (µs):                0.0
CPU 10 ISR total execution time (s):                   0.0
CPU 10 ISR count:                                      0
CPU 10 DPC highest execution time (µs):                63.762987
CPU 10 DPC total execution time (s):                   0.04830
CPU 10 DPC count:                                      9300
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s):                       2.053830
CPU 11 ISR highest execution time (µs):                0.0
CPU 11 ISR total execution time (s):                   0.0
CPU 11 ISR count:                                      0
CPU 11 DPC highest execution time (µs):                39.060065
CPU 11 DPC total execution time (s):                   0.035921
CPU 11 DPC count:                                      16988
_________________________________________________________________________________________________________

I'm already seeming to notice differences in performance - ill keep testing. It seems the BSOD problem was still happening. Will test right now...

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

yeah, still happening. Can't really figure out why. Only happens when:

1. Reaper is open
2. FF800 driver is being used
3. FF800 is shut off

ofc, I could just not shut it off - but I have an auto shut off for my studio at 3am in case I leave it on, but keep in mind that no matter HOW I shut it off, the BSOD happens.

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

If it does not happen with other asio hosts it could be a reaper bug. Yes it is the RME driver cashing, but reaper causes the crash. Just a thought of course

Vincent, Amsterdam
https://soundcloud.com/thesecretworld
BFpro fs, 2X HDSP9652 ADI-8AE, 2X HDSP9632

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I think it would be a good idea to cross-check with another "major" DAW to exclude DAW problems, e.g., Cubase demo version.

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

ramses wrote:

I think it would be a good idea to cross-check with another "major" DAW to exclude DAW problems, e.g., Cubase demo version.

happens with all DAWs.

And since there are many RME users and specifically even FF800 users (over the past 18 years), I am certain it would have been squashed. As posted in the first post, this has been addressed there to no avail.

this thread, however, has been VERY helpful smile

34

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I am astonished that someone expects switching off a hardware while used (with ongoing data transfers !) will NOT cause a BSOD...

Regards
Matthias Carstens
RME

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

True, I over read that. That is indeed a false expectation.

BR Ramses - UFX III, 12Mic, XTC, ADI-2 Pro FS R BE, RayDAT, X10SRi-F, E5-1680v4, Win10Pro22H2, Cub13

36 (edited by jasonbrianmerrill 2023-06-18 15:48:06)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

I've never had that before - with any interface. It's not a huge deal, I was just wondering if something was wrong with my config or PC.

I've used:

Firepod
Tascam 1608
Focusrite saffire/clarett interfaces. (I've straight up pulled the cord out of the USB port and nothing happened with these!!! hah)

Also, the folks at the Reaper forum who responded to this do not have this issue. So I am sitting here thinking there's something wrong with my setup. Or what if power goes out, and only my PC is connected to the UPS? The UPS would be ineffective since the pc would just BSOD haha. And the RME driver is "transferring data" the entire time like if I'm playing a video in VLC or watching a youtube video. How can I shut it off those times and nothing happens? So the whole time I'm worried if there is something wrong with my config. I am not blaming anyone or anything, just wondering - inquiring. That's all.




Let's not be too astonished now. It's just a question. Everyone is fine, no one has been actually hurt by this thread, and actually I got some great, concise advice!! big_smile




and IM SO GLAD because this interface is my FAVORITE that I've ever had smile


Really, the answer is simple to me:

Don't do that, dumbass

Just don't shut the damned interface off while Reaper is on, or make sure to set reaper to dummy audio if i walk away and forget to shut down before the end of the night.

haha

just making sure there isn't something else wrong with my system. Whatever little niggles I have to deal with are fine, considering how awesome this 19 year old interface is. haha.

So let's chill. I'm not hurting anyone wink

37

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

No one said you do. But the so called 'surprise removal' is best working with USB, with the old FireWire driver less so. But even with USB it could happen that the player software hangs then. At least no BSOD - in most cases.

Regards
Matthias Carstens
RME

38 (edited by jasonbrianmerrill 2023-06-18 16:47:12)

Re: FF800 BSOD on shtdwn, unusable after Sample rate/Buffer length change

well, see that makes PERFECT sense and is a great answer!!!

thank you smile and thank you for all of your hard work. Best audio interface. Nothing else holds up.

Again, thought there was something wrong with my system, so I figured I would try and figure it out. This thread has been immensely helpful! thank you to all of you