Event ID 41 PC Crash

[Atriox]

My PC keeps randomly crashing using an error code of Event ID 41 without a BSOD.

The issue started happening after I had a windows update.

What happens is the PC will freeze, I can hear sounds for a few seconds and then the PC completely crashes.

I don't know how to fix it, I have tried to use SFC and DISM to repair it, and I have updated my graphics card driver but the issue is still going on.

It's worth noting that I have a 13900KF, so this might be causing the issues? Should I get an RMA?

I don't even know how to troubleshoot what could be causing these issues because windows does not give much information.

[Masque]

Originally posted by smokerob79:

this is one of the problem CPU's from intel.....so good odds its a bad chip.....

I made the other thread earlier -- how odd. We'll see if others start reporting this happening.

Except my CPU is 4th gen i7-4790k. Never overclocked, either.

[Atriox]

Sorry, I didn’t post the rest because it said it would’ve been too big to post.

I ran DISM and installed another new driver for my GPU and I didn’t have any crashes last night, so here’s hoping it’s fixed.

I did see this though which may be useful:

Arguments:

Arg1: ffffb9889130e010, Optional pointer to internal TDR recovery context (TDR\_RECOVERY\_CONTEXT).

Arg2: fffff8029ecf0120, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

[Atriox]

Originally posted by Masque:

Originally posted by smokerob79:

this is one of the problem CPU's from intel.....so good odds its a bad chip.....

I made the other thread earlier -- how odd. We'll see if others start reporting this happening.

Except my CPU is 4th gen i7-4790k. Never overclocked, either.

Sometimes BIOS settings can have factory overclock settings that you don’t even know about

[Atriox]

Just uploaded the full dump file to reddit - steam doesn't want to let me upload it on here because it says that it is too big. https://www.reddit.com/r/pcmasterrace/comments/1ey1k8j/pc_crashes_and_restarts_with_no_bsod_video_tdr/

[Illusion of Progress]

This one...

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffda8107546010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff80670ad1120, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

...Would match what I mentioned in a previous post.

Here's further reading on it...

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x116---video-tdr-failure

My recommendation is mostly the same, with one new addition.

1. Set the system to stock. This means XMP off. Also, do whatever may be needed to ensure the CPU is "Intel default" whatever that may be.

2. Uninstall and reinstall video drivers.

3. Wait and see if the new CPU helps if the above two steps don't help.

However, there isn't a faulting process listed, but instead it says...

MODULE_NAME: memory_corruption

So my additional recommendation is...

4. Test the memory and VRAM.

MemTest86, OCCT, and/or or even Windows Memory Diagnostic can be used for memory.

OCCT may be able to test VRAM?

I didn't see it listed earlier, but do you have a CPU-Z link to show total configuration (namely, interested in RAM setup).

If you have other RAM or graphics cards to test, those wouldn't be bad ideas to rule out where the issue may be.

Edit: If your BIOS isn't the latest, I'd consider updating it as well.

[Atriox]

Originally posted by Illusion of Progress:

This one...

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffda8107546010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff80670ad1120, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

...Would match what I mentioned in a previous post.

Here's further reading on it...

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x116---video-tdr-failure

My recommendation is mostly the same, with one new addition.

1. Set the system to stock. This means XMP off. Also, do whatever may be needed to ensure the CPU is "Intel default" whatever that may be.

2. Uninstall and reinstall video drivers.

3. Wait and see if the new CPU helps if the above two steps don't help.

However, there isn't a faulting process listed, but instead it says...

MODULE_NAME: memory_corruption

So my additional recommendation is...

4. Test the memory and VRAM.

MemTest86, OCCT, and/or or even Windows Memory Diagnostic can be used for memory.

OCCT may be able to test VRAM?

I didn't see it listed earlier, but do you have a CPU-Z link to show total configuration (namely, interested in RAM setup).

If you have other RAM or graphics cards to test, those wouldn't be bad ideas to rule out where the issue may be.

Edit: If your BIOS isn't the latest, I'd consider updating it as well.

