Intermittent Blue screen

Question

Hello, 

I am having an issue with an intermittent bluescreen while gaming and It appears to be related to my video drivers. I have uninstalled and reinstalled my drivers a couple of times yet it persists so I am turning to you for help! 

Below is the dump file from the latest bluescreen:

Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff802`23c09000 PsLoadedModuleList = 0xfffff802`24024790
Debug session time: Sun Apr 21 15:57:59.502 2019 (UTC - 7:00)
System Uptime: 0 days 21:56:10.827
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`23dbc730 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb20a`222e25b0=000000000000000a
10: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff801b1789149, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff801b1789149, address which referenced memory

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

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER:  Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME:  MS-7B79

SYSTEM_SKU:  To be filled by O.E.M.

SYSTEM_VERSION:  1.0

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1.30

BIOS_DATE:  04/23/2018

BASEBOARD_MANUFACTURER:  Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT:  X470 GAMING PRO (MS-7B79)

BASEBOARD_VERSION:  1.0

DUMP_TYPE:  1

BUGCHECK_P1: fffff801b1789149

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff801b1789149

READ_ADDRESS:  fffff801b1789149 

CURRENT_IRQL:  2

FAULTING_IP: 
+0
fffff801`b1789149 ??              ???

CPU_COUNT: c

CPU_MHZ: e10

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 8

CPU_STEPPING: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

ANALYSIS_SESSION_HOST:  DESKTOP-0N1A3NT

ANALYSIS_SESSION_TIME:  04-21-2019 16:06:30.0773

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

TRAP_FRAME:  ffffb20a222e26f0 -- (.trap 0xffffb20a222e26f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000127
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801b1789149 rsp=ffffb20a222e2880 rbp=ffffb20a222e2980
 r8=0000000000008000  r9=0000000000000000 r10=ffffce0f09b22000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff801`b1789149 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80223dcde69 to fffff80223dbc730

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff801`b1789149 ??              ???

STACK_TEXT:  
ffffb20a`222e25a8 fffff802`23dcde69 : 00000000`0000000a fffff801`b1789149 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffb20a`222e25b0 fffff802`23dca28e : 00000001`00251040 ffffb20a`222e2900 00000000`0009fc00 fffff802`31148755 : nt!KiBugCheckDispatch+0x69
ffffb20a`222e26f0 fffff801`b1789149 : 00000000`0000c1c0 ffffb20a`222e2980 00000000`00000001 00000000`2000020f : nt!KiPageFault+0x44e
ffffb20a`222e2880 00000000`0000c1c0 : ffffb20a`222e2980 00000000`00000001 00000000`2000020f 00000001`00010004 : 0xfffff801`b1789149
ffffb20a`222e2888 ffffb20a`222e2980 : 00000000`00000001 00000000`2000020f 00000001`00010004 ffffb20a`0019e4ff : 0xc1c0
ffffb20a`222e2890 00000000`00000001 : 00000000`2000020f 00000001`00010004 ffffb20a`0019e4ff ffffb20a`00000122 : 0xffffb20a`222e2980
ffffb20a`222e2898 00000000`2000020f : 00000001`00010004 ffffb20a`0019e4ff ffffb20a`00000122 fffff802`31005d00 : 0x1
ffffb20a`222e28a0 00000001`00010004 : ffffb20a`0019e4ff ffffb20a`00000122 fffff802`31005d00 ffffce0f`098f7180 : 0x2000020f
ffffb20a`222e28a8 ffffb20a`0019e4ff : ffffb20a`00000122 fffff802`31005d00 ffffce0f`098f7180 fffff802`23dbe6c5 : 0x00000001`00010004
ffffb20a`222e28b0 ffffb20a`00000122 : fffff802`31005d00 ffffce0f`098f7180 fffff802`23dbe6c5 00000001`00000126 : 0xffffb20a`0019e4ff
ffffb20a`222e28b8 fffff802`31005d00 : ffffce0f`098f7180 fffff802`23dbe6c5 00000001`00000126 00000001`00008000 : 0xffffb20a`00000122
ffffb20a`222e28c0 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff802`3115ecb2 : nvlddmkm+0x5d00

THREAD_SHA1_HASH_MOD_FUNC:  57bd2645b6b0775b5c75d343f2a6e2cc4fdca6ac

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cd3cf7f8a9550b7c1a75520f053cc0e4c92280d1

THREAD_SHA1_HASH_MOD:  99270aa9efddf51499339f5ea82e28c2a8c9f7b4

FOLLOWUP_IP: 
nvlddmkm+5d00
fffff802`31005d00 0000            add     byte ptr [rax],al

FAULT_INSTR_CODE:  3b480000

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  nvlddmkm+5d00

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5cac844b

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  5d00

FAILURE_BUCKET_ID:  AV_CODE_AV_BAD_IP_nvlddmkm!unknown_function

BUCKET_ID:  AV_CODE_AV_BAD_IP_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS:  AV_CODE_AV_BAD_IP_nvlddmkm!unknown_function

TARGET_TIME:  2019-04-21T22:57:59.000Z

OSBUILD:  17763

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2005-12-02 00:58:59

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  28f7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_code_av_bad_ip_nvlddmkm!unknown_function

FAILURE_ID_HASH:  {fc5d8785-d3cf-6594-6653-1314cd049c46}

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

10: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff802`31000000 fffff802`3242a000   nvlddmkm   (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_37ec54c19854e219\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Apr  9 04:38:51 2019 (5CAC844B)
    CheckSum:         013D18E1
    ImageSize:        0142A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Answer 1

Hi,

As you expected Nvidia driver was a cause. If you have tried a newer version of the driver, can you try an older driver from 5/6 months and see if it resolves the issue?

Completely remove everything of Graphics driver using DDU:

http://www.guru3d.com/files-details/display-dri...

You can head to either the card manufacturer or device manufacturer to get an older driver.

Let us know if you require any assistance.

Disclaimer:

This is a non-Microsoft website which would provide accurate and safe information. Watch out for ads on the site which are frequently classified as a PUP (Potentially Unwanted Products). There is no need to buy paid products to fix your computers as they do more harm than good sometimes.

Answer 2

Contents of the minidump folder:

https://1drv.ms/u/s!AnNwgMdquiFElmZ3LNCzALhtEVKg

The MSinfo32 file:

https://1drv.ms/u/s!AnNwgMdquiFElmcsz-FUI49\_iBDJ

Answer 3

Hi Thx,

I am Sumit, an Independent Advisor and a 2-Year Windows Insider MVP here to help.

We need log files(called dump files) that tell us what lead to crash.

Please share them with us for a better analysis of the problem. Instructions can be found here:

https://answers.microsoft.com/en-us/windows/for...

Please let us know if you need any assistance about posting dump files.

Answer 4

Hi THX

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

I see some important updates for your motherboard i recommend you apply to see if it improves stability:

BIOS Update March 2019

http://download.msi.com/bos_exe/mb/7B79v19.zip

Chipset Update March 2019

http://download.msi.com/dvr_exe/mb/amd_chipset_...

Note: This is a non-Microsoft website. The page appears 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.

Answer 5

Hi,

this is NVidia's driver fault. Please try to reinstall drivers from PC (or motherboard) manufacturer's site.

Please run Windows memory diagnostic tool in wide mode.