Original Post — Direct link

Hey guys, I've ran into an error that I really can't diagnose for the life of me. I've tried a litany of different approaches which I'll outline in a second.

Rainbow Six Extraction seems to be able to run fine for widely varying amounts of time. I've even had a session with no issues.

But most of the time, at seemingly random points in the game - my monitor will turn blank. I will then get a "no signal received" message. The game audio doesn't always crash, and background audio such as music (if any) doesn't really crash either. The computer stays on for all intents and purposes. I just can't seem to get any signal out of my graphics card. It's as if my graphics card is just giving up. And it's an okay card.

Naturally, the first conclusion you would draw would be that this is a graphics card issue, so I did some digging around. I investigated it for overheating, but found that it didn't really get anywhere near a critical level when gaming in 4k with ultra settings.

Then I checked out my FPS when in-game. It was over 1000 in the menus (??). So I turned on the FPS limiter to 75 fps in the config, and whilst my computer no longer sounded like a vacuum cleaner in the in-game menus, the blank screen error still remained.

I tried undervolting my GPU - no change.

I ensured all my drivers and operating system were perfectly up to date - no change.

I am launching via UBISOFT CONNECT.

The problem persists, even when in a windowed mode with a lowered resolution.


My Specs:

  • Windows 11 Home
  • Intel® Core™ i7-10700K (3.8 GHz base frequency, up to 5.1 GHz with Intel® Turbo Boost Technology, 16 MB L3 cache, 8 cores)
  • HyperX® 16 GB DDR4-3200 XMP RGB MHz RAM (2 x 8 GB)
  • 512 GB WD Black PCIe® NVMe™ TLC M.2 SSD + 2 TB 7200 rpm SATA HDD
  • NVIDIA® GeForce RTX™ 3080 (10 GB GDDR6X dedicated) with LHR


My Monitor:

4k Samsung LU32J590UQRXXU

Any ideas?





over 2 years ago - Ubi-Mushy - Direct link

@daecron Hey there! Sorry to hear you ran into this issue, but thanks for the update!

@kogami00 Could you test if rolling back your drivers fixes things for you? If not, please go ahead and complete our basic PC troubleshooting and update this thread with your results.