Game won't launch after hours of playing

[JacobHarvest]

I've played this game for over 20hrs now. I just got to the end of the dreamland quest when the game closed and error report log popping up. Now the game won't launch at all. I've tried restarting the system and verifying the files.

[No_SuRReNDeR001*]

I am having the same issue lvl 26 now my game wont launch - check if your CUDA gpu is eneable in 3d settings in nvidia CP - for me my rtx8000 seems to have a prob here... I guess my 6000 dollar card is failing- fml

[The Gavinator]

I'm literally having the exact same problem. haven't had a single problem my entire playthrough and now my game is completely bricked. rtx 4080 super

EDIT: I fixed it! I don't know if this will work for everyone, but on my NVIDIA App, I went to drivers, reinstall latest driver, custom installation, and I checked the clean install option and I was able to load Oblivion and complete the quest without crashing. I'm reinstalling the driver update now

[Cinemax]

Try renaming the UPIPELINECACHE. It's in the games saved folder.

[The Gavinator]

Originally posted by Cinemax:

Try renaming the UPIPELINECACHE. It's in the games saved folder.

rename it to what? anything specific or just anything at all

[Cinemax]

Originally posted by The Gavinator:

Originally posted by Cinemax:

Try renaming the UPIPELINECACHE. It's in the games saved folder.

rename it to what? anything specific or just anything at all

Anything, just to preserve the file but prevent the game from accessing it.

[The Gavinator]

Originally posted by Cinemax:

Originally posted by The Gavinator:

rename it to what? anything specific or just anything at all

Anything, just to preserve the file but prevent the game from accessing it.

I tried renaming it and it didn't do anything. I also removed it from the file and threw it onto my desktop and that didn't do anything either

[MoaningMurdle]

Originally posted by The Gavinator:

I'm literally having the exact same problem. haven't had a single problem my entire playthrough and now my game is completely bricked. rtx 4080 super

i have a 3070 and ran 56 hours on this game and now i cant even get the main menu load screen just a black screen and crash report...

[The Gavinator]

Originally posted by MoaningMurdle:

Originally posted by The Gavinator:

I'm literally having the exact same problem. haven't had a single problem my entire playthrough and now my game is completely bricked. rtx 4080 super

i have a 3070 and ran 56 hours on this game and now i cant even get the main menu load screen just a black screen and crash report...

did it happen during that dream quest?

[Cinemax]

Originally posted by The Gavinator:

Originally posted by Cinemax:

Anything, just to preserve the file but prevent the game from accessing it.

I tried renaming it and it didn't do anything. I also removed it from the file and threw it onto my desktop and that didn't do anything either

Okay, this would be a lot easier to do if I actually had the problem so I could troubleshoot it myself but...

Reasonable to assume the game is reading a file it doesn't like. Most of its writes are in that saved folder. Renaming it to saved.bak would force it to recreate. If it launches, then something in that folder is the culprit, bring over a recent save to the recreated folder and leave the rest behind.

Of course, it could be something else, like corrupt shader cache. To find out exactly what it is... well probably procmon64 is the best bet. In procmon, you would stop capture (CTRL-E), clear (CTRL-X), start capture (CTRL-E) Then quickly open the game. After it crashes stop capture (CTRL-E), and set a filter (CTRL-L) to "Process Name is Oblivionremastered.exe". Scroll down to the end of the capture and see what the last actions the game took before it crashed. If it's reading a file or registry hive, that is likely the culprit.

[LeftPaw]

I just bought the game and it crashed on creating my character. Looks like a refund job.
Seems like it was steam overlay that was causing the crash.

[The Gavinator]

Originally posted by Cinemax:

Originally posted by The Gavinator:

I tried renaming it and it didn't do anything. I also removed it from the file and threw it onto my desktop and that didn't do anything either

Okay, this would be a lot easier to do if I actually had the problem so I could troubleshoot it myself but...