I tried to run Windows Memory Diagnostic and I had no signal on my monitor the whole time. What kept happening is the monitor would keep coming on and off again with no signal about every 20 seconds. I tried to unplug the power to the monitor, which usually fixes signal issues but there was still no display.
I chose to shut down and restart the PC instead.

Do you think that points to the RAM being the issue?

It's probably worth pointing out that I have zero issues when the PC is idle or when I am browsing online - it typically happens when I am playing certain games which are perhaps pushing the system hard, such as doing a shader cache. I have had no problems playing Team Fortress 2 so far, which is understandable because it's an old game which doesn't push the system hard.

I know for a fact that earlier in the year when I tried to play Suicide Squad and Tekken 8, I got an out of video memory error despite having a 4090, which everyone said was the 13900KF - though up until now the PC at least didn't have TDR failures, it would just crash to desktop in certain games. Over time though more and more games just kept getting unstable, it used to be that new Unreal Engine games were the only culprit, but then games like Diablo 4, Resident Evil 4, Dragon's Dogma 2, Baldurs Gate 3 etc. started getting the CTDs with no error message.

I managed to get by in Baldurs Gate 3 by capping my fps to match my monitor refresh rate of 240fps, so I assumed that it was a high fps bug at the time - because back then people didn't know that 13900 CPUs had issues.

What would typically happen is the game would stutter for a few seconds, and then it would crash to desktop. I never got error messages.

My RAM is Kingston FURY Beast Black RGB 64GB (4x16GB) 6000MT/s DDR5

GPU is RTX 4090 STRIX OC

CPU is 13900KF

Power Supply is Corsair HX1500i

Motherboard is Z790 ASUS MAXIMUS HERO

[Atriox]

I may have fixed the PC crashes but game crashes continue.

I kept getting Gameinput service errors whenever I launched my PC, but I didn’t pay much mind to it because it didn’t flag up when the pc crashed.

I looked up the error and it turned out other people have been getting black screens and restarts because of the game input service error. I uninstalled and then re-enabled it when windows launched again.

I tried a graphics intensive game which would’ve before crashed the entire pc, and it still crashes the game but this time the PC didn’t crash overall.

If me uninstalling and then re-enabling gameinput service fixed the PC crashes, then I can only assume that the game crashes are being caused by the CPU.

[Atriox]

Originally posted by Atriox:

I may have fixed the PC crashes but game crashes continue.

I kept getting Gameinput service errors whenever I launched my PC, but I didn’t pay much mind to it because it didn’t flag up when the pc crashed.

I looked up the error and it turned out other people have been getting black screens and restarts because of the game input service error. I uninstalled and then re-enabled it when windows launched again.

I tried a graphics intensive game which would’ve before crashed the entire pc, and it still crashes the game but this time the PC didn’t crash overall.

If me uninstalling and then re-enabling gameinput service fixed the PC crashes, then I can only assume that the game crashes are being caused by the CPU.

The PC crashes aren't gone - this time it just happened randomly whilst browsing on my desktop. I ran CHKDSK and this is what it shows in event viewer.

No idea if this has fixed it or not. If it hasn't, then I'm using DDU. If that doesn't work, I'm turning off XMP. Failing that, hopefully the new CPU fixes it whenever I'm allowed to order one. If that doesn't fix it, I honestly don't know what to do next.

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
Cleaning up instance tags for file 0x1fbe0.
1184768 file records processed.
File verification completed.
Phase duration (File record verification): 6.21 seconds.
39211 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 1.44 milliseconds.

Stage 2: Examining file name linkage ...
3746 reparse records processed.
1585794 index entries processed.
Index verification completed.
Phase duration (Index verification): 15.82 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 1.82 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 3.70 seconds.
3746 reparse records processed.
Phase duration (Reparse point and Object ID verification): 9.51 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 6800 unused index entries from index $SII of file 0x9.
Cleaning up 6800 unused index entries from index $SDH of file 0x9.
Cleaning up 6800 unused security descriptors.
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
Phase duration (Security descriptor verification): 108.36 milliseconds.
200514 data files processed.
Phase duration (Data attribute verification): 1.60 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

