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
Will try that. Stuffing my face with Pringle’s. Deep down I knew it was bricked but I just needed to hear it from someone else.
Sorry should have been more clear I got workstations version because I used to work for corporations. I’m kinda Used to business version of windows. Forget home and even other versions exist.
In the home version of 11 do you have VM’s on the task bar? Tbh that’s why I liked the work station version.
Yeah work stations has it on by default. With gigabyte AMD it even works without messing with bios cpu settings so you can OC. Makes it easy to game and work. All the virtual monitors ready to go is nice to.
Games are launching, files aren’t corrupting as soon as they are made atm.
Did a local reinstall then iso. Didn’t bother checking after the local.
Key automatically worked without even asking once setting up windows.
Your solution would probably have saved me a lot of time.
I had to local reinstall windows twice, and once from the cloud. After this last local instal, installed fresh off a none infected pc and appears healthy.
No 0000x ram errors either.
Actually my committed memory is also idling at 10-15% so 15% lower. Was hovering 30-40.
It’s also sleeping on it’s own so that’s a first in a few days.
My brother you will not believe this, it took about 1 hour and bam corruption.
I went into the memory partitions and noticed my SSD’s had around 4 partitions made a piece. Each partition contained 5mb-100mb.
I deleted and wrote over the partitions, and got the iso to work. I was down bad at one point like my pc press key to recognize boot drive wasn’t even working.
Now my issue is the usb stick I used has a funky partition. I can’t delete it because I used my pc to make iso. I may have shot myself in the foot.
The answer to why you have four partitions is: The EFI partition is used to store files used by UEFI. Recovery and restore are used to hold system files needed when performing for example a factory reset & they are exactly like you said from 5 to 100 mb and upwards. Can't say anything about your USB tho but I think if you make a recovery bootable ISO it creates a partition also to be able to boot it.
Edit.
Just as I tought to convert back to regular USB
How to Convert Bootable USB to Normal on Windows?
Press Windows + E keys to open File Explorer. Under "This PC" section, find the bootable USB flash drive.
Right click on the bootable USB flash drive. ...
Choose the file system NTFS or FAT32 and the allocation unit size (as per your need). ...
Finally, hit the "Start" button and format it.
I deleted the partitions. There’s only 2 partitions per SSD, factory for evo. I’m unsure what the other 2 were. I deleted them. I also power cycled and reset my bios/motherboard. Reseated everything in pc physically.
Other than using a possibly dirty usb thing is bone stock now
I also want to mention for the 2 generic partitions you can format them, the 4 I was suspicious of gave no options other than to delete. I deleted and rechecked and they were permanently gone.
Played cs for like an hour, set up all my apps, reactived my key, and did some memory scans, and repairs. Took about an hour to complete. Used powershell and cmd.
I’m a little tired but a quick google search lead to suspicious partitions being a sign of pretty bad malware.
0x8007025d
0xc0000005
Few more I didn’t document.
I’m no expert and clearly so aren’t a lot of people who write these articles. In my little bit of tech exp, it seems more like broken ransomware. Seems the goal here was to corrupt/encrypt files, while bricking a pc during windows reset.
My suspicion is to ram can hold memory as long as there’s power to the motherboard. Wonder if power cycling killed the worm. It was impressive enough to kill my pc during iso install.
Corrupt installation file. If any file in the image is corrupt, this can cause the installation process to be interrupted. Windows Setup may find it impossible to decode some files, thus causing this error.
Bad USB drive. The bootable device itself might be corrupt. There may be an unreadable or bad sector, which means the data stored in that sector cannot be read.
Bad HDD or SSD sector. Just as the issue may lie with your USB device, your internal storage device may also have problems. If there is a bad sector on your drive, Windows Setup may not be able to copy the necessary files to it, leading to errors like this one.
Damaged or Corrupt RAM. One of the advantages of a clean Windows 10 installation is that it doesn’t compete with other programs for memory space. Since there is nothing on the machine, not even an OS, the installation can have all the system memory to itself. However, if the memory is bad or damaged in some way, it can render this benefit useless. In such a scenario, Windows Setup stops and throws the 0x8007025D error.
Second error ending 005
Information is here : https://www.stellarinfo.com/blog/how-to-fix-error-code-0xc0000005-in-windows/amp/
It may have nothing to do with a virus or malware and could and possibly is a issue with one of your pc components listed there. Not everything these days work perfectly all it takes is a bad sector to cause issues.
Memory scan didn’t find a single bad sector. Power shell repaired the damaged drivers.
My wild theory is the worm lived in my ram, power cycling along with reseating the ram killed it. The partitions were the executable code.
I installed my ram, wiped the partitions so far pc is clean.
This took me around 20 hours to think I’ve fixed at this point.
20 f’n hours I’m losing my mind.
This isn’t just regular malware, this is something that creates partitions. This is a full on worm. It literally writes itself, and bloats that .comsurrogate for some reason.
The advice you gave me, I used and it worked for now, the only thing different I did was physically reseat all connections, and the ram power reset bios.
I used your advice initially, I thought it worked but it must have took about an hour for the worm to rewrite itself and corrupt the drivers.
With process I just explained it’s been like 4 hours and pc is doing alright.
Ram doesn’t hold memory unless there’s power.
I kept my pc on and a notepad up to see if it was RAT assuming not.