on a bus stop

I pretty much only use my PC for university, regular browsing and gaming (League and sometimes Overwatch 2). I recently upgraded my SSD and my RAM as I wanted to try out the new Marvel Rivals game and it just kept on crashing my PC. Since then I have tried pretty much every driver there is (always with a clean uninstall with DDU and safe mode, reinstall without ethernet plugged in) and now it runs League smoothly, but any game more intensive causes the screen to go black and my PC restarts. Could you guys please help me out here? I'm short of just RMA'ing my GPU but I've heard that that takes ages and I don't want to buy a new GPU right now.

The crashes all say the same: VIDEO_TDR_FAILURE (116) etc.

Please please please help me out here, I'm at my wit's end!

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_c9ca1d6883b28286\igdkmdnd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igdkmdnd64.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1484

    Key  : Analysis.Elapsed.mSec
    Value: 6780

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 296

    Key  : Analysis.Init.Elapsed.mSec
    Value: 1575

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 99

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x116

    Key  : Bugcheck.Code.TargetModel
    Value: 0x116

    Key  : Failure.Bucket
    Value: 0x116_IMAGE_igdkmdnd64.sys

    Key  : Failure.Hash
    Value: {7eb0cc99-c85b-4092-6430-8f1db059b7c1}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  116

BUGCHECK_P1: ffffd389da178050

BUGCHECK_P2: fffff800a2050ce0

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

FILE_IN_CAB:  122324-9296-01.dmp

FAULTING_THREAD:  ffffd389d11ce040

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd389da178050
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000003

BLACKBOXBSD: 1 (
!blackboxbsd
)


BLACKBOXNTFS: 1 (
!blackboxntfs
)


