BSOD Crash Dump Debugger Report

Question

A few days ago i change my ssd and did a clean windows 10 installation with usb tool from microsoft. Since then i have random freezes and bsod while gaming (ac valhalla, ac black flag, RDR2). The ssd is a WD blue 500gb m.2 and the previous one was a WD green 240Gb m.2.

Windows 10 is installed there along with the games. Before changing the ssd i had no issues whatsoever with the current nvidia driver. But what is different appart from the ssd was the windows version i had, it wasnt the latest 10.0.19041.1. I dont remember wich one was, but it was a version where you could see if windows was activated trough "this pc - properties". 

Here is the dump that was generated. It points to "nvlddmkm". Nvidia driver. But that's odd, forgot to mention i had clean installed windows 3 times since the first BSOD, and with each new installation the same issue. As i mentioned, the only thing different is the ssd (which i analized with tools and no damage there) and the new windows 10 version i installed. So could be a combination of the new windows and the driver? Or in fact a faulty ssd? (which i doubt because it only crashes when im gaming, i can use windows for hours otherwise)

Thanks in advance to whoever take a look into this! :)

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8014e140e36, The address that the exception occurred at
Arg3: fffff4029d258ef8, Exception Record Address
Arg4: fffff4029d258730, Context Record Address

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5546

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-SQU8CAL

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 70777

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8014e140e36

BUGCHECK_P3: fffff4029d258ef8

BUGCHECK_P4: fffff4029d258730

EXCEPTION_RECORD:  fffff4029d258ef8 -- (.exr 0xfffff4029d258ef8)
ExceptionAddress: fffff8014e140e36 (nvlddmkm+0x00000000007c0e36)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

CONTEXT:  fffff4029d258730 -- (.cxr 0xfffff4029d258730)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffe381724dc1d8
rdx=0000000000000000 rsi=ffffbb8bb076611a rdi=ffffe38172446000
rip=fffff8014e140e36 rsp=fffff4029d259130 rbp=ffffe38172467f20
 r8=0000000000000006  r9=0000000000000000 r10=0000000000000000
r11=ffffbb8bb0766186 r12=0000000000000000 r13=0000000000000000
r14=0000000000000002 r15=ffffe38172446180
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
nvlddmkm+0x7c0e36:
fffff801`4e140e36 ff5048          call    qword ptr [rax+48h] ds:002b:00000000`00000048=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff801436fa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8014360f330: Unable to get Flags value from nt!KdVersionBlock
fffff8014360f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000048 

ERROR_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%p hace referencia a la memoria en 0x%p. La memoria no se pudo %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000048

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
fffff402`9d259130 00000000`00000000     : fffff801`4dae9543 00000000`00000001 fffff801`42dd3608 00000000`000000ff : nvlddmkm+0x7c0e36

SYMBOL_NAME:  nvlddmkm+7c0e36

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr 0xfffff4029d258730 ; kb

BUCKET_ID_FUNC_OFFSET:  7c0e36

FAILURE_BUCKET_ID:  AV_nvlddmkm!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup:     MachineOwner
---------

Answer 1

I changed the ssd because i was running out of space.  And the old one is being used by someone else. Looking trough google people is pointing out to a certain windows 10 update. 

"KB4598242 for Win 10 20H2"

https://www.reddit.com/r/Windows10/comments/kyxchy/nvlddmkm\_crashing\_since\_this\_week/

https://techcommunity.microsoft.com/t5/windows-10/kb4598242-kb4598229-bsod-crash-with-critical-process-died-errors/m-p/2071663

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/427727/gpu-is-not-responding/?commentPage=11

And those are not the only posts, so i uninstalled that update an haven't got a bsod for 8 hours straight of gaming with the latest nvidia driver (461.09)

Seems that particular update is messing with nvidia drivers, specifically with "nvlddmkm.sys". If i got a bsod again i'll let you know. 

Thanks for your response!

Answer 2

Hi,

Searching trough google looks like a certain windows 10 update is messing around with nvidia drivers.

"KB4598242 for Win 10 20H2"

https://www.reddit.com/r/Windows10/comments/kyxchy/nvlddmkm\_crashing\_since\_this\_week/

https://techcommunity.microsoft.com/t5/windows-10/kb4598242-kb4598229-bsod-crash-with-critical-process-died-errors/m-p/2071663

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/427727/gpu-is-not-responding/?commentPage=11

I uninstalled that update an haven't got a bsod for 8 hours straight of gaming with the latest nvidia driver (461.09).

If that doesn't work i'm gonna try reverting back the gpu driver. 

And here where you said "The PC that I was built for my friend uses the WD 1T SSD; that should be the problem." You mean the ssd?

Thank you for reply!

Answer 3

Thanks for the feedback!

Here to help,

Rob

Answer 4

Hi, 

Try to download the Nividia driver from the preview version. The PC that I was built for my friend uses the WD 1T SSD; that should be the problem. I suggested he use this one, and it seems to work fine.

https://www.nvidia.com/download/driverResults.aspx/166627/en-us

Answer 5

Hi claualarcon94, I am Rob, an independent and a 15 time and dual award MVP specializing in Windows troubleshooting and Bluescreen analysis. Please remember as independents we are not responsible for the development of Windows or the computer hardware and drivers. If you will work with me I will be here to help until the issue is resolved.

Of course, the cause does seem to be the Nvidia drivers.

The issue could be the new SSD. Or even something was jarred during its installation.

Why did you change SSD?

Have you tried putting the original SSD back in?

======

We might be able to glean more information from the DMP file.

Troubleshoot blue screen errors <-- read this link

http://windows.microsoft.com/en-us/windows-10/t...

If there are any memory.dmp files created in C:\Windows or xxxxxxxx.dmp files in C:\Windows\minidump then post those so I can analyze them.

We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire). If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.

One-Drive - Share files and folders and change permissions

http://windows.microsoft.com/en-us/onedrive/sha...

Upload photos and files

http://windows.microsoft.com/en-us/onedrive/add...

Zip or upload the contents of C:\Windows\minidump

Use OneDrive to upload collected files

https://support.microsoft.com/en-us/office/uplo...

======

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

are essentially the same).

http://www.winvistaclub.com/t79.html

Using Driver Verifier

https://msdn.microsoft.com/en-us/library/window...

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

If Driver Verifier creates a minidump upload it and post the link here so we can

analyze it.

Here to help,

Rob

---

Standard Disclaimer: Those may be non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Please let us know the results and if you need further assistance. Feedback definitely helps us help all.