Question Got a BSOD while playing normal video in discord

Dec 31, 2020
22
0
10
0
So I just normally open a video in discord. The first time it's fine, but when I replay, my pc just BSOD.....sometime I'll get this bsod randomly while doing general stuff....this is my system

Intel Core 2 Quad Q6600 (3.00 GHz)
Micro Star (MSI) OEM Motherboard for Acer Aspire M1641
Gigabyte GT630 1GB
Kingston & Elpida DDR2 memory
500w AVF PSU (old model)
Hitachi 2.5 inch HDD
Hitachi 7200rpm 3.5 inch HDD

This is my Dump file report:

Microsoft (R) Windows Debugger Version 10.0.21349.1004 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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8043b400000 PsLoadedModuleList = 0xfffff8043c02a230
Debug session time: Mon Jun 21 08:00:14.189 2021 (UTC + 8:00)
System Uptime: 0 days 0:33:53.920
Loading Kernel Symbols
...............................................................
................................................................
........................Page 157a7 not present in the dump file. Type ".hh dbgerr004" for details
........................................

Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000006ac018). Type ".hh dbgerr001" for details
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804
3b7f6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff80442673c80=000000000000000a
0: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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: 00000000000003c0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff804476609a7, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4249

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 15708

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

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

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

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


BUGCHECK_CODE: d1

BUGCHECK_P1: 3c0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff804476609a7

READ_ADDRESS: 00000000000003c0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Overwolf.exe

DPC_STACK_BASE: FFFFF80442674FB0

TRAP_FRAME: fffff80442673dc0 -- (.trap 0xfffff80442673dc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd40aa86ea000
rdx=fffff80442673fb8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804476609a7 rsp=fffff80442673f50 rbp=fffff80442674001
r8=0000000000000000 r9=0000000000000000 r10=00000000ffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x3a09a7:
fffff804
476609a7 4c8b90c0030000 mov r10,qword ptr [rax+3C0h] ds:00000000000003c0=????????????????
Resetting default scope

STACK_TEXT:
fffff804
42673c78 fffff8043b808b69 : 000000000000000a 00000000000003c0 0000000000000002 0000000000000000 : nt!KeBugCheckEx
fffff804
42673c80 fffff8043b804e69 : 0000000000000000 ffffd40aa74c0000 ffffd40aa0e33120 fffff80447a9aca5 : nt!KiBugCheckDispatch+0x69
fffff804
42673dc0 fffff804476609a7 : ffffd40aa7fd69a0 fffff80447484c9b ffffd40aa7fd69a0 000001d98e427110 : nt!KiPageFault+0x469
fffff804
42673f50 fffff80447484c9b : ffffd40aa7fd69a0 000001d98e427110 fffff80442674001 0000000000000000 : nvlddmkm+0x3a09a7
fffff804
42673f60 fffff804476cbbf5 : 000000000000002b ffffd40aa86ea000 fffff8040000001f fffff80400000024 : nvlddmkm+0x1c4c9b
fffff804
42674060 fffff804476c974f : 000000000000001f fffff804426741c9 ffffd40aa7fd69a0 000000000000001f : nvlddmkm+0x40bbf5
fffff804
42674120 fffff804476ca26c : ffffd40aa7fd69a0 ffffd40aa7fd69a0 000000000000002b ffffd40aa7fd69a0 : nvlddmkm+0x40974f
fffff804
42674230 fffff80447668736 : ffffd40aad8fa720 fffff8041a151000 000000000000002b 0000000000000008 : nvlddmkm+0x40a26c
fffff804
42674340 fffff804476690dc : 000000000e0d9b63 ffffd40aa8e20000 fffff80400000000 000000000e0d9b63 : nvlddmkm+0x3a8736
fffff804
42674450 fffff804476666d8 : fffff80400000000 ffffd40a00000000 ffffd40aa8e20000 fffff80447a3fb80 : nvlddmkm+0x3a90dc
fffff804
42674560 fffff804476692fd : 0000000000000008 fffff8044736c3a5 fffff804426746f0 ffffd40aa86ea000 : nvlddmkm+0x3a66d8
fffff804
42674670 fffff804476697ea : ffffd40aa86ea000 0000000010000000 ffffd40aa8e20000 ffffd40aa86ecae0 : nvlddmkm+0x3a92fd
fffff804
426746c0 fffff804475c6d68 : ffffd40aa8e20000 fffff80442674760 0000000000000000 ffffd40aa86ea000 : nvlddmkm+0x3a97ea
fffff804
42674720 fffff804475c6896 : ffffd40aa86ea000 ffffd40aa86ea000 ffffd40aa86ea000 fffff8044737f333 : nvlddmkm+0x306d68
fffff804
426747a0 fffff804475c6ac7 : ffffd40aae224790 ffffd40a00000015 ffffd40aa86ea000 ffffd40aa07355a0 : nvlddmkm+0x306896
fffff804
426747f0 fffff804475c7cfb : 0000000000000004 fffff80442674a10 0000000000000004 ffffd40aa86ea000 : nvlddmkm+0x306ac7
fffff804
42674870 fffff804475c366b : fffff80442674a10 fffff8044736a7e6 ffffd40aa86ea000 ffffd40aa86d8010 : nvlddmkm+0x307cfb
fffff804
426748d0 fffff80447345277 : ffffd40aa86ea000 ffffd40aa86d8010 0000000000140001 000000000000000e : nvlddmkm+0x30366b
fffff804
42674910 fffff8043b7230ce : fffff80439da5240 fffff80442674cb0 fffff80442674e70 fffff80439da2180 : nvlddmkm+0x85277
fffff804
42674bb0 fffff8043b7223b4 : fffff80439da2180 0000000000000000 0000000000000008 0000000000012f2b : nt!KiExecuteAllDpcs+0x30e
fffff804
42674d20 fffff8043b7fdc65 : 0000000000000000 fffff80439da2180 ffffa580d7eee140 00007ffb4fd7b708 : nt!KiRetireDpcList+0x1f4
fffff804
42674fb0 fffff8043b7fda50 : ffffd40aa70f0080 fffff8043b6c656a 0000000000000000 0000000000000000 : nt!KxRetireDpcList+0x5
ffffbe8a
0b8a0c00 fffff8043b7fd305 : 00007ffb4fd7b708 fffff8043b7f8791 00000000222c4df4 00000000277eee58 : nt!KiDispatchInterruptContinue
ffffbe8a
0b8a0c30 fffff8043b7f8791 : 00000000222c4df4 00000000277eee58 ffffffffffff8ad0 ffffd40a00000000 : nt!KiDpcInterruptBypass+0x25
ffffbe8a
0b8a0c40 00007ffb4fc788e2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptDispatch+0xb1
00000000
277ef6e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb4fc788e2


SYMBOL_NAME: nvlddmkm+3a09a7

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 3a09a7

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
---------
 

ASK THE COMMUNITY