Screenshot in Windows 10 after installing the NVIDIA GeForce GTX 760 graphics card driver using live stacking in SharpCa

[turfpit]

That looks a good place to start. Disabling the graphics card acceleration is sensible as it simplifies any troubleshooting. RAW 16 is best for deep sky but consider using RAW 8 for planetary (faster fps).

Good luck.

Dave

[pastorgalactico]

OK thanks.

[pastorgalactico]

Hello;
Tested tonight and it seems to be working well.
M5 with 10 minutes of live stacking and USB traffic at 80%, without losing any frames.

M5.jpg (462.18 KiB) Viewed 799 times

[turfpit]

Glad it is working for you now.

Dave

[pastorgalactico]

pastorgalactico:
Hi
It happened to me again, and it seemed to be working fine when I allocated 8000MB of RAM to both the frame rate cache and live stacking, since they recommend using half the PC's RAM.
Last night it seemed to be working fine until SharpCap started freezing, and then I got the blue screen with this error.

Screenshot_2026-08-19-15-48-02-466_com.whatsapp.jpg (655.71 KiB) Viewed 741 times

So what I did was completely uninstall the Nvidia driver, the most recent one, and install an older, more stable one. I installed version 472.12 and we'll see what happens. Before, without having installed the latest driver, I never got these blue screens, and it only started after I installed the latest one.
I'll try it again tonight with the older, more stable Nvidia GTX 760 driver and see what happens. I used to use live stacking with regular SharpCap and this never happened to me, even though I was using the same graphics card but without the latest driver.
I'll keep you posted.
Regards

[admin]

Hi,

Blue screen crashes of Windows are always caused by an underlying bug in either the Windows operating system itself or in a driver of one sort or another. If the code of both the Windows operating system and drivers was bug free then blue screens would only happen in response to hardware errors (for instance memory contents changing when they shouldn't or the processor miscalculating something).

It's quite possible that applications like SharpCap or games or other applications are the things that set up the conditions for the bug in the driver or operating system to show up - less memory available, or being asked to draw something particularly complex on the screen, but it's important to remember that if the application is trying to do something that is legitimate then the operating system/driver should cope with it and if the application tries to do something illegitimate (asking for too much memory for instance) then the operating system should refuse the request - possibly crashing the application but with no blue screen.

cheers,

Robin

[pastorgalactico]

Hi,
Since I'm only going to use SharpCap with live stacking for now, could I allocate more memory (14 GB) to live stacking and only 2 GB to the frame rate cache?

Also, I only get this error when using SharpCap Pro. I still need to try the new 472.12 driver, which I was told was more stable.

I also don't have much of an idea of ​​how much RAM I might need or use for live stacking with the Uranus C, and considering that so far I haven't seen it drop any frames on the SSD where it records.

You'll have to tell me how much RAM I would need to use out of the 32 GB the PC has.

The other night, when I got the error, SharpCap slowed down until it froze, and then the dreaded blue screen appeared.

I only saw that screen when using SharpCap Pro.
Before now, I was already doing live stacking with the standard SharpCap, and I only had 2 GB of RAM, even though the PC had 32 GB. I never got that blue screen, nor did SharpCap ever slow down.
There shouldn't be any problems with SharpCap that we don't know about, right?
Regards.

[turfpit]

Since I'm only going to use SharpCap with live stacking for now, could I allocate more memory (14 GB) to live stacking and only 2 GB to the frame rate cache?

My capture laptop runs Sharpcap Pro. It has 16Gb of memory, configured as below. I don't do Live Stacking, my interest is lunar, hence I have configured memory usage to favour the high speed frame cache. I operate at 54 to 100 fps with a 1920x1200 capture area over USB3.

SharpCap_memory_config.JPG (46.76 KiB) Viewed 698 times

If you were using Live Stacking then set the slider as far over as it will go, leaving the high speed cache at default. As you are stacking deep sky then the exposures will be longer.

You seem to have made 2 changes - SharpCap product from free to pro and video driver version. To help with debugging, make only one change then test that configuration. You could test in daylight against a tree for example. Make one change and retest. Eventually you should have a stable combination. With video drivers I remove driver, reboot, install driver to ensure a clean install. Hopefully you have both versions of the driver.

For testing, I have a Cmount CCTV lens, something like
https://www.amazon.co.uk/Camera-CCTV-De ... 591&sr=8-6

which screws directly into the camera and is good enough for testing in daylight.

Dave

[pastorgalactico]

Hi;
I'll leave it like this and try it tonight if the weather allows.
Regards
They recommend half the system's RAM, and you have more than half of your system's RAM.

capturada.jpg.jpg (112.94 KiB) Viewed 695 times

[pastorgalactico]

Hi;

I've been testing it for a while and it seems to be working well.
I've attached screenshots showing the saved and lost frames.
Let me know if this is okay.

Regards

capturada4.jpg (196.73 KiB) Viewed 677 times

capturada3.jpg (217.41 KiB) Viewed 677 times

capturada1.jpg (196.98 KiB) Viewed 677 times

M17.jpg (639.29 KiB) Viewed 677 times