Reasonable to assume the game is reading a file it doesn't like. Most of its writes are in that saved folder. Renaming it to saved.bak would force it to recreate. If it launches, then something in that folder is the culprit, bring over a recent save to the recreated folder and leave the rest behind.

Of course, it could be something else, like corrupt shader cache. To find out exactly what it is... well probably procmon64 is the best bet. In procmon, you would stop capture (CTRL-E), clear (CTRL-X), start capture (CTRL-E) Then quickly open the game. After it crashes stop capture (CTRL-E), and set a filter (CTRL-L) to "Process Name is Oblivionremastered.exe". Scroll down to the end of the capture and see what the last actions the game took before it crashed. If it's reading a file or registry hive, that is likely the culprit.

I used the event properties and it said the faulting application name is OblivionRemastered-Win64-Shipping.exe and the faulting module name is nvwgf2umx.dll so I tried renaming/removing that file but it needs special permissions to allow it to be modified or removed, and there is no option to do that. I would like to think that's the culprit but it seems I can't do anything about it

[Cinemax]

Originally posted by The Gavinator:

Originally posted by Cinemax:

Okay, this would be a lot easier to do if I actually had the problem so I could troubleshoot it myself but...

Reasonable to assume the game is reading a file it doesn't like. Most of its writes are in that saved folder. Renaming it to saved.bak would force it to recreate. If it launches, then something in that folder is the culprit, bring over a recent save to the recreated folder and leave the rest behind.

Of course, it could be something else, like corrupt shader cache. To find out exactly what it is... well probably procmon64 is the best bet. In procmon, you would stop capture (CTRL-E), clear (CTRL-X), start capture (CTRL-E) Then quickly open the game. After it crashes stop capture (CTRL-E), and set a filter (CTRL-L) to "Process Name is Oblivionremastered.exe". Scroll down to the end of the capture and see what the last actions the game took before it crashed. If it's reading a file or registry hive, that is likely the culprit.

I used the event properties and it said the faulting application name is OblivionRemastered-Win64-Shipping.exe and the faulting module name is nvwgf2umx.dll so I tried renaming/removing that file but it needs special permissions to allow it to be modified or removed, and there is no option to do that. I would like to think that's the culprit but it seems I can't do anything about it

You can't remove it because it's constantly running in memory because it's a core library for your card... Nvidia right? You'll need a specialized removal utility to uninstall it, for example:
https://www.wagnardsoft.com/content/Download-Display-Driver-Uninstaller-DDU-18111
Once it's eliminated and rebooted you won't necessarily want to reinstall the same driver cause that may introduce the same problem. YMMV but I am on a 4080 Super and with my somewhat out-of-date driver (being 08/24) I only get crashes once every ~6 hours (not counting the crashes when I hit quicksave, ♥♥♥♥♥♥♥ those are annoying). I am running 560.81:
https://www.nvidia.com/en-us/drivers/details/230595/
Not that this version is the be-all-end-all, there's room for experimentation. The drivers that are marked as purpose-made for this game seem to ♥♥♥♥ it up by all accounts, coupled with the auto-updates from what is now branded the "Nvidia App" (uncheck the option to install that ♥♥♥♥♥♥♥♥, of course) leads us to the present mess. So I think testing an older driver is a good next step.

[The Gavinator]

Originally posted by Cinemax:

Originally posted by The Gavinator:

I used the event properties and it said the faulting application name is OblivionRemastered-Win64-Shipping.exe and the faulting module name is nvwgf2umx.dll so I tried renaming/removing that file but it needs special permissions to allow it to be modified or removed, and there is no option to do that. I would like to think that's the culprit but it seems I can't do anything about it

