No, no updates have been installed.Ah, okay. Hopefully CDPR can figure it out.
New computer = new quirks. Old computer = new problems, so new quirks.
Did you double-check that the Windows Updates released in Jan. and Feb. of 2026 are not installed / uninstalled?
(Myself personally, I think it's more to do with why Gwent is not appearing on the market.)
It's unfortunate... I don't remember having any problems with other games (at least they were solvable) and I didn't have blue screens...
That's the first I'm hearing of blue screens. Did you take down the error code? That would be the most significant thing brought up here.
A BSoD is the result of either system corruption at the kernel level or a hardware fault, which could be lots of different things.
One thing is certain: there's something on your system that is not working the way it should be. Are you seeing any other issues with other programs? How often has the blue screen crash occurred? If you didn't take down the actual error code, do you at least remember if it was the same code each time or different codes?
_______________
Two things to run:
1.) Find Command Prompt, R-click on it, and select "Run as administrator." Then, type the following exactly:
sfc /scannow
Note the space between "sfc" and "/". Let that scan run and do not interrupt it for any reason, even if it seems to be frozen. (It's not.) It will scan your file system and fix any errors it finds.
2.) Restart your system after the scan above. At the desktop select "Run..." (Win-R) and type:
mdsched.exe
Select "Check for problems the next time I start," and restart the PC. Again, don't interrupt that scan.
Possibilities:
A BSoD is the result of either system corruption at the kernel level or a hardware fault, which could be lots of different things.
One thing is certain: there's something on your system that is not working the way it should be. Are you seeing any other issues with other programs? How often has the blue screen crash occurred? If you didn't take down the actual error code, do you at least remember if it was the same code each time or different codes?
_______________
Two things to run:
1.) Find Command Prompt, R-click on it, and select "Run as administrator." Then, type the following exactly:
sfc /scannow
Note the space between "sfc" and "/". Let that scan run and do not interrupt it for any reason, even if it seems to be frozen. (It's not.) It will scan your file system and fix any errors it finds.
2.) Restart your system after the scan above. At the desktop select "Run..." (Win-R) and type:
mdsched.exe
Select "Check for problems the next time I start," and restart the PC. Again, don't interrupt that scan.
Possibilities:
- Damaged master file table (corrupted data, damaged sectors on an HDD/SSD, etc.) Not bad, and PCs can normally work around it.
- Bad RAM sectors. Happens with older RAM or chips that have been damaged in a power surge or something. Again, not too bad, and Windows can normally just work around the bad sectors.
- Corrupted Windows installation. Could be anything from damage caused by a power-surge, to a virus, to not having enough space free for storage and swap file. Might be easy/automatic to fix...or it might be something that does require a complete OS wipe and reinstallation.
- Bad PSU. Inconsistent current from the PSU can result in all sorts of craziness, and it can be difficult to detect as the source of the problem. But, good news, it's one of the least-expensive fixes (especially if you're able to replace it yourself.)
- Damaged RAM, GPU/VRAM, CPU, motherboard, modem, sound card, etc. Worst-case scenario. This type of thing might be as simple as pulling out or replacing a couple sticks of RAM...or it might be new PC time.
No problems have been identified. And I told you, I didn't see any blue screens, otherwise I would have noticed it. I also don't leave my PC on if I leave for a long time, so this couldn't have happened without my knowledge.
Because the support service told me that my reports from msinfo32 allegedly had blue screens of death... I've attached a screenshot of this message.
Ah, ok -- so you were totally unaware of the blue screens? You have no idea how many times it happened or what the errors were? (That's kind of surprising. Especially if it happened more than once, you never received anything like a, "Windows failed to shut down properly," warning or something similar when you finally interacted with it again?)
Same difference, though. The msinfo won't lie -- it's direct records of events recorded by your PC. The steps above would be good steps to start figuring out what's causing it.
1.) File system scan detecting and repairing errors (which will be captured in detail in log files) = Good sign. There might be simple corruption of Windows files that can be repaired.
2.) Memory scan detecting bad RAM sectors = Meh, not the end of the world. The existing sticks will probably still function, but replacing at least one matched pair of system RAM is eventually going to be needed.
If both scans come back completely clean...that's actually bad news. That means there's serious OS/BIOS/UEFI/firmware problems or that you have a hardware issue. I'd definitely try a clean drive wipe and reinstallation of the OS at that point...but to be honest, multiple BSoDs within a short time frame are usually indicative of something hardware related. (Usually, not definitely.)
Well, maybe tomorrow I'll reinstall Windows, let's see what happens.
I think that's a fair idea. I would also wipe the drive and create a new User Account, ensuring it is an administrator account. Importantly, keep eyes on the system in the months to come for any potential restarts, hangs, or crashes. Whenever that happens, there should be a very visible indicator on the screen, whether a message window or an alert in the lower-right notifications area, even if you're not present for the actual BSoD.
Of course, there is no point in reinstalling Windows without cleaning the disk.
Ja.
Just throwing out a few more things, assuming they're probably not needed, but just avoiding any future complications:
1.) Don't format SSDs. HDDs, yes -- do reformat. Just remove the data from the SSDs.
2.) If the drives have been partitioned in any way, remove the partition. If you want a multi-boot system for Windows / Mac / Linux, plan on getting completely different drives for each OS environment.
3.) Once reinstalled, if there's any instability, try going into your BIOS/UEFI and disabling any CPU "boost" technology. Overdrive, TurboBoost, etc. Turn it ALL off.
XMP for RAM is fine (provided you know the actual RAM speed and you have identical chips, whether 2 or 4,) but kill all the CPU stuff.
Why shouldn't I format the ssd? I only have ssd, I don't have hdd
Last edited:
Unnecessary. Solid state does not ever need to be reformatted or defragged. (Unless you're intentionally switching between NTFS and Fat32, which won't be needed for anything a typical user would do.) Doing so just writes needlessly to all sectors, decreasing the lifespan of the drive.
Just use the "Quick format/wipe" option or whatever the manufacturer provides: secure erase tool, clean OS installation tool, etc.
Not yet, I have more important things to do right now. Unfortunately, there is no time to reinstall Windows yet.
I know that feeling very well. (Presently on a laptop from 2011. Fun times.)
I do not know how, but the problem disappeared by itself, I started the game again, and redlauncher demanded that I log in to my account from the browser (before that, the login was done automatically), I logged in and the problem disappeared!
Since the last moment of activity on the forum, I have not taken any action to solve the problem, I have not reinstalled Windows, I just accepted the problem, and now it has disappeared on its own.
I do not know if it affected me, but 2 days ago I was playing cyberpunk, the problem was still there. Yesterday, another person joined my family on steam who also has this game, and today I launch the game and everything works as it should. If this affected the solution to the problem, I can't figure out how, because I didn't even launch the copy of the game that the new family member has.
This...is not unheard of. It's...it's what computers...do...sometimes.
At least the problem is gone! For now. Hooray...!