Share via

EVENT ID 41(Bugcheck code-278)

Anonymous
2023-03-25T05:26:39+00:00

I get this issue every 7-9 days. I tested the ram with memtest86 and it passed the test. I have also turned off all overclocking of the cpu and the gpu. XMP is turned off in the bios. I have a dump file but i have no idea how to analyse it, I have linked the dump file below. I think it is a Video TDR failure issue. Please help me fix it.

System Specs:

CPU: Intel i5 11400f

GPU: Inno3d RTX 2060

RAM: XPG Adata D30 8GBX2 3200mhz

Mobo: MSI H510M A PRO

PSU: DEEPCOOL PF650

LINK FOR DUMP FILE: Click here to download dump file.

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2023-03-25T20:00:00+00:00

The logs did not report bugcheckcode 278.

This BSOD bugcheck is commonly seen with malfuctioning hardware.

The logs reported BSOD and Live kernel bugchecks related to problems with GPU.

There was one mini dump file collected.

The debugging indicated problems with the Nvidia GPU drivers nvlddmkm.sys

If you've uninstalled and reinstalled the GPU drivers nvlddmkm.sys then that will conclude the troubleshooting.

Please make a new restore point:

https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

If you have any new BSOD in the next 30 days you can open a new thread and refer to this thread.

Monitor the computer for one week using Reliability Monitor:

https://www.howtogeek.com/166911/reliability-monitor-is-the-best-windows-troubleshooting-tool-you-arent-using/

Name NVIDIA GeForce RTX 2060

PNP Device ID PCI\VEN_10DE&DEV_1F08&SUBSYS_12FD10DE&REV_A1\4&22AF55FA&0&0008

Adapter Type NVIDIA GeForce RTX 2060, NVIDIA compatible

Adapter Description NVIDIA GeForce RTX 2060

Adapter RAM (1,048,576) bytes

Installed Drivers C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvldumdx.dll

Driver Version 31.0.15.3141

INF File oem41.inf (Section001 section)

Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_50916785244854F2\NVLDDMKM.SYS (31.0.15.3141, 55.55 MB (58,244,656 bytes), 3/23/2023 8:26 PM)

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

24 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-03-25T07:58:20+00:00

    The memory dump displayed BSOD bugcheck E2.

    This bugcheck indicates that there was a manually initiated crash.

    How come a manually initiated crashed was made?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-03-25T07:50:47+00:00

    Was this answer helpful?

    0 comments No comments
  3. DaveM121 891.6K Reputation points Independent Advisor
    2023-03-25T07:17:16+00:00

    Hi Tushar Sharma_088,

    I am Dave, I will help you with this.

    Your extra large Memory.dmp file is failing to extract to a 16GB file, please check to see if your PC is producing any minidump files in C:\Windows\Minidump, and upload those for analysis.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-03-25T06:22:11+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    When posting memory dump files make sure:

    a) that the size is < 2.5 GB

    b) that they are zipped

    c) that they are posted as separate share links

    The memory dump file in the opening post was not viewed.

    The prior thread in MicrosoftAnswers was viewed and is consistent with malfunctioning hardware.

    Was this answer helpful?

    0 comments No comments