BSOD New Computer

[n2rga]

I just got a new Dell
Device name N2RGA_Flex
Processor Intel(R) Core(TM) i5-14400 2.50 GHz
Installed RAM 16.0 GB (15.7 GB usable)
System type 64-bit operating system, x64-based processor

I'm getting BSOD when I hit Off on the Radio software.
latency monitor says:
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 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.

I have the latest updates and Bios was just updated on the first setup yesterday.

[n2rga]

Shut off Network Ethernet, Wireless and Bluetooth
Same error
---------------------------------
_________________________________________________________________________________________________________
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 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.
LatencyMon has been analyzing your system for 0:09:34 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: N2RGA_FLEX
OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)
Hardware: Inspiron 3030, Dell Inc.
BIOS: 1.3.0
CPU: GenuineIntel Intel(R) Core(TM) i5-14400
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 16072 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 2496 MHz
Reported CPU speed (registry): 2496 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): 725.80
Average measured interrupt to process latency (µs): 11.739020

Highest measured interrupt to DPC latency (µs): 720.80
Average measured interrupt to DPC latency (µs): 4.016577


_________________________________________________________________________________________________________
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): 1336.386619
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.035349
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.059798

ISR count (execution time <250 µs): 775665
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 11
ISR count (execution time 1000-2000 µs): 2
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): 1175.887420
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.198941
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.209174

DPC count (execution time <250 µs): 574281
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 11
DPC count (execution time 1000-2000 µs): 1
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 309
Hard pagefault count of hardest hit process: 212
Number of processes hit: 15


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 37.764489
CPU 0 ISR highest execution time (µs): 1336.386619
CPU 0 ISR total execution time (s): 3.044503
CPU 0 ISR count: 424412
CPU 0 DPC highest execution time (µs): 1175.887420
CPU 0 DPC total execution time (s): 10.693623
CPU 0 DPC count: 366698
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 24.004193
CPU 1 ISR highest execution time (µs): 158.378205
CPU 1 ISR total execution time (s): 0.545613
CPU 1 ISR count: 78442
CPU 1 DPC highest execution time (µs): 183.283654
CPU 1 DPC total execution time (s): 1.933428
CPU 1 DPC count: 45071
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 16.799768
CPU 2 ISR highest execution time (µs): 145.961138
CPU 2 ISR total execution time (s): 0.564834
CPU 2 ISR count: 74745
CPU 2 DPC highest execution time (µs): 204.086138
CPU 2 DPC total execution time (s): 1.758248
CPU 2 DPC count: 40826
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 16.289819
CPU 3 ISR highest execution time (µs): 650.520833
CPU 3 ISR total execution time (s): 0.383707
CPU 3 ISR count: 54431
CPU 3 DPC highest execution time (µs): 758.337340
CPU 3 DPC total execution time (s): 1.328255
CPU 3 DPC count: 29001
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 13.115283
CPU 4 ISR highest execution time (µs): 137.735176
CPU 4 ISR total execution time (s): 0.580573
CPU 4 ISR count: 87854
CPU 4 DPC highest execution time (µs): 249.957532
CPU 4 DPC total execution time (s): 2.123888
CPU 4 DPC count: 53953
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 28.923535
CPU 5 ISR highest execution time (µs): 124.789663
CPU 5 ISR total execution time (s): 0.325844
CPU 5 ISR count: 48181
CPU 5 DPC highest execution time (µs): 163.941907
CPU 5 DPC total execution time (s): 1.102596
CPU 5 DPC count: 27058
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 12.428886
CPU 6 ISR highest execution time (µs): 134.311699
CPU 6 ISR total execution time (s): 0.012296
CPU 6 ISR count: 1739
CPU 6 DPC highest execution time (µs): 720.213942
CPU 6 DPC total execution time (s): 0.129848
CPU 6 DPC count: 6027
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 12.482395
CPU 7 ISR highest execution time (µs): 122.075321
CPU 7 ISR total execution time (s): 0.024278
CPU 7 ISR count: 3409
CPU 7 DPC highest execution time (µs): 155.530449
CPU 7 DPC total execution time (s): 0.088423
CPU 7 DPC count: 2558
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 7.411951
CPU 8 ISR highest execution time (µs): 22.149840
CPU 8 ISR total execution time (s): 0.003836
CPU 8 ISR count: 536
CPU 8 DPC highest execution time (µs): 141.082131
CPU 8 DPC total execution time (s): 0.020971
CPU 8 DPC count: 1255
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 7.499788
CPU 9 ISR highest execution time (µs): 53.463542
CPU 9 ISR total execution time (s): 0.012228
CPU 9 ISR count: 1929
CPU 9 DPC highest execution time (µs): 95.195913
CPU 9 DPC total execution time (s): 0.044213
CPU 9 DPC count: 1257
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 6.838561
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): 127.324119
CPU 10 DPC total execution time (s): 0.005439
CPU 10 DPC count: 428
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 7.297840
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): 124.194311
CPU 11 DPC total execution time (s): 0.000765
CPU 11 DPC count: 70
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1.852289
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 62.609776
CPU 12 DPC total execution time (s): 0.000468
CPU 12 DPC count: 47
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1.845089
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 29.478365
CPU 13 DPC total execution time (s): 0.000167
CPU 13 DPC count: 17
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 1.802323
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 140.270833
CPU 14 DPC total execution time (s): 0.000415
CPU 14 DPC count: 17
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 1.286891
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 44.475160
CPU 15 DPC total execution time (s): 0.000133
CPU 15 DPC count: 10
_________________________________________________________________________________________________________

