Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
What I had to do was FULLY erase everything full sector wipe to get rid of Richocet. I had BSOD, GPU shutting off, PC Shuting off, etc,. after I erased it all (upgraded to win 11 because they probably put more support and testing on it) and I haven't had an issue since the last 4 days.
I'm not saying you have this issue. I would start with smaller steps like reinstalling the game.
I don't think so: the shout down is an hardware problem and very serius, not a software problem.
MW" need a LOT of GPU electric power and you need so have a SUPER PSU (mine is 1200W) and a decent graphic card.
When the game graphic make under stress work the GPU it will ask to the PSU a lot of power, if there is some problem there, is the good time for the motherboard bios to shut down all the system to prevent burn issues
I have a 10k set up my guy and have been building PCs since I was 6 back during CS 1.6 beta. It's definitely the game also like I said it's clearly software. You don't just reinstall the OS and suddenly all your hardware defects stop. Does that make sense to you? Just logically it was clearly a boot sector issue messing with the Kernal I know cause that was most of the errors I was getting. I haven't had a BSOD or crash of any kind. Nor has the GPU had any issues of any kind either since I fixed it.
Kernal level things can really mess with your system. Gaming since DOS brother. I'm about 100% sure this game has some serious defects and a lot of people don't realize their "hardware" issues is just this games invasive rootkit.
I'm not saying his is because this game has so many issues that appear to be hardware from graphical artifacts to shader corruption.
This does the EXACT same thing on CONSOLE that's how you know 100% it's a software issue.
CONSOLE has freezes and crashes as well.
Dude is a question of experience, not a question of how much years you build your comp set up.
You did only 1: your...i did MANY different comps in MANY in MANY years, when working to pay my study. Is an hardware issue for sure.
If you can try using a PSU of one your friend, will be easy for you to try this since you made yourself your comp: then if will be np mean is the PSU.
or buy a voltage and consumption reader with display to interface between the PSU and the motherboard and the various boards. there are many on ebay, so you can get a real measurement of the problem and you will see that when the electricity consumption goes up, the computer shuts down.
No rootkit or Matrix movie software, just a PSU under power issue OR the PSU has failed (it can happen).
But why wouldn't this reoccur during a stress test? The test is made to push the graphics card to the limit.
That doesn't make any sense he said he ran a stress test for 7 mins if it was a PSU issue it would fault and crash. That's how you know it's not a PSU issue. It could be a weak rail sure but unlikely if it won't show in a stress test it's very unlikely.
I've built dozens of PCs so over 35 years experience with PC builds, maintenance and repair on many more. Working IT contract for Fortunate 500s. I might know a little bit.]
I'm not saying IT IS NOT A PSU problem and I suggesting going small to big, but like I said it could purely be the game. Not everyone has a bunch of extra parts sitting around.
It's just weird that putting it under heavy load doesn't cause it to shut down is all I'm saying.
Exactly my point what they are saying is HIGHLY unlikely if your putting it under testing load and it's not shutting off it's likely something else.
I personally have an old program that work under dos (now using a DOS BOX) that do the test ONLy for the graphic card ram (i use it when i buy a new card to be sure it no have a problem to discover when the warranty time is finished)
The solution I gave you is the most statistically probable: try it to remove the doubt