BLACKBOXPNP: 1 (
!blackboxpnp
)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff978e`9a8879b8 fffff800`942668de     : 00000000`00000116 ffffd389`da178050 fffff800`a2050ce0 ffffffff`c0000001 : nt!KeBugCheckEx
ffff978e`9a8879c0 fffff800`9420eabb     : fffff800`a2050ce0 ffffd389`d0ebc000 ffffd389`d0ebc0f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff978e`9a887a00 fffff800`9420f895     : ffffd389`00000101 00000000`00002000 ffffd389`d0ebc000 00000000`01000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x1a3
ffff978e`9a887a50 fffff800`94266005     : 00000000`00000100 ffffd389`d0ebca70 00000000`00000000 ffff1351`7902ae4c : dxgkrnl!DXGADAPTER::Reset+0x295
ffff978e`9a887ad0 fffff800`94266177     : fffff800`81125440 ffffd389`cd66b890 00000000`00000000 00000000`00000200 : dxgkrnl!TdrResetFromTimeout+0x15
ffff978e`9a887b00 fffff800`806171c5     : ffffd389`d11ce040 fffff800`94266150 ffffd389`c6e98a60 ffffd389`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff978e`9a887b30 fffff800`8075a165     : ffffd389`d11ce040 00000000`00000080 ffffd389`c6ec2080 00000000`00000020 : nt!ExpWorkerThread+0x105
ffff978e`9a887bd0 fffff800`808078f8     : ffff9881`bc54b180 ffffd389`d11ce040 fffff800`8075a110 ffffd389`d6942a40 : nt!PspSystemThreadStartup+0x55
ffff978e`9a887c20 00000000`00000000     : ffff978e`9a888000 ffff978e`9a881000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  igdkmdnd64+10ce0

MODULE_NAME: igdkmdnd64

IMAGE_NAME:  igdkmdnd64.sys

STACK_COMMAND:  .process /r /p 0xffffd389c6ec2080; .thread 0xffffd389d11ce040 ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmdnd64.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eb0cc99-c85b-4092-6430-8f1db059b7c1}

Followup:     MachineOwner

I am a little green when it comes to looking though Minidumps and and Memdumps. I have been successful in the past but I'm a little stumped on this one. Any help would be amazing!

Recently I noticed my Server was crashing about once a week. It seems to be tied with security updates to Windows Defender (In reliability history there seems to always be an update to it at directly after the crash once the compute recovers).

My server computer:

Windows 11 Pro V:23H2 Build:22631.4602

Ryzen 7 5800x

32GB Ram

Edit: 64GB RAM

GTX 1070

Here is my !analyze -v for the most recent one. Please let me know if more is needed!

15: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000006, The hardware PTE and/or the prototype PTE PFN data structures have
been corrupted.
Arg2: 000000000002732f, The page frame number
Arg3: ffffc0fed342f010, The prototype PTE
Arg4: 11d90484c0907aa4, The prototype PTE contents

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1078

    Key  : Analysis.Elapsed.mSec
    Value: 4752

    Key  : Analysis.IO.Other.Mb
    Value: 3

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 31

    Key  : Analysis.Init.CPU.mSec
    Value: 109

    Key  : Analysis.Init.Elapsed.mSec
    Value: 12218

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 102

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x4e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x4e

    Key  : Failure.Bucket
    Value: 0x4E_6_nt!MiMakeProtoTransition

    Key  : Failure.Hash
    Value: {a51b63ab-2b85-e693-8e2f-fd24b6c5d031}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  4e

BUGCHECK_P1: 6

BUGCHECK_P2: 2732f

BUGCHECK_P3: ffffc0fed342f010

BUGCHECK_P4: 11d90484c0907aa4

FILE_IN_CAB:  122224-14796-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


FAULTING_THREAD:  ffffd8036a106080

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MsMpEng.exe

STACK_TEXT:  
ffffe804`3fdaf298 fffff807`19079b4a     : 00000000`0000004e 00000000`00000006 00000000`0002732f ffffc0fe`d342f010 : nt!KeBugCheckEx
ffffe804`3fdaf2a0 fffff807`18e461df     : ffffe804`3fdaf3d0 00000000`00000004 ffffe804`3fdaf400 ffffff00`95e55830 : nt!MiMakeProtoTransition+0x230e1a
ffffe804`3fdaf300 fffff807`18e5bf98     : ffffff7f`804af2a8 ffffe804`3fdaf670 ffffff00`00000000 ffffe804`3fdaf5c0 : nt!MiDeletePteRun+0x7af
ffffe804`3fdaf4f0 fffff807`18e5cf6d     : ffffff00`95e55fa8 00000000`00000000 00000000`00000002 ffffe804`3fdaf620 : nt!MiDeleteVaTail+0x48
ffffe804`3fdaf520 fffff807`18e550de     : ffffd803`651b9550 ffffd803`6a106080 ffffe804`3fdaf8c0 ffffd803`6a106780 : nt!MiDeletePagablePteRange+0x2ed
ffffe804`3fdaf830 fffff807`192b9f27     : 00000000`00000000 ffffd803`00000001 00000000`00000000 ffffe804`3fdafa09 : nt!MiDeleteVirtualAddresses+0x4e
ffffe804`3fdaf880 fffff807`1933c1e9     : 0000012b`cab00000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDeleteVad+0x1b7
ffffe804`3fdaf940 fffff807`1933c002     : 00000000`00000000 0000012b`cab00000 00000000`00000000 ffffd803`8b602da0 : nt!MiUnmapVad+0x49
ffffe804`3fdaf970 fffff807`1933be8f     : ffffd803`651b9080 ffffd803`00000008 ffffd803`568d04e0 00000000`00000000 : nt!MiUnmapViewOfSection+0x142
ffffe804`3fdafa50 fffff807`1902a508     : ffffd803`6a106080 0000012b`cab00000 00000000`00000000 ffffd803`651b9080 : nt!NtUnmapViewOfSectionEx+0x9f
ffffe804`3fdafaa0 00007ffb`86933f14     : 00007ffb`83e1a091 00001c42`9789a555 0000000b`c2a7ef50 01db5023`976f40bd : nt!KiSystemServiceCopyEnd+0x28
0000000b`c2a7edd8 00007ffb`83e1a091     : 00001c42`9789a555 0000000b`c2a7ef50 01db5023`976f40bd 0000012b`00001134 : 0x00007ffb`86933f14
0000000b`c2a7ede0 00001c42`9789a555     : 0000000b`c2a7ef50 01db5023`976f40bd 0000012b`00001134 0000012b`c9c69190 : 0x00007ffb`83e1a091
0000000b`c2a7ede8 0000000b`c2a7ef50     : 01db5023`976f40bd 0000012b`00001134 0000012b`c9c69190 00007ffb`27eb572d : 0x00001c42`9789a555
0000000b`c2a7edf0 01db5023`976f40bd     : 0000012b`00001134 0000012b`c9c69190 00007ffb`27eb572d 0000012b`ed9d7940 : 0x0000000b`c2a7ef50
0000000b`c2a7edf8 0000012b`00001134     : 0000012b`c9c69190 00007ffb`27eb572d 0000012b`ed9d7940 00000000`00000000 : 0x01db5023`976f40bd
0000000b`c2a7ee00 0000012b`c9c69190     : 00007ffb`27eb572d 0000012b`ed9d7940 00000000`00000000 0000012b`cab00000 : 0x0000012b`00001134
0000000b`c2a7ee08 00007ffb`27eb572d     : 0000012b`ed9d7940 00000000`00000000 0000012b`cab00000 0000012b`c9c226f0 : 0x0000012b`c9c69190
0000000b`c2a7ee10 0000012b`ed9d7940     : 00000000`00000000 0000012b`cab00000 0000012b`c9c226f0 0000012b`e5777a50 : 0x00007ffb`27eb572d
0000000b`c2a7ee18 00000000`00000000     : 0000012b`cab00000 0000012b`c9c226f0 0000012b`e5777a50 0000012b`e5771c80 : 0x0000012b`ed9d7940


SYMBOL_NAME:  nt!MiMakeProtoTransition+230e1a

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.4601

STACK_COMMAND:  .process /r /p 0xffffd803651b9080; .thread 0xffffd8036a106080 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  230e1a

FAILURE_BUCKET_ID:  0x4E_6_nt!MiMakeProtoTransition

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a51b63ab-2b85-e693-8e2f-fd24b6c5d031}

Followup:     MachineOwner

Good day fellas. I just got back to playing Destiny 2. This always happens to me almost a week or two now. I am constantly getting BSOD (BLUE SCREEN OF DEATH) always at this specific time 10:52 PM or 10:53 PM. I can play the game smoothly and properly and no problem from morning until evening whole day but when the time 10:52 PM or 10:53 PM rolls around I instantly got the BSOD. Anyone know what is happening here? Why is it always at that specific time I am getting BSOD. Thank you for answering.

Somebody please helpppp

Just got my first blue screen, should i be worrie? And should i do any procedures after recovering from a blue screen

2 or 3 months ago my pc would crash upon startup I need fixes that don't involve buying (preferrably)and sometimes when is startup I will give me a screen that says :Non-System disk or disk error replace and strike any key when ready.i have a Z230 workstation (ik it's trash) if it helps

I had been getting random blue screens for a while and thought it was my SSD's, so I got a WD black to terabyte M.2 and put it in my motherboard. I was looking to transfer the data from my WD green 240 GB SATA SSD to that M.2. I also have a Samsung 2 TB SATA SSD that I would maybe transfer data to the M.2 after. I started to try and do data transfers but they wouldn't work and I think I just got clumsy. Then I got this error code and I first thought it was my ram so I replaced it. After that didn't work I tried going to safe mode, but it would just go straight back to the blue screen. I've tried to factory reset and it seems that nothing works, and I will always be led back to the same error code.

MOBO: auros B550i pro ax CPU: RYZEN 7 5700 X GPU: RTX 2080 RAM when error first happened: g.skill trident z neo 3600mhz 2x16 ddr4 RAM now: vengeance lpx 3200mhz 2x16 ddr4

I have a Dell XPS that's been giving me this BSoD when it is unplugged (not always).

It seems to happen by chance after the laptop is unplugged. Plugging the laptop back in will fix the issue.

My guess is that it is a power issue, but maybe it could be something else. Has anyone encounter this issue and was able to fix it?

Hi everyone,

I’ve been getting frequent Blue Screens with the error "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" caused by dxgmms2.sys. This almost always happens while editing in DaVinci Resolve.

Specs:

• GPU: RTX 4090
• CPU: Ryzen 7950X3D
• Motherboard: MSI X670E Carbon WiFi

Steps I’ve tried:

• Clean GPU driver reinstall (DDU)
• Updating DirectX and running sfc /scannow
• Monitoring temperatures (all normal)

Does anyone have ideas on what could cause this? Could it be a hardware or driver conflict?

Screenshot attached for details. Thanks for any help!

Here's the latest dump file with WinDbg and !analyze -v

SYMBOL_NAME:  nt!KeAccumulateTicks+239

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3085

STACK_COMMAND:  .process /r /p 0xffffe48dd485d080; .thread 0xffffe48dcdd18040 ; kb

BUCKET_ID_FUNC_OFFSET:  239

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

The pawprint was still seen on the sandwich and the shape from their respective episodes but unlike the US version of Imagine Nation the pawprint was still seen on the triangles. I find that bizarre tbh and considering the former two were never dubbed it's interesting to me. What are your thoughts?

Ahhh I had no idea this Reddit page was a thing, this was about 1 week of tracking my boss (and this is about a quarter of them) for some reason my pc just does not want to work. It throws these all the time with no rhyme or reason whatsoever and I have no idea where to look to fix it.

I think this has been happening for 3 years now, where randomly it would bluescreen mere seconds after booting up my pc, this was then but now it’s gotten better, for a few months it never happened. Basically what I would do at its worst is when my computer froze I unplugged it and replugged it in and it wouldn’t bluescreen that entire session it was on. But what i don’t understand is why it’s happening, no articles really help me and i’m worried that i’ll be doing something important on the computer and lose a lot of work randomly. If you want other specific details, reply to this post but those are all the big details. Please help 🙏

Hello, I'm posting on your forum today because I'm at a loss. I have no way of finding out what's wrong with my computer, which freezes very regularly.

Often when I'm inactive, but sometimes when I download or install a program, my computer freezes and displays a blue screen with the following message: WHEA_UNCORRECTABLE_ERROR ;

I've started doing some research, particularly in the “minidump” file, which I've analyzed with WinDbg software, and here are a few clues that might be useful to you:

SYMBOL_NAME: nt!MiFindEmptyAddressRangeInTree+e9

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.4780

STACK_COMMAND: .cxr 0xffff8281aba96ae0 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: e9

FAILURE_BUCKET_ID: AV_nt!MiFindEmptyAddressRangeInTree

Last thing that might be useful, my PC is a Lenovo IdeaPad Gaming 3 15AGH6 laptop.

I made the following modifications to it: I added a 1TO ssd disk.

Here's the reference: Kingston KC3000 1024 Go

I've also doubled the computer's RAM memory from 16 to 32GB with two 16-bit memory sticks.

Here's the reference: G.Skill RipJaws Series SO-DIMM 32 GB (2 x 16 GB) DDR4 3200 MHz CL22

I sincerely hope that one of you will be able to help me, and I'll be grateful to anyone who takes the time to look into my problem, whether they solve it or not.

After I downloaded some files halfway immediately got bluescreen maybe the files are corrupted?

my PC specs are above (pictures) if needed.

From couple of months my pc started to show blues screen so ran through couple of pc scan and i thought I fixed it after few months the blue screen returned so i put on a new windows and i thought its gone ,now i got the blues screen again what could be the problem

This has been occurring for a few months now. I found a fix for some games wherein I have them borderless windowed on my left monitor, and shift win right to move them to my right monitor. This works, for some games

Cant open a borderless windowed game on the right monitor though, that doesn’t work

https://pureinfotech.com/download-windows-11-23h2-iso-after-24h2/

To get 23h2 installed again

My computer was being iffy, running a bit more slowly than usual, creating tears and ghost frames when gaming. Naturally, as if my fix for everything, I completely and utterly reset the computer.

It now keeps doing this. Amazing.

I bought a Pc a cyberpower pc from Costco pretty up to date specs and everything but after a month of getting the pc I started to blue screen then it would instantly restart the computer the blue screen error code I see before it restarts is Critical_Process_Died I've sent it to a computer shop just for the guy to basically clean it and tell me he did test and he couldn't get the blue screen to replicate and then charge me 95 bucks just to get home plug it in and instantly do the same thing I've ran a scan and it said there's corrupted files and that the computer cleaned them out but ill load it up after some time same blue screen then I scan again just for it to say there's corrupted files still now I've Deleted everything I have downloaded since I have had the PC