You can't remove it because it's constantly running in memory because it's a core library for your card... Nvidia right? You'll need a specialized removal utility to uninstall it, for example:
https://www.wagnardsoft.com/content/Download-Display-Driver-Uninstaller-DDU-18111
Once it's eliminated and rebooted you won't necessarily want to reinstall the same driver cause that may introduce the same problem. YMMV but I am on a 4080 Super and with my somewhat out-of-date driver (being 08/24) I only get crashes once every ~6 hours (not counting the crashes when I hit quicksave, ♥♥♥♥♥♥♥ those are annoying). I am running 560.81:
https://www.nvidia.com/en-us/drivers/details/230595/
Not that this version is the be-all-end-all, there's room for experimentation. The drivers that are marked as purpose-made for this game seem to ♥♥♥♥ it up by all accounts, coupled with the auto-updates from what is now branded the "Nvidia App" (uncheck the option to install that ♥♥♥♥♥♥♥♥, of course) leads us to the present mess. So I think testing an older driver is a good next step.

I'll definitely give that a try. do you think it'll be fixed in a driver or game update? it would give me a reason to play one of my other backlogged games in the meantime

[Cinemax]

Originally posted by The Gavinator:

Originally posted by Cinemax:

You can't remove it because it's constantly running in memory because it's a core library for your card... Nvidia right? You'll need a specialized removal utility to uninstall it, for example:
https://www.wagnardsoft.com/content/Download-Display-Driver-Uninstaller-DDU-18111
Once it's eliminated and rebooted you won't necessarily want to reinstall the same driver cause that may introduce the same problem. YMMV but I am on a 4080 Super and with my somewhat out-of-date driver (being 08/24) I only get crashes once every ~6 hours (not counting the crashes when I hit quicksave, ♥♥♥♥♥♥♥ those are annoying). I am running 560.81:
https://www.nvidia.com/en-us/drivers/details/230595/
Not that this version is the be-all-end-all, there's room for experimentation. The drivers that are marked as purpose-made for this game seem to ♥♥♥♥ it up by all accounts, coupled with the auto-updates from what is now branded the "Nvidia App" (uncheck the option to install that ♥♥♥♥♥♥♥♥, of course) leads us to the present mess. So I think testing an older driver is a good next step.

I'll definitely give that a try. do you think it'll be fixed in a driver or game update? it would give me a reason to play one of my other backlogged games in the meantime

While either side could potentially release a fix the issue does seem to be on the driver side. Nvidia are also more likely to be first to release a fix since they have far more resources than Virtuos. Either way I'd assume the issue will be high priority for both parties.

[Ianatom]

Having the exact same issue.
Thought it would just be a funny bug / crash, I'd be able to get back into the game after this happened, but nada.
The game just won't launch now.

I was using 7 mods that subtly change the difficulty and some armor settings through Vortex and everything worked fine up until I finished the dialogue with Henantier to exit his dreamworld.

I've tried:
-Disabling + uninstalling all mods + just uninstalling vortex completely
-Backing up + deleting sl.pcl.dll from the install folder
-Giving the game all permissions in firewall
-Launching the game as admin
-Repairing game files through Steam
-Backing up + Deleting the UPIPIELINECACHE file in the Saved folder
-Running the game in compatibility mode (Windows 7)

-And this one's a doozie: I've also tried reinstalling my current drivers through the Nvidia App and gave myself a light heart attack because my display went to black and wouldn't turn up again. After 10 minutes of waiting for my GPU to respond, it didn't turn back on again, so I hard reset my PC and thankfully, everything reverted back to before I tried reinstalling the drivers.
This one's especially strange, since my GPU drivers updated normally every time before this one problem appeared.

Every application and game is running fine, but Oblivion Remastered still just refuses to launch after all of these failed fixes.

System specs, if anyone will be wondering / willing to help:
AMD Ryzen 7 7700 5,3GHz AM5
32GB DDR5 ram
GeForce RTX 4070 Ti Super

I'd also like to mention that I'm currently running the game from a hard drive instead of an ssd, but I suspect that shouldn't make a difference.

I'm currently reinstalling the entire game.


EDIT: I reinstalled the game and it still won't launch, signifying a problem with the save file / shaders on that part of my save (I presume)