976196831 KB total disk space.
842173312 KB in 655537 files.
474668 KB in 200517 indexes.
0 KB in bad sectors.
1290367 KB in use by the system.
65536 KB occupied by the log file.
132258484 KB available on disk.

4096 bytes in each allocation unit.
244049207 total allocation units on disk.
33064621 allocation units available on disk.
Total duration: 27.73 seconds (27735 ms).

Internal Info:
00 14 12 00 fb 0f 0d 00 5a ef 16 00 00 00 00 00 ........Z.......
82 0b 00 00 20 03 00 00 00 00 00 00 00 00 00 00 .... ...........

[Illusion of Progress]

Originally posted by Atriox:

I tried to run Windows Memory Diagnostic and I had no signal on my monitor the whole time. What kept happening is the monitor would keep coming on and off again with no signal about every 20 seconds. I tried to unplug the power to the monitor, which usually fixes signal issues but there was still no display.
I chose to shut down and restart the PC instead.

Do you think that points to the RAM being the issue?

Not necessarily. I'd say what was happening is either it wasn't POSTing to begin with, or if you think it was, your display just wasn't syncing in that mode.

I sometimes have my display lose signal and cycle after the Windows loading screen/before the "welcome" screen before the desktop. I don't know why but it only happens there (used to be random until I got a new cable and it only started once I went from DVI to DP) a power cycling always fixes it. But it's one of those things in your case. We can't determine anything about the RAM unless we can see the results.

I'd say to try MemTest86 or OCCT instead.

But I'm now wondering if the memory was a Red herring. I went back and looked over the slew of WHEA crashes I had a year ago with the same symptoms, and most of mine had something else for the faulting module, but I did find some with "memory_corruption" like yours (and in my case, it was a failing GPU, not memory, that was at cause). I'd still check the memory but I'm wondering if it's less suspect now.

Originally posted by Atriox:

It's probably worth pointing out that I have zero issues when the PC is idle or when I am browsing online - it typically happens when I am playing certain games which are perhaps pushing the system hard, such as doing a shader cache. I have had no problems playing Team Fortress 2 so far, which is understandable because it's an old game which doesn't push the system hard.

I know for a fact that earlier in the year when I tried to play Suicide Squad and Tekken 8, I got an out of video memory error despite having a 4090 I know for a fact that earlier in the year when I tried to play Suicide Squad and Tekken 8, I got an out of video memory error despite having a 4090, which everyone said was the 13900KF - though up until now the PC at least didn't have TDR failures, it would just crash to desktop in certain games. Over time though more and more games just kept getting unstable, it used to be that new Unreal Engine games were the only culprit, but then games like Diablo 4, Resident Evil 4, Dragon's Dogma 2, Baldurs Gate 3 etc. started getting the CTDs with no error message.

Yeah, mine was the same way (minus the shader compilation part). in that it never happened when idle or during lighter loads, and only crashed when the GPU was under medium to heavy load, and not always.

I think in your case, you either have an unstable/degraded CPU (the Raptor Lake issue), or an unstable video card.

Knowing that some of the unstable CPUs can exhibit symptoms that looks like a GPU error, and that you mention shader compilation as a key time (and having gotten the specific out of memory error known to occur with the unstable CPUs), has me looking even more at the CPU.

Originally posted by Atriox:

My RAM is Kingston FURY Beast Black RGB 64GB (4x16GB) 6000MT/s DDR5

This is a very heavy memory configuration, by the way.

What I mean by "heavy" is that RAM is harder to stabilize with the following conditions...

1. More DIMMs.

