Crashing non stop after the patch (0xc0000005) and (0x80000003)

[DrExK]

As above. I can't play for longer than 5 minutes. It doesn't help that the loading design is so flaw - you've to start a new game before you can load a save!

Any method to circumvent this? I've already set the graphics setting to low (even though I've a 1070 card).

[Karas]

Originally posted by Tom Cruise:

Originally posted by TBombadil:

Did you add the two registry REG_DWord called TdrDelay (decimal value 10) and TdrDebugMode (hexadecimal/decimal value 2) too?

It's QWord. Look at the pic for confirmation. DWord is a 32 bit value. QWord is a 64 bit value.

My game always crashes without any hints or warnings，how to fix？thx

[ktulu117]

Originally posted by TBombadil:

Originally posted by ktulu117:

Sadly, this didn't work for me - still got the 0x80000003 error on an RTX 2080 :(

Did you add the two registry REG_DWord called TdrDelay (decimal value 10) and TdrDebugMode (hexadecimal/decimal value 2) too?

I went back and added TdrDebugMode, with both entries as QWord. Played through the butler challenge pack without any crashes, so here's hoping that worked!

[RodroG]

Originally posted by Tom Cruise:

Originally posted by TBombadil:

Did you add the two registry REG_DWord called TdrDelay (decimal value 10) and TdrDebugMode (hexadecimal/decimal value 2) too?

It's QWord. Look at the pic for confirmation. DWord is a 32 bit value. QWord is a 64 bit value.

With QWord it didn't work for me, the crashes persisted. Read here: https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys

Don't know why @Hardware suggested QWord (64 bit) instead and TdrDebugMode is DWord anyway. Both entries should be REG_DWord (32 bits) according with MS documentation and I can confirm it works.

[RodroG]

Originally posted by ktulu117:

Originally posted by TBombadil:

Did you add the two registry REG_DWord called TdrDelay (decimal value 10) and TdrDebugMode (hexadecimal/decimal value 2) too?

I went back and added TdrDebugMode, with both entries as QWord. Played through the butler challenge pack without any crashes, so here's hoping that worked!

Will check with both QWord. Both DWord worked fine for me too.

[Tabsf1]

Press Windows Key + R to open "Run" or Press Windows Key the type "Run"
Type “regedit” in the box and press Enter.
"Registry Editor" will open, navigate to the following file path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

If on 32 bit system:
Right Click New > DWORD (32-bit) Value
Call it "TdrDelay"
Double-click the entry set the value as “20” (Hex Value, others have stated 10 in Decimal but this didn't work for me
Then Right Click New > DWORD (32-bit) Value
Call the 2nd one "TdrDdiDelay"
Double-click the entry also set the value as “20”
If on 64 bit system: use "QWORD (64-bit) Value” for both but keep names and 20 the same

[raiderfan247365]

There are hardly any mentions of the 0x80000003 on Hitman and IOI's timeline on Twitter. More public pressure couldn't hurt, send your tweets folks, make sure you reference 0x80000003 or 0xc0000005 in your tweet!

[ktulu117]

Just got a crash...will try again with hex values set to 20, and adding TdrDdiDelay. If still crashing with that, I'll try DWord instead (but I am on a 64-bit system).

[RodroG]

Originally posted by ktulu117:

Just got a crash...will try again with hex values set to 20, and adding TdrDdiDelay. If still crashing with that, I'll try DWord instead (but I am on a 64-bit system).

I'm on a 64-bit system and DWord worked fine, you should add TdrDebugMode too (TdrDidDelay isn't needed, I think). I experienced crashes with QWord and without TdrDebugMode.

[birms]

Tried all the suggested edits as both Dword and Qword but I'm still gettting the 0x80000003. It seemed like it was working at first. I played Santa Fortuna for 3+ hours and it was fine. Now I'm in Mumbai and it won't stop crashing again. -RTX 2080

[Scott]

Did you reboot after you made the change? because reg changes usually don't do anything until you do.

[Erebus]

Originally posted by ktulu117:

I'll try DWord instead (but I am on a 64-bit system).

Don't it have more to do with the value being stored and not the system type?

[Python Jones P.I.]

Originally posted by butterstick_:

Tried all the suggested edits as both Dword and Qword but I'm still gettting the 0x80000003. It seemed like it was working at first. I played Santa Fortuna for 3+ hours and it was fine. Now I'm in Mumbai and it won't stop crashing again. -RTX 2080

It's not really a fix, your just giving the graphics card a longer chance to recover unless I'm mistaken. Try what ktulu117 suggested and increase the time.

[Passie1288]

Originally posted by Python Jones P.I.:

Originally posted by butterstick_:

Tried all the suggested edits as both Dword and Qword but I'm still gettting the 0x80000003. It seemed like it was working at first. I played Santa Fortuna for 3+ hours and it was fine. Now I'm in Mumbai and it won't stop crashing again. -RTX 2080

It's not really a fix, your just giving the graphics card a longer chance to recover unless I'm mistaken. Try what ktulu117 suggested and increase the time.

The TDR delay is there to prevent the computer from completely freezing up. After 2 seconds windows will restart the GPU driver, even if it's not necessary. A delay of 2 seconds, doesn't always mean that there is really an error or something fishy going on with the GPU. The game might just take a bit longer to load something, but windows will still see it as a problem.

Increasing the TDR delay will only work, if the game isn't crashing the GPU. If the game is making the GPU crash, increasing the TDR delay will still lead to a GPU driver reset, but only after the amount of seconds that you set it to. Disabling TDR delay will freeze up the computer and a (hard) reset is required.

So TDR delay is a wonderful thing in most cases, but might lead to unnecessary driver resets in some cases. Either way, there is still a problem with the game, if the game takes longer than 2 seconds to respond. It really shouldn't be necessary to change a registry value, to play a game properly.

[Erebus]

Originally posted by Passie1288:

Originally posted by Python Jones P.I.:

It's not really a fix, your just giving the graphics card a longer chance to recover unless I'm mistaken. Try what ktulu117 suggested and increase the time.

The TDR delay is there to prevent the computer from completely freezing up. After 2 seconds windows will restart the GPU driver, even if it's not necessary. A delay of 2 seconds, doesn't always mean that there is really an error or something fishy going on with the GPU. The game might just take a bit longer to load something, but windows will still see it as a problem.

Increasing the TDR delay will only work, if the game isn't crashing the GPU. If the game is making the GPU crash, increasing the TDR delay will still lead to a GPU driver reset, but only after the amount of seconds that you set it to. Disabling TDR delay will freeze up the computer and a (hard) reset is required.

So TDR delay is a wonderful thing in most cases, but might lead to unnecessary driver resets in some cases. Either way, there is still a problem with the game, if the game takes longer than 2 seconds to respond. It really shouldn't be necessary to change a registry value, to play a game properly.

I think altering the TDRdelay (or something connected to it) was the "AMD/Nvidia" fix for Nier Automata's "white screen of death". In that case it was doing something screwy with the compute shader and the default "reset" for some archs was so short it'd "die" before it could "rectify". That game still does some wildly problematic stuff behind the scenes, but since the driver doesn't sorta kill itself prematurely it can keep going now. iirc

[Galaxy 👻]

I hope they fix this problem this year.. i cant play the game since 4 month without crash to desktop. :(