[ke9ns]

I am assuming your running a Flex-3000 or Flex-5000 and so have a 1394 FireWire card in your PC?

DPC latency issues are usually seen as a freeze that occurs on your Pan Display, not a crash.
For latency you can run the FlexRadio.exe program (for FireWire) and change the FireWire operating mode to Safe mode, to see if that fixes or helps?
Also running at a 96khz sample rate can sometimes fix issues, if the FireWire card or bus is having troubles with the higher 192khz speed.

If your getting a BSOD Crash, I would look to the FireWire Card.
I run Win11 x64 Pro with no problems. I use a FireWire PCI-Express TI chip "XIO2213B" IEEE-1394b (the card has both 1394A an 1394B ports even though you only need the A port)
I have a FireWire (left side) link on my website showing all the things related to FireWire issues.

Darrin

[n2rga]

I am assuming your running a Flex-3000 or Flex-5000 and so have a 1394 FireWire card in your PC?

DPC latency issues are usually seen as a freeze that occurs on your Pan Display, not a crash.
For latency you can run the FlexRadio.exe program (for FireWire) and change the FireWire operating mode to Safe mode, to see if that fixes or helps?
Also running at a 96khz sample rate can sometimes fix issues, if the FireWire card or bus is having troubles with the higher 192khz speed.

If your getting a BSOD Crash, I would look to the FireWire Card.
I run Win11 x64 Pro with no problems. I use a FireWire PCI-Express TI chip "XIO2213B" IEEE-1394b (the card has both 1394A an 1394B ports even though you only need the A port)
I have a FireWire (left side) link on my website showing all the things related to FireWire issues.

Darrin

running flex 5000a yes firewire in PCIe slot, the same card as other older computer that took a Dump

I was just listening to the frequency and it just Blue Screened.

I have a Syba SY-PEX30016 3 Port IEEE 1394 Firewire 1394B & 1394A PCIe 1.1 x1 Card TI XIO2213B Chipset Requires Legacy Driver for Windows 8 10
I'm using the port that has the point on it says port 2 on the card. got it from amazon.

[n2rga]

I just followed your instructions in "I have a FireWire (left side) link on my website showing all the things related to FireWire issues"
I do have a conflict.

Screenshot 2024-05-14 131911.png (19.24 KiB) Viewed 19114 times

I tried disabling the firewire and enabling it with no luck even rebooted then tried enabling it with no luck.

[ke9ns]

Have you tried running just the normal FireWire drivers (not the legacy drivers)?
When I moved to a AMD Ryzen CPU and motherboard, I run only the standard TI Firewire driver.

You can try moving the FireWire card to any other PCIe slot (no matter how large the slot is).
Some PCIe slots are actually shared with other devices on the motherboard (like a SSD NVME m.2 slot)

From your CPU, I figured you have a very modern motherboard, so I am surprised to see an IRQ conflict?
Modern motherboards typically use MSI (the Negative IRQ numbers) over IRQ (positive IRQ numbers)