2. More ranks (16 GB is typically single rank in DDR5 by now but I don't know what yours are).

3. Higher frequency.

If it can't stabilize, it won't pass POST. And sometimes it might pass POST but still be problematic as it's borderline unstable.

DDR5 in particular is even harder to stabilize than DDR4, and this is why you've been hearing it doesn't like four DIMMs (and sometimes it doesn't even like dual rank on just two DIMMs). You often have to drop to 4,800 MHz to 5,600 MHz to stabilize things.

It would have been better to choose 2x 32 GB (they would be dual rank DIMMs, but slightly easier to stabilize than four single rank DIMMs) but I get the impression you made the purchase before those were as common/cheap.

Seeing your RAM configuration now, I would absolutely try disabling XMP to see if that plays into things. I mean, I would have done it as a rule anyway, but I'd stress doing it now if you haven't already.

I have a somewhat heavy memory configuration myself (4x 16 GB 3,600 MHz DDR4, all dual rank DIMMs) and when I was having my issues, I ironically found the issue got worse when I disabled XMP and ran at default speeds. I never figured out why since the it was changing the GPU that both introduced/resolved the issue. It was strange, but it's worth mentioning that a heavy memory configuration can complicate stability issues and always needs questioned.

I also tested with two of the DIMMs/half the RAM at one point, and would suggest the same. If you do this, make sure you use DIMM slots 2 and 4 (the farther "set" from the CPU socket), not slots 1 and 3. The reason for this is that this on daisy chain motherboards (which is almost all of them these days, unfortunately), having slots 2 and 4 unpopulated results in them acting as "open ends" which introduces interference and that, too, makes a RAM configuration harder to stabilize.

Originally posted by Atriox:

I kept getting Gameinput service errors whenever I launched my PC, but I didn’t pay much mind to it because it didn’t flag up when the pc crashed.

I get those too. I wouldn't worry about them.

Anyway, to summarize, I'm still sort of in the same spot.

1. Wait on CPU and see if that resolves things.

2. Test RAM (and other things to minimize how "heavy" the memory configuration is, such as disabling XMP and possibly removing half the RAM). Might even want to wait and do this after you get new CPU because if the current one is degraded, they are known to possibly result in I/O issues, which can appear to be RAM issues.

3. It could be the GPU, but I'd wait until you ruled out the CPU to proceed to this one. I'd normally be suspecting the GPU with these symptoms under normal circumstances, but since you have a CPU known to result in exactly what you're dealing with, I'd wait on ruling out the CPU.

[Atriox]

Originally posted by Illusion of Progress:

Originally posted by Atriox:

I tried to run Windows Memory Diagnostic and I had no signal on my monitor the whole time. What kept happening is the monitor would keep coming on and off again with no signal about every 20 seconds. I tried to unplug the power to the monitor, which usually fixes signal issues but there was still no display.
I chose to shut down and restart the PC instead.

Do you think that points to the RAM being the issue?

Not necessarily. I'd say what was happening is either it wasn't POSTing to begin with, or if you think it was, your display just wasn't syncing in that mode.

I sometimes have my display lose signal and cycle after the Windows loading screen/before the "welcome" screen before the desktop. I don't know why but it only happens there (used to be random until I got a new cable and it only started once I went from DVI to DP) a power cycling always fixes it. But it's one of those things in your case. We can't determine anything about the RAM unless we can see the results.

I'd say to try MemTest86 or OCCT instead.

But I'm now wondering if the memory was a Red herring. I went back and looked over the slew of WHEA crashes I had a year ago with the same symptoms, and most of mine had something else for the faulting module, but I did find some with "memory_corruption" like yours (and in my case, it was a failing GPU, not memory, that was at cause). I'd still check the memory but I'm wondering if it's less suspect now.

Originally posted by Atriox:

It's probably worth pointing out that I have zero issues when the PC is idle or when I am browsing online - it typically happens when I am playing certain games which are perhaps pushing the system hard, such as doing a shader cache. I have had no problems playing Team Fortress 2 so far, which is understandable because it's an old game which doesn't push the system hard.

I know for a fact that earlier in the year when I tried to play Suicide Squad and Tekken 8, I got an out of video memory error despite having a 4090 I know for a fact that earlier in the year when I tried to play Suicide Squad and Tekken 8, I got an out of video memory error despite having a 4090, which everyone said was the 13900KF - though up until now the PC at least didn't have TDR failures, it would just crash to desktop in certain games. Over time though more and more games just kept getting unstable, it used to be that new Unreal Engine games were the only culprit, but then games like Diablo 4, Resident Evil 4, Dragon's Dogma 2, Baldurs Gate 3 etc. started getting the CTDs with no error message.

Yeah, mine was the same way (minus the shader compilation part). in that it never happened when idle or during lighter loads, and only crashed when the GPU was under medium to heavy load, and not always.

I think in your case, you either have an unstable/degraded CPU (the Raptor Lake issue), or an unstable video card.

Knowing that some of the unstable CPUs can exhibit symptoms that looks like a GPU error, and that you mention shader compilation as a key time (and having gotten the specific out of memory error known to occur with the unstable CPUs), has me looking even more at the CPU.

Originally posted by Atriox:

My RAM is Kingston FURY Beast Black RGB 64GB (4x16GB) 6000MT/s DDR5

This is a very heavy memory configuration, by the way.

What I mean by "heavy" is that RAM is harder to stabilize with the following conditions...

1. More DIMMs.

2. More ranks (16 GB is typically single rank in DDR5 by now but I don't know what yours are).

3. Higher frequency.

If it can't stabilize, it won't pass POST. And sometimes it might pass POST but still be problematic as it's borderline unstable.

DDR5 in particular is even harder to stabilize than DDR4, and this is why you've been hearing it doesn't like four DIMMs (and sometimes it doesn't even like dual rank on just two DIMMs). You often have to drop to 4,800 MHz to 5,600 MHz to stabilize things.

It would have been better to choose 2x 32 GB (they would be dual rank DIMMs, but slightly easier to stabilize than four single rank DIMMs) but I get the impression you made the purchase before those were as common/cheap.

Seeing your RAM configuration now, I would absolutely try disabling XMP to see if that plays into things. I mean, I would have done it as a rule anyway, but I'd stress doing it now if you haven't already.

I have a somewhat heavy memory configuration myself (4x 16 GB 3,600 MHz DDR4, all dual rank DIMMs) and when I was having my issues, I ironically found the issue got worse when I disabled XMP and ran at default speeds. I never figured out why since the it was changing the GPU that both introduced/resolved the issue. It was strange, but it's worth mentioning that a heavy memory configuration can complicate stability issues and always needs questioned.

I also tested with two of the DIMMs/half the RAM at one point, and would suggest the same. If you do this, make sure you use DIMM slots 2 and 4 (the farther "set" from the CPU socket), not slots 1 and 3. The reason for this is that this on daisy chain motherboards (which is almost all of them these days, unfortunately), having slots 2 and 4 unpopulated results in them acting as "open ends" which introduces interference and that, too, makes a RAM configuration harder to stabilize.

Originally posted by Atriox:

I kept getting Gameinput service errors whenever I launched my PC, but I didn’t pay much mind to it because it didn’t flag up when the pc crashed.

I get those too. I wouldn't worry about them.

Anyway, to summarize, I'm still sort of in the same spot.

1. Wait on CPU and see if that resolves things.

2. Test RAM (and other things to minimize how "heavy" the memory configuration is, such as disabling XMP and possibly removing half the RAM). Might even want to wait and do this after you get new CPU because if the current one is degraded, they are known to possibly result in I/O issues, which can appear to be RAM issues.

3. It could be the GPU, but I'd wait until you ruled out the CPU to proceed to this one. I'd normally be suspecting the GPU with these symptoms under normal circumstances, but since you have a CPU known to result in exactly what you're dealing with, I'd wait on ruling out the CPU.

Thanks for the response. Yeah I think it’s best to start doing all of these tests when I have a new CPU to rule it out as being the most obvious choice.

I hope if anything that it’s not the 4090 because I know that ASUS support isn’t exactly good.

[Atriox]

I haven't had any pc crashes for a few days now, so I'll put it down to CHKDSK fixing that issue.

Just replaced the 13900KF with a 13900K and games aren't crashing anymore too. Feels good lol.