Dell XPS Crashing Again Texas Instruments Firewire Card

[n2rga]

Dell XPS Crashing Again Texas Instruments Firewire Card.
I had a problem with the Firewire card with a via chipset card and it worked fine until a month ago.
I reinstalled Windows 11 Home by wiping the old install.
I reinstalled PowerSDR as recommended before by Darrin

" Downloaded the Full and Incremental installers from my website.
Set "Compatibility" of the Full installer to "Window 7"

Installed Full Installer (which also installs the FireWire drivers for PowerSDR). Reboot.
Installed Incremental install.

Set the Compatibility of the PowerSDR (Desktop icon) to "Windows 7" and "run as Admin" (so I can use it to sync the PC clock)

Ran in DEMO mode first (so FireWire is ignored) just to make sure everything was OK
Then powered up The Flex-5000 and launched PowerSDR.

Made a bunch of adjustments to the settings.
Set the Primary Sample Rate to 192khz (because the default is 96khz because some FireWire cards have trouble with 192khz)"

I also followed the how-to https://ke9ns.com/flexpage.html#firewire I did everything
I purchased another card and it did the same, but I didn't realize it was the same chipset. so it BSOD also only with the power off button.
Went back to Amazon yesterday and bought a Syba SY-PEX30016 3 Port IEEE 1394 Firewire with a TI XIO2213B Chipset and installed the legacy Driver.

I hit Aply or ok in Device Manager BSOD. Hit off BSOD. Hit Save Profile BSOD. Try to increase PFN Crash Dely and try to save BSOD.
Running 308 of PowerSDR.
Anyone Have this card and have it running ok?
How did you fix your BSOD?

[n2rga]

I did a latencyMon test and got this:

Conclusion: Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. Also one or more ISR routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

[n2rga]

anyone?
Not sure how to fix latency findings

Downloaded the Legacey Firewire Driver from Darrin's website and Same happened

[py5vb]

Some radio amateurs are giving up on their FLEX3000/FLEX5000 because they are unable to use it stably on new PCs with Windows 10/11.
I don't know how Darrin manages to use PowerSDR 24/7 without experiencing BSOD with Windows 11. I and many others have not had success, with the most diverse hardware configurations on the desktop, the BSOD appears quite frequently. We used all the tips available on Darrin's website.
If you use Windows 10 in MBR format of SSD/HD partition, it is quite stable regarding BSOD, but sometimes the PowerSDR screen closes abruptly when changing bands or quickly changing the QRG, this rarely happens.
Now, if you want to use PowerSDR with 100% reliability without experiencing absolutely any setbacks, use Windows 7 Ultimate. It's old and some current PCs don't allow you to install Windows 7. I dedicated a 3rd generation Intel i7 PC with 4G of RAM and 128G SSD exclusively for PowerSDR and I'm extremely satisfied and using my FLEX5000A/PowerSDR 2.8.309 all the time.
73, Villas - PY5VB

[n2rga]

Some radio amateurs are giving up on their FLEX3000/FLEX5000 because they are unable to use it stably on new PCs with Windows 10/11.
I don't know how Darrin manages to use PowerSDR 24/7 without experiencing BSOD with Windows 11. I and many others have not had success, with the most diverse hardware configurations on the desktop, the BSOD appears quite frequently. We used all the tips available on Darrin's website.
If you use Windows 10 in MBR format of SSD/HD partition, it is quite stable regarding BSOD, but sometimes the PowerSDR screen closes abruptly when changing bands or quickly changing the QRG, this rarely happens.
Now, if you want to use PowerSDR with 100% reliability without experiencing absolutely any setbacks, use Windows 7 Ultimate. It's old and some current PCs don't allow you to install Windows 7. I dedicated a 3rd generation Intel i7 PC with 4G of RAM and 128G SSD exclusively for PowerSDR and I'm extremely satisfied and using my FLEX5000A/PowerSDR 2.8.309 all the time.
73, Villas - PY5VB

Installing win 7 on this PC is not posable.
I had it running for a long time then all of a sudden BOOM no good. Dam windows updates

[ke9ns]

You can try upping the PFN delay value and see if that helps?


Darrin

[n2rga]

You can try upping the PFN delay value and see if that helps?


Darrin

I put up to 1500 saved to my profile. hit ok and crashed

[n2rga]

You can try upping the PFN delay value and see if that helps?


Darrin

I tried it again and it took this time and didn't crash. going to test through out the day.
What is the highest setting I can go to?
thanks

[n2rga]

You can try upping the PFN delay value and see if that helps?


Darrin

@Darrin
Didn't work keeps crashing. I have PRN Delay at Max 1500.

[ke9ns]

One thing to try would be to disable the Win11 defender real-time protection. See if PowerSDR will run with defender real-time turned off?
And make sure Windows core isolation->memory integrity is OFF.
(Just remember that the real-time defender will turn back on every time you turn your PC OFF/ON)
Otherwise you can try a firewire card with a VIA chip instead of a TI
I have had people swap cards to find one chip works much better than another.
In my past, I have found some motherboards worked only with VIA FireWire chips, and others only with TI chips.

Running PowerSDR on my Lenovo Ryzen laptop, i tried a few different PCIe cards (see image below)
I found 1 card that was causing PFN crashes, and 1 that has no issues.
Under win11 you can no longer use the legacy FireWire drivers because Win11 requires a signed driver (which the version i was able to find is not signed).

IMG_9786.JPG (4.45 MiB) Viewed 7282 times

Darrin

[n2rga]

One thing to try would be to disable the Win11 defender real-time protection. See if PowerSDR will run with defender real-time turned off?
And make sure Windows core isolation->memory integrity is OFF.
(Just remember that the real-time defender will turn back on every time you turn your PC OFF/ON)
Otherwise you can try a firewire card with a VIA chip instead of a TI
I have had people swap cards to find one chip works much better than another.
In my past, I have found some motherboards worked only with VIA FireWire chips, and others only with TI chips.

Running PowerSDR on my Lenovo Ryzen laptop, i tried a few different PCIe cards (see image below)
I found 1 card that was causing PFN crashes, and 1 that has no issues.
Under win11 you can no longer use the legacy FireWire drivers because Win11 requires a signed driver (which the version i was able to find is not signed).
IMG_9786.JPG
Darrin

Nice Yes I have both Card Via and TI both are doing the same. The Via worked fine for months and about 2 months ago after a windows update BAM BSOD every time I shut down.
I re-installed and still no good.
I have the Legacy Driver on it.
And yes Defender is shut down

[n2rga]

@Darrin
I re-read your reply above and thought I had Windows core isolation->memory integrity is OFF

It's off now and BAM! I will spit up into the air and say it's fixed. I will test it later today and verify it. I turned it off about 4 times and wrote AM and SSB settings to DB 4 times and pressed ok went off then on - no BSOD Yaaaaa!

Thank You

[ke9ns]

Cross your fingers. If it does happen again, try turning off the real-time defender to see that helps or not?

Darrin

[n2rga]

I turned it all off in Defender and It did happen again.

[ke9ns]

The only thing I can think of is If your using a TI chip FireWire, try using a VIA chip FireWire its claims to be Win10 or 11 compatible?

[n2rga]

I got so frustrated that I put it on the side for a while and thought about selling the 5000a.
But I hate to give up.

Recap:
I have the VI chipset card installed getting the same Blue screen Of Death as the TI card that I returned to Amazon. when pressing the Stop button or switching to another profile.
I set the PFN Crash Setting to 1500 and still doing it.
I ran the View Reliability History I read in another BSOD post. this is what I got

Code: Select all

Problem signature
Problem Event Name:	BlueScreen
Code:	4e
Parameter 1:	9a
Parameter 2:	3a6b72
Parameter 3:	6
Parameter 4:	2
OS version:	10_0_26100
Service Pack:	0_0
Product:	768_1
OS Version:	10.0.26100.2.0.0.768.101
Locale ID:	1033

Files that help describe the problem
022825-52093-01.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
WERInternalRequest.xml

[n2rga]

Here are the files that it mentioned:

[ke9ns]

From the crash data, your running Win10?
And it says your running the 1394 Legacy driver?

I have noticed that some cards crash with Legacy driver, and some the "Legacy" fixes them.

So if you just changed cards, you may want to try all available drivers

This also assumes that the IRQ for the new card is still OK and not shared with something else.

Also, I once had a laptop with FireWire, and PowerSDR would periodically crash. I ended up disabling the wi-fi in the laptop and everything cleared up.
I have not idea why.
So if your using wi-fi from your desktop, temporarily "disable" the hardware wi-fi device and see if you notice anything improve?

The other thing to try is to lower the setup->Audio->Primary->Sample Rate to 48khz and see if it improves?

Im just thowing out anything I can think of, since I am at a loss.

I dont have the source code for the FireWire part of PowerSDR, so I can look at software code to fix it.

Darrin

[n2rga]

Thank So much for your help I will try those

[n2rga]

when I try to change setup->Audio->Primary->Sample Rate to 48khz it blue screens as soon as I switch it, before saving