- Nov 5, 2016
- 4
- 0
- 1,520
Hi y'all. So recently (yesterday, at the time of posting) there was an update for a game of which I frequently play, Rainbow Six: Siege. Before the update the game ran fine, even moments before the update was scheduled, literally < 10 minutes before I updated it I had the game running. Post update though, it won't even launch, as soon as the process starts my computer BSODs with the error "Page Fault in Unpaged Area", naturally I googled the problem to learn what it meant and find any potential fixes, most places I looked said that faulty RAM or RAM slots are usually the culprit, in most cases I'd believe that and head straight for that as the source - if I hadn't have literally replaced my motherboard, CPU and RAM with entirely new parts just over a week ago.
So I looked at the other fixes first, including the ones on this site's page, some saying running SFC and Disc Check from the cmd, which I did - SFC came back with corrupted files and repaired them, I thought "great, sorted" and tried again, not the solution.
Some said that it was drivers that needed updating, I did so, nothing.
Some said to modify the paging file, I did, nope.
I tried verifying the game files from inside Steam, nope.
I tried running as admin, nope.
I tried cleaning my registry, nope.
I tried running without any background apps, nope.
I tried checking for windows updates.
I tried running virus scans with MB.
Then I tried fiddling with my RAM just in case, swapping slots and reseating and removing single sticks etc.
Nothing.
I've ran out of ideas, short of the only three things I have left to try, a memory diagnostic, reinstalling the game and reinstalling windows altogether. Which I'm going to reinstall the game overnight I guess?
I've even already reinstalled windows not too long ago because of a real similar BSOD-on-launch problem that randomly started with another Ubisoft game, Ghost Recon Wildlands, with I think a somewhat related error code "memory management" and I vaguely recall getting the "page fault.." one too at some point as well, difference with that one is that I actually narrowed it down to a specific anti cheat EXE that ran in tandem to the game that was broken, ubi support was useless with that one so I don't have much faith in my next correspondence with them. I couldn't fix it in the end, it just randomly started working again a few months later when I decided to try it again, so goodness knows what happened there.
Anyway, if anyone has any out-of-the-box or in-the-box ideas I may have missed, or if anyone out there is having the same problem as me, please let me know. I'm at a loss right now.
System specs -
Mobo: ROG Strix B350-F
CPU: Ryzen 7 1800X 8 Core 3.6Ghz
GPU: AMD Radeon R9 390 8GB VRAM
RAM: 16GB Corsair Vengeance LPX DDR4
So I looked at the other fixes first, including the ones on this site's page, some saying running SFC and Disc Check from the cmd, which I did - SFC came back with corrupted files and repaired them, I thought "great, sorted" and tried again, not the solution.
Some said that it was drivers that needed updating, I did so, nothing.
Some said to modify the paging file, I did, nope.
I tried verifying the game files from inside Steam, nope.
I tried running as admin, nope.
I tried cleaning my registry, nope.
I tried running without any background apps, nope.
I tried checking for windows updates.
I tried running virus scans with MB.
Then I tried fiddling with my RAM just in case, swapping slots and reseating and removing single sticks etc.
Nothing.
I've ran out of ideas, short of the only three things I have left to try, a memory diagnostic, reinstalling the game and reinstalling windows altogether. Which I'm going to reinstall the game overnight I guess?
I've even already reinstalled windows not too long ago because of a real similar BSOD-on-launch problem that randomly started with another Ubisoft game, Ghost Recon Wildlands, with I think a somewhat related error code "memory management" and I vaguely recall getting the "page fault.." one too at some point as well, difference with that one is that I actually narrowed it down to a specific anti cheat EXE that ran in tandem to the game that was broken, ubi support was useless with that one so I don't have much faith in my next correspondence with them. I couldn't fix it in the end, it just randomly started working again a few months later when I decided to try it again, so goodness knows what happened there.
Anyway, if anyone has any out-of-the-box or in-the-box ideas I may have missed, or if anyone out there is having the same problem as me, please let me know. I'm at a loss right now.
System specs -
Mobo: ROG Strix B350-F
CPU: Ryzen 7 1800X 8 Core 3.6Ghz
GPU: AMD Radeon R9 390 8GB VRAM
RAM: 16GB Corsair Vengeance LPX DDR4
Facebook
Twitter
Instagram