A last resort would be to use MSI_Util_v3 and possibly move the "High def audio controller" from IRQ to MSI. If the device is listed as MSI compatible it still comes with a risk, so make sure to do a full System backup, just in case your forced to do a full system Restore, as some devices dont work under MSI.

Darrin

[n2rga]

Have you tried running just the normal FireWire drivers (not the legacy drivers)?
When I moved to a AMD Ryzen CPU and motherboard, I run only the standard TI Firewire driver.

You can try moving the FireWire card to any other PCIe slot (no matter how large the slot is).
Some PCIe slots are actually shared with other devices on the motherboard (like a SSD NVME m.2 slot)

From your CPU, I figured you have a very modern motherboard, so I am surprised to see an IRQ conflict?
Modern motherboards typically use MSI (the Negative IRQ numbers) over IRQ (positive IRQ numbers)

A last resort would be to use MSI_Util_v3 and possibly move the "High def audio controller" from IRQ to MSI. If the device is listed as MSI compatible it still comes with a risk, so make sure to do a full System backup, just in case your forced to do a full system Restore, as some devices dont work under MSI.

Darrin

Yes Downloaded the drivers you listed for 64bit
Only have one PCIe slot and one PCI.
Everything else is built on the motherboard. It is a cheap $600 Dell Basic computer I just bought for only the radio I don't even have speakers on it.
Thank you for the Info I will try the MSI Utility
While typing on my other computer It just BSO on me.
Thanks

[n2rga]

I think it's fixed I used the MSI_Util_v3 and moved the "High def audio controller" from IRQ to MSI
running good since last post
Thanks

[n2rga]

NOPE!!!!
Now every time I hit off BSOD and reboots
Any other suggestions?

[ke9ns]

Are you still using the legacy driver OR the Texas instruments 1394 OHCI compliant host controller driver?
What Setup->Audio->Primary->Sample rate are you using 92khz or 192khz (try 92khz)?
What Setup->Options->Process Priority level do you have it set to?
When you run the Flexradio.exe program change the operating mode to Safe Mode and see if it makes any difference?
Try launching PowerSDR in Win7 compatibility mode and see if it makes any difference?
Trying a different FireWire Card is the only other thing I can think of?

I have a Similar Dell PC running Win10 at work. I will put a FireWire card into that and see what happens.

[ke9ns]

I did a virgin PowerSDR 2.8 install on an old Dell Optiplex 7010 i5(Intel quad core) running a fully updated Win10 x64 PRO OS.
Its power mode is "high performance".
This unit has 1 half height PCIe x16 slot. I plugged the FireWire card into it.

I used a FireWire PCIexpress card with a TI XIO2200A Chip (Made sure to Plug in the PC power supply to the old style 4 term Molex connector on the card).
Checked device manager to make sure it was running the TI OHCI FireWire driver.
(I found it did have an IRQ conflict with a Intel USB bus device, but I left the conflict to see what was going to happen.)

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)
Setup a new TX profile, and made some appearance changes. (as a test of FireWire stability)
Changed bands and PTT'ed a bunch of times.

Start/Stop and Open/Closed PowerSDR a bunch of times (as a test)

Did a Setup->export to create a backup database.

Running fine with no crashes for freezes. It ran smoother than I expected since this is an old Quad Core.

Darrin

IMG_8736.JPG (4.26 MiB) Viewed 19041 times

IMG_8738.JPG (395.41 KiB) Viewed 19041 times

[n2rga]

Are you still using the legacy driver OR the Texas instruments 1394 OHCI compliant host controller driver?
What Setup->Audio->Primary->Sample rate are you using 92khz or 192khz (try 92khz)?
What Setup->Options->Process Priority level do you have it set to?
When you run the Flexradio.exe program change the operating mode to Safe Mode and see if it makes any difference?
Try launching PowerSDR in Win7 compatibility mode and see if it makes any difference?
Trying a different FireWire Card is the only other thing I can think of?

I have a Similar Dell PC running Win10 at work. I will put a FireWire card into that and see what happens.

No using the legacy driver. says Microsoft 6/21/2006 Version 10.0.22621.2606
using 192khz I tried also 92khz same problem
Setup->Options->Process Priority level = HIGH
Firewire card is the one chipset that's recommended. (Syba SY-PEX30016 3 Port IEEE 1394 Firewire 1394B & 1394A PCIe 1.1 x1 Card TI XIO2213B Chipset)

