Crashing while gaming

vx22

vx22

Member
Joined
Oct 21, 2024
Posts
18
Event viewer says:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000119 (0x0000000000000002, 0xffffffffc000000d, 0xffffea824f927220, 0xffffa4840598a7f0). A dump was saved in: C:\WINDOWS\Minidump\103124-21203-01.dmp. Report Id: 442cc0cb-d2a6-4d73-bc50-71d7764ef6fb.

Attached that dmp file. Only happens during CS2. Specs are in my profile.

Thank you.
 

Attachments

It would help if you followed the BSOD Posting Instructions so that we get all the required data.

From the two dumps, which are identical, the problem is graphics realted; both bugchecks are 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR, which indicates that a fatal problem has occurred either in the graphics driver or in the graphics card. Your graphics driver appears up to date, it's dated 15th Oct 2024, so it's possible that it's the card.

The way to test whether it's the card is to download DDU and the most recent four graphics driver versions from the Nvidia website. Then use DDU to uninstall the current (latest) driver and then install the one-level back driver. If it BSODs then use DDU to uninstall that driver and install the two-level back driver.

If it BSODs on all four oif the most recent driver versions then the problem is much more likely to be with the graphics card.

One other thing: you are clocking your RAM at it's design speed of 6000MHz, however the maximum RAM speed that your Ryzen 7 7800X3D CPU is guaranteed to support is 5200MHz - see https://www.amd.com/en/products/processors/desktops/ryzen/7000-series/amd-ryzen-7-7800x3d.html. It is very common for CPUs to be perfectly stable with RAM clocked faster than this guaranteed speed, but (as you might imagine) stability is not guaranteed. Since it's not impossible that this is a RAM issue I suggest you remove the RAM overclock and run it at the native SPD speed, probably 4800MHz. If it doesn't BSOD at that speed you can try overclocking to 5200MHz and if it's stable there then it's effectively working as designed. You could try increasing RAM speed one step at a time to find the highest speed you can clock it at and remain stable.
 
Thank you for the reply. I really hope it's not the GPU, I think it's out of warranty but I will do those checks for you and also post the requested logs tonight.
 
I really would strongly suggest that you remove the overclock on the RAM and see whether the system is then stable. When dealing with BSODs it's vital that all overclocks (and undervolts) are removed.

In addition there are several .NET Runtime errors in your Application log that could well be RAM related (they have invalid memory access exceptions 0xC0000005)...
Code: 
Log Name:      Application
Source:        .NET Runtime
Date:          01/11/2024 03:48:23
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AV7ATR9
Description:
Application: Explorer.EXE
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFB128BA9DD

In addition, in your System log, there are repeated errors for what appears to be an MFT error for a Razer Synapse file...
Code: 
Log Name:      System
Source:        Ntfs
Date:          01/11/2024 04:02:52
Event ID:      55
Task Category: None
Level:         Error
Keywords:   
User:          SYSTEM
Computer:      DESKTOP-AV7ATR9
Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1b000000002d88.  The name of the file is "\Users\dylan\AppData\Local\Razer\Synapse3\Log\Razer Synapse 3.log".
In addition there are other corrected errors for your C: drive that may or may not be for the same file.

I strongly suggest that you at least run a chkdsk /f on that drive. I can see that it's a SKHynix_HFS512GDE9X081N, but that could be rebadged under another vendor's name. Check whether the drive vendor has an SSD diagnostics or management tool. If so download and run it and use that to perform a full diagnostic test of the drive. Also post the SMART data from that drive here and check for firmware and driver updates fro the drive with the same tool.
 
ubuysa said:
I really would strongly suggest that you remove the overclock on the RAM and see whether the system is then stable. When dealing with BSODs it's vital that all overclocks (and undervolts) are removed.

In addition there are several .NET Runtime errors in your Application log that could well be RAM related (they have invalid memory access exceptions 0xC0000005)...
Code: 
Log Name:      Application
Source:        .NET Runtime
Date:          01/11/2024 03:48:23
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AV7ATR9
Description:
Application: Explorer.EXE
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FFB128BA9DD

In addition, in your System log, there are repeated errors for what appears to be an MFT error for a Razer Synapse file...
Code: 
Log Name:      System
Source:        Ntfs
Date:          01/11/2024 04:02:52
Event ID:      55
Task Category: None
Level:         Error
Keywords:  
User:          SYSTEM
Computer:      DESKTOP-AV7ATR9
Description:
A corruption was discovered in the file system structure on volume C:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x1b000000002d88.  The name of the file is "\Users\dylan\AppData\Local\Razer\Synapse3\Log\Razer Synapse 3.log".
In addition there are other corrected errors for your C: drive that may or may not be for the same file.

I strongly suggest that you at least run a chkdsk /f on that drive. I can see that it's a SKHynix_HFS512GDE9X081N, but that could be rebadged under another vendor's name. Check whether the drive vendor has an SSD diagnostics or management tool. If so download and run it and use that to perform a full diagnostic test of the drive. Also post the SMART data from that drive here and check for firmware and driver updates fro the drive with the same tool.
Click to expand...

Thank you, I will run chkdsk on that drive tonight. Also, I do not believe I have set any overclock on the memory, besides having XMP on, is that what you are referring to? I made sure to buy RAM that supports XMP. I recently set my BIOS to default besides XMP to remove some changes I made, so there is no more under volt or tuning enabled.

ET_Explorer said:
There is no information in the > DxDiagx86.txt > Windows Error Reporting
Click to expand...

I will try re-running the collector and post that ASAP.
 
XMP is the RAM overclock. RAM has a native (SPD) speed (probably 4800MHz for your RAM) and is certified to be capable of being overclocked to the stated speed of 6000MHz. Overclocking always introduces the possibility of instability, even if the RAM has been certified at that speed. We need to see whether the system is stable at the native RAM speed, so please disable the XMP profile you have.

The DxDIag file is still missing WER data, which is curious. But this time the msinfo32 output is corrupted, and that's worrying. That makes it even more important that you remove the XMP profile for that RAM.
 
vx22 said:
Only happens during CS2.
Click to expand...
Have you confirmed, via the Steam CS forum, that CS2 is not the problem?

Also, have you removed the XMP RAM overclock yet? It is vital that we ensure that the overclocked RAM isn't unstable - and it sometimes is. It's still running at 6000MHz in this latest dump. In the latest upload the msinfo32.nfo file is corrupted and won't open, so there is still something very wrong there, so - please disable the XMP profile.

The dump shows that the failure happened during a graphics operation, can can see several calls to the Windows DirectX kernel driver dxgkrnl.sys in the immediate lead-up to the bugcheck. That's why I also suggest you ensure that this isn't a C2 issue.
 
CS2 is not the problem. I sent crashdumps to valve previously. I did turn off the overclock but it reverted back for some reason. Will report back. Should I wait until it crashes again or just run data collector again?
 
Make sure the RAM overclock is off and when you get more BSODs run the data collector app again and upload the new output.

I am still concerned that since the problem only happens in CS2 the most likely cause is something that CS2 is doing. Perhaps it uses a graphics feature that nothing else does? It's more likely though that CS2 is misbehaving in some way and if so, I'm not surprised that Valve won't fess up. Is there a CS2 forum? Can you ask on there whether others are experiencing similar problems?
 
@
ubuysa said:
Make sure the RAM overclock is off and when you get more BSODs run the data collector app again and upload the new output.

I am still concerned that since the problem only happens in CS2 the most likely cause is something that CS2 is doing. Perhaps it uses a graphics feature that nothing else does? It's more likely though that CS2 is misbehaving in some way and if so, I'm not surprised that Valve won't fess up. Is there a CS2 forum? Can you ask on there whether others are experiencing similar problems?
Click to expand...

Hey - it happened again with XMP off. I think it happens in CS2 because its basically the only new/high spec requirement game I play a lot.

Here is the attachment.

Thank you!
 

Attachments

That's another 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR bugcheck. There has been a graphics driver update since the version you have (566.03 - Oct 22nd), the latest game ready driver is 566.14 - Nov 12th. Be sure to use the game ready driver and NOT the studio driver. You should update to this driver and see whether the problem remains. Use DDU to fully remove the old driver first, it's possible there are traces of still earlier drivers lying around.

If the problem does remain then I think there are three possible causes....
  1. CS2 is flaky (that's the most likely)
  2. The graphics card is flaky (that's a possibility)
  3. The graphics driver is flaky (unlikely since you'll have tried two different versions).
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top