[n2rga]

I did a virgin PowerSDR 2.8 install on an old Dell Inspiron 7010 (Intel quad core) running a fully updated Win10 x64 PRO OS.
Its power mode is "high performance".
This unit has 1 half height PCIe x16 slot. I plugged the FireWire card into it.

I used a FireWire PCIexpress card with a TI XIO2200A Chip (Made sure to Plug in the PC power supply to the old style 4 term Molex connector on the card).
Checked device manager to make sure it was running the TI OHCI FireWire driver.
(I found it did have an IRQ conflict with a Intel USB bus device, but I left the conflict to see what was going to happen.)

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)
Setup a new TX profile, and made some appearance changes. (as a test of FireWire stability)
Changed bands and PTT'ed a bunch of times.

Start/Stop and Open/Closed PowerSDR a bunch of times (as a test)

Did a Setup->export to create a backup database.

Running fine with no crashes for freezes. It ran smoother than I expected since this is an old Quad Core.

Darrin

IMG_8736.JPG
IMG_8738.JPG

My new computer doesn't have extra connectors so I can't even get an adaptor for the old style. I didn't use it on the old computer seem to run fine.
Should I look for another computer or another Firewire card?
Should I uninstall powerSDR and install it per your instruction?
I just set the compatibility to Windows 7


Mitch
N2RGA

[n2rga]

At the point that I can't use my Radio.
I looked and they sell 15-pin female Sata to 4-pin Female Molex connectors. I ordered one and will get it tomorrow via amazon.
Let's see if that is the problem.
No IRQ conflict anymore.
Power Set to High with Turbo mode on.
All energy saving options set to NONE
Sample rate set to 192khz

I'm at the point where I will have to buy a more expensive computer and see what happens. That power cord is hopefully the key. if not I will reinstall the factory OS and try the install Darrin suggested.
Thanks all for the help I will let you all know

EDITED:
A new thing started happening. It started clicking several times while receiving. it then happened again in a little while and then froze. and stop button, VFO Lock button, and freq readout on receiver 1 started Blicking on and off while frozen. then eventually BSOD!

[ke9ns]

Not sure what you mean by Turbo Mode? That usually a BIOS tweak to overclock the PC. I would not do that as that can lead to instability
Just make sure the Control Panel "Power Options" is set to "High Performance" and that any BIOS feature that is used to save power (which just shuts down CPU cores) should be disabled.

Not sure if you really need the extra power connector, I just always plug them in?

Does your Dell have a virus protection program running (other than the built in Windows Defender?)
If it does, I would completely uninstall it and just use the built in Defender.

I would try uninstalling PowerSDR and FlexRadio programs (then delete all the folders) and reinstall the Full installer with "Win7 compatibility", and use the TI FireWire driver, not the legacy driver, and see what happens?

Its possible that your "Syba SY-PEX30016" card has an issue, but the TI chip is the one I am also using at home.
You could try a different card manufacture with the TI chip? The card I used on the Dell at work was made by SIIG (definitely an old card)

I mainly did the Virgin install on a computer at my work, to make sure I have not done anything to the PowerSDR code that would prevent it from working on a Win10 machine.

[n2rga]

The first thing I did was install powersdr.
I will try the fresh install.
No anti virus
Yes set to high Performance.
Let you know the outcome

[n2rga]

Installed the power adapter keyed the mic unkeyed and froze then blue screened.
And turbo mode is off

Edited
Took out legacy driver
Install Mcrosfts Win 11 driver seems to be working let it run some reboot and turn it on and off, open setup, shut it off a few times and I will see what happens.
I hope I did not jink myself.

[n2rga]

No good keeps BSOD
I don't know what card to get now I have the recommended card from the website. and even the one recommended.
Syba SY-PEX30016 3 Port IEEE 1394 Firewire 1394B & 1394A PCIe 1.1 x1 Card TI XIO2213B Chipset?
should I get a TI XIO2213B Chipset or the one Darrin has TI XIO2200A Chipset?
Or one completely different?

[n2rga]

Ordered another firewire card will have it tommorrow

[n2rga]

Installed New Card same problem BSOD!

Edited:
Still getting BSOD